Hydra Generator reporting errors

Description (Required)
The main problem is that the Hydra Generator and Hydra Turbines are throwing errors when trying to be used.
We connected a water source to the Hydra Turbines and put a Energy Regulator next to it but didn't generate any power.
Steps to reproduce the Issue (Required)
connected a water source to the Hydra Turbines and put a Energy Regulator next to it but didn't generate any power.

Expected behavior (Required)
Generator Power lol
Server Log / Error Report
DynaTech error report
https://pastebin.com/qWr4E7Fc
Server Log
https://pastebin.com/ThE45kMf
Environment (Required)

Minecraft Version: 1.18.2
CS-CoreLib Version: Not Used
Slimefun Version: Stable RC - 31
Plugin Version: 163

Addictional:
Discord User: Ryan DeTree#4293

Water generators need to be waterlogged to generate power. It also needs to be within -64 - 320 in y height. It seems you tried to place a hydro generator at y ~4000 which caused it to error

Water generators need to be waterlogged to generate power. It also needs to be within -64 - 320 in y height. It seems you tried to place a hydro generator at y ~4000 which caused it to error

Ok and how do I waterlog it ?

I also do not support stable releases of slimefun. Please use a dev build of slimefun

Switched to latest DEV build 1013

Just right click the wall with a water bucket to waterlog it


Cells remain Expand

Hi i am using your FZAccordionTableView i am using this with segment control each segment control will show different data. the problem is when i select a section it expands until now its fine but without closing the section if i click on next segment the selected section remains opens for the selected segment as well
i am reloading the table but still can't achieve it .i want it to be closed how can i achieve it
Help would be great
thank you

This code would find all the sections that are open and then 'toggle' them, therefore closing them:
for (NSInteger i = 0; i < self.tableView.numberOfSections; i++) {
   if ([self.tableView isSectionOpen:i]) {
      [self.tableView toggleSection:i];
   }
}

If you'd like to disable the animations:
[UIView setAnimationsEnabled:NO];
// Animations happen here
[UIView setAnimationsEnabled:YES];

Hope that works. I can foresee some problems with calling toggleSection and reloadData at the same time, but we'll see.

Thanks mate it worked Fine Thank You so much


cannot see logs or exec into pod when using TLS bootstrapping

I have a cluster of below given configuration And i am using 1.12.0v release of k8s.
Master : <IP_ADDRESS>/22 (i.e node1,node2 respectively)
worker: <IP_ADDRESS> (node3)

After configuring master, when i am bootstrapping worker nodes through TLS . The worker node csr get approved and issued by master  as shown below.
(scraping) : vikash.singh $ kubectl describe csr node-csr-Cqwausxb1QPdcZ4ceu6KPH_tccD2YSa8xAzHuv1EACQ

Name:               node-csr-Cqwausxb1QPdcZ4ceu6KPH_tccD2YSa8xAzHuv1EACQ
Labels:             <none>
Annotations:        <none>
CreationTimestamp:  Sun, 17 Feb 2019 12:11:14 +0530
Requesting User:    kubelet-bootstrap
Status:             Approved,Issued
Subject:
         Common Name:    system:node:node3
         Serial Number:
         Organization:   system:nodes
Events:  <none>

But after spinning a pod and trying to get logs or exec into it , It started throwing x509 certificate error on IP of node3(worker) node.
(scraping) : vikash.singh $ kubectl logs -f  nginx-sdsrvsz
Error from server: Get https://<IP_ADDRESS>:10250/containerLogs/nginx-sdsrvsz: x509: cannot validate certificate for <IP_ADDRESS> because it doesn't contain any IP SANs

I can fix this issue by creating a certificate for this node manually but that totally override objective of TLS bootstrapping. Is there any other way around.
@kelseyhightower i have seen this issue. But it still happening.

Got it Fixed, It is even wrote in Docs
Only need to add --rotate-server-certificates and --rotate-certificates  in kubelet configuration and approved manually.

 Thanks a lot @vikash32


Note fork from another plateform

Feature Description
Like:

https://github.com/coreutils/coreutils
Related to !wkyjxWeAOBpKMvHbno:matrix.org/$v-Th_2WydnUhCYamRCNJ2x08LnlJy7Jg44ak5v-VV48.
+30
Screenshots
No response

https://codeberg.org/USERNAME?tab=repositories Filter > Forks or Mirrors may help.

Related to #18.


Adjust website language to Polish

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (e40b5c9) 100.00% compared to head (855fb82) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main       #13   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines           55        55
=========================================
  Hits            55        55

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Generate enum types

The protoc plugin generates structs for messages together with their types. It doesn't however do that for enums and it could be very helpful to generate types for enums too, so that they can be reffered to in other areas of the code.
Let me know what you think :)

I am looking forward to being able to use this. Has it been released?

@amiel No. I will release the new version recently with other changes.

Thanks!


Ongoing dev for v0.0.2

Make sure we've documented halt - https://github.com/pimoroni/pimoroni-pico/issues/594

Bumped to build against Pimoroni Pico release v1.19.17 - https://github.com/pimoroni/pimoroni-pico/releases/tag/v1.19.17


Add registry function to register the call pluggables

Summary
Add registry function to register the call pluggables.
Ticket Link
Hackaton
Related Pull Requests
https://github.com/mattermost/mattermost-plugin-calls/pull/128
Release Note
Added new plugin registry function to register pluggables for Calls

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

Only 1/5, but would it be a good idea to do this in a more generic way so that Calls and other products/plugins could add their own pluggables more easily? I guess that would bring us closer to just having people dispatching RECEIVED_PLUGIN_COMPONENT themselves, but I would like to keep the plugin registry as a layer of abstraction in front of the Redux actions.
I'm also realizing this isn't exactly a pluggable in the sense of of the Pluggable component since that's expected to be rendering a React component. It's not the first place we've done this, so it's an existing issue with our naming, but we're definitely abusing the fact that we're storing everything in a field called components. No wonder the type definitions for this part of the code are either non-existent or awful 😛

I guess that would bring us closer to just having people dispatching RECEIVED_PLUGIN_COMPONENT themselves

https://github.com/matterpoll/matterpoll/blob/d432d0899b3bb6327d6b31c2cfa878a5ce64d150/webapp/src/plugin.jsx#L55-L70 :P

would it be a good idea to do this in a more generic way so that Calls and other products/plugins could add their own pluggables more easily?

I was considering something like "registering a registry function", but then we get "the chicken and the egg" problem. For example... Calls, when initialized register this registry function. And Playbooks wants to use that registry function to register an action to create a playbook from a call (because why not, it is an example :P). But the order or initialization is not determined, so playbooks may init before Calls, and then the registry function doesn't exist. So let's make the products start first and in a determined order. Then what if calls wants to add a call button in a playbook? It could not, because it is always initialized first and the registry function does not exist.
We could try to make a two rounds initialization, or a "on all plugins loaded" kind of hook. But then what happens if we install calls after we had the plugins installed and working? Do we need to disable and reenable them form them to show the information?
It feels a bit too troublesome, but if you have better ideas, I am always happy to listen :D

https://github.com/matterpoll/matterpoll/blob/d432d0899b3bb6327d6b31c2cfa878a5ce64d150/webapp/src/plugin.jsx#L55-L70 :P

Ah, backwards compatibility

would it be a good idea to do this in a more generic way so that Calls and other products/plugins could add their own pluggables more easily?

I was considering something like "registering a registry function", but then we get "the chicken and the egg" problem. For example... Calls, when initialized register this registry function. And Playbooks wants to use that registry function to register an action to create a playbook from a call (because why not, it is an example :P). But the order or initialization is not determined, so playbooks may init before Calls, and then the registry function doesn't exist. So let's make the products start first and in a determined order. Then what if calls wants to add a call button in a playbook? It could not, because it is always initialized first and the registry function does not exist. We could try to make a two rounds initialization, or a "on all plugins loaded" kind of hook. But then what happens if we install calls after we had the plugins installed and working? Do we need to disable and reenable them form them to show the information?
It feels a bit too troublesome, but if you have better ideas, I am always happy to listen :D

I was thinking more like having a generic registerPluginPluggable method which takes some string telling the pluggable where to show up rather than having a specific method for each location of the pluggable. We could even go more general and have a registerPluggable that semi-replaces all these other methods, but then we lose out on any ability for this code to act as self-documentation. The core web app would still hold onto the data about what's been registered in the same way it does now, so I don't think we'd have any order-of-initialization issues

@hmhealey I am going to block the merge, mainly for the calls team to make a decision if they want that in the product, and so on. In the meanwhile, not sure if you want any QA for this PR, or we can skip it.

Closing since there is no short-term plan to add this. Can be reopened if there is a change in this.


chore: simplified styles in BaseLayout.astro

PR Checklist

[x] Addresses an existing open issue: fixes #59
[x] That issue was marked as status: accepting prs
[x] Steps in CONTRIBUTING.md were taken

Overview
As suggested, streamlines the style includes a bit.
Co-authored-by: Elian Van Cutsem<EMAIL_ADDRESS>

@all-contributors please add @eliancodes for code.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


String literals in mapped type lost when passing an object type to a function

Bug Report
🔎 Search Terms
mapped type string literals lost
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about mapped types and string literals

⏯ Playground Link
Playground link with relevant code
💻 Code
interface Foo {
  key: string;
  fixed_values: 'foo' | 'bar';
}

type Bar<T extends Foo[]> = Record<`_${T[number]['key']}`, string>;

// using the type directly works:

let direct: Bar<[
  {
    key: 'foo',
    fixed_values: 'foo',
  },
  {
    key: 'bar',
    fixed_values: 'bar',
  },
]>;
// "_foo" and "_bar" are present on "direct" (working)

// but the following doesn't work:

const ret = (function <T extends Foo[]>(input: T) {
  return {} as Bar<T>;
})([
  {
    key: 'foo',
    fixed_values: 'foo',
  },
  {
    key: 'bar',
    fixed_values: 'bar',
  },
]);
// "_foo" and "_bar" are missing from "ret"

🙁 Actual behavior
The mapped type in the variable ret doesn't have any fields.
This problem occurs because the string literals are reduced to the string type. This is also shown by the below screenshots.
The type should look like this:

But it just has string instead of the actual values:

It works, when replacing the type of the key field with a string literal union like in fixed_values or a template literal. But then the value is restricted.
🙂 Expected behavior
The resulting type should be an object with the "key" fields of the objects from the input array as the keys but prefixed with an underscore.
The values are irrelevant in this example.
The expected behavior is achieved when using the type without a function as shown in the code snippet.
In the real code which brought me to this problem, the input array is used as value and type at the same time.

Literals are only inferred automatically~ when they have a direct primitive constraint. Your overall constraint is an object type and it only has a string property - so the type there is widened to a string. You can work around this using const type parameters: TS playground

Thank you! It works now.


Add infos for node lts support

a proposal to fix #687 and #688

@stevepiercy feel free to merge, if you are ok with these changes

Thanks, @loechel, I pushed some English grammar fixes. This is very helpful. Merging after green.

Can we please next time make sphinx configuration changes in different PRs, @stevepiercy
Changes like "Show TODO directives." could need some action for authors.

@ksuess {todo} directives they should be published. It shows that work needs to be done.  If we don't show them, it could mislead the user to think that everything is OK, and that would be much worse.
If instead the author intends a private comment, then they should use % my-comment or % TODO: something for the author only as that never shows and does not indicate future work is needed in a public way.

@ksuess {todo} directives should be published. It shows that work needs to be done. If we don't show them, it could mislead the user to think that everything is OK, and that would be much worse.
If instead the author intends a private comment, then they should use % my-comment or % TODO: something for the author only as that never shows and does not indicate future work is needed in a public way.

A sphinx configuration change is off topic here.
This change needs action and therefore should next time be visible as a separate PR.


A B A Cyclic dependencies

(Probably been asked before, but I can't find doc's on this)
libA -> libB -> libA.
What I expect is that when libB is constructed, it will discover that libA is already being built, so will not attempt to re-add it.
What I see is that the add_library in libA will be executed twice and cmake will complain that the library is already being built.
Is there a solution to this apart from breaking the cyclic dependency by hand?
Thanks

Imho this sounds like a won't fix issue on first thoughts. However, the use of cyclic dependencies should probably be a use-case that CPM should detect and provide a more useful error message.
This sort of issue, if CPM could somehow satisfy, will likely just peel back a layer of underlying issues that cyclic dependencies would cause. You should handle this in the same manner as how you solve cyclic header-includes and separate out the re-used code and/or add interface abstractions and use dependency inversion/injection principles etc.
Also, to cover more CPM related concerns as to what logic would even resolve a cyclic dependency? Then lets start with what if we included versions to the dependencies. This would be a developer nightmare as you may build either libA or libB as the top-level project and end-up with hard to discern package versions being used so unit-testing would be potentially broken. (see Limitations- First version used)

<EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>

Actually in this case it's not a 'true' cyclic dependency.
I believe this works 'ok':
If libC depends on LibA and libB, and libA depends on libB, libC will pull in the required libraries (A and B), and (it seems) cmake will correctly allow libA to make use of libB and visa-versa. Both libA and libB are 'dependencies' and cmake 'finds' them when required for libA/B.
The issue is only when we attempt to build e.g. libA. Since libA is not a dependency of libA, cmake (seems to) add it as a dependency of libB and attempt to pull it in, even though libA is the current target that is being built. This is the dependency that causes the issue.
I'd expect that if e.g. libB depends on libA, and libA is currently being built, that libB's "dependency" for libA would be special cased and 'point back' to the library being built. Clearly this might be tricky to achieve. Of course (as you suggest) there are invariably ways around the issue (worst case introduce a libC).

The issue as I understand is that when configuring libA alone CPM is not aware that libA is already included in the project. When configuring libC and libA is added using CPM then it is aware that libA already exists and doesn't attempt to add it again within libB.
I think the only solution to configure libA would be somehow make CPM aware that libA is already available. One way could be to call CPMRegisterPackage(libA <libA Version>) in libA's CMakeLists before adding any dependencies.

Makes sense, but that would then break libA when it was used elsewhere? - Otherwise, why isn't this the default behaviour?

Makes sense, but that would then break libA when it was used elsewhere?

I don't think so, it should only change the behaviour to act as if libA as added by CPM itself.

Otherwise, why isn't this the default behaviour?

How would CPM know the name of the current project? We could infer it implicitly, e.g. from the PROJECT_NAME, but I'm not a fan of that option as build behaviour shouldn't change based on the project name.

Confirm this works and is a reasonable solution - THANKS for the help


If useSWR is dependent on state, the return values are undefined

const Pokemon = () => {
  const [pokemon, setPokemon] = useState(null);

  const loadPokemon = (url) => setPokemon(url);

  const { data, error } = useSWR('https://pokeapi.co/api/v2/pokemon', fetch);
  const { pokemonData, pokemonError } = useSWR(pokemon, fetch);

  // This is null
  console.log(pokemonData, pokemonError)

  if (error) return
failed to load

  if (!data) return
loading...

  return
{data.results.map(pokemon => {
    return
 loadPokemon(pokemon.url)}>{pokemon.name}

  })}

}

Don't know what I am doing wrong. But the second useSWR is always undefined, even though I see the network calls going through.

try
const { data: pokemonData, error: pokemonError} = ...

That works thank you so much


HardFault on some stm32 devices.

Hi, its looks like some stm32f103(blue pill) and stm32f(401)/(411) dont properly work under embassy, but works fine under stm cube code generation. I build blinky example from stm32f1 and stm32f4 and try run it on my boards, but on some of them I fall into HardFault handler before main start(I put breakpoint on main func). One of the the 2 blue pill boards work fine and all of 2 black pills boards fall into HardFault. Any idea?
Backtrace:
#0  0x0800df82 in cortex_m_rt::HardFault_ (ef=0x0) at src/lib.rs:1046
#1  <signal handler called>
#2  0x00000000 in ?? ()

These chips are definitely supported, they should work.
Most common cause for immediate hardfault is specifying the wrong chip name in the embassy-stm32 dependency in Cargo.toml, or specifying the wrong RAM size in memory.x if you're supplying it manually.

It's seems like I really had wrong chip name in Cargo.toml's features of embassy-stm32 dependency. I also notice, that memory.x should be use directly, like for nrf52. Thanks for help!


make the configuration race detector safe.

The go race detector notices that we may overwrite the configuration
while reading it as there are no locks to prevent this.  This is
most likely to happen when you send SIGHUP to the running process
as it is quite busy.
So replace config.Config with config.Config() and return a copy of
the pointer to the configuration.
Load() Reload() and ForceReload() have been adjusted to use locking
and to also create a new copy of the configuration rather than
modify the existing one. The new copy then replaces the original
configuration and this process is surrounded by locking.  Configuration
modifications by the application are now done via calls which also
lock.
A Pull Request should be associated with an Issue.

We wish to have discussions in Issues. A single issue may be targeted by multiple PRs.
If you're offering a new feature or fixing anything, we'd like to know beforehand in Issues,
and potentially we'll be able to point development in a particular direction.

Related issue: https://github.com/github/orchestrator/issues/0123456789

Thank you! We are open to PRs, but please understand if for technical reasons we are unable to accept each and any PR

Description
This PR [briefly explain what is does]

In case this PR introduced Go code changes:

[ ] contributed code is using same conventions as original code
[ ] code is formatted via gofmt (please avoid goimports)
[ ] code is built via ./build.sh
[ ] code is tested via go test ./go/...

You need to apply same changes in *_test.go files.

Please hold off on applying this. I want to test more first. It's probably ok but also with the other PRs you have pending (the use TLS if necessary and some missing patches of mine) it probably will need  to be adjusted.

Going to close this. I'll come back to it again later.


use with_metadata argument as switch

It is a breaking change. I lost 30k of title extraction due to this change.
Not to complain, but why make with_metadata=False the default?
For normal users, more data is a good thing as metadata also provides useful information. For advances users, they know how to turn off metadata extraction for speed.
I suggest making the default True. just my 0.2 cents.


@vue/shared generateCodeFrame can infinite loop

Vue version
3.4.26
Link to minimal reproduction
https://github.com/aturingmachine/vue-sfc-infinite-loop
Steps to reproduce
Have a component making use of a Generic in it's Props that extends an enum.
i.e. (this is pulled from the linked reproduction)
<script setup lang="ts" generic="K extends SomeEnum">
import type { SomeEnum } from '@/consants';
import type { EventParams } from '@/event-params';
import { onMounted } from 'vue';

interface Props<K extends SomeEnum> {
  eventParams: EventParams[K]
}

const props = defineProps<Props<SomeEnum>>()

also occurs if the generic attribute is not used

Have SomeEnum defined in another file (in this case src/constants.ts)

This part I have not fully figured out the exact cases but please bear with me

If the lengths of the 2 files match some (currently) unknown condition, the call to generateCodeFrame will get stuck in an infinite loop in its inner for loop.
Link to Line in Question
What is expected?
That the compiler will report the error at the correct lines.
What is actually happening?
The Compiler gets stuck in an infinite loop and hangs indefinitely.
System Info
System:
  OS: Linux 6.6 Manjaro Linux
  CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
  Memory: 46.28 GB / 62.65 GB
  Container: Yes
  Shell: 5.9 - /usr/bin/zsh
Binaries:
  Node: 22.0.0 - ~/.nvm/versions/node/v22.0.0/bin/node
  npm: 10.5.1 - ~/.nvm/versions/node/v22.0.0/bin/npm
npmPackages:
  vue: ^3.4.21 => 3.4.26

Any additional comments?
This issue has been brought up once and resolved seen here.
The issue can be "resolved" by reducing the number of lines in either the Component file or the file containing the Enum.
It seems the case j >= lines.length on line 26 leading to the continue trips the infinite loop, but I may be wrong.
The provided reproduction link is a simplified version of our production code that triggered the initial issue.

As the issue points out, the endless loop happens because generateCodeFrame doesn't handle invalid end values correctly, causing the loop.
I fixed this in PR #10883.
About expecting the compiler to report errors, in Vue, always softly fail on failed runtime type inference. You can find the code here.
The specific call to generateCodeFrame with an incorrect end value is here. The exact reason isn't clear yet.
Hope this helps :)


Unable to install nokogiri using Ruby 1.9.3

I'm using ruby 1.9.3 on my app and I'm unable to run bundle because nokogiri requires a Ruby version >= 2.1.0. I've already tried the following command line with no success.
gem install nokogiri -- --use-system-libraries=true --with-xml2-include=/usr/include/libxml2
ERROR:  Error installing nokogiri:
nokogiri requires Ruby version >= 2.1.0.
PS: At the moment I cannot upgrade my ruby version and I really need to install nokogiri otherwise my app won't run.

You can force a Ruby-1.9.3 compatible nokogiri version by setting
gem "nokogiri", "<1.7.0"

in your Gemfile. But note, that Ruby versions below 2.1 are no longer maintained and no longer supported by nokogiri.

It's probably worth noting here that Ruby 1.9.3 reached end-of-life on 2015-02-23, nearly two years ago.


False positive: TemplateHaskell is not redundant when using Typed template haskell splices

In this module, the TemplateHaskell pragma is considered redundant but it isn't:
{-# LANGUAGE TemplateHaskell #-}
module Example where

val = $$(spliceHere)

Using HLint 3.8 I get:
Sample.hs:4:9-20: Warning: Redundant bracket
Found:
  (spliceHere)
Perhaps:
  spliceHere

1 hint

Which I think is actually correct. Which version are you using?

Oh, looks like I'm using (recently upgraded to) 3.6.1:
/nix/store/0f8wii5x1vnjmgy1asyh2175092xy8rm-hlint-3.6.1/bin/hlint smos-docs-site/src/Smos/Docs/Site/Changelog.hs
smos-docs-site/src/Smos/Docs/Site/Changelog.hs:3:1-32: Warning: Unused LANGUAGE pragma
Found:
  {-# LANGUAGE TemplateHaskell #-}
Perhaps you should remove it.
Note: may require `{-# LANGUAGE TemplateHaskellQuotes #-}` adding to the top of the file

I'll see if I can try out a newer hlint. Feel free to close this if it's indeed fixed already.


fix egress route for ipv6

Describe your changes
Provide Issue ticket number if applicable/not in title
Provide link to Netmaker PR if required
Provide testing steps
Checklist before requesting a review

[x] My changes affect only 10 files or less.
[x] I have performed a self-review of my code and tested it.
[ ] If it is a new feature, I have added thorough tests, my code is <= 1450 lines.
[x] If it is a bugfix, my code is <= 200 lines.
[ ] My functions are <= 80 lines.
[ ] I have had my code reviewed by a peer.
[ ] My unit tests pass locally.
[x] Netclient & Netmaker are awesome.

close it and raise with a new PR for avoiding the code conflict.


Polished is not being tree-shaken

polished version: 2.3.3
styled-components version: 4.1.3
react version: 16.7.0
create-react-app version: 2.1.1

Mixin/Helper/Shorthand you were using and how you were using it:
import React, { Component } from "react";
import styled from "styled-components";
import { transparentize } from "polished";

const Header = styled.div`
  background-color: ${transparentize(0.5, '#ffcc00')};
`;

class App extends Component {
  render() {
    return (
      <Header>
          Learn React
      </Header>
    );
  }
}

export default App;

What you are seeing:

Name
Size

polished.es.js file
94 KB

polished.es.js bundle part
92.6 KB

File:

Bundle visualizer output:

What you expected to see:
I expect the size of just transparentize to be smaller.
Reproduction:
Use create-react-app, I ejected to add webpack-bundle-visualizer and install styled-components and polished. Change the app component to the one above and run npm run build.

@mikeheddes thanks Mike! How this shows up in the bundle visualizer even throws me off (this changed recently ).


Failing test: Linux packages_autoroller

Type
postsubmit test broken and tree is closed.
It doesn't look like any recently merged PR broke this test.
Error log

Error logs
Unhandled exception:
Bad state: Expected all diffs after re-generating gradle lockfiles to end in .lockfile, but encountered: [dev/benchmarks/test_apps/stocks/lib/i18n/stock_strings_en.dart, dev/benchmarks/test_apps/stocks/lib/i18n/stock_strings_es.dart]
#0      PackageAutoroller._regenerateGradleLockfiles (package:conductor_core/src/packages_autoroller.dart:162:9)

#1      PackageAutoroller.roll (package:conductor_core/src/packages_autoroller.dart:100:7)

#2      run (file:///b/s/w/ir/x/w/flutter/dev/conductor/core/bin/packages_autoroller.dart:83:3)

Steps to reproduce
N/A
Expected results
N/A

It looks like gradle lockfile generation is touching some files it shouldn't? https://github.com/flutter/flutter/blob/master/dev/conductor/core/lib/src/packages_autoroller.dart#L148

It looks like this is caused by the fact that the tool invokes "flutter pub get". I'm not sure why, but for this test app that updates lib/i18n/stock_strings_en.dart and lib/i18n/stock_strings_es.dart. Looking in to if that is something that needs to be fixed for this app, or if we should remove the check that only lockfiles are touched.

https://github.com/flutter/flutter/commit/dca37ad17ff0354924f9b5bbbcbb2ce6ed819230 changed the contents of the localization files generated during flutter pub get and flutter gen-l10n.
Previously it looks like the files checked into https://github.com/flutter/flutter/tree/master/dev/benchmarks/test_apps/stocks/lib/i18n were manually updated when the tool output changes.

I suspect the reason that this wasn't caught when the commit @jason-simmons pointed out landed (dca37ad) was because the check succeeds if the bot already has an open PR, and it may have had an open PR for the entire time since that commit landed till the first time it failed

This turned out to be true, the check just auto succeeded from run 12777 to run 12866 because https://github.com/flutter/flutter/pull/158347 was open the whole time. This is why it took so long for the failure after the original commit.


📝 Add Go version badge

The Go version is a little confusing because this library doesn't really care what version you use as long as it's after 1.12 when they added the main module version. OTOH, the best version to use is 1.18, so it supports revision info. Best to just leave it out.


[examples/raytrace-parallel] Replace Bash with Python for Windows compatibility

I wanted to get this example running on my Windows machine without fiddling with Powershell environment variables, so I just rewrote the shell scripts as Python scripts.
Since this example already requires you to have a Python3 installation, this PR makes the example work cross-platform without introducing a new dependency on Python3.
It looks like CI has some dependency on build.sh existing, so I just made it redirect to build.py. That may make any error messages look a bit less friendly in CI, since they'll be Python tracebacks😥 I'll let you decide if this is worth the tradeoff!

I would be fine with it since the server is already in Python. Though I dislike that we are using shell scripts or Python at all here.
Considering all this stuff needs nightly anyway, maybe we could use cargo scripts instead?
Though this LGTM, I'm not familiar with Python, so another maintainer should have a look at this.

This also seems fine to me.
I think it'd make sense to do the same thing for the wasm-audio-worklet example as well, since it also uses multithreading and as a result needs a basically identical build script and Python server. The same goes for #3606 and #3607.

Almost all of this was merged in when you merged #3603, because I had rebased #3603 onto this branch. The only things left to merge in this PR now are the README changes. Sorry for not communicating this better😥


Documentation improvements.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.77%. Comparing base (5c0ce46) to head (1cd5108).

Additional details and impacted files
@@            Coverage Diff             @@
##             main       #4      +/-   ##
==========================================
- Coverage   99.77%   99.77%   -0.01%
==========================================
  Files           8        7       -1
  Lines         891      877      -14
==========================================
- Hits          889      875      -14
  Misses          2        2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Format tpv config and add more singularity tools

Add singularity_enabled for a number of tools have difficult conda environments. I've also run 'tpv format' on tools.yml which resulted in some lost comments that did not seem worth preserving.

Formatting was necessary in order to add the tools programmatically. It sorts they keys alphabetically. I'd prefer to keep comments in future - this is something I will follow up with TPV.


FalseDoubleEntry Doesn't Work

FalseDoubleEntry doesn't work.  Broken during a previous code review.

Slated for release 1.1.3

#10


Add support to unregister from lifecycle notifications

Description: Return a handle from registration methods that can be used to unregister. This is needed for registrations made by objects that can have a shorter lifetime than the server (such as filters or access logs). When those objects are destroyed the callbacks will be invalidated so the registrations should be removed to avoid memory access violations.
Risk Level: low
Testing: unit tests
Signed-off-by: Elisha Ziskind<EMAIL_ADDRESS>

/review @htuch

@eziskind thanks, LGTM. I think in terms of other places where this patterns comes up, check out ClusterUpdateCallbacksHandleImpl and ConfigTrackerImpl::EntryOwnerImpl. Probably others as well. Do you want to generalize in this PR or leave this as a TODO?

Thanks, I'll leave this as a TODO for a followup PR.

@eziskind LGTM if you can add the TODO or file an issue for the general case.

@eziskind LGTM if you can add the TODO or file an issue for the general case.

Filed #7020


Improve compile times

Abysmal since #51.
Avoid gigantic types (which require upping type_length_limit).
Avoid closures that I think are monomorphised for parameters that aren't relevant?
Try out cargo llvm-lines.

#80 fixed most of the fallout from #51, so type_length_limit no longer needs upping and compile times are back to bearable.


View generates inconsistent sort order

Just trying out bonsaidb for the first time. I've been reading about it and I can't wait to use it. Thanks so much for this amazing project
However, my first attempt at using Views leads to some inconsistent behaviour.
I've copied the BlogPost example into my own crate to test things out. But the thing is this query https://github.com/khonsulabs/bonsaidb/blob/main/book/book-examples/tests/view-example-string.rs#L93
sometimes logs
Retrieved post #7$1 "New version of BonsaiDb released"
Retrieved post #7$2 "New Rust version released"
Retrieved post #1 "New version of BonsaiDb released"
Retrieved post #2 "New Rust version released"

and others this:
Retrieved post #7$2 "New Rust version released"
Retrieved post #7$1 "New version of BonsaiDb released"
Retrieved post #2 "New Rust version released"
Retrieved post #1 "New version of BonsaiDb released"

At first I thought it may be because the example doesn't use any specific sort, but then the docs say that ascending is the default. Indeed, I can see the query is build with forwards scanning.
Adding ascending or descending  to the view have the same erratic results
I don't really have a way to reproduce this, except running the test many times

The Order controls the order of keys being returned. In that example, the key is the category, not the post title. When querying with a range of keys, the sort order will ensure the keys are returned in the order queried.
For example, here is some code that can be pasted into that example:
    for mapping in db.view::<BlogPostsByCategory>().query()? {
        println!("Key: {:?}, Document ID: {}", mapping.key, mapping.source.id);
    }
    for mapping in db.view::<BlogPostsByCategory>().descending().query()? {
        println!("Key: {:?}, Document ID: {}", mapping.key, mapping.source.id);
    }

The output for me for me is:
Key: Some("Cooking"), Document ID: 7$3
Key: Some("Rust"), Document ID: 7$2
Key: Some("Rust"), Document ID: 7$1
Key: Some("Rust"), Document ID: 7$2
Key: Some("Rust"), Document ID: 7$1
Key: Some("Cooking"), Document ID: 7$3

From this, it looks like it's behaving as I hoped it would. The order of multiple entries with the same key is undefined, and unaffected by the sort order.

Thanks for updating the comments. It does make sense now. Following what you said, I've been reading on Couchdb's map/reduce and I was surprised at how similar it is to bonsaidb. By reading your posts, I knew you took inspiration from it, but now I can see that if you know couchdb, you can expect bonsaidb to be very similar.
With this in mind, I thought it would be nice to add to the User guide (rather than just the docs) something like:

Map/reduce is similar to creating indexes in both SQL and NoSQL databases. However, they are also different in some important ways. BonsaiDb is in alpha stage and the implementation may change. But in the meantime, if you're new to the concept of map/reduce for database indexing, a good place to start may be the CouchDb guide for views as BonsaiDb is heavily inspired by it.

I know that referring to another database may not be wise but at least it's something for now? Their guide was very revealing to me. After reading it, I could see why the expected behaviour for sorting documents with the same key is undefined.
So that's about docs.
On the subject of how to sort blog posts by category, I had assumed that when emitting the same key in the map function, the ordering would the be the same as insertion (i.e.: by document id if not using natural ids). I can see now that I was totally wrong.
But then, this leads me to the goal I was trying to achieve. Let's imagine I have a Blog and I want to show users all posts within the category "Rust". Since there are too many to display on one page, the frontend needs to paginate posts within that category. The Rust category page should only show the first most recent posts and then, have a link to other pages. The query needed would be blog posts by category, sorted by some kind of timestamp. I found an exact question like this on stackoverflow for couchdb
According to that answer, in couchdb, the map function can emit an array like [key, sorting_token]. Having specified the sort token, it would then be possible to query using start_key and end_key to manage the sorting order. However, there is nothing like that in bonsaidb for what I can see. Is this correct?
I can see you can query key ranges, but there is no way to specify a sorting token in the query.
I've been thinking hard about this one, and my experience with DynamoDb came to mind, where you create composite string keys for partition keys. Would this be a good workaround?
In the map function
document.header.emit_key_and_value(format("{}_{}", post.category, post.publication_date), 1);

and then
let rust_posts = db
            .view::<BlogPostsByCategory>()
            .with_key_prefix("Rust".to_string())
            .descending()
            .query_with_collection_docs()?;

This does work, but being new with bonsaidb, I wonder if this could be an anti-pattern

I know that referring to another database may not be wise but at least it's something for now?

It's funny, I actually used to call out how similar it was, but as I've grown further from CouchDB's core design, I started trying to rely on my own docs more. CouchDB's view guide definitely serves as a good guide on the fundamentals, but it breaks down on anything more than the basic concepts as you ran into.
I truly appreciate the feedback.
Another invaluable area of finding inspiration for neat ways to use views is Redis' Indexing guides. As Redis is primarily a key-value store and views are primarily a key-value mechanism, many of these indexing tricks will work in BonsaiDb too.

According to that answer, in couchdb, the map function can emit an array like [key, sorting_token].

This is one of the areas where BonsaiDb differs greatly. In CouchDB, everything is JSON, so it's easy to write code that compares two values -- after all, JSON can only contain a limited number of types.
The way I solved this is to create the Key trait, which allows any implementor to serialize itself into bytes in such a way that ordering is preserved in binary form.
One of the implementations is for tuples:
#[derive(Debug, Clone, View)]
#[view(collection = BlogPost, key = (Option<String>, String), value = u32, name = "by-category")]
pub struct BlogPostsByCategory;

impl ViewSchema for BlogPostsByCategory {
    type View = Self;

    fn map(&self, document: &BorrowedDocument<'_>) -> ViewMapResult<Self::View> {
        let post = BlogPost::document_contents(document)?;
        document
            .header
            .emit_key_and_value((post.category, post.title.to_lowercase()), 1)
    }

    fn reduce(
        &self,
        mappings: &[ViewMappedValue<Self::View>],
        _rereduce: bool,
    ) -> ReduceResult<Self::View> {
        Ok(mappings.iter().map(|mapping| mapping.value).sum())
    }
}

The next question is: how to query? Well, unfortunately tuples don't have an implementation of IntoPrefixRange (this is a newer trait, but a custom type could implement this for easier querying). Instead, we have to manually build a range to represent all possible keys:
    let rust_posts = db
        .view::<BlogPostsByCategory>()
        .with_key_range(dbg!(String::from("Rust")
            .into_prefix_range()
            .map(|category| (Some(category), String::default()))))
        .query_with_docs()?;
    for mapping in &rust_posts {
        let post = BlogPost::document_contents(mapping.document)?;
        println!(
            "Retrieved post #{} \"{}\"",
            mapping.document.header.id, post.title
        );
    }

This is a little ... non-ergonomic, but it will always produce the correct sort order. Common advice for both CouchDB and BonsaiDb would be to limit the length that the sort key can be. In the future, deriving Key will be possible which will make using custom types instead of tuples easier.
Of note, don't try this on main -- this example shows a bug caused by my recent refactor that didn't get caught by unit tests. It works correctly in the released version.

@ecton this is awesome! I thought about a tuple but then I didn't have a clue how I would query by a tuple if I didn't know the second element (the timestamp). This solves it, and I love how it's done
There's a section on the Key trait in the User Guide, but the information there doesn't do justice to everything that Bonsaidb can do already. My entry point to bonsaiDb was the User Guide. I read all sections before daring to write a single line. On retrospect, it feels like an introduction to data modelling and the query API would have been useful.
Would you be open to creating a new section in the "User guide" for the data model and query API? If you help me with the structure you'd like, I'd be happy to start a draft PR for this.
Some ideas off the top of my head:

How data modelling and schema design should work for an application using BonsaiDb (this has always felt like a compulsory section on any noSQL database to me): differences with other databases, idiosincracies, anti-patterns, etc.
How are Keys used in collections and views and how this affects schema design and queries
Best practices when choosing a Key for a collection and a view (when to use one value, composite keys, etc.)
How to query collections and views (with the usual sections on find one, find many, filter, sort, etc.) with both single and composite Keys, ranges, prefixes, etc.

I would be silly to refuse such an offer! These are all incredibly great ideas to focus on. Additionally, as you encounter things that seem "more complicated" than they should be, please do let me know, as I may be able to improve ergonomics fairly easily for certain use cases.
I don't really know how to structure it -- it's one of the reasons I shipped v0.4.0 without more revisions to the guide. I moved the Key trait section, but it's woefully inadequate. At some point, I am planning on spinning the key module into its own crate so that Nebari and any other key-value store in Rust could use these encoding functions. At that point, I'm not sure where the Key-related documentation should live. Regardless, we can cross that bridge when we get there.
I'm very flexible about the documentation at this stage. I would encourage you to just start and send a pull request whenever you have some content you'd like me to review. I'm an open book and am happy to answer any questions about anything you're uncertain of.
Thank you so much for the offer!

Great! I'll probably start by writing some more examples I can then refer to. It's a bit hectic on my side, so this may take time, but it'll come

I'm excited to see what you come up with, but please do not feel any pressure on my accord! Thank you again!

@ecton I am facing a similar issue, but not with view, just by querying a standard collection. I had to sort the document by myself (I know the current implementation is inefficient, but I am only using it on very small datasets (dozens of docs).
Here's a code sample:
pub async fn get_tracks(&self, track_ids: Vec<String>) -> AnyResult<Vec<Track>> {
    let docs = self.tracks_collection().get_multiple(&track_ids).await?;

    match self.decode_docs::<Track>(docs) {
        Ok(mut tracks) => {
            // document may not ordered the way we want, so let's ensure they map to track_ids
            tracks.sort_by_key(|track| track_ids.iter().position(|id| id == &track._id));
            Ok(tracks)
        }
        Err(err) => Err(err),
    }
}

Is this the intended behavior when using get_multiple?

@martpie This is a deficiency in the documentation and potentially missing functionality. The return order is not guaranteed, although in current implementations it will be the binary-sorted order since that's the order they are contained on disk and how the underlying storage format works.
When writing this I had a choice: add the extra sorting step and possibly slow down some use cases where order didn't matter, or just return them as-is. I decided the latter for the initial implementation.


DeRecIdentity updates

Fixes issue #29 by adding public encryption and signature keys to DeRecIdentity
Fixes issue #30 by adding a method equalsKey()
Fixes issue #31 by adding public encryption key id to DeRecIdentity

Why do we use strings for the key material rather than bytes?
Since the keys are PEM encoded, they are strings in our protobufs as well as the API.

Gotcha thanks


Update links to js-ipfs project

https://github.com/ipfs-inactive/interface-js-ipfs-core is inactive and obsolete/archived. Link to the right documentation.

@vasild  Let's continue to bring CPP-IPFS to the next level 👍🏽

Coverage remained the same at 100.0% when pulling b448b678b8a7b572013e45ae1c01fb572fe9a0af on danger89:patch-1 into 763e59ad698f3e3846f85df11e01c18ef3fbc401 on vasild:master.

Thanks!


Add email

Confirm "email.vccs.edu" belongs to Virginia Community College System

@jna2065 This domain is blacklisted because the college allows to register an email address there even if you are not a student of the college. If you are the student of this college, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


Files are downloaded multiple times if different members have different paths

Suppose a shared folder is called MY_PROJECT.
If one Dropbox for Business member has the shared folder in their Dropbox root folder (the default) and another has it as a subfolder of a non-shared folder (say, /projects/MY_PROJECT), then the files in that project are downloaded twice.
The "entries" metadata from /delta has a key called root but the value is always 'dropbox' as far as I can tell.
There does not seem to be a unique ID for the file. http://stackoverflow.com/questions/15209512/dropbox-file-unique-identifier-restful-api

Perhaps use a set containing the "shared_folder" values in the "entries" metadata dict returned by /delta to mark those folders as polled already.
Check that the shared_folder_id is unique to that folder and consistent across members.


[documentation] minor fixes for links affected by renamed files…

…in README.md

I did sign the CLA and sent it to<EMAIL_ADDRESS>

@marcellanz Thanks for your PR! There seems to be some merge conflicts which need to be resolved before this can be merged, let me know when it is ready to be merged. :)

let me know when it is ready to be merged. :)

@viktorklang I merged upstream and it should be ready now.


How to execute code after ytdl.exec() finishes downloading?   [question][help]

I'm pretty new to node so please bear with me.
I'm trying to make a web server with node and express to pipe videos to the client, here's the example:
const reqbody = {
  fps: '30',
  quality: '1080'
};
const url = 'https://www.youtube.com/watch?v=1La4QzGeaaQ';
const options =  ['-f', `bestvideo[fps=${reqbody.fps}][height<=${reqbody.quality}]+bestaudio`];
const video = ytdl(url, options);

  video.on("info", function(info) {
    res.set({
      "Content-Disposition": `attachment; filename=${info._filename}`,
    });

    video.pipe(res);
  });

Everything works well if I omit +bestaudio or +bestvideo in options. Once I include it I have the following error:
url.js:150
    throw new ERR_INVALID_ARG_TYPE('url', 'string', url);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "url" argument must be of
type string. Received type undefined
    at Url.parse (url.js:150:11)
    at Object.urlParse [as parse] (url.js:144:13)
    at processData (/mnt/e/projects/youtube-extractor/node_modules/youtube-dl/lib/youtube-dl.js:47:21)
    at getInfo (/mnt/e/projects/youtube-extractor/node_modules/youtube-dl/lib/youtube-dl.js:109:9)
    at done (/mnt/e/projects/youtube-extractor/node_modules/youtube-dl/lib/youtube-dl.js:295:9)
    at done (/mnt/e/projects/youtube-extractor/node_modules/youtube-dl/lib/youtube-dl.js:202:9)
    at ChildProcess.exithandler (child_process.js:279:7)
    at ChildProcess.emit (events.js:182:13)
    at maybeClose (internal/child_process.js:962:16)
    at Socket.stream.socket.on (internal/child_process.js:381:11)

I tried fiddling with ytdl.exec() function as in this example, and it downloads videos fine on server machine but since it doesn't return a stream I'm not sure how can I pass it to client.
How can I make this work ?
Edit
I thought about it more and it's unlikely that it's possible to merge video and audio on the fly using ytdl(url, options). If using ytdl.exec() is the only option, how do I wait till a file downloads and only then create a stream and pipe it to the client?

Can't believe I haven't saw that exec function has a callback. Issue solved.


Port Respawn Button from Cosmatic Drift.

About the PR

Ports the respawn button from Cosmatic Drift. Most of this code was originally made by Lank.
Why / Balance

I expect this would be reverted when the server is higher pop, but I think it would be nice to not have to stay as a ghost while the server is such low pop. I have seen it where most of the payers are ghosts that would join if they were able to.
Technical details

Cherry-Picks the following commits/PRs from CD:

https://github.com/cosmatic-drift-14/cosmaticdrift/commit/1474f057100515a16d274a160b5b3c3971622ab8
https://github.com/cosmatic-drift-14/cosmatic-drift/pull/135

I ended up manually integrating them because they were created before we started namspacing things on CD.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

A public method on the ghost gui had it's prototype changed, but this is not really a big deal.
Changelog

:cl: Aquif, Whoever this was copy-pasted from.

add: The respawn button has been ported from cosmatic drift.

I expect the tests to fail here until #8 is merged.

Going to talk with the team before merging this one.

I think its a heisentest thats happening upstream as well

awesome!


overlay: abort if backing fs lacks support for d_type

From https://github.com/moby/moby/pull/27433

CI failing because travis uses old ubuntu
?   	github.com/containerd/containerd/fs/fstest	[no test files]
--- FAIL: TestSupportsDTypeWithFType0XFS (0.01s)
	fsutils_linux_test.go:46: Executing `mkfs.xfs [-m crc=0 -n ftype=0 /tmp/fsutils-image058889521]`
	fsutils_linux_test.go:49: mkfs.xfs: invalid option -- 'm'
		unknown option -m
		Usage: mkfs.xfs
		/* blocksize */		[-b log=n|size=num]
		/* data subvol */	[-d agcount=n,agsize=n,file,name=xxx,size=num,
					    (sunit=value,swidth=value|su=num,sw=num),
					    sectlog=n|sectsize=num
		/* inode size */	[-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2,
					    projid32bit=0|1]
		/* log subvol */	[-l agnum=n,internal,size=num,logdev=xxx,version=n
					    sunit=value|su=num,sectlog=n|sectsize=num,
					    lazy-count=0|1]
		/* label */		[-L label (maximum 12 characters)]
		/* naming */		[-n log=n|size=num,version=2|ci]
		/* prototype file */	[-p fname]
		/* quiet */		[-q]
		/* realtime subvol */	[-r extsize=num,size=num,rtdev=xxx]
		/* sectorsize */	[-s log=n|size=num]
		/* version */		[-V]
					devicename
		<devicename> is required unless -d name=xxx is given.
		<num> is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB),
		      xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB).
		<value> is xxx (512 byte blocks).

	fsutils_linux_test.go:52: exit status 1
--- FAIL: TestSupportsDTypeWithFType1XFS (0.00s)
	fsutils_linux_test.go:46: Executing `mkfs.xfs [-m crc=0 -n ftype=1 /tmp/fsutils-image413445771]`
	fsutils_linux_test.go:49: mkfs.xfs: invalid option -- 'm'
		unknown option -m
		Usage: mkfs.xfs
		/* blocksize */		[-b log=n|size=num]
		/* data subvol */	[-d agcount=n,agsize=n,file,name=xxx,size=num,
					    (sunit=value,swidth=value|su=num,sw=num),
					    sectlog=n|sectsize=num
		/* inode size */	[-i log=n|perblock=n|size=num,maxpct=n,attr=0|1|2,
					    projid32bit=0|1]
		/* log subvol */	[-l agnum=n,internal,size=num,logdev=xxx,version=n
					    sunit=value|su=num,sectlog=n|sectsize=num,
					    lazy-count=0|1]
		/* label */		[-L label (maximum 12 characters)]
		/* naming */		[-n log=n|size=num,version=2|ci]
		/* prototype file */	[-p fname]
		/* quiet */		[-q]
		/* realtime subvol */	[-r extsize=num,size=num,rtdev=xxx]
		/* sectorsize */	[-s log=n|size=num]
		/* version */		[-V]
					devicename
		<devicename> is required unless -d name=xxx is given.
		<num> is xxx (bytes), xxxs (sectors), xxxb (fs blocks), xxxk (xxx KiB),
		      xxxm (xxx MiB), xxxg (xxx GiB), xxxt (xxx TiB) or xxxp (xxx PiB).
		<value> is xxx (512 byte blocks).

	fsutils_linux_test.go:52: exit status 1
--- FAIL: TestSupportsDTypeWithExt4 (0.01s)
	fsutils_linux_test.go:46: Executing `mkfs.ext4 [/tmp/fsutils-image115846389]`
	fsutils_linux_test.go:49: mke2fs 1.42.9 (4-Feb-2014)
		/tmp/fsutils-image115846389 is not a block special device.
		Proceed anyway? (y,n)
	fsutils_linux_test.go:52: exit status 1
FAIL

maybe worth reconsidering adding Dockerfile (https://github.com/containerd/containerd/issues/541)

As a workaround, updated the PR to skip the test when mkfs fails.
I think this is now mergeable without introducing Dockerfile.
PTAL @dmcgowan

Codecov Report

Merging #815 into master will decrease coverage by 0.26%.
The diff coverage is 20%.

@@           Coverage Diff            @@
##           master   #815      +/-   ##
========================================
- Coverage   59.26%    59%   -0.27%
========================================
  Files           5      5
  Lines         739    744       +5
========================================
+ Hits          438    439       +1
- Misses        198    200       +2
- Partials      103    105       +2

Impacted Files
Coverage Δ

snapshot/overlay/overlay.go
52.17% <20%> (-0.9%)
:arrow_down:

Continue to review full report at Codecov.

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

LGTM


PINRemoteImageManager's Disk Space Usage Too High

My app's disk size grows seemingly unbounded. I would like to set a byte limit on PINRemoteImageManager. When investigating, I see this folder growing with each image downloaded: com.pinterest.PINDiskCache.PINRemoteImageManagerCache -- found at this path: ~/Library/Developer/CoreSimulator/Devices/<id>/data/Containers/Data/Application/<other-id>/Library/Caches/com.pinterest.PINDiskCache.PINRemoteImageManagerCache
I see there exists PINDiskCache.sharedCache().byteLimit I have tried setting the byteLimit, but that has no effect on my problem.
Also tried setting this, with no luck solving my problem: PINRemoteImageManager.sharedImageManager().defaultImageCache().diskCache.byteLimit
The ways in which I'm using PINRemoteImage are:

pin_setImageFromURL() for each view I am setting.
And then calling these next 2 just a single time on viewDidLoad
PINRemoteImageManager.sharedImageManager().setMaxNumberOfConcurrentOperations()
PINRemoteImageManager.sharedImageManager().setMaxNumberOfConcurrentDownloads()

Happens on Simulator and devices; iOS 8, 9 and 10; Xcode 7 and 8; Swift 2.3 and 3.0;

I solved my problem by setting: PINRemoteImageManager.sharedImageManager().cache.diskCache.byteLimit

Yeah, hmm, there's probably two learnings here:

We should probably set a default disk cache limit.
Default image cache is a bit confusing, it's intended only for override and should only ever be called once by the PINRemoteImageManager itself. That should be better documented.

Is it safe for me to set it on app launch?
On Oct 7, 2016, 10:19 AM -0700, Garrett Moon<EMAIL_ADDRESS>wrote:

Yeah, hmm, there's probably two learnings here:

We should probably set a default disk cache limit.
Default image cache is a bit confusing, it's intended only for override and should only ever be called once by the PINRemoteImageManager itself. That should be better documented.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub (https://github.com/pinterest/PINRemoteImage/issues/253#issuecomment-252310166), or mute the thread (https://github.com/notifications/unsubscribe-auth/ACBDvsdR4ghfuDgaLrmEOsFhfbfxtvv9ks5qxn8KgaJpZM4KRNbl).

@JoeFerrucci that's a good question, and why I'm now thinking we shouldn't set the cache limit by default.
When it's set it immediately trims to that size. So if we default to setting it to 50MB, and you later set it to 100MB, you'll lose 50MB of cache on every startup.
So I think I'll update the documentation and avoid setting a default limit at this time.
As far as setting it on app launch, it depends on how sensitive you are to performance. We don't set the beteLimit until x number of seconds after app launch (though that allows it to grow unrestrained until we do set the limit and then the disk cache has a lot of work to do to get back into shape).
Long term, and something that we're slowly working toward, we should have the disk cache trim on a lower priority than other operations.

#254


feature/banner-carousel

resolve the conflicts

@Khushbu1819  you are using the classes name directly in your js please use best practices. Find them inside of component instead of looking in entire document. In anchor tag the link is static please make it dynamic


Cannot display a notification in singleWindowApplication

Describe the bug
Cannot display a notification in singleWindowApplication.
Affected platforms

[x] Desktop

Versions

Kotlin version*: 1.7.20
Compose Multiplatform version*: 1.2.2
OS version(s)* (required for Desktop and iOS issues): Mac OS 12.6.1
OS architecture (x86 or arm64): x86

To Reproduce
Steps and/or the code snippet to reproduce the behavior:

Create a singleWindowApplication
Try sending notifications using TrayState
No error message and the notification won't be shown

Also, is creating a Tray mandatory in a window in-order to send notifications?

To facilitate our examining of the issue I would suggest to add a reproducing example nevertheless it seems the reproducing scenario looks simple.

Also, is creating a Tray mandatory in a window in-order to send notifications?

Yes, unfortunately. It is limitation of the current implementation. We plan to provide API that don't require it in the future. Until then, you have to look for a third-party library or call the native API directly.

Also, is creating a Tray mandatory in a window in-order to send notifications?

Yes, unfortunately. It is limitation of the current implementation. We plan to provide API that don't require it in the future. Until then, you have to look for a third-party library or call the native API directly, if you don't need an icon in the tray

I think this answers my question since Tray can be created only in an ApplicationScope and not in a FrameWindowScope, As suggested I might need to use native API directly.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Bump ceph SHAs

This bump is to include commits [1] and [2] which fix issue #879 which
was introduced by the last SHA bumps.  That issue is limited to OSD
hosts running 4 GB of RAM or below and was therefore not discovered in
our gating.
[1] https://github.com/ceph/ansible-ceph-common/commit/0bfa01a6cb5a934e4c2d203eeceb51af3c3de186
[2] https://github.com/ceph/ansible-ceph-common/commit/739230648581659a337902e7159c974547e94898
Closes issue #879
(cherry picked from commit 98ee984ad39769dfaacf1cc22674f5cf032774c9)
Signed-off-by: Matthew Thode<EMAIL_ADDRESS>

LGTM

👍


Feature: Create an OG Image for dev cards

Suggested solution
Currently, Dev Cards aren't shareable. We want to be able to share the DevCards on social media with the OSCR rating on them.
Here's an example from daily.dev: https://app.daily.dev/devcard
They have both vertical and horizontal, but I think we should start with horizontal since we already have things set up that way and we can display both the OSCR and the front and the back info bc there's more real estate. If we find that people are sharing these, we can consider adding the vertical. The challenge there is that we don't get all the info on the front and the back of the card.
Ref: discussion

cc: @isabensusan if you have design ideas.

Moving this to the app as we're using Edge functions for newer OG images.

@nickytonline sorry this took so long! but here's a quick approach to the OG image (all files are in better res in this drive folder too)
Wasn't sure what was the best way to create the images, so I made two different approaches to the same design, and you can pick the one that's better!
Approach 1: entire image as template

Approach 2: devcard image and background as separate images

@nickytonline sorry this took so long! but here's a quick approach to the OG image (all files are in better res in this drive folder too)
Example of OG Image

Wasn't sure what was the best way to create the images, so I made two different approaches to the same design, and you can pick the one that's better!
Approach 1: entire image as template

Approach 2: devcard image and background as separate images

No worries @isabensusan! Looks great! I'll start working on this tomorrow.


ParseHtmlToJson loses folder structure

The destination folder contains all json files in the root. The folder structure of the source is not mapped into destination folder. This causes the help to refer to the wrong html file.

Thanks, we're working on that issue.

Hello @dys-solutions
Thank you for your feedback! We have published a new version of the toolkit with a bunch of bugfixes, including the one you pointed out. Please check out the new version from the master branch, and read about the new and changed tools here: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/help/custom-help-toolkit


Fix typo

👍

Docs Build status updates of commit 0edcc88:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/nuspec.md
:white_check_mark:Succeeded
View

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.


Ignoring asset only npm packages

We have a package that only has fonts (to help trim our Electron package). It has no entrypoint (recently taken out of our package.json). How can we start using flow-typed yet ignore this one package?
$ flow-typed install
• Found<EMAIL_ADDRESS>installed. Installing libdefs compatible with this version of Flow...
• Found 72 dependencies in package.json. Searching for libdefs...
• Installing 7 libdefs...
  • flow-typed/npm/moment_v2.x.x.js already exists!
    └> Use --overwrite to overwrite the existing libdef.
  • flow-typed/npm/react-dnd-html5-backend_v2.1.x.js already exists!
    └> Use --overwrite to overwrite the existing libdef.
  • flow-typed/npm/react-dnd_v2.x.x.js already exists!
    └> Use --overwrite to overwrite the existing libdef.
  • flow-typed/npm/react-redux_v4.x.x.js already exists!
    └> Use --overwrite to overwrite the existing libdef.
  • flow-typed/npm/redux_v3.x.x.js already exists!
    └> Use --overwrite to overwrite the existing libdef.
  • flow-typed/npm/react-addons-test-utils_v15.x.x.js already exists!
    └> Use --overwrite to overwrite the existing libdef.
  • flow-typed/npm/enzyme_v2.x.x.js already exists!
    └> Use --overwrite to overwrite the existing libdef.
UNCAUGHT ERROR: Error: Cannot find module 'nteract-assets' from '/Users/kylek/code/src/github.com/nteract/nteract'
    at /Users/kylek/.nvm/versions/node/v6.7.0/lib/node_modules/flow-typed/node_modules/resolve/lib/async.js:46:17
    at process (/Users/kylek/.nvm/versions/node/v6.7.0/lib/node_modules/flow-typed/node_modules/resolve/lib/async.js:173:43)
    at ondir (/Users/kylek/.nvm/versions/node/v6.7.0/lib/node_modules/flow-typed/node_modules/resolve/lib/async.js:188:17)
    at load (/Users/kylek/.nvm/versions/node/v6.7.0/lib/node_modules/flow-typed/node_modules/resolve/lib/async.js:69:43)
    at onex (/Users/kylek/.nvm/versions/node/v6.7.0/lib/node_modules/flow-typed/node_modules/resolve/lib/async.js:92:31)
    at /Users/kylek/.nvm/versions/node/v6.7.0/lib/node_modules/flow-typed/node_modules/resolve/lib/async.js:22:47
    at FSReqWrap.oncomplete (fs.js:123:15)

To get around this temporarily:
touch node_modules/nteract-assets/index.js

Even though we don't need it in the packages. What should be added to the package or adapted here to handle this? I got rid of the main, thinking that's what would lead flow somewhere.

@rgbkrk This is a showstopper for many. We could have many modules with this issue and doesn't make sense to touch a bunch of files all the time when we install modules. Any module that doesn't meet the criteria should be skipped silently or there could be an optional warning.

I've just published<EMAIL_ADDRESS>with https://github.com/flowtype/flow-typed/commit/d295e7d150309b8e950ee623ef7fb05df18cc4e3, which should fix this.
Please try it out and let me know if you have any more issues!
(NOTE: This is the same issue as https://github.com/flowtype/flow-typed/issues/338)

In the meantime I added a dummy index.js to make this work cleanly.
I'll certainly try out the beta, thanks for hopping on this!


[ReferenceError]: navigator is not defined

Describe the Bug
Getting this error after updating. Seems to be introduced by https://github.com/wbkd/react-flow/commit/32101dde66cccbbd64b4486e47e9441182d93e7b#diff-4dc1db8ddcb4b4ab77751f196ddc803c80c059ce3fe31281ad41d13c6b091b57R130
(I'm using nextJS)
I believe that code should be checking for typeof window !== "undefined".
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Update to 11.8.0
Render the <ReactFlow /> element

Expected behavior
It works on nextJS
Screenshots or Videos
No response
Platform

OS: macOS
Browser: Chrome

Additional context
No response

Thanks @Reflejo !
Fixed in 11.8.1


test: behaviors-message_on_lock_failure (2024-02-19 22:49:03.918038+00:00)

automatic test cleanup


Update to k8s 1.14.0 client libraries using go.mod

Signed-off-by: Tamal Saha<EMAIL_ADDRESS>

Codecov Report

Merging #352 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #352   +/-   ##
======================================
  Coverage    0.95%   0.95%
======================================
  Files           5       5
  Lines         418     418
======================================
  Hits            4       4
  Misses        414     414

Impacted Files
Coverage Δ

pkg/operator/config.go
0% <ø> (ø)
:arrow_up:

pkg/operator/operator.go
0% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


english version?

Hello, thanks for template.
Has english version?

Sorry, I do not plan to support the English version in the near future.
Maybe you can consider ant design pro
https://github.com/vueComponent/ant-design-vue-pro


[BD-46] fix: stretch the message block to the full width

Description
Add stretching the message block to the full width
Deploy Preview
Include a direct link to your changes in this PR's deploy preview here (e.g., a specific component page).
Merge Checklist

[x] If your update includes visual changes, have they been reviewed by a designer? Send them a link to the Netlify deploy preview, if applicable.
[x] Does your change adhere to the documented style conventions?
[x] Do any prop types have missing descriptions in the Props API tables in the documentation site (check deploy preview)?
[x] Were your changes tested using all available themes (see theme switcher in the header of the deploy preview, under the "Settings" icon)?
[x] Were your changes tested in the example app?
[x] Is there adequate test coverage for your changes?
[x] Consider whether this change needs to reviewed/QA'ed for accessibility (a11y). If so, please add wittjeff and adamstankiewicz as reviewers on this PR.

Post-merge Checklist

[x] Verify your changes were released to NPM at the expected version.
[x] If you'd like, share your contribution in #show-and-tell.
[x] 🎉 🙌 Celebrate! Thanks for your contribution.

Thanks for the pull request, @monteri!
When this pull request is ready, tag your edX technical lead.

@monteri 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 21.0.0-alpha.25 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update Gates.md

This gives a little more clarify to this doc. Someone at Blue Apron had some issues reading the documentation so I added a little clarity.
@jnunemaker

Thank you so much for contributing to the docs! Really appreciate it.


Can't build android with com.google.playservices 22.0.0 with ionic

Hi,
i'm trying to play with your plugin on a Nexus 5 device.
I read on another post that i should use com.google.playservices 22.0.0 to have it working properly but using that version then
$ionic build android
doesn't work anymore
What i do is:
$ionic start myapp
$cd myapp
$ionic platform add android
$cordova plugin add https://github.com/wf9a5m75/google-play-services#v22

Now if i run
$ionic run android
it throws an error:
[aapt] invalid resource directory name: /home/sergio/virt/ionic/myapp/platforms/android/com.google.playservices/google-play-services_lib/bin/res crunch
So i remove myapp/platforms/android/com.google.playservices/google-play-services_lib/bin/res
Now
$ionic run android
runs fine so i install the plugin with command
$cordova plugin add plugin.google.maps --variable API_KEY_FOR_ANDROID="XXXXXX...."
Now ionic run android stop working with error:
BUILD FAILED
/home/sergio/virt/ionic/android-sdk-linux/tools/ant/build.xml:720: The following error occurred while executing this line:
/home/sergio/virt/ionic/android-sdk-linux/tools/ant/build.xml:734: Compile failed; see the compiler error output for details.

Total time: 5 seconds

/home/sergio/virt/ionic/myapp/platforms/android/cordova/node_modules/q/q.js:126
                    throw e;
                          ^
Error code 1 for command: ant with args: debug,-f,/home/sergio/virt/ionic/myapp/platforms/android/build.xml,-Dout.dir=ant-build,-Dgen.absolute.dir=ant-gen
Error: /home/sergio/virt/ionic/myapp/platforms/android/cordova/run: Command failed with exit code 8
    at ChildProcess.whenDone (/usr/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:135:23)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:766:16)
    at Process.ChildProcess._handle.onexit (child_process.js:833:5)

And i dunno what to do to get rid of this error.
Any help appreciated
Thank you

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/8901900-can-t-build-android-with-com-google-playservices-22-0-0-with-ionic?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github).

Hi, you were close to the right way. But your not allowed to delete the "res" folder, only the crunch folder inside of it. I had the same issue once. Try to create the tea folder again, it should work.
Nonetheless, everytime you open eclipse with your project it will create this folder again.

Hi Hirbod,
thanks for your reply.
I tried:
$ ionic start myapp
$ cd myapp/
$ cordova plugin add https://github.com/wf9a5m75/google-play-services#v22
$ rm -r platforms/android/com.google.playservices/google-play-services_lib/bin/res/crunch/
$ cordova plugin add plugin.google.maps --variable API_KEY_FOR_ANDROID="XXXXXX...."
$ ionic build android

but i get the same error:
BUILD FAILED
/home/sergio/virt/ionic/android-sdk-linux/tools/ant/build.xml:720: The following error occurred while executing this line:
/home/sergio/virt/ionic/android-sdk-linux/tools/ant/build.xml:734: Compile failed; see the compiler error output for details.

Total time: 9 seconds

/home/sergio/virt/ionic/myapp/platforms/android/cordova/node_modules/q/q.js:126
                    throw e;
                          ^
Error code 1 for command: ant with args: debug,-f,/home/sergio/virt/ionic/myapp/platforms/android/build.xml,-Dout.dir=ant-build,-Dgen.absolute.dir=ant-gen
Error: /home/sergio/virt/ionic/myapp/platforms/android/cordova/build: Command failed with exit code 8
    at ChildProcess.whenDone (/usr/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/superspawn.js:135:23)
    at ChildProcess.emit (events.js:98:17)
    at maybeClose (child_process.js:766:16)
    at Process.ChildProcess._handle.onexit (child_process.js:833:5)

If i just install the plugin without using the v 22 com.google.playservices it builds wihtout need to delete any folder, but then the map is blank on the device.

$> cd platforms/android/
$> ant clean
$> cd ../../
$> ionic build android

You installed plugin.google.maps version which is the same as master branch, however master branch uses Google Play Services v21 not v22.
In order to use v22, you have to use the test branch.
It's really different.
$> cordova plugin rm plugin.google.maps
$> cordova plugin add https://github.com/wf9a5m75/phonegap-googlemaps-plugin#test --variable API_KEY_FOR_ANDROID=...

You' re right!!!
At the end running
$ ionic start myapp
$ cd myapp/
$ ionic platform add android
$ cordova plugin add https://github.com/wf9a5m75/google-play-services#v22
$ rm -r platforms/android/com.google.playservices/google-play-services_lib/bin/res/crunch/
$ cordova plugin add https://github.com/wf9a5m75/phonegap-googlemaps-plugin#test --variable API_KEY_FOR_ANDROID="...."
$ ionic run android

works like a charm on the device too!
Thanks a lot for quick reply!!


Missing PowerPlatformPlex in this article

PowerPlatformPlex
This tag represents the IP addresses used by the infrastructure to host Power Platform extension execution on behalf of the customer.
Inbound
Yes
Yes

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

ID: 215ab00d-9ad0-1e91-184c-218dd64a7d73
Version Independent ID: 337562d4-dab0-ccf9-b272-5de16e88476a
Content: Power Platform URLs and IP address ranges - Power Platform
Content Source: power-platform/admin/online-requirements.md
Service: power-platform
Sub-service: admin
GitHub Login: @sericks007
Microsoft Alias: sericks

Thanks for your comment, @XrmGuru. This issue has been assigned to the doc author for review.


Object mutability and synchronization

Current design of Device trait, for example, assumes the mutable borrow on it for most of the methods you can use, such as resource creation/destruction. This may sound good in theory, but the backing native APIs have different, more flexible approach.
In Vulkan, only some of types are externally synchronized: CommandBuffer, CommandPool, DescriptorPool, Fence, Event, Queue, and Memory. Others, such as Device, can be concurrently used from multiple threads safely.
We should follow Vulkan here: have all Device methods to get &self borrow, and require Device: Sync. Same for other things that are internally synchronized.

have all Device methods to get &self borrow

Sounds good and should be possible

require Device: Sync

This could become an issue for GL. My first idea would be some multithread feature ..

This could become an issue for GL. My first idea would be some multithread feature ..

FWIW I had an idea where the Device implementation on GL would proxy all calls back to whichever thread that holds the GL context. So if the acting thread doesn't match the thread that holds GL context, it sends any arguments and waits until it receives the return value.
It's probably similar to how gfx GL command buffers were emulated, but more granular, and hiding the send/receive from the caller. This is nontrivial and magical though, and I'm not sure it's even worthwhile considering the additional overhead. I was planning to create a proof-of-concept for WebGL a long time ago but decided web worker latency was likely too high for it to be useful.

@grovesNL that would be an interesting experiment, but we can start by just having the Sync/Send bounds not enforced by gfx-hal but still available by the backend's concrete types.


Fix navigation and state management for web

Most States should be represented by URL so that if anything url copy pasted it should be able to restore the state

@bhujoshi FYI

@bhujoshi FYI


How to: automatic publishing with multiple packages

https://dart.dev/tools/pub/automated-publishing mentions "multiple packages" a couple of times. But it doesn't show how to specify working-directory to support this.
Is this possible or do I have to create a separate workflow for each package?
cc @devoncarew

There's an example of using automated publishing and mono-repos here:
https://github.com/google/dart-neats/blob/master/.github/workflows/publish.yml

It's a creative combo of bash and sed.
Separately, the dart team has some prescriptive tooling built on top of the pub + github automation; https://github.com/dart-lang/ecosystem/tree/main/pkgs/firehose. That's not really intended for broad use but is something we ourselves will use to publish packages. It'll detect whether it's running from a single package repo or a mono-repo; you can see an example of the integration here: https://github.com/dart-lang/shelf/blob/master/.github/workflows/publish.yaml.

Oh nice! It would be worth pointing out in the docs that no further action is required

Dumped a comment in https://github.com/dart-lang/site-www/pull/4574
I think it's fairly reasonable to make a workflow file per package. The thing I did in dart-neats repo is only going to work in cases where the package folder is the package name, and the tag pattern is <package>-{{version}}.
I'm open to providing better logic, but honestly, it's probably better if we just tweak mono_repo to generate workflows for publishing.

Filed https://github.com/google/mono_repo.dart/issues/434


Circular path references on subscribes result in infinite loops

if you have a circular reference in a subscribe, then the event will trigger an infinite loop:
const Entangld=require("./index.js");

let s = new Entangld();
let a = new Entangld();
let b = new Entangld();

s.attach("path1.A",a);
s.attach("path2.B",b);
a.attach("path3.B",b);
b.attach("path4.A",a);

s.transmit((msg, store)=>store.receive(msg, s));
a.transmit((msg, store)=>store.receive(msg, a));
b.transmit((msg, store)=>store.receive(msg, b));

s.subscribe('path1.A.path3.B.path4.A.data', () => {});

// a has two subscription objects, one terminal and one passthrough:
console.log(a.subscriptions.map(v => v.path)); // === [ 'path3.B.path4.A.data', 'data' ]

a.set('data', 1); // causes `RangeError: Maximum call stack size exceeded`

The last line causes an error because while the terminal subscription object behaves as expected, the passthrough subscription also gets triggered by index.js line 853. This second trigger will send an event type message around through b a back to a and trigger both subscription objects again? Not totally sure.

Nope, it is actually line 743 that causes the issue -- since both subscription object have the same uuid

For now, let's detect it and throw an error -- add it to the todo on a major revision


Version 1.21.1

hatcling 1.21.1
Destination channel: defaults
Links

PKG-4064
Upstream repository
Upstream changelog/diff

Explanation of changes:

Update version and sha256
Reset build number
Update python build skip to <38

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_4d8qffnbnc/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:29: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:26: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:31: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 6 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(124): `conda run conda-lint /tmp/abs_12z8tk1_g4/clone` failed. (See above for error)
The following problems have been found:
===== WARNINGS =====

clone/recipe/meta.yaml:26: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:31: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:28: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:29: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
clone/recipe/meta.yaml:30: host_section_needs_exact_pinnings: Linked libraries host should have exact version pinnings.
===== Final Report: =====
0 Errors and 6 Warnings were found


Update to Unicode 16

https://www.unicode.org/versions/Unicode16.0.0/
UAX#29 changed

The definition of GCB=V was updated to include Kirat Rai vowels. The description of rules GB6 - GB8 was updated.

A custom build of Node.js (including custom icu data) is required for PBT, but maybe I can just wait until the next version is released.


Using a scalar in allclose raises an AttributeError

Problem
Using a scalar in allclose raises AttributeError: PROJ_1D_1D_.
To reproduce

step 1: create test.pyfrom legate import numpy as lnp
import numpy as realnp

# vanilla numpy works
a = realnp.full(10, 1e-1)
print(realnp.allclose(a, 1e-1))

# legate numpy not working
la = lnp.full(10, 1e-1)
print(lnp.allclose(la, 1e-1))

step 2: run test.py with legate --cpus 1 ./test.py -lg:numpy:test

Output
The first part that uses vanilla NumPy prints True.
The second part that uses Legate NumPy raises:
Traceback (most recent call last):
  File "<prefix>/lib/python3.8/site-packages/legion_top.py", line 408, in legion_python_main
    run_path(args[start], run_name='__main__')
  File "<prefix>/lib/python3.8/site-packages/legion_top.py", line 200, in run_path
    exec(code, module.__dict__, module.__dict__)
  File "./test.py", line 10, in <module>
    print(lnp.allclose(la, 1e-1))
  File "<prefix>/lib/python3.8/site-packages/legate/numpy/module.py", line 459, in allclose
    return ndarray.perform_binary_reduction(
  File "<prefix>/lib/python3.8/site-packages/legate/numpy/array.py", line 2068, in perform_binary_reduction
    dst._thunk.binary_reduction(
  File "<prefix>/lib/python3.8/site-packages/legate/numpy/deferred.py", line 5167, in binary_reduction
    ) = self.runtime.compute_broadcast_transform(
  File "<prefix>/lib/python3.8/site-packages/legate/numpy/runtime.py", line 2500, in compute_broadcast_transform
    self.first_proj_id + getattr(NumPyProjCode, proj_name),
  File "<prefix>/lib/python3.8/enum.py", line 384, in __getattr__
    raise AttributeError(name) from None
AttributeError: PROJ_1D_1D_

Expected behavior
Working like vanilla NumPy, or raising an exception with a clear message of what is not supported.

Should be fixed by 8b85c00. @piyueh can you pull and try again?

@magnatelee It's working now. But there's a minor difference in the outputs of vanilla NumPy and Legate NumPy. Vanilla NumPy returns a Python's native bool, while Legate NumPy returns a 1D boolean ndarray with shape (1,). For example, the above example code returns:
True
[ True]

However, this is a minor issue for me.
I'll close the issue if you think this behavior (i.e., not returning a native bool) will not be changed soon.

I think I can fix it quickly, so let's keep this open.

Please pull and try again.

@magnatelee Thanks! It's working. Closing the issue.

@magnatelee I reopened this issue because if there's no -lg:numpy:test flag, the test failed. This is the error traceback
[0 - 7f77b186f000]    0.819757 {6}{python}: python exception occurred within task:
Traceback (most recent call last):
  File "<prefix>/lib/python3.8/site-packages/legion_top.py", line 408, in legion_python_main
    run_path(args[start], run_name='__main__')
  File "<prefix>/lib/python3.8/site-packages/legion_top.py", line 200, in run_path
    exec(code, module.__dict__, module.__dict__)
  File "./test.py", line 10, in <module>
    print(lnp.allclose(la, 1e-1))
  File "<prefix>/lib/python3.8/site-packages/legate/numpy/module.py", line 459, in allclose
    return ndarray.perform_binary_reduction(
  File "<prefix>/lib/python3.8/site-packages/legate/numpy/array.py", line 2068, in perform_binary_reduction
    dst._thunk.binary_reduction(
  File "<prefix>/lib/python3.8/site-packages/legate/numpy/eager.py", line 947, in binary_reduction
    self.array[:] = np.allclose(
IndexError: too many indices for array: array is 0-dimensional, but 1 were indexed

Should be fixed now. Please pull and try again.

Hi, I got this error:
[0 - 7f81bbd5c7c0]    0.742322 {6}{python}: python exception occurred within task:
Traceback (most recent call last):
  File "<prefix>/lib/python3.8/site-packages/legion_top.py", line 408, in legion_python_main
    run_path(args[start], run_name='__main__')
  File "<prefix>/lib/python3.8/site-packages/legion_top.py", line 200, in run_path
    exec(code, module.__dict__, module.__dict__)
  File "./test.py", line 10, in <module>
    print(lnp.allclose(la, 1e-1))
  File "<prefix>/lib/python3.8/site-packages/legate/numpy/array.py", line 770, in __str__
    self._thunk.get_scalar_array(stacklevel=2), self.shape
  File "<prefix>/lib/python3.8/site-packages/legate/numpy/eager.py", line 159, in get_scalar_array
    return self.array.reshape(())
AttributeError: 'bool' object has no attribute 'reshape'

Please pull and try again with febd3bf390f

It wroks. Thanks! Closing the issue.


Integration Testing

30 min- set up, talking, and start in class

30 min- implementation, puling in other branches

30 min- finish implementation, need to be able to read an entire restaurant to a file and then save it to fully pass


[easy-coding-standard] Document how to integrate with Github Actions

I followed the instructions here: https://github.com/marketplace/actions/easy-coding-standard-action
And added the lines to my action
  - name: Easy Coding Standard Action
    uses<EMAIL_ADDRESS>
https://github.com/survos/SurvosMakerBundle/blob/main/.github/workflows/coding-standards.yml#L44-L46
But the action is failing:
1s
Run<EMAIL_ADDRESS>with:
version: master
env:
COMPOSER_PROCESS_TIMEOUT: 0
COMPOSER_NO_INTERACTION: 1
/usr/bin/docker run --name e3188b24f7f975495d92801b95b085a59c_79da15 --label 5364e3 --workdir /github/workspace --rm -e "COMPOSER_PROCESS_TIMEOUT" -e "COMPOSER_NO_INTERACTION" -e "INPUT_VERSION" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/SurvosMakerBundle/SurvosMakerBundle":"/github/workspace" 5364e3:188b24f7f975495d92801b95b085a59c  "master" ""
Connecting to github.com (<IP_ADDRESS>:443)
Connecting to github.com (<IP_ADDRESS>:443)
wget: server returned error: HTTP/1.1 404 Not Found
/entrypoint.sh: line 9: /usr/local/bin/ecs: not found
https://github.com/survos/SurvosMakerBundle/actions/runs/3177578606/jobs/5178178690

Hi, we actually don't maintain that package.
That's different repository, you can create issue in there.


Error handling issue

It seems like error handler in recaptcha2 doesn't really send error, but just a normal response.

could you please describe whole scenario of this issue . i don't understand your point .

The error message sent from recaptcha.translateErrors(err) does not act like an error, but just a normal response. Does it make sense for you?

So now in addition to error handler on my front-end, I have to implement additional coding to check if my response is ["missing-input-secret"] and fire an error.

as you can see in :
https://developers.google.com/recaptcha/docs/verify
google returns cause of error as a standard string , you can check Error code reference section .
in this library translateErrors method just translate error codes to human readable text and does not throw exception or anything special.
errors handled in promise catch so it's not classic try catch exception .
if you need errors as exception you can use javascript generators and yield library promise .

I see. Thank you for your clear and details answer!


any plan to support depended graph?

curl  'https://www.npmjs.com/browse/depended/execa?offset=36' --header 'x-spiferack: 1'

No immediate plans for this.  While this information is interesting, I don't see it as directly relevant to the main problem that NPMGraph is trying to solve - which is to help developers understand the nature of the dependency tree their projects rely on..


#82: Softlink creation requires admin privileges during software installation

#82 Softlink creation requires admin privileges during software installation

TODO :
https://github.com/devonfw/IDEasy/blob/main/documentation/symlinks.asciidoc  has yet to be created.

@moritzLanger thanks for your update. Now perfect and ready for merge 👍 Should I wait until you add the documentation or can you simply set this as ready for review and provide the documentation in a separate PR?

I set the PR as ready for review. I will add the documentation in a separate PR in the coming days.


New version Exercism: 0.1.3

Registering: Exercism
Repository: https://github.com/exercism/Exercism.jl
Version: v0.1.3
Commit: 3352374c6fe859d1509cc9cd3880a8db72f9577e
Proposed by: @SaschaMann
Reviewed by: @SaschaMann
Reference: https://github.com/exercism/Exercism.jl/commit/3352374c6fe859d1509cc9cd3880a8db72f9577e#commitcomment-33367259

Updated it to JSON  = "0.19, 0.20"

Consider enabling TagBot to make sure the release is persistent in your repo, see https://discourse.julialang.org/t/ann-tagbot-creates-tags-and-releases-for-your-julia-packages-when-theyre-registered/23084

For now I'll do it manually. Adding apps with write access requires bothering other people in the org about it, which isn't worth it atm, but thanks for the heads-up.


[RELEASE] Release version 2.9.0

This is a component issue for {REPLACE_WITH_RELEASE_VERSION}.
Coming from https://github.com/opensearch-project/opensearch-build/issues/3616. Please follow the following checklist.
Please refer to the DATES in that post.
How to use this issue

This Component Release Issue
This issue captures the state of the OpenSearch release, on component/plugin level; its assignee is responsible for driving the release. Please contact them or @mention them on this issue for help.
Any release related work can be linked to this issue or added as comments to create visiblity into the release status.
Release Steps
There are several steps to the release process; these steps are completed as the whole component release and components that are behind present risk to the release. The component owner resolves the tasks in this issue and communicate with the overall release owner to make sure each component are moving along as expected.
Steps have completion dates for coordinating efforts between the components of a release; components can start as soon as they are ready far in advance of a future release. The most current set of dates is on the overall release issue linked at the top of this issue.
The Overall Release Issue
Linked at the top of this issue, the overall release issue captures the state of the entire OpenSearch release including references to this issue, the release owner which is the assignee is responsible for communicating the release status broadly.  Please contact them or @mention them on that issue for help.
What should I do if my plugin isn't making any changes?
If including changes in this release, increment the version on __{REPLACE_MAJOR_MINOR_PATCH}__ branch to __{REPLACE_MAJOR_MINOR_PATCH}__ for Min/Core, and __{REPLACE_MAJOR_MINOR_PATCH_0}__ for components. Otherwise, keep the version number unchanged for both.

Preparation

[x] Assign this issue to a release owner.
[x] Finalize scope and feature set and update the Public Roadmap.
[x] All the tasks in this issue have been reviewed by the release owner.
[x] Create, update, triage and label all features and issues targeted for this release with v__REPLACE_MAJOR_MINOR_PATCH__.

CI/CD

[x] All code changes for __{REPLACE_MAJOR_MINOR_PATCH}__ are complete.
[x] Ensure working and passing CI.
[x] Check that this repo is included in the distribution manifest.

Pre-Release

[ ] Update to the __REPLACE_MAJOR_MINOR__ release branch in the distribution manifest.
[ ] Increment the version on the parent branch to the next development iteration.
[ ] Gather, review and publish release notes following the rules and back port it to the release branch.git-release-notes may be used to generate release notes from your commit history.
[ ] Confirm that all changes for __{REPLACE_MAJOR_MINOR_PATCH}__ have been merged.
[ ] Add this repo to the manifest for the next developer iteration.

Release Testing

[ ] Find/fix bugs using latest tarball and docker image provided in parent release issue and update the release notes if necessary.
[ ] Code Complete: Test within the distribution, ensuring integration, backwards compatibility, and performance tests pass.
[ ] Sanity Testing: Sanity testing and fixing of critical issues found.
[ ] File issues for all intermittent test failures.

Release

[ ] Complete documentation.
[ ] Verify all issued labeled for this release are closed or labelled for the next release.
[ ] Verify the release date mentioned in release notes is correct and matches actual release date.

Post Release

[ ] Prepare for an eventual security fix development iteration by incrementing the version on the release branch to the next eventual patch version.
[ ] Add this repo to the manifest of the next eventual security patch version.
[ ] Suggest improvements to this template.
[ ] Conduct a retrospective, and publish its results.

@prudhvigodithi Since the 2.9.0 has been released, I will close this issue. Feel free to re-open it if there is any updates.