Cannot create MongoDB database with Adminer

ISSUE TYPE

Bug Report

Checklist

[x] .env file is attached
[ ] docker-compose.override.yml is attached (if it exists)
[ ] Custom configs from cfg/ dir are attached (if customized)
[x] docker-compose logs and log/ output is added
[x] I've looked through the docs: https://devilbox.readthedocs.io/en/latest/
[x] I've looked through existing issues: https://github.com/cytopia/devilbox/issues
[x] I've read troubleshooting: https://devilbox.readthedocs.io/en/latest/support/troubleshooting.html

env.txt
OS / ENVIRONMENT

Host operating system and version: Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
(Windows) Native Docker or Docker Toolbox:
Docker version: Docker version 19.03.1, build 74b1e89
Docker Compose version: docker-compose version 1.23.2, build 1110ad01
(Linux) Is SELinux enabled?:

SUMMARY

Using Adminer I like to create a MongoDB database and tables. When I try to create a table I get the following error.
Fatal error: Uncaught Error: Call to a member function createCollection() on null in /var/www/default/htdocs/vendor/adminer-4.7.1-en.php:1202 Stack trace: #0 /var/www/default/htdocs/vendor/adminer-4.7.1-en.php(1840): alter_table('', 'item', Array, Array, NULL, '', '', '', '') #1 {main} thrown in /var/www/default/htdocs/vendor/adminer-4.7.1-en.php on line 1202.

When I simply just create a MongoDB database inside Adminer and then log out of Adminer and go back to check https://localhost/db_mongo.php the newly created database is not listed, it is not there.

STEPS TO REPRODUCE

docker-compose up -d
Go to localhost, then click > Tools > Adminer.
On Adminer Login page select System : MongoDB and Server : mongo. I could not find info in the docs on the MongoDB Username or Password so I just leave those empty.
Next click Create database, give it a name, Save, done. Even though this database seems to have been created it does not show when going to https://localhost/db_mongo.php. Why?
Still in Adminer, with the newly created database click Create table, give it a name and hit Save.
Then you get Fatal error: Uncaught Error: Call to a member function createCollection() on null in /var/www/default/htdocs/vendor/adminer-4.7.1-en.php:1202 Stack trace: #0 /var/www/default/htdocs/vendor/adminer-4.7.1-en.php(1840): alter_table('', 'item', Array, Array, NULL, '', '', '', '') #1 {main} thrown in /var/www/default/htdocs/vendor/adminer-4.7.1-en.php on line 1202.

EXPECTED BEHAVIOUR

Being able to create MongoDB databases and tables with Adminer.
ACTUAL BEHAVIOUR

Created database is never saved or shown under https://localhost/db_mongo.php.
Fatal error when trying to create database table.
OTHER INFORMATION
Start command

$ docker-compose up -d

File and user permissions (Linux & MacOS)

$ id
uid=1000, gid=1000, docker=999

$ ls -la
root

$ ls -la data/www
root

Creating the MongoDB database and collections via the CLI inside the PHP container works. Once that is done and a document (db entry) is created the database also starts showing on https://localhost/db_mongo.php.
So I made a database with a User and Password.
But still, when I try to log on to that specific database via the Adminer login page I get this error.
Database does not support password.
However in my code, in the connection string, when I change the user or password I cannot connect, so for me that proves that the database in question does indeed have the right user and access rights.
Here is the code I used to make a user and password for the database.
db.createUser(
  {
    user: "user",
    pwd: "password",
    roles: [ { role: "readWrite", db: "simpleappdb" } ]
  }
)

When I go into Adminer and just select System : MongoDB and Server : mongo I can see the database that was created with the CLI. However if I try to change it or add to it I get various fatal errors, depending on if I am trying to add, edit or delete a document or collection.
Why does it say Database does not support password. when I try to login through Adminer?

@robots4life Works fine here. What PHP, Mongo and Adminer version are you using?


Question: Retry failed action in single flow

How would one implement the following flow?
Dispatch API action > API middleware executes request > Request fails (401, auth token needs to be refreshed) > Refresh auth token (refresh token action called from middleware) > Re-execute original action
Is it possible to do this all in the flow of a single action? I can post code if necessary, hope my question is clear enough.

I would say that I recommend https://github.com/yelouafi/redux-saga for async control flow like this.

Thanks @gaearon I'll check that out.


apostrophe-pieces manage view should be tested with some fake data

Insert some grommets in the db and see if you can get them to show up.
Clicking on them should try to launch the edit modal although making that modal work is my problem.

data now shows up in manage view


Header in Card

Please add something like header in the card

For what reason? The Card is a generic control / layout of material design.

There are also a couple of Group Box controls.... One of them is basically a card with a header and you can change the header style yourself

Yes, Card is totally generic. Adding a Header is inappropriate here.


When importing module with js extension also try to resolve corresponding module with tsx extension

Clear and concise description of the problem
A similar functionality was already implemented in https://github.com/vitejs/vite/pull/5510 but the implementation only tries once to either resolve $module.ts or  $module.tsx (depending on the extension used in the import).
TypeScript typecheck does not complain when using  .js and there only exist a corresponding .tsx module. So Vite would behave closer to how TypeScript works when this would be implemented, following basically the same reasoning as in the aforementioned merged PR.
Suggested solution
Vite could also try to resolve a module using .tsx (instead of only .ts) even if the import uses just .js.
Alternative
No response
Additional context
No response
Validations

[x] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I have also encountered this when migrating a project to vite. Is there any workout currently?

This seems to be no longer a problem as of version 2.9.0-beta.0. Thank you!


Refactor/auth

Description

Closes

https://armory.atlassian.net/browse/CLOUD-880
https://armory.atlassian.net/browse/CLOUD-1315

Motivation and Context

https://armory.atlassian.net/browse/CLOUD-880
https://armory.atlassian.net/browse/CLOUD-1315

How has this been tested? How can a reviewer test these changes?

UATing cloud-880 I used prod and my local dev
- I logged into an org w/ 1 env and it didn't prompt
- I logged into an org with multiple envs and it did prompt
- I set the -e flag for an org with multiple envs and it didn't prompts
**UATing cloud-1315

I set my clock back on-pupose and attempted to log in, got IAT issue, dev'd and re-ran with bad clock and it workd

Have your performed the following tests?
Please confirm you have done the following tests to ensure your pull request is ready to be merged..

[X] If this change modifies the deployment flow have triggered a deployment using this branch (i.e. build/dist/darwin_amd64/armory deploy start -f <path to file>)?
[X] If this change modifes the login flow have you tried logging in and out with this branch (i.e. build/dist/darwin_amd64/armory login) and verified the credentials work?
[X] Have you verified the specific change made in this PR?

The title of this Pull Request needs to be changed to match the format:
<type>(<scope>): <subject>

See more details here: https://www.spinnaker.io/community/contributing/submitting/#commit-message-conventions
Some common examples are:
feat(armory.io): add docs.armory.io
fix(parser): grammar and spelling
style(loadingPage): made it super pretty!
refactor(helpMessages): changed order to make more sense

The title of this Pull Request needs to be changed to match the format:
<type>(<scope>): <subject>

See more details here: https://www.spinnaker.io/community/contributing/submitting/#commit-message-conventions
Some common examples are:
feat(armory.io): add docs.armory.io
fix(parser): grammar and spelling
style(loadingPage): made it super pretty!
refactor(helpMessages): changed order to make more sense


Backend shortcuts

TEMPLATED_EMAIL_BACKEND = 'templated_email.backends.vanilla_django.TemplateBackend'  is more than 80 chars length.
It would be nice to have some sort of shortcut for this :)

Open to suggestions for how to make it shorter.

We can omit TemplatedBackend class and try to treat whole string as module in get_connection and then fallback to current behavior.

Can you open a pull request with a prototype of what you feel would be a good solution?

done

closing issue cuz we have another one for pull request


UI Suggestions: Hide locked concepts, hot keys and diffing between LHS and RHS

Title. I would like to suggest a few UI improvements to the game.

The player should have the right to hide/unhide the locked concepts (tactics, definitions, theorems...) with a button on each topic. That way, they can focus on what they already have.
They should also be able to assign hot keys to quickly insert "concepts".
For the diffing part, there should also be a hide/unhide button to do the trick. The color scheme should be reasonable, too (though I doubt this is a LSP problem - out of scope for this game).

I would like to introduce these with a PR, but unfortunately I'm still new to Lean and couldn't do much. Hope my idea would help!

Thanks for the suggestions. They are best placed as individual issues at github.com/leanprover-community/lean4game

I'm gonna close it for now, thank you.

You can keep it open until there are issues on the other repo. I might make them myself once I have time :)


No debug option available

I'm trying to debug an issue of missing dependencies, and PyInstaller recommends to use the --debug=imports option. See PyInstaller docs here.
Unfortunately, the Poetry plugin doesn't support this argument. Or, does it?
poetry build --debug=imports
...
The option "--debug" does not exist

Thx @thmahe for the quick fix, much appreciated!


Types of variables change if source is from spread object

Bug Report

🔎 Search Terms

spreads
strict mode
union types

🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about Type System Behavior

⏯ Playground Link

https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgEJwM4QCoE8AOEGyA3gLABQyywAJgPwBcyGYUoA5sgD7ICuIWhBigItANyVqMAPYzmrdiA6SqyAEZwwzEHwC266KoC+lSqEixEKAEoQAjn2BQxeQsXJq6CtpxNmKIQQAGzgXZBgBBDBgGRBkDggwAElaAAoASh8lFQDIkGjY+NkZAB43ImQIAA9IQWJ0LAqMAD40kgi5ABpkADp+2i04ZGNmZozSKWQEONZkIXg+YJTaZABeBKTUzNVqGZA5vVxU9fmh3roeXgW4JZXd6dmwZGrmO0dnVwJKjc9qam8yCOqS6U1MFHBQA
💻 Code

interface BaseTypes {
  id?: string | undefined;
  foo: string;
  bat: number;
}

interface RequiredTypes {
  id: string;
}

declare function getId(): string;

function foo<Types extends BaseTypes>({ foo, ...data }: Types) {
  const defaultId = getId();
  const myId = data.id || defaultId;
  const x: RequiredTypes = {
    id: myId,
  }
}

If I change the code to the following the bug goes away
function foo<Types extends BaseTypes>(data: Types) {
  const defaultId = getId();
  const myId = data.id || defaultId;
  const x: RequiredTypes = {
    id: myId,
  }
}

🙁 Actual behavior

The type of myId in function foo is string | Types["id"].
🙂 Expected behavior

The type of myId is string.

There’s some special logic that happens on expressions like data.id where data is a type parameter (e.g. Types) with a constraint (e.g. BaseTypes) where it goes ahead and simplifies from the most specific type (Types["id"]) to a wider but more immediately usable type (BaseTypes["id"] → string). In the former example, the type of data is Omit<Types, "foo"> instead of just Types, so we don’t recognize that the simplification is safe to make. I’m not sure whether there’s a simple, generalizable way around this. @weswigham thoughts?


Cache doesn't take source into account

The cached result does not take into account the target language of the translation. For example, if I translate the string "Hello" to Spanish, the cache stores "Hola". Then, if I try to retranslate it into French, it will still say "Hola" because the cache does not store the language it is translated into. I will see if there is a way to fix this issue myself, but for now, I have the caching code in FGTranslator.m commented out.

Thanks for spotting this Evan! I merged your fix and released a new version (1.1.1) to CocoaPods.


Fix new doc XML issues introduced recently

Fixing CS errors: 157x, 1580, and 1591.

These errors pollute the ref doc build.


dbt should throw a compilation error for shared resource paths

Please make sure to fill out either the issue template or the feature template and delete the other one!
Issue
Issue description
If resources are configured to have the same path, dbt doesn't throw any sort of error.
e.g.
# dbt_project.yml
source-paths: ["models"]
test-paths: ["models"]

Results
When you dbt compile it runs fine. If you dbt test --data, you'll get errors back because the select statements return rows.
Expected results
This should throw an error:
source-paths: ["models"]
test-paths: ["models"]

As should this
source-paths: ["models"]
test-paths: ["models/tests"]

This should not:
source-paths: ["resources/models"]
test-paths: ["resources/tests"]

System information
dbt version 0.14.0

It's probably worth noting for whoever ends up implementing this that docs-paths can and by default does overlap with source-paths (or really, anything, since it looks for .md instead of .sql)

I'd like these paths to go away long-term. Things like the {% snapshot %} blocks + #184 will mean that each resource will define what type of resource it is. We already do this for {% docs %} blocks, and it would be good to think about how to do it for custom data tests too! The really cool benefit of this approach is that multiple resource types can live inside of the same file (if desired).
I'd be in favor of renaming these paths more sensibly (#1607) than adding yet more logic around path names

OK! Happy for you to close in that case :)


Handlers need to check that service is installed before trying to restart them

This happens on initialization of the server.  If the service has not yet been installed, but a handler is asking to restart it.  The handler fails, and the host does not continue in the play.

Closing as duplicate of #361


How to use the functions of the old version

IDE:
vscode
Plugin Version:
3.6.14
Engine Version:
4.4.127-47
Issue Details:
I have enabled the new version, but it is not as good as the previous version.
But I can't find how to close the new version, and I don't know how to set it to the old version.
How should I set it?
gz#17566

What functions do you want back? We appreciate your feedback and would love to hear it.

I use vscode. Now the prompt function only has the prompt like copilot, and there is no automatic completion of the drop-down selection box.
I prefer auto completion with drop-down selection.
The current completion method can only complete words simply, and rarely complete effective intelligent prompts.
In addition, when using the drop-down box method, multiple cursors can also complete filling, but not now.
I prefer the usage in the screenshot below。

You should stay tuned for the dropdown returning to vscode (as an optional behavior) :)
Also, see https://github.com/codota/TabNine/issues/541

but  there is no way to set anying.

It is not released yet. We are working on it.

bring back old-style completion with drop-down selection only feature


When building rootless docker image move chown&chmod to build stage

Have not tested, need feedback
Fixes #13577
@sapk could this work?

Anyway does chmod is really needed. imho golang build will already provide binary with such attributes

Codecov Report

Merging #13578 (0ec9e39) into master (0de5460) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13578   +/-   ##
=======================================
  Coverage   42.21%   42.22%
=======================================
  Files         696      696
  Lines       76520    76520
=======================================
+ Hits        32303    32309    +6
+ Misses      38917    38911    -6
  Partials     5300     5300

Impacted Files
Coverage Δ

modules/charset/charset.go
70.78% <0.00%> (-2.25%)
:arrow_down:

modules/log/event.go
58.96% <0.00%> (-0.95%)
:arrow_down:

services/gitdiff/gitdiff.go
69.68% <0.00%> (+1.96%)
: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 0de5460...27df0e2. Read the comment docs.

Tested building locally and seems to be building with correct attributes and owner

🚀

@techknowlogick yes that the good solution. I overlook this part as I wanted to be sure that the permission was forced but it wasn't efficient.


[Issue] List of subscriptions is too broad

[ ] Make sure you've installed the latest version using instructions in the wiki

Output from azd version
Run azd version and copy and paste the output here: azd version 1.3.0 (commit 6605c5768cb3ab6d9e0e6c2d892c9e8b49e1f720)
Describe the bug
when I provision, the list of subscriptions is too broad - I should only have 2 subscriptions for my personal email which is also tied to my FTE VS Enterprise subscription.
To Reproduce

In CodeSpaces, open https://github.com/Azure-Samples/contoso-real-estate.
azd auth login
azd provision - this shows more than my 2 subscriptions I have using my personal account

   1. 1-Pay-As-You-Go (xxx)
   2. AICP-API-QnAMaker-MSFT-Non-Prod (xxx)
   3. Azure VMware Solution Licensing Calculator (xxx)
   4. Microsoft for Startups for tech staff to learn and test (xxx)
   5. Visual Studio Enterprise Subscription (xxx)

Number 1 and 5 are what I should see. No idea where 2,3, and 4 came from. This seems like a security issue with how azd is getting the list.
Expected behavior
Only show me 1 and 5.
Environment
Information on your environment:
* Language name and version
* IDE and version : [e.g. Visual Studio 16.3]
Additional context
Add any other context about the problem here.

@rajeshkamal5050 Can we get someone to investigate? Seems like a bug.

This seems like a security issue with how azd is getting the list.

AZD pulls all the subscriptions from all the tenants the user has access to, not just the user's default tenant.  This behavior is similar to what az does.  @diberry wondering if you also see these other subscriptions when you do an az account list with the az CLI?

@ellismg Yes, they all show up. Weird is that 2 weeks ago, only the QnAMaker was the addition to the list. Now there are 2 more. There isn't anyway  my personal account should be seeing this unless somehow access to the VS enterprise sub is giving it to me. I'm using a Google chrome browser logged into with my personal account only.
If I log into the azure portal with the personal account, I only see the 2 I'm supposed to see.

From the az account list screenshot above. Looks like these aggregated subs are coming from two different tenants which the user is associated with. Doesn't seem to be a security issue. cc @weikanglim

@diberry In the screenshot, Subscriptions == global filter is applied. Does removing the filter change the result?

@weikanglim

@rajeshkamal5050 Do my personal account is in the corporate tenant somehow. How can I find that and remove it?

@diberry Let me work with you to see if we can't get it resolved.

Closing since the original issue has been resolved. azd is listing subscriptions across all tenants that the user has access to.


Copied get_vector implementation from Input to InputEvent

I need this functionality so that I can handle user input both  from InputEvents and the Input singleton in a uniform way.
I could have implemented something in gdscript, but I think this is an improvement to the engine.
I have read the contributing guidelines, but I didn't take the effort to write a proposal issue, sorry!
If anyone else finds this PR useful let me know, it's needed I will add the issue.

Not sure about having duplicate implementations in the Input/InputEvent, maybe there's some way the Input class could use the definition from InputEvent instead, so that there's only one implementation to maintain.
Also you might want to update docs for InputEvent (or just copy/paste it from Input)
doc\classes\InputEvent.xml

I have read the contributing guidelines, but I didn't take the effort to write a proposal issue, sorry!
If anyone else finds this PR useful let me know, it's needed I will add the issue.

That's what proposals are for too. It's unlikely PRs like these gather interest by themselves.

The two implementations Input.get_vector and InputEvent.get_vector differ, because they use different get_action_raw_strength(), so I'm not yet convinced, that they can be used in the same way.
@davids91 Can you please describe the difference between the two function calls:
func _input(event: InputEvent) -> void:
	var x: Vector2 = Input.get_vector("a", "b", "c", "d", 0.1)
	var y: Vector2 = event.get_vector("a", "b", "c", "d", 0.1)

Or would you expect, that they behave in the same way, so that x and `y´ are always the same?

My expectation is that they behave the same way, but I do not base that on any system knowledge, only based onthe names of the functions.
Actually I'm not sure about the difference based on the implementation, and documentation only mentions Input::get_vector.


[FLINK-2120] Rename AbstractJobVertex to JobVertex

Renamed AbstractJobVertex to JobVertex

My build is green: https://travis-ci.org/mjsax/flink/builds/66925468
IMHO, ready to be merged. It's only a renaming thing.

LGTM


Standardize on nodepool labeling conventions

From @consideRatio in https://github.com/2i2c-org/pilot-hubs/pull/134#discussion_r541023273:

The configuration scheduling.corePods.nodeAffinity.matchNodePurpose=require will make all core pods of the jupyterhub chart have a required node affinity toward the node label hub.jupyter.org/node-purpose=core.
By using hub.jupyter.org/pool-name it seems like there is a predefined meaning of that label and can cause some confusion, it isn't having a predefined meaning right? If it is a label with meaning for the 2i2c.org pilot hubs, I think we should name it like 2i2c.org/pool-name instead.

We should investigate either node-purpose or switch to a different namespace.

We'll3

By using hub.jupyter.org/pool-name it seems like there is a predefined meaning of that label and can cause some confusion, it isn't having a predefined meaning right? If it is a label with meaning for the 2i2c.org pilot hubs, I think we should name it like 2i2c.org/pool-name instead.

The k8s label hub.jupyter.org/pool-name is no longer in use, we are instead referencing the k8s label node.kubernetes.io/instance-type for such purposes I think. We have also stopped using the hub.jupyter.org label prefix for labels we define (#1256).
I'll go for a close here, lets open a new issue if there is some concrete aspect to focus on remaining that I've failed to capture.


Implement objc method swizzling

Hi,
This is a great project - I love your work. I've got a PR to add method swizzling for Objective-C methods. I've also included an example to show one of the reasons this is useful. I want to be able to show the user notifications from a Golang binary. NSNotificationCenter refuses to do this if [[NSBundle mainBundle] bundleIdentifier], which is the case for non-.app apps.
I don't expect this to be merged as-is, it's more a concrete example to get your thoughts. Specifically, TODO_RegisterClassInMap is likely something you wouldn't want. I suppose there are a few options:

(At startup?) Enumerate the list of all classes registered with the runtime using objc_copyClassList and add them all to the classMap.

Register pre-existing classes (and their methods) lazily in MethodForSelector.

Something else entirely.

What are your thoughts?

Oh it would be rad to get notifications working! Interesting situation, too. What if we added a Class method to Object that registers if not already? This way
nsbundle := cocoa.NSBundle_Main().Send("class").(objc.Class)
objc.TODO_RegisterClassInMap(nsbundle)

would become
nsbundle := cocoa.NSBundle_Main().Class()

It would definitely be nice to have that Class method regardless. That solution would work. The only pitfall I can think of is that the side-effect inside what users would assume is a simple accessor method could be surprising. So they might not realise that they have to invoke it this way. But on the other hand, swizzling is such a niche need that it probably doesn't matter.
Want me to make that change? Happy to edit the PR 👍

I don't think it's a big deal. We could also put it in Get/GetClass, I don't think the bookkeeping overhead is a big deal, esp if it only has to happen once per class. This way there isn't a way to get a class that doesn't do it. Your call. 👍

Would love to see this make it in! This represents a big step in unlocking more of the objc runtime to go.

@tmc if you (or @aidansteele) can finish this PR i'd love to merge

Sorry for the delay @progrium - I've pushed that change now. Let me know if it doesn't match what you were expecting.

@aidansteele no worries thank you for following up!


RFC - introduce new resolver package for resolving policy per identity

The current way that policy is generated in Cilium is in need of refactoring: the rules in the policy repository are iterated over many times, in different functions, for both determining whether policy is denied (due to FromRequires and ToRequires), L3-only, and L4 (and L7) policy. This iteration in different stages also has resulted in a bunch of different structures for storing policy-related data, which are tightly coupled with the datapath implementation (in the past, Consumable, and currently, the list of PolicyKeys for BPF PolicyMaps per endpoint, and the L4Filter type). None of these type give a clear view of the policy for a given identity that is synthesized based off of the rules in the policy repository. Furthermore, some of these types have to be translated by their corresponding datapath implementations (for instance, translating the L4Policy object for each endpoint into a cilium.NetworkPolicy for use by Envoy). This plethora of types, and the conventions surrounding them (i.e., what represents an allow-all w.r.t. endpoint selectors, etc.), is quite subtle. As such, it behooves us to change how we parse policy in Cilium to make the code more maintainable and easier to understand.
To address these issues, introduce a new subsystem, whose sole purpose is purely to resolve policy for a given security identity given a mapping of numeric security identity to labels, and a list of rules. This implementation clearly specifies what represents an allow-all at a specific layer (L3, L4, L7), deny-all, etc. This code does two passes over the provided set of rules:

Determining whether policy explicitly denies any identities (due to FromRequires and ToRequires)
Parsing over the rules and seeing whether they apply to the identities which were not denied after the first pass.

The resultant object (cilium.NetworkPolicy) contains a complete view of all policy that applies to the given identity (including L3, L4, and L7), with all relationships specified in terms of numeric security identities instead of endpoint selectors. As such, this object can be used by any datapath implementation to take care of specific tasks (for instance, configuration of the Envoy proxy for HTTP, configuration of the Kafka proxy for Kafka rules, and insertion into PolicyMaps for endpoints for L3/L4 lookups).
This puts all policy resolving logic into one package, and has a single parent function for returning policy for a given identity (ResolveIdentityPolicy).
Things this PR does not do:

Optimize the generated policy. This is coming in a future PR after this is merged.
Check whether there are conflicts at L7 at the same port for the given identity in the generated cilium.NetworkPolicy. This will occur at the optimization layer.
Use of this object in Cilium. The current policy resolving subsystem that is actually used by Cilium has not changed. This is intentional, as to avoid having this PR be enormous, and introduce bugs.

I've done my best to add extensive unit tests to this. Please check to see if there are any gaps that you want covered, as I want to make sure this is as rock-solid as possible :)
Signed-off by: Ian Vernon<EMAIL_ADDRESS>

This change is

test-me-please

test-me-please

test-me-please

@tgraf per your request to rename this from 'resolver' to avoid confusion with DNS, @joestringer and @rlenglet and I decided to change the package pkg/policy/distiller :)

I have a couple of high level remarks/questions after taking a first glance:

Initially I thought this is about replacing the logic in pkg/endpoint/policy.go to decouple it from the endpoint but this seems to be a replacement for mostly pkg/policy/repository.go and pkg/policy/rule.go which already contains code decoupled from the endpoint to calculate the policy for what we call a SearchContext. Is this attempting to replace all of that code that is well covered with tests and proven to work? There is no doubt that it can be optimized to not traverse the list of rules multiple times but does that justify almost a complete rewrite? The main difference seems to be that instead of a search context which is label based, this is requiring an identity which then also translates into labels.
A lot of functionality seems to be missing which makes it difficult to understand the total required scope of this work.

No CIDR
No tracing
No localhost policy

Making the NPDS API be the primary representation for all policy has some serious architectural consequence: As we extend NPDS for non Envoy needs, is Envoy expected to implement all of these APIs?

@tgraf I've realized that I haven't adequately stated my motivations for this package / what the scope of it is here. I've scheduled a table-top review to give more context to a variety of Cilium team members this upcoming week. I will address some of your concerns inline:

Initially I thought this is about replacing the logic in pkg/endpoint/policy.go to decouple it from the endpoint but this seems to be a replacement for mostly pkg/policy/repository.go and pkg/policy/rule.go which already contains code decoupled from the endpoint to calculate the policy for what we call a SearchContext. Is this attempting to replace all of that code that is well covered with tests and proven to work? There is no doubt that it can be optimized to not traverse the list of rules multiple times but does that justify almost a complete rewrite? The main difference seems to be that instead of a search context which is label based, this is requiring an identity which then also translates into labels.

This code is meant to replace that code in pkg/policy/repository.go, and pkg/policy/rule.go, with the goal of creating a unified, generated policy per-identity, which the current subsystem does not do.

A lot of functionality seems to be missing which makes it difficult to understand the total required scope of this work.

No CIDR

This is true for ingress CIDR. For egress CIDR policy, we actually generate labels / identities for CIDRs, which are stored in the identity cache. So, egress CIDR policy resolution is actually included because it is identity-based as part of this PR. I agree that ingress CIDR will have to be dealt with separately until (if) we decide to make it based off of identity. Currently, we do this via resolveL3Policy. I'm fine with keeping that as is for now, as ingress CIDR is somewhat of a special case.

No tracing

Tracing is quite limited right now in its current form (no L7 support, returns once the first rule that allows traffic is hit, etc.), and requires a full iteration over the rules for each call to cilium policy trace. I think that coupling policy resolution with tracing makes things messy, as both resolution and tracing use the same data, but to generate a different representation based off of it (one for a model for use by various datapath subsystems, the other to give information to the user). I'm for decoupling policy resolution from tracing, and instead creating a separate code path for tracing all-together.

No localhost policy

This is out of scope for this current PR; I realize that I have not clearly stated what the purpose of the generated output from the functions in this PR is in relation to, say, an endpoint's policy, which is on me. I wanted to decouple generation of policy based off of rules in the repository, and policy from endpoint configuration / daemon configuration. In other commits (which I intentionally did not push as part of this PR), I take into account localhost configuration, as well as 'world as host' configuration.

Making the NPDS API be the primary representation for all policy has some serious architectural consequence: As we extend NPDS for non Envoy needs, is Envoy expected to implement all of these APIs?

I'm unsure what you mean by "all of these APIs"; NPDS is the API that is consumed by Envoy. I utilized NPDS because I felt it addressed the need to have a unified policy per-identity, which encodes all of the relations across L3, L4, and L7. The model that we pass to any subsystem can be utilized as that subsystem sees fit; for instance, we won't' take into account L7Rules when generating the PolicyKeys for the PolicyMap. The only thing that the generated policy should do, is uphold the guarantees that are outlined in the definitions of NPDS. Envoy can consume these as it sees fit, and for instance, ignore L3-only policy.
I am happy to follow-up on these concerns in the proposed tabletop review.

Closing this PR, as this was meant to be an RFC of the overarching proposal which will be done piecemeal in #4722 .


Add Example Usage

what

Add example invocation

why

We need this so we can soon enable automated continuous integration testing of module

will be addressed in the first commit


feat!: upgrade to 0.8

What I did

fixes: #
How I did it
How to verify it
Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

struggling - as i am getting passing tests locally, and this plugin is holding up a lot


Vagrant gui

Fixes #189
Allow usage of a local X server installed on the Vagrant virtual machine, instead of connecting to an X server on the host. This should be significantly faster because the (one or two) TCP links are replaced by a local UNIX socket (X is normally used this way).
Should make interactive apps (and visualizations) much faster, when using this mode.

This works! Now to make it pretty... but should be showable for SIGMOD.

Great! We should do a release before SIGMOD.
On Fri, Jun 24, 2016 at 5:59 PM, Remi Rampin<EMAIL_ADDRESS>wrote:

This works! Now to make it pretty... but should be showable for SIGMOD.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ViDA-NYU/reprozip/pull/191#issuecomment-228472387,
or mute the thread
https://github.com/notifications/unsubscribe/ABYHQMMM-eSFT2VuKOUAbxvaw4UeJeKjks5qPFMvgaJpZM4I-Ijy
.

--
Fernando Chirigati
Research Assistant and Doctoral Candidate at NYU
http://bigdata.poly.edu/~fchirigati/ http://vgc.poly.edu/~fchirigati/

New image remram/debian-8-amd64-x correctly resizes. It also has upstart instead of systemd, so we might want to use it as base for the reprozip-examples VM?


enketo: incorporate enketo into the docker setup.

According to https://enketo.github.io/enketo-express/tutorial-10-configure.html, the support email is important to set.
https://github.com/enketo/enketo-express/search?q=supportEmail&unscoped_q=supportEmail is how it's used. I'm not sure what the right approach here is. Maybe we explicitly set it to an empty string?

i can reuse the letsencrypt contact email?

On Jun 22, 2020, at 08:38, Yaw Anokwa<EMAIL_ADDRESS>wrote:

According to https://enketo.github.io/enketo-express/tutorial-10-configure.html, the support email is important to set.
https://github.com/enketo/enketo-express/search?q=supportEmail&unscoped_q=supportEmail is how it's used. I'm not sure what the right approach here is. Maybe we explicitly set it to an empty string?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Martijn says, "I think the survey administrator is the one to use." @lognaturel agrees and thinks this is something that should be configurable at the project level (for Enketo and Collect).
For now, the LetsEncrypt email is sufficient, but we should plan on having configurable at the project level.

Martijn says, "I think the survey administrator is the one to use." @lognaturel agrees and thinks this is something that should be configurable at the project level (for Enketo and Collect).
For now, the LetsEncrypt email is sufficient, but we should plan on having configurable at the project level.

okay but that would be an enketo change then, no? if it's configured on a server-by-server basis?

You are right. If it's project by project, there would need to be an Enketo change to have a support email.


yarn can't add some package

I'm submitting a
dependencies:
"tui-editor": "^1.4.10",
error An unexpected error occurred: "https://raw.githubusercontent.com/seonim-ryu/Squire/fd40b4e3020845825701e9689f190bab3f4775d4/package.json: connect ECONNREFUSED <IP_ADDRESS>:443".

try the latest code?

try the latest code?

i deleted yarn.lock and than run yarn install, it's still error.
the error message:
yarn install v1.22.5
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning element-ui > async-validator > babel-runtime ><EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
warning jsonlint ><EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
warning<EMAIL_ADDRESS>Object.assign was not transformed during the build of sortablejs, so it won't work in browsers where this does not exist (for example IE11). Please downgrade your version to 1.10.2 to keep supporting <=IE11 or upgrade to >2.0 where IE will no longer be supported.
error An unexpected error occurred: "https://raw.githubusercontent.com/seonim-ryu/Squire/fd40b4e3020845825701e9689f190bab3f4775d4/package.json: connect ECONNREFUSED <IP_ADDRESS>:443".
info If you think this is a bug, please open a bug report with the information provided in "/Users/clark/Documents/company/program/PC/vue-typescript-admin-template/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.


stac_catalog and others

Hi,
I have installed intake version 0.6.4, but when I run this line, it did not show what I should see, as you can check it here.
# You should see 'stac_catalog, stac_collection, stac_item, and stac_item_collection' if intake-stac is installed
list(intake.registry)
['yaml_file_cat', 'yaml_files_cat', 'alias', 'catalog', 'csv', 'intake_remote', 'ndzarr', 'numpy', 'textfiles', 'zarr_cat']
I need to use open_stac_catalog but it does not exist, the code generate this couple of errors:
cat = intake.open_stac_catalog(url)
KeyError: 'open_stac_catalog'
AttributeError: open_stac_catalog
Any advice to fix it?
Thanks in advance, JL

This still seems to be an issue in 0.6.5
@jaimebayes did you have any luck opening a stac catalog with intake?
The docs suggest this should be possible: https://intake-stac.readthedocs.io/en/latest/tutorial.html


Call for feature requests

Don't hesitate to add your feature requests as new issues.

I used gjukebox for many many years, and it's a great jukebox that yours could take features from.
When we deployed gjukebox, we had three requirements:

Good random play, if noone put anything in the queue, gjukebox's claim to fame
Remote volume control
remote pause, play, ff, rewind

HTH

Hey jfmatth,
thanks a lot for your proposals.

Democratic jukebox already tries to play music according to the logged in users preferences once the queue is empty. See this patch for details. Please propose improvements to the current behavior if it doesn't satisfy your needs.
Volume controls depends on the selected playback method. Unfortunately there is no way to control the volume of a shoutcast stream.
Same goes for pause and play. I plan to release an update that allows users to skip the current song. Maybe I'll find the time to work on it during christmas.

Greetings from the cold and stormy germany.
loci

sorry to mention stuff it may already do, i haven't taken the time to install and actually try it, although I'm intrgued that you've used django (my favorite framework) to build it.
There were some esoteric features of gjukebox we never used, but might be worth looking at, check it out if you're interested, I think it's pretty dead these days,but the website is still up gjukebox.sourceforge.com
I'll install yours pretty soon,
thanks for the effort and keep it up.
Greetings from Palm Springs, CA USA, cold and gloomy today.


Feature/character card UI

Describe your changes
Added a character inventory on the main page where you can scroll through your characters. The scrolling uses infinite scrolling that was already present in the project, and takes up 50% of the view-height to prevent cluttering the view.
The information displayed for the character:

key (name)
eilodon
level
break effect
crit rate
crit dmg
def
effect hit rate
effect res
energy regen
heal boost
hp
speed

The content is displayed inside an accordion. Basic typografy from MUI is used in displaying the stats.
No further styling is applied.
Issue or discord link

Resolves https://github.com/frzyc/genshin-optimizer/issues/1550

Testing/validation

Checklist before requesting a review (leave this PR as draft if any part of this list is not done.)

[x] I have commented my code in hard-to understand areas.
[x] I have made corresponding changes to README or wiki.
[x] For front-end changes, I have updated the corresponding English translations.
[x] I have run yarn run mini-ci locally to validate format and lint.
[x] If I have added a new library or app, I have updated the deployment scripts to ignore changes as needed

Please note that the linter for mini-ci does not support the typescript version that the project uses.

If you want to link your PR to the issue, edit your description to:
Issue or discord link
- Resolves #1550

Finished the updates request. The names of the stats might be off since I don't play the game, so please fix at your leisure.

@JelteDirks looks good, yes, you will need to merge. Your CharacterInventory will need to go in PageHome.tsx instead of App.tsx after the merge

Merged origin master into this feature. I still have the accordion since it was request, but it is on PageHome now.


Add similarity calculation for all pairs of vectors in the unit test …

…for the circular function
As mentioned in https://github.com/hyperdimensional-computing/torchhd/issues/108#issuecomment-2413286496 the circular test just test the similarity between first vector and other vectors while we have to test the similarity between all pairs of vectors
Description
Added a loop wrapping the previous code and rolling the list of vectors in the end of the loop.
Checklist

[ ] I added/updated documentation for the changes.
[ ] I have thoroughly tested the changes.

Thank you @milad2073 for making the unit tests more robust!


PFF Variable Lookup

Source data: 2 Excel files sent by EM: 2006 - 2010 and 2016 - 2020
Taking the base variable from the input excel sheet, include a new pff variable column in the target schema according to the field mappings present in https://github.com/NYCPlanning/db-factfinder/tree/221-Aug-2022-Build/factfinder/data/acs.

Addressed by https://github.com/NYCPlanning/db-factfinder/pull/231


Provide libraries

this project could/should provide libraries around the commands' functionalities so people can write additional tooling.

On Thu, Sep 15, 2016 at 07:56:49AM -0700, Antonio Murdaca wrote:

this project could/should provide libraries around the commands'
functionalities so people can write additional tooling.

Work in that direction in opencontainers/image-spec#159 ;).  Should I
re-open that over here?

Work in that direction in opencontainers/image-spec#159 ;).  Should I
re-open that over here?

we need to slightly refactor the code at least according to https://github.com/opencontainers/image-spec/pull/234#issuecomment-246798847 before taking into consideration https://github.com/opencontainers/image-spec/pull/159 (there has been no consensus in there also) IMO

On Thu, Sep 15, 2016 at 08:31:38AM -0700, Antonio Murdaca wrote:

Work in that direction in opencontainers/image-spec#159 ;).  Should I
re-open that over here?

we need to slightly refactor the code at least according to
https://github.com/opencontainers/image-spec/pull/234#issuecomment-246798847
…

I already have a callback-based ref walker [1,2] (following a @stevvooe
suggestion 3).

I think libraries with fairly stable APIs would be great!
Unpacking can be error-prone, signature validation (once it becomes part of the spec) is not code you want to write yourself and anything that has to do with CAS would be good to share. For all these reasons I would love OCI to expose this functionality through reusable and configurable Go APIs in addition to the CLIs.

@runcom Go doesn't have "libraries" - it has packages. ;)
Indeed, the goal is to provide rich APIs, but I don't think we are even close to a point where we can stabilize an API. The current code is fine for purpose, but I don't think the interface is flexible enough to stand the test of time.

On Thu, Sep 15, 2016 at 12:33:24PM -0700, Stephen Day wrote:

Indeed, the goal is to provide rich APIs, but I don't think we are
even close to a point where we can stabilize an API. The current
code is fine for purpose, but I don't think the interface is
flexible enough to stand the test of time.

Possibly true, but you have to start somewhere ;).

Agree with @wking, starting somewhere and defining a versioned API shouldn't hurt anyone. We can't just wait because we're not at the point to fully stabilize (other projects broke backward compatibility, libraries break compatibility at almost each major release..).

@runcom Go doesn't have "libraries" - it has packages. ;)

Yet are libraries to me, but whatever

is there progress on this? someone want to own this?

umoci's interfaces are already split up into packages (and I'm currently doing more cleanups in this area in preparation for the merge of the libraries into this project).

I can dip my toe in, but probably not until late next week; not sure what
the timeline is like.
On Thu, Mar 9, 2017 at 3:20 PM, Aleksa Sarai<EMAIL_ADDRESS>wrote:

umoci's interfaces are already split up into packages (and I'm currently
doing more cleanups in this area in preparation for the merge of the
libraries into this project).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opencontainers/image-tools/issues/2#issuecomment-285516377,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABJ6xL27Gezb1sdhYZweMRH7uu5z3VBks5rkIkvgaJpZM4J9-AM
.

I'm currently planning on implementing v1.0.0-rc5 support in umoci's libraries before merging them into this project. Currently that requires some improvements to oci/cas (which would be the first thing I'd want to move here). oci/casext is good as-is (though I'd like to add more tests). oci/config/* is fairly okay though I want to improve some of the interfaces. oci/{diff,layer} needs some work to make it more useful as a library.
So there are the current things I wouldn't mind getting a hand with (though the v1.0.0-rc5 support is something I'm going to tackle by myself).

Looking forward to seeing the umoci stuff merging in.


zookeeper: fix panic

The zookeeper SD constructor returned nil with no error when it couldn't couldn't connect to the server(s). Eventually it triggered a panic in the Run() method. The issue was already present in previous releases of Prometheus.
Closes #4668

:+1:


CoseError doesn't seem to implement std::error::Error.

The CoseError doesn't seem to implement the standard Error trait, and it makes this error hard to manage when building other types of errors with other tools, such as thiserror, or anyhow. Even a simple impl line for this should be sufficient:
impl std::error::Error for CoseError{}

but this has to be done inside of the coset crate.

Try enabling the std feature:
https://github.com/google/coset/blob/main/src/common/mod.rs#L90-L91

(Reopening as a reminder to update the README to mention the std feature)

Another option would be to make std the default, and could be explicitly disabled when needed. This seems to be how most crates handle this.

Making std the default would be a breaking change and necessitate a major version bump, so non-default was better.   Hopefully core::error::Error will stabilise and we can drop the need for the feature in future.
README updated, so closing.


Can't enter any numbers

When setting the masked field to this
textBox.Attributes.Add("data-inputmask", $"'alias': 'integer', {(MultiValue ? "'mask': '000000000\n000000000\n000000000\n000000000\n000000000\n000000000\n000000000\n000000000\n000000000\n000000000\n', " : string.Empty)}'min': {int.MinValue}, 'max': {int.MaxValue}");
I get this,

But when I try to enter any numbers it won't let me, any tips on what I am doing wrong?

I decided to just generate more textboxes instead of a text area so problem solved another way.


Merge editor: long branch names should be truncated

Testing #150389

Create  merge conflict in a branch with a long name
Open the merge editor

bug
The long branch name wraps to the next line and seems to break the layout slightly:

Instead I think we should truncate the branch name

Yes closing as fixed since this was opened

I'm still seeing the same issue on insiders.

So weird...

I can reproduce. But only when the long name is in input2 (RHS)


Create a prototype client

Create a client that uses the HttpUrlConnection class.
Because it is an early prototype it is not yet expected to use PATCH methods or implement asynchronous communication.
This client will be expanded on in future sprints.

This was completed for the Week 8 report. Not committed, as it'll just be removed again.


[Feature] Party entity/sheet

Purpose: define a party as a set of player characters and apply effects or manage their inventory and currency in a unified way from a new character sheet. Similar to the implementation of Groups in DND5E 2.1.x.
Functionality

[ ] Drag and Drop Player Characters to a Party sheet to manage what characters are part of the Party.
[ ] Party Token that can be put on wilderness or city maps to move all players together. Shared vision among all included characters in the Party when put on such maps, instead multiple individual character tokens.
[ ] Shared Effects that apply RE to all members of the party. Like Scout Exploration that gives each member of the party +1 to initiative.
[ ] Shared Currency that is sum of all the money the party has. Allows the DM to group-give and group-take money, distributed equally between all members (or other methods, if this is further advanced) to no longer struggle with asking players to add money, or to spread expenses for one purchase between multiple players adding overhead discussions to the game.
[ ] Shared Inventory for quest items, etc. Shared Inventory is in the Party sheet, but also inside every player's sheet as a special container that doesn't count against bulk. This can represent "rule of cool" simplified quest item storage, or party's horse cart they travel with, etc.

This has been a thing we've been talking about internally for a long time (in fact, even before DND5e got it, I can almost assume atro heard us talking about it and liked the idea) but we haven't been able to jump to it because of a myriad of other projects.

I am very happy to hear that it is considered. I am definitely aware this is an epic and shouldn't expect it anytime soon. I wanted to just compile all potential uses that are usable for my games.

From #6611:

If possible, it would be nice to have an option to toggle on for the crafting section of the player sheet for characters using infused reagents where they can dictate temporary items such as alchemical items that are to be sent to either the party sheet or if they have the correct permissions, directly to player sheets. This would make the life of alchemists out there infinitely easier. Just a thought!


Handle NodeJS stacktraces

Your test has the : in c:/, which causes an exception when resolving the line number from the source string. I remove that : in the nodejs probe so it ends up as /c/path instead of file:///c:/path

I took that stack trace off StackOverflow to use a real example. I looked around for other examples but they all looked the same. If you have a legit stack trace that this won't work for we can expand the logic. I don't think you should manipulate the stack trace to make it easier to parse. I'd like this logic to work on the original data so it can be used elsewhere.
Please give provide example stack traces that don't work and I'll add tests.

I think calling LiveStackTraceElement#sourceAsLineNumber on that stack trace should throw an exception, since it takes everything after the first :

Ah, I see what you mean. I'll expand the tests, thanks.


Gems that require Ruby 3.0+ are giving updates when on Ruby 2.7.8 that don't run or work

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
bundler
Package manager version
2.4.12
Language version
2.7.8
Manifest location and content before the Dependabot update
/Gemfile
dependabot.yml content
package-ecosystem: "bundler"
    directory: "/"
    schedule:
      interval: "daily"
    versioning-strategy: increase
    open-pull-requests-limit: 10
    insecure-external-code-execution: deny
    commit-message:
      prefix: "[bundler] "
    allow:
      - dependency-type: "all"

Updated dependency
plaid, for example ---> from 16.0.0 to anything beyond
same as selenium-webdriver (4.9.0) to 4.9.1 ( see https://github.com/SeleniumHQ/selenium/commit/cd3216e68dbc4ae61c0efae6e2969d5e18776bdb)
What you expected to see, versus what you actually saw
Dependabot should either:

Not propose a gem update that conflicts with ruby version (and perhaps a config for which ruby version to use, or read .ruby-version)
have a separate error message in the Dependabot.yml to suggest ruby upgrade

Note: I am aware Ruby 2.7.8 is EOL (or soon to be), but dependabot can handle this better, in my opinion
Native package manager behavior
it doesn't suggest an update is available when running bundler update
Images of the diff or a link to the PR, issue, or logs
n/a
Smallest manifest that reproduces the issue
.ruby_version of 2.7.8 (or any other way to set based on your environment.
A Gemfile with
gem "plaid",          "~> 16.0.0"
gem "selenium-webdriver", "~> 4.9.0"

@broksonic21 Thanks for the report. I just deployed a potential fix for this. If you now comment @dependabot recreate on those unexpected PRs, I think Dependbaot should close them with a message like "Looks like <dependency> is no longer updatable, so this is no longer needed."


python311Packages.omnikinverter: 0.9.1 -> 1.0.0

Diff: https://github.com/klaasnicolaas/python-omnikinverter/compare/refs/tags/v0.9.1...v1.0.0
Changelog: https://github.com/klaasnicolaas/python-omnikinverter/releases/tag/v1.0.0
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 279042 run on aarch64-darwin 1

2 packages built:

python311Packages.omnikinverter
python311Packages.omnikinverter.dist


host.json settings when updating to version 5.x+ of service bus extensions

Information on updating service bus settings when updating to version of 5.x+ of service bus extensions are not clear.
I don't understand this part - https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus#additional-settings-for-version-5x
It says "Additional settings" yet some of them seem to override settings mentioned on the same page, above.
My question is, when updating to version 5.x+ should I use settings from this section or should I merge settings from section above (https://docs.microsoft.com/en-us/azure/azure-functions/functions-bindings-service-bus#hostjson-settings) with those from version 5?
Let's take maxAutoLockRenewalDuration. It's mentioned that this takes place of maxAutoRenewDuration that was previously defined in messageHandlerOptions section. So, is this whole section no longer to be used?
Then again, we have maxConcurrentSessions which also seems to override same setting in sessionHandlerOptions section but documentation doesn't mention it. So at least these docs should be updated to make it clearer.

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

ID: 0440205f-adcc-0fc5-3adb-db4dbe1d1292
Version Independent ID: 14ad1300-590c-8102-6887-366078e1882a
Content: Azure Service Bus bindings for Azure Functions
Content Source: articles/azure-functions/functions-bindings-service-bus.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

Hello @PiotrPerak - Thank you for your feedback! We will review and update as appropriate.

+1 to this, current documentation on SB trigger is really confusing

@PiotrPerak @flareair This doc updated and the issues shared in this feedback were addressed as part of: https://github.com/MicrosoftDocs/azure-docs/commit/75d6c9a162aaec93634a4955243e79f8c0d0e2ca
Thank you for your feedback and help in driving improvements towards MS Docs!
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Swap DNS to PaaS-backed infrastructure

This will move away from our self-managed AWS infrastructure to PaaS.
Things to double-check before deploying: Terraform shows that this will be resource modifications. We need to double check that this isn't modelled as a delete/create so that we won't end up with any records that are unresolvable for a period of time.

I had a quick look at this and it appears that the DNS changes happen as either upserts or transactional changes to Route53 which should mean that we see zero downtime when swapping over.


User removal support

Description
[Describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves]
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable

@flaccid yeah I think it does. But I'm looking at it again, and i might give it a tidy up, removing the chef solo stuff in it.

Could you please rename data bag attribute to be like last PR merged ? https://github.com/sous-chefs/openvpn/commit/1495ee2c4276b462baa00ac578edbaa0c8d3ba61
Thanks.

if that's the case the data_bag shouldn't be an attribute that can be changed (if changing it breaks it)

Hard for me to find review time currently, but some real nice easy steps in the readme on how to use this functionality would certainly help a chef solo only user like myself..

@flaccid if it's a new version of Chef Solo/Zero, it'll have "search" built in. But tbh we shouldn't be using Search directly in cookbooks, otherwise it ties users into a particular way of using the cookbook rather than being flexible with the implementation.

@damacus seems like this could be rebased on top of v3.0.0 to carry it forward, no?

Oh yeah totally. I'm going to rebranch from master rather than rebase.


when i install UItweaks 4.0.0 in BS 1.37.1, it make my game freeze

detail in log
2<IP_ADDRESS>.48.25.log

and config file
UITweaks.json

Hello!
Thank you for submitting this issue. This is a known bug and is currently being worked on. The current workaround is to enable "Advanced HUD" inside of the player settings page.
UITweaks v4.0.1 will fix this issue and I will link it back here upon release.

UITweaks v4.0.1 has fixed this issue. 👍


docs: docker-and-private-modules

@MylesBorins the previous PRs have pivoted too much and their goal was not stated clearly. This is my fault so this is a final PR that will attempt to clearly and shorty state its purpose and what problems it's trying to fix.
The reason behind this PR is to securely download private npm packages when building a docker image and address the pitfalls with the current set-up in the documentation which are also explained in this article.
Current set-up will save your npm token in the final docker image. This PR solves that problem by showing you how to use the --secret flag with the docker build command and not have your npm token saved in your final docker image.

@MylesBorins I remember you've mentioned that this Docker image might not work on CI.
This works with GitHub Actions:
- name: Build and Push Docker image
        run: |
          echo "//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}" > .npmrc
          docker buildx build . -f Dockerfile -t ${{ secrets.DOCKER_USERNAME }}/${{ secrets.DOCKER_REPOSITORY }} --secret id=npmrc,src=.npmrc --push

@MylesBorins @monishcm I've tried to address the previous concerns but maybe I could improve this PR in any way?

Thanks for all the hard work and patience on seeing this through!


Cannot access templateVars.options in templates

Version
v2.7.0
Reproduction link
https://codesandbox.io/s/946pw7j9k4
Steps to reproduce
a) create a module that injects a plugin
b) have plugin use lodash syntax to fill in vars from templateVars
c) notice that even though templateVars.options exists, it's { } in the written template
The problems seems to be with https://github.com/nuxt/nuxt.js/blob/dev/packages/builder/src/builder.js#L515 which merges options with the template, even if options isn't passed.
What is expected ?
My assumption is that anything you see in templateVars should be accessible in a template!
What is actually happening?
options prop is being reset
Additional comments?
a) could maybe see if options is being passed to the template, then let it override it (which still is kind of crummy)
b) could move either options or templateVars.options into a new prop in templateVars so it's always accessible.

This bug report is available on Nuxt community (#c9215)

Actually, I am wondering why do we have templateVars.options initialized with Nuxt options.
An idea @clarkdo?

@Atinux I'm not sure the initial situation, but I suppose that user may need sth like options.dev or other options to do some special process in templates.
@hecktarzuli Thanks for the reporting, I'll propose a fix.

In our case, our system generates 6 websites, and so we have an advanced config system and need config data in our plugins so we can build them using the right settings.
We are using this for now until this patch is in place.

@hecktarzuli As @pi0 pointed, merge options into template may be a breaking change, so I added nuxtOptions as nuxt options in template and keep options as template.options, do this make sense for you ?

Sounds good to me.  That's probably the safest course of action.

@hecktarzuli There are some other libraries are using tempalte.options like serializing template.options, if we merge options, the serialized object will be huge and contain all nuxt.options.

@hecktarzuli Internal modules that really need can leverage it. Indeed we can document it in the future it is a general use case. Not documenting is more because to not encourage using it over explicit templateFile.options.


Unable to locate file

Hi, I keep receiving the following error on line 250 and am unsure on how to resolve it as I cannot locate the "historical_prior_simulations.rds" file in the data folder.
Error:
In gzfile(file, "rb") :
cannot open compressed file 'data/historical_prior_simulations.rds', probable reason 'No such file or directory'
Thank you!

Not in the code anymore. Shouldn't need it.


Seed layers only after application.properties is loaded

NetflixOSS » archaius » archaius-pull-requests #105 SUCCESS
This pull request looks good

archaius-pull-requests #274 SUCCESS
This pull request looks good


Import markdown files?

I'm trying to move from my markdown files to Meemo and try to import my text files using "Import" feature and it doesn't work. Isn't is supposed to import *.md and *.txt files?

As of now, the import only works with the output from the export feature. That "format" is a tarball, which also includes attached images. The content itself is imported from a json file inside that tarball. It is possible to write other importer methods, I will have a look at that.

It would be great to have an option to select a bunch of *.md or *.txt files and get them imported with one click.

Thanks for the project, BTW!


Upgrade terraform-provider-azurerm to v3.77.0

This PR was generated via $ upgrade-provider pulumi/pulumi-azure.

Upgrading terraform-provider-azurerm from 3.75.0  to 3.77.0.
Fixes #1391
Fixes #1386
Upgrading pulumi-terraform-bridge from v3.61.0 to v3.62.0.

/release minor


bytes: bytes.Clone(), using copy is faster than append.

// default
func clone(b []byte) []byte {
	if b == nil {
		return nil
	}
	return append([]byte{}, b...)
}

// fast
func cloneV2(b []byte) []byte {
	if b == nil {
		return nil
	}
	nb := make([]byte, len(b))
	copy(nb, b)
	return nb
}

// normal
func cloneV3(b []byte) []byte {
	if b == nil {
		return nil
	}
	nb := make([]byte, 0, len(b))
	return append(nb, b...)
}

var toTestB = []byte("JFIOSJFOISJFOIAJFKSDFSDlkadjfskfdskdfj31231111111111111111111111111111111111111111111")

func Benchmark_clone(b *testing.B) {
	for i := 0; i < b.N; i++ {
		clone(toTestB)
	}
}

func Benchmark_cloneV2(b *testing.B) {
	for i := 0; i < b.N; i++ {
		cloneV2(toTestB)
	}
}

func Benchmark_cloneV3(b *testing.B) {
	for i := 0; i < b.N; i++ {
		cloneV3(toTestB)
	}
}

Benchmark_clone
Benchmark_clone-6   	35159740	        74.59 ns/op	      96 B/op	       1 allocs/op
Benchmark_cloneV2
Benchmark_cloneV2-6   	43229692	        59.33 ns/op	      96 B/op	       1 allocs/op
Benchmark_cloneV3
Benchmark_cloneV3-6   	39171712	        71.48 ns/op	      96 B/op	       1 allocs/op

CC @icholy, @martisch, @ianlancetaylor.

The title seems to suggest that bytes should use copy rather than append. Perhaps we can view this instead as figuring out why append is slower than copy in this case and optimize that instead?

"make+copy" will also find the smallest allocation size class. So the actual reason why "append" is slower is it will zero additional space.
Now the "make+copy" optimization has many restrictions. Calling make with 3 arguments will not trigger the optimization.

My idea is that since the internal implementation of Clone(), uses append, it should be optimized as much as possible, because this function will be called a lot.


F1 continously pressed

Hi all.
I am using Asus C201 + Crouton + Trusty + Xfce4 mainly to write and compile LaTeX.
My favourite editor is TeXStudio, whose "compile+view" keybinding is F1.
No problem, with Search+← one gets F1.
The problem is that this F1 doesn't stop.
With xev one can see it really easily, it is like F1 stays pressed.
To "unpress" it, it is enough to re-press it.
Unfortunately, in the meanwhile, one has launched like 100 compilations of the same TeX file, which is pretty annoying.
Is it a known issue? What else can I provide to debug the problem?

No idea. I hope this is not an issue anymore.


feat: update from upstream

feat: update from upstream

Sorry, I made a mistake.Please close this PR.


RuntimeError: Problem in scipy.optimize.least_squares for targetid XX

There are just 5 crashes in Iron all with a scipy.optimize.least_squares runtime error. Investigate and fix.
fastspec /global/cfs/cdirs/desi/spectro/redux/iron/healpix/main/dark/66/6642/redrock-main-dark-6642.fits --targetids<PHONE_NUMBER>0608311
fastspec /global/cfs/cdirs/desi/spectro/redux/iron/healpix/main/dark/267/26731/redrock-main-dark-26731.fits --targetids<PHONE_NUMBER>6226836
fastspec /global/cfs/cdirs/desi/spectro/redux/iron/healpix/main/dark/63/6383/redrock-main-dark-6383.fits --targetids<PHONE_NUMBER>5855316
fastspec /global/cfs/cdirs/desi/spectro/redux/iron/healpix/main/dark/218/21848/redrock-main-dark-21848.fits --targetids<PHONE_NUMBER>8704776
fastspec /global/cfs/cdirs/desi/spectro/redux/iron/healpix/main/dark/270/27054/redrock-main-dark-27054.fits --targetids<PHONE_NUMBER>4029314

The first four crashes were the same underlying issue: high-redshift targets with a masked z-band camera, so that not even Lyman-alpha was in the wavelength range. #104 fixes this problem of not having any emission lines to optimize, during fitting and also when generating the QA plot.
The last crash<PHONE_NUMBER>4029314) was a run-of-the-mill target but because of a somewhat odd spectrum, the lower bound on two of the Balmer emission lines ended up being zero and equal to the initial value, which least_squares does not like / allow. The fix was straightforward and implemented in #104.


Error 404 when deleting a user which does not exist

Describe the bug
If you have a project_user in your TF state which does not exist in Artifactory anymore, the apply fails because of a 404 error. The exact error is:
Error:
404 DELETE https://host/access/api/v1/projects/hcpo/users/myuser
{
"errors" : [ {
"code" : "NOT_FOUND",
"message" : "Could not find user: `myuser`"
} ]
}

Requirements for and issue

[x] A fully functioning terraform snippet that can be copy&pasted (no outside files or ENV vars unless that's part of the issue)

resource "project" "myproject" {
  key = "myproj"
  display_name = "My Project"
  description  = "My Project"
  admin_privileges {
    manage_members   = true
    manage_resources = true
    index_resources  = true
  }
  max_storage_in_gibibytes   = 10
  block_deployments_on_limit = false
  email_notification         = true
}

resource "project_user" "myuser" {
  project_key = "myproj"
  name        = "myuser"
  roles       = ["Viewer"]
  ignore_missing_user = true
}

[x] Your version of artifactory (you can curl it at $host/artifactory/api/system/version

7.99.2

[x] Your version of terraform

1.5.6
Expected behavior
The delete operation should be considered successful in this case. If the user doen't exist (anymore), the operation can be considered a success.
Additional context
In our case we created the project_user really with ignore_missing_user = true and the user never existed, and now we want to remove him fully. But I assume this problem can also happen if somebody manually removes the user in Artifactory and then trying to update terraform afterwards.
We have seen another issue that the "refreshing state" might have some problems aorund project_user inconsistencies. I might file anoter bug report for that but need to narrow things down first. I thoughts its worth mentioning.

seems we were on a very old TF provider version. On code I saw that the scenario should be covered. I updated the provider on our side. If the problem reoccures I might reopen this issue.
Sorry for the noise.


Ontop Extract-DB-Metadata Fails for oracle.jdbc.driver.OracleDriver

Description
Extracting DB Metadata using OntopExtractDBMetadata from the command-line results in an error/failure using the oracle.jdbc.driver.OracleDriver.
Steps to Reproduce

Start Docker Oracle XE 21.3.0
docker run --rm --name ontop-oracle -p 1521:1521 -e "ORACLE_PWD=Rdb2RdfTest" container-registry.oracle.com/database/express:21.3.0-xe
Create Rdb2RdfTest User/Schema in Oracle in the PDB
Configure database connection properties:

jdbc.driver=oracle.jdbc.driver.OracleDriver
jdbc.url=jdbc:oracle:thin:@//localhost:1521/XEPDB1
jdbc.user=Rdb2RdfTest
jdbc.password=Rdb2RdfTest

Run ontop-cli:
Ontop extract-db-metadata -p _test/db.properties -o _test/db-metadata.txt

Expected behavior: [What you expect to see]
Produce a db-metadata.txt database metadata file for the Rdb2RdfTest Oracle schema.
Actual behavior: [What actually happens]
Syserr Message:
Cannot find relation "CTXSYS"."SYS_IOT_OVER_64708" (available choices: [ ...(every Oracle Schema/Table)... ]
Reproduces how often: [Does it happen every time?]
Every time.
Versions
Ontop 4.2.1 (JARs from Maven Central)
Additional Information
Workaround 1: Use oracle.jdbc.OracleDriver
Ontop's default sql-settings.properties also supports use of the oracle.jdbc.OracleDriver. Using this driver resolves the issue.
jdbc.driver=oracle.jdbc.OracleDriver
jdbc.url=jdbc:oracle:thin:@//localhost:1521/XEPDB1
jdbc.user=Rdb2RdfTest
jdbc.password=Rdb2RdfTest

Workaround 2: Add correct setting in user/database properties:
jdbc.driver=oracle.jdbc.driver.OracleDriver
jdbc.url=jdbc:oracle:thin:@//localhost:1521/XEPDB1
jdbc.user=Rdb2RdfTest
jdbc.password=Rdb2RdfTest
oracle.jdbc.driver.OracleDriver-metadataProvider=it.unibz.inf.ontop.dbschema.impl.OracleDBMetadataProvider

Fix - change sql-settings.properties
4.2.1:   oracle.jdbc.Driver.OracleDriver-metadataProvider = it.unibz.inf.ontop.dbschema.impl.OracleDBMetadataProvider
FIXED: oracle.jdbc.driver.OracleDriver-metadataProvider = it.unibz.inf.ontop.dbschema.impl.OracleDBMetadataProvider
#556 Fixes this issue

Many thanks @thomasjtaylor !
I also appreciated you provided a complete example to reproduce the issue.
Best,
Benjamin


Antrea native secondary network feature e2e test framework.

Signed-off-by: Arunkumar Velayutham<EMAIL_ADDRESS>

@jianjuns yes, the 2nd commit was a mistake during rebase and move my local repo to a different workspace. I will get it address. please review the other commit on this PR.

@arunvelayutham : could you check these two comments from @antoninbas ?
https://github.com/antrea-io/antrea/pull/4252#discussion_r1008398624
https://github.com/antrea-io/antrea/pull/4252#discussion_r1008394693

@jianjuns @antoninbas addressed the pending comments as well and updated the PR couple of days back. Please review further.

@arunvelayutham : please fix the test errors (could you check the failed tests after an update?):

Error: test/e2e/connectivity_test.go:74:61: undefined: podInfo
Error: test/e2e/connectivity_test.go:95:60: undefined: podInfo
Error: test/e2e/connectivity_test.go:191:98: undefined: podInfo
Error: test/e2e/antreaipam_test.go:254:21: undefined: podInfo
Error: test/e2e/antreaipam_test.go:260:30: undefined: podInfo
Error: test/e2e/antreaipam_test.go:280:17: undefined: podInfo
Error: test/e2e/antreaipam_test.go:344:87: podIPs.ipv4 undefined (type *PodIPs has no field or method ipv4)
Error: test/e2e/antreapolicy_test.go:2319:15: server0IP.ipv4 undefined (type *PodIPs has no field or method ipv4)
Error: test/e2e/antreapolicy_test.go:2325:15: server1IP.ipv4 undefined (type *PodIPs has no field or method ipv4)
Error: test/e2e/antreapolicy_test.go:2335:15: server0IP.ipv6 undefined (type *PodIPs has no field or method ipv6)
Error: test/e2e/antreapolicy_test.go:2335:15: too many errors

/test-all

/test-all

@arunvelayutham : there are still unresolved conflicts. For example: https://github.com/antrea-io/antrea/pull/4252/files#diff-324aca6894566ddefcf73b4ec0cd7a70a4555749e4cce64fa56969c5181ad892R623

/test-all

/test-ipv6-e2e
/test-all

/test-ipv6-e2e
/test-all

/test-ipv6-e2e

/test-ipv6-e2e


add website

Website (if applicable): https://foreverliketh.is/
This PR is:

[x] Adding a new domain

[x] The domain is in the correct alphabetical order
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ page, particularly the red section about inappropriate content, and I attest that this site is appropriate based on those criteria.

[x] Check to confirm

- domain:
  url:
  method:
  last_checked:

Thanks for adding your site!


client bundle not working as intended in cloudflare (only in production)

Reproduction: fork this in develop branch https://github.com/mathix420/mathix.dev/tree/develop
Config:
export default defineNuxtConfig({
  future: { compatibilityVersion: 4 },
  compatibilityDate: "2024-04-03",

  nitro: {
    prerender: {
      crawlLinks: true,
      routes: ["/", "/blog"],
    },
  },

  icon: {
    mode: "svg",
    clientBundle: {
      // list of icons to include in the client bundle
      icons: [
        "simple-icons:github",
        "simple-icons:bento",
        "simple-icons:stackoverflow",
        "simple-icons:matrix",
        "simple-icons:linkedin",
        "ic:round-email",
      ],
    },
  },
});

Production logs:
16:25:44.157 [error] [nuxt] [request error] [unhandled] [500] Unexpected token 'F', "File size "... is not valid JSON
16:25:44.157   at JSON.parse (<anonymous>)
16:25:44.158   at parseJSONFromBytes (node:internal/deps/undici/undici:5472:19)
16:25:44.158   at successSteps (node:internal/deps/undici/undici:5454:27)
16:25:44.158   at fullyReadBody (node:internal/deps/undici/undici:4381:9)
16:25:44.158   at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
16:25:44.158   at async consumeBody (node:internal/deps/undici/undici:5463:7)
16:25:44.159   at async Object.fluent-emoji (./node_modules/.cache/nuxt/.nuxt/prerender/chunks/runtime.mjs:6006:17)
16:25:44.159   at async defineCachedEventHandler.group (./node_modules/.cache/nuxt/.nuxt/prerender/chunks/runtime.mjs:6199:39)
16:25:44.159   at async ./node_modules/.cache/nuxt/.nuxt/prerender/chunks/runtime.mjs:1075:20
16:25:44.159   at async _resolve (./node_modules/.cache/nuxt/.nuxt/prerender/chunks/runtime.mjs:897:23)
16:25:44.466 [warn] [Icon] loading icon `simple-icons:github` timed out after 500ms
16:25:44.468 [warn] [Icon] loading icon `simple-icons:bento` timed out after 500ms
16:25:44.468 [warn] [Icon] loading icon `simple-icons:stackoverflow` timed out after 500ms
16:25:44.469 [warn] [Icon] loading icon `simple-icons:matrix` timed out after 500ms
16:25:44.469 [warn] [Icon] loading icon `simple-icons:linkedin` timed out after 500ms
16:25:44.470 [warn] [Icon] loading icon `ic:round-email` timed out after 500ms

After production deployment, we can see that icons are still fetched after initial load.

Icons missing:

Expected behavior (like local preview):

had the same issue.

Same issue, any updates?

Same issue on Netlify. Only with some icons in a modal.


VS Code extension

Would be nice with a VS Code version too :)

well it turns out that is entirely possible.
https://github.com/KevinJump/UmbSense/tree/vs-code
there is no 'code' other than a lot of json mangling, it sort of feels like it should be something we can scrape from the repo but that might be pushing it.
it will need some work. I will raise some issues, for the steps.

Looking at the JSON, (e.g. umb-button.json) now it's got me wondering if we could generate the C# classes from it too. 🤔  "Single source of truth" and all that jazz!

thats the dream 👍
I think we need to look at how the ngDoc stuff actually generates help, and see if it can generate machine readable code, then munge it into c# / json files.


Expose package:linux:32 and package:linux:64

Having deb and rpm for different architectures is great, but it then requires that the user have those package systems installed, which is not ideal for users of distributions that don't use debs or rpms. Building able to package for different architectures would prevent that issue.

LGTM :+1:
Just waiting on CI


fix: apply SDK app hash fix

Description
Applies some fixes, some more unit tests pass now, the rest still need to be debugged
closes: #XXXX
Commit Message / Changelog Entry
type: commit message

see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

thankyou for your help


Travis-ci: added support for ppc64le

Hi,
I have added support for ppc64le build on travis-ci in the branch . The travis-ci build log can be tracked on the link :https://travis-ci.com/github/sanjaymsh/fortran-language-server/builds/190095318 . I believe it is ready for the final review and merge.
Please have a look on it and if everything looks fine for you then please approve it for merge.
Thanks !!

Great, thanks for the contribution!

Thanks !!


Fixed broken links in doc

Tried to fix this issue https://github.com/spring-cloud/spring-cloud-stream/issues/2773

@Claudio-code Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@Claudio-code Thank you for signing the Contributor License Agreement!


[Bug]: Professor card highlighting

What did you expect to happen?
The highlighting for "Average Difficulty" to be green when the number is lower and red when higher.
The highlighting for "Percentage Taking Again" to be green when the number is higher and red when lower.
What happened?
The highlighting for "Average Difficulty" is reversed.
The highlighting for "Percentage Taking Again" is always red.
Version
Beta 0.1.0
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Code of Conduct

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

Fixed in consistency edits


Feed data into intermediate layer in forward pass

Is there a way to feed data into an intermediate symbol in the forward pass without constructing a new graph, similar to how you can use a feed_dict in tensorflow to feed data into every node of the computation graph?
I.e., conceptually, I would like to do something like this:
A=mx.sym.Variable('A')
B=mx.sym.Variable('B')
C=mx.sym.add_n(A, B, name='C')
D=mx.sym.Variable('D')
E=C*D
executor=E.bind(mx.cpu(), {'C':mx.nd.array([2]), 'D':mx.nd.array([3])})

My use case is a pretrained network, for which I would like to compute a forward pass for either a new input X or some feature representation at an intermediate layer (which might come from another network or some processed representation.
I presume there should be some way to do this; however, I have not been able to find it. Sorry if this question has already been answered elsewhere

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!
Also, do please check out our forum (and Chinese version) for general "how-to" questions.


📝 Update includes in docs/de/docs/advanced/async-tests.md

Thanks for the effort! :cake:
This was handled in another PR, so I'll close this one now. :coffee:


Necessary Edits Done

Background Image & Issue no.: #8

https://lostgirljourney.github.io/tower-of-hanoi/index.html
Link of the game for trial.


Use automatic service registrations

This showcases how to keep the minimalism by leveraging a source generator to emit all those pesky AddXXX calls to register services. The (compile-time) emitted source code is even more optimal than the previous one (no run-time lookup of a constructor).
See https://github.com/devlooped/DependencyInjection.Attributed for reference.
Perhaps that analyzer/source generator should be built-in ASP.NET?
BTW, since this adds "magic" that's not too visible to users, it might not be appropriate for the sample.

It also seems quite opinionated.

Yea, I'm personally not a fan of this style.


arm64 v8 pause container not matched

/kind bug
Description

Steps to reproduce the issue:

Install Ubuntu 20.04 (arm64) on a Raspberry Pi 4

Install Podman using the Ubuntu instructions (apt integration)

podman pod create

Describe the results you received:
# podman pod create
ERRO[0000] Error freeing pod lock after failed creation: no such file or directory
Error: unable to create pod: error adding Infra Container: unable to pull k8s.gcr.io/pause:3.2: unable to pull image: Error choosing an image from manifest list docker://k8s.gcr.io/pause:3.2: no image found in manifest list for architecture arm64, variant v8, OS linux

Describe the results you expected:
Pod created
Additional information you deem important (e.g. issue happens only occasionally):
Looking at the skopeo output of:
skopeo inspect --raw docker://k8s.gcr.io/pause:3.2 | jq .

I noticed that the arm64 pause container does not specify a variant:
    {
      "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
      "size": 526,
      "digest": "sha256:31d3efd12022ffeffb3146bc10ae8beb890c80ed2f07363515580add7ed47636",
      "platform": {
        "architecture": "arm64",
        "os": "linux"
      }
    },

My guess is that the "v8" variant is preventing a match for the pause container but I'm not having any luck finding a way to override it. An --override-variant option might work here, but perhaps the absence of a variant specification on the upstream container should match all variants? That seems to be the approach being advocated here:
https://github.com/containers/image/issues/898
Output of podman version:
Version:            1.9.3
RemoteAPI Version:  1
Go Version:         go1.13.8
OS/Arch:            linux/arm64

Output of podman info --debug:
debug:
  compiler: gc
  gitCommit: ""
  goVersion: go1.13.8
  podmanVersion: 1.9.3
host:
  arch: arm64
  buildahVersion: 1.14.9
  cgroupVersion: v1
  conmon:
    package: 'conmon: /usr/libexec/podman/conmon'
    path: /usr/libexec/podman/conmon
    version: 'conmon version 2.0.16, commit: '
  cpus: 4
  distribution:
    distribution: ubuntu
    version: "20.04"
  eventLogger: file
  hostname: REDACTED
  idMappings:
    gidmap: null
    uidmap: null
  kernel: 5.4.0-1011-raspi
  memFree: 30969856
  memTotal:<PHONE_NUMBER>
  ociRuntime:
    name: runc
    package: 'runc: /usr/sbin/runc'
    path: /usr/sbin/runc
    version: 'runc version spec: 1.0.1-dev'
  os: linux
  rootless: false
  slirp4netns:
    executable: ""
    package: ""
    version: ""
  swapFree: 0
  swapTotal: 0
  uptime: 220h 11m 50.06s (Approximately 9.17 days)
registries:
  search:
  - docker.io
  - quay.io
store:
  configFile: /etc/containers/storage.conf
  containerStore:
    number: 0
    paused: 0
    running: 0
    stopped: 0
  graphDriverName: overlay
  graphOptions: {}
  graphRoot: /var/lib/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "true"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 2
  runRoot: /var/run/containers/storage
  volumePath: /var/lib/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman/unknown 1.9.3~1 amd64
podman/unknown,now 1.9.3~1 arm64 [installed]
podman/unknown 1.9.3~1 armhf
podman/unknown 1.9.3~1 s390x

Additional environment details (AWS, VirtualBox, physical, etc.):

Thanks for your report; this should be fixed in Podman 2.0.0, which has been released since. Can you retest, please?

Closing, reopen if it is not fixed.


Support backup sidecar's own NodeSelector

A backup sidecar pod seems to use the NodeSelector of cluster's pod. So, When I set anti-affinity with etcd pods, one etcd pod couldn't be scheduled due to a backup sidecar pod.
It would be good to give a flexibility to set the backup sidecar's own NodeSelector.

reasonable. we will add a podpolicy into backup policy. so backup pod will only respect the pod policy there.


Lazy properties are not supported

Description
Hello!
It seems that lazy properties are currently not supported.
Let's say that I have the following code:
@Perceptible
class Feature {
  lazy var magic = 3.14
}

I will not be able to compile the project due to the following error:

'lazy' cannot be used on a computed property
FIX: Remove 'lazy '

which (correct me if I'm wrong) but does not seem to be an accurate diagnostic.
The fix will indeed make my code compile but it will not respect the behaviour I wanted to have in the first place.
What do you think should be done for this kind of situation ?
I tried to add a very basic workaround by rejecting lazy properties similar to what you did for immutable properties:
// in Sources/PerceptionMacros/Extensions.swift
extension VariableDeclSyntax {
  // ...
  var isLazy: Bool {
    for modifier in modifiers {
      for token in modifier.tokens(viewMode: .all) {
        if token.tokenKind == .keyword(.lazy) {
          return true
        }
      }
    }
    return false
  }
}

// in Sources/PerceptionMacros/PerceptibleMacro.swift
extension VariableDeclSyntax {
  // ...
  var isValidForPerception: Bool {
    !isComputed && isInstance && !isImmutable && !isLazy && identifier != nil
  }
}

but is it really what should be done?
I'm reporting the issue but based on what you decide, I would gladly help and make the appropriate changes if necessary 😄
Checklist

[X] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
Either fully support the source code input or reject it but with a more appropriate diagnostic
Actual behavior
Not compiling and inaccurate diagnostic
Steps to reproduce
No response
Perception version information
1.1.1
Destination operating system
No response
Xcode version information
15.2
Swift Compiler version information
swift-driver version: 1.87.3 Apple Swift version 5.9.2 (swiftlang-<IP_ADDRESS>.56 clang-15<IP_ADDRESS>.5)
Target: arm64-apple-macosx14.0

@McNight This is an issue that affects Swift's @Observable, as well:
@Observable class Foo {
  lazy var bar = 1  🛑
}

Something isn't working due to a bug in the library.
So we think if you'd like to fix it it'd be best to do so upstream with a bug filed to apple/swift.
Since this isn't a bug with our library I'm going to convert it to a discussion.


Adds the packaging scripts from SS14

Copies the scripts over from https://github.com/space-wizards/space-station-14/tree/master/Tools which are needed to package game builds. Mainly so players connecting through the launcher actually have a client to download.
I made minimal changes to the scripts to accommodate our renaming. I'm not 100% sure everything is functional until I've finished sorting out the test server, hence this being a draft.

It works.

Why is a script packaging the client necessary? Doesn't the server already do that?

/shrug
I didn't bother to figure out the reasoning, I just know ACZ dies unless both are present.

> Approved without merge
😩


Streaming downloads via range requests, in-memory only blobs (WIP)

@jackrobison is this ready to merge? Can the /get endpoint redirect to the source url (i.e. if I use an external IP, it redirects to local host)
These errors fixed? ```2019-04-05 01:03:11,905 ERROR    lbrynet.extras.daemon.Daemon:559: error handling api request
Traceback (most recent call last):
File "/home/tom/lbry/lbrynet/extras/daemon/Daemon.py", line 551, in _process_rpc_call
result = fn(self, *_args, **_kwargs)
File "/home/tom/lbry/lbrynet/extras/daemon/Daemon.py", line 69, in _inner
return fn(*args, **kwargs)
File "/home/tom/lbry/lbrynet/extras/daemon/Daemon.py", line 1585, in jsonrpc_file_list
sort, reverse, comparison, **kwargs
File "/home/tom/lbry/lbrynet/stream/stream_manager.py", line 277, in get_filtered_streams
streams.sort(key=lambda s: getattr(s, sort_by))
TypeError: '<' not supported between instances of '_asyncio.Future' and '_asyncio.Future'

```raceback (most recent call last):
  File "/home/tom/lbry/lbrynet/extras/daemon/Daemon.py", line 551, in _process_rpc_call
    result = fn(self, *_args, **_kwargs)
  File "/home/tom/lbry/lbrynet/extras/daemon/Daemon.py", line 68, in _inner
    "%s" % json.dumps(components))
lbrynet.error.ComponentsNotStarted: the following required components have not yet started: ["wallet"]
Traceback (most recent call last):
  File "/usr/local/bin/lbrynet", line 11, in <module>
    load_entry_point('lbrynet', 'console_scripts', 'lbrynet')()
  File "/home/tom/lbry/lbrynet/extras/cli.py", line 296, in main
    loop.run_until_complete(loop.shutdown_asyncgens())
  File "/usr/lib/python3.7/asyncio/base_events.py", line 571, in run_until_complete
    self.run_forever()
  File "/usr/lib/python3.7/asyncio/base_events.py", line 539, in run_forever
    self._run_once()
  File "/usr/lib/python3.7/asyncio/base_events.py", line 1775, in _run_once
    handle._run()
  File "/usr/lib/python3.7/asyncio/events.py", line 88, in _run
    self._context.run(self._callback, *self._args)
  File "/home/tom/lbry/lbrynet/dht/node.py", line 203, in stream_peer_search_junction
    yield junction