Clarification on //link/must_be_base_link element

While addressing a downstream issue https://github.com/robotology/gym-ignition/issues/385, I discovered the existence of //link/must_be_base_link. After checking upstream, I only found references to the specification, but I didn't find any place where this element is actually read.
Is it used elsewhere? Should it be deprecated in favor of the new //model/@canonical_link attribute?
Environment
Issue related to SDF specification.
Description

Expected behavior: clarify if this element is used and read at least in Gazebo (Classic / Ignition)
Actual behavior: this element seems ignored

Judging by the specification both tags would have slightly different behavior since @canonical_link would also attach the implicit __model__ frame to the named link. Also, it would be impossible to attach multiple links of one model to the implicit world frame.
However, there is enough overlap to make this quite redundant indeed and multiple //must_be_base_link elements inside the same model scope is probably just an edge case that I use for unit tests; I doubt it has much adoption "in the wild".

The only place I've seen it used is in Gazebo classic in the Simbody support classes. https://github.com/osrf/gazebo/blob/f54f95e7cad959d22d5af1549149da6e81c12bed/gazebo/physics/simbody/SimbodyLink.cc#L61.
Conceptually, I think it's different from the canonical link, since the canonical link is simply the link to which the model frame (__model__)  is attached. This link can be any link in the model. Whereas, the documentation for //link/must_be_base_link states that the link will have 6DOF. This is more like the concept of the root link in https://github.com/ignitionrobotics/ign-physics/issues/233.
Since it was only used for one physics engine, I'm in favor of deprecating it. If the need for a similar tag arises for a physics engine in the future, perhaps we can use custom elements instead.

@azeey After reading through https://github.com/ignitionrobotics/ign-physics/issues/233 and considering your comment in https://github.com/ignitionrobotics/sdformat/issues/705#issuecomment-926909748 I'm actually wondering if it would be useful to not fully depreciate this element, but rather to replace it.
What I was thinking was that, indeed, //must_be_base_link doesn't quite fit the semantics of the current spec; however a //joint with type "free" does (which would be a 6DoF joint). In this case, //must_be_base_link could be replaced with
<link name="this_link" />
<joint name="fancy_joint" type="free">
<parent>world</parent>
<child>this_link</child>
</joint>

A nice implication of this would be that it now becomes easy to spot errors in the pose graph of an SDF. Currently a SDF of the form
<?xml version="1.0"?>
<sdf version="1.7">
  <world name="my_world">
    <model name="M1">
      <link name="L1"/>
      <link name="L2"/>
    </model>
  </world>
</sdf>

is a bit ambiguous in the sense that it is unclear if the author intended to create two independently moving (free) links, or if the author has forgotten to add a link. Adding the type="free" joint, would make this very easy to spot since now every //link will have to be connected to world via a chain of //joints. It could also be me not being aware of documentation on this, but I think that the behavior of the above model (multiple, independently floating links) is not explicitly defined by the spec. Perhaps this could be an opportunity to clear that up, too.
On a sidenote, it would also make my life easier. In scikit-bot I have a feature that builds the pose graph by connecting all frames declared in the SDF using //joints and //frame/attached_to (+ implicit attachment rules of //model, //sensor, etc.). My current problem with this is that I often don't end up with a single tree where world is the root, but rather with a set of trees, because something like a mobile robot / mobile base, won't define an explicit constraint w.r.t. world.
As a result, I have to walk over all declared frames after the graph(s) is/are connected and find connected components (afterwards, because I have to account for model nesting). Then, for each connected component, I have to insert a 6DoF connections (i.e. type="free" joints) to world so that all the nodes are connected and the behavior matches that of ignition gazebo. It would be a lot simpler if I could rely on SDFormat setting this joint explicitly, so that this can be solved naturally during graph construction instead of doing this complex clean up step.


Parses single line comments

This PR:

Extracts single line comments with the python tokenizer
Matches them to the closest node according to a heuristic
Fixes Region computation to match sarif region formats
Adds region computation to implicitly added CompoundStatements and ParamVariableDeclaration

Hi @konradweiss
I tried your PR with the following code snippet and the results did not look very convincing to me:
# A comment

i = 42  # a number

# a function
def foo(): # foo
    pass

def bar(i,  # a parameter
        j  # another parameter
        ):
    pass

a = ('start'  # comment start
     'end')  # comment end

b = {
    "a": 1,  # a entry
    "b": 2  # b entry
}

I can only find a single comment (that happens to be the entire file) when exploring the above code with the neo4j query MATCH (n) WHERE n.comment IS NOT NULL RETURN n.
I would also like to keep this feature optional, as it currently requires to parse the code multiple times (however, I do not see an easy solution with Python's ast module for adding this functionality).
Currently, I would prefer to not merge this PR. I think this functionality should be in an optional Pass or something similar. There is also a discussion why ast is not carrying comments here: https://bugs.python.org/issue24119

String comments are currently available in the Python front end (as string literals). Would it not be cleaner to make use of them in a Pass and attach them with some heuristic to a node?
""" a comment """
def foo():
  """ more text """
  pass

(This would work for @immqu)

@maximiliankaul Finished all the requested changes including separating the comment matching code from the frontend, and the comment extraction into a new file. The feature is also optional, default off, and configurable over the translation configuration. If its OK I would merge this now

@maximiliankaul Finished all the requested changes including separating the comment matching code from the frontend, and the comment extraction into a new file. The feature is also optional, default off, and configurable over the translation configuration. If its OK I would merge this now

An acutual unit test for the comment matched would be nice as well.

@oxisto @maximiliankaul I made the requested changes including adding a Unit test, using the error uncovering sample provided by @maximiliankaul.


SqlServerCompiler Limit generates different query on compile compared to previous versions

Using the limit example from the docs, and comparing to the online playground tool (see here), the below query generates a different query in the latest release of SqlKata when using SqlServerCompiler. Matter of fact, the change in behavior happened sometime after 2.3.7 (same issue still in v3 beta).
Query:
var query = new Query("Posts").OrderByDesc("Date").Limit(10)
Results (>= 2.3.9):
SELECT * FROM [Posts] ORDER BY [Date] DESC OFFSET 0 ROWS FETCH NEXT 10 ROWS ONLY
Expected Results (<= 2.3.7):
SELECT TOP (10) * FROM [Posts] ORDER BY [Date] DESC
The "new" generated query is valid and will run, however my expectation would be to receive the previous generated query over the new one first. Offset/Fetch usage only makes sense when I have a range of records that I want to return (i.e. for paging). For simple cases, I would expect the usage of TOP. Additionally, the docs also dictate that the TOP example is what should be returned for this example query.

Hi @gerneio, the change is documented here https://sqlkata.com/release/v2.3.8#sqlserver-is-now-using-the-new-offset-pagination-by-default
You can use the old behavior by setting new SqlServerCompiler { UseLegacyPagination = true }

Ah got ya, the correlation wasn't super obvious to me when looking through the docs and changelog. Actually the change you linked to kind of introduced what could be considered a breaking change (i.e. since generated sql of simple query changes between versions), but I understand why it was done. Looks like the docs I linked to could also be updated for slightly better clarification on that first example (i.e. just show legacy & non-legacy outputs).
In my case, there is a sql parser middleware between what I generate and what is actually executed on the actual db server, and the parser can be a little picky about what is allowed (basically just doesn't have 100% compatability with all sql conventions). So I just needed to have a way to have predictable output, so that flag should help I believe.
I think the docs code is hosted on this repo, but couldn't find the playground code. Is that stored separately somewhere? I noticed that it's using an older version of the library, which further lead to more of my confusion.

You are right about the breaking change thing, this should be handled more carefully next time,
The site/playground code is not public yet, and the playground version does not reflect the latest release yet, something should be done here.


Remove schema validation gating production deploy

See relevant Slack context here. We already have some protections
here in Peril/Danger, so there will still be some feedback when service
schemas aren't compatible.

Already done in https://github.com/artsy/force/pull/3197

Great minds...


When I plot top-down map, info["top_down_map"]["agent_rotation"] is missing.

Hi @ChanganVR
I want to plot top-down map, but when I execute the following command:
--run-type eval --exp-config ss_baselines/savi/config/semantic_audionav/savi.yaml EVAL_CKPT_PATH_DIR data/pretrained_weights/semantic_audionav/savi/best_val.pth EVAL.SPLIT test USE_SYNC_VECENV True RL.DDPPO.pretrained False
the following error occurs:

I check the info. It seems to lack info["top_down_map"]["agent_rotation"].

How can I solve this problem? Thank you very much!

@ruohaoguo hello,I would like to ask if you have completed the model training process? I encountered some problems during the training.

@ruohaoguo hello,I would like to ask if you have completed the model training process? I encountered some problems during the training.

Yes, I completed the training process. Do you have any questions?

When I executed the command: python ss_baselines/av_nav/run.py --run-type eval --exp-config ss_baselines/av_nav/config/audionav/replica/val_telephone/audiogoal_depth.yaml --model-dir data/models/replica/audiogoal_depth, the program unexpectedly terminated at 400.pth, which seems to be caused by multithreading or insufficient memory.  My computer has 96G of memory.

When I executed the command: python ss_baselines/av_nav/run.py --run-type eval --exp-config ss_baselines/av_nav/config/audionav/replica/val_telephone/audiogoal_depth.yaml --model-dir data/models/replica/audiogoal_depth, the program unexpectedly terminated at 400.pth, which seems to be caused by multithreading or insufficient memory.  My computer has 96G of memory.

Sorry, I haven't encountered this problem. Maybe you can print out the error message or ask @ChanganVR .

May I ask what versions of your soundspace, habitat-lab, and habitat-sim are? Thank you very much.

soundspaces==1.0
habitat-lab==0.2.2
habitat_sim==0.2.2
torch==2.3.1
tensorflow==2.16.1

May I ask what versions of your soundspace, habitat-lab, and habitat-sim are? Thank you very much.

Thank you very much!

@Star-down I have encountered this problem. My email address is<EMAIL_ADDRESS>I think we can communicate.

你好@ChanganVR
我想绘制自上而下的地图，但是当我执行以下命令时： --run-type eval --exp-config ss_baselines/savi/config/semantic_audionav/savi.yaml EVAL_CKPT_PATH_DIR data/pretrained_weights/semantic_audionav/savi/best_val.pth EVAL.SPLIT test USE_SYNC_VECENV True RL.DDPPO.pretrained False 出现以下错误：

我检查了一下`info`。好像缺少了`info["top_down_map"]["agent_rotation"]`。

我该如何解决这个问题？非常感谢！

@ruohaoguo May I ask how your problem was solved?

Hi @ChanganVR
I want to plot top-down map, but when I execute the following command: --run-type eval --exp-config ss_baselines/savi/config/semantic_audionav/savi.yaml EVAL_CKPT_PATH_DIR data/pretrained_weights/semantic_audionav/savi/best_val.pth EVAL.SPLIT test USE_SYNC_VECENV True RL.DDPPO.pretrained False the following error occurs:

I check the `info`. It seems to lack `info["top_down_map"]["agent_rotation"]`.

How can I solve this problem? Thank you very much!

@ruohaoguo May I ask how your problem was solved?

@FrankZxShen hello,May I ask if the dataset you are using is MP3D? I am missing a file called 'data/scene_datasets/mp3d/mp3d.scene_dataset_comfig.json'. Do you have this file? We can use it to<EMAIL_ADDRESS>Contact, thank you!

You can get it here. Do you have a solution for this issue?

@FrankZxShen Sorry, I am unable to resolve this issue at the moment，perhaps https://aihabitat.org/docs/habitat-lab/habitat-lab-tdmap-viz.html Could this link solve your problem?

@Star-down Thanks, this worked for me!


Error golang deadlock when iterating over large amount of S3Objects

I'm having an issue with regards to S3Object just this past week. The error initially was just a stuck nuke process, no error, even with trace log enabled. After doing some more digging, it turns out to be a specific issue in-us-east-1, and with a specific log bucket.
In my sandbox env, there is an access log bucket with roughly 67k objects (with total bucket size <50MB), this is from a single bucket. I'd estimate the grand total for all existing buckets would be roughly 70k objects. This causes a golang deadlock error when iterating over the S3Object resources. I then tried to empty the access log bucket, and retry the aws-nuke cli again, and it worked.

Some more context, my config regarding S3Object does not filter anything. And this is also the first time I've seen this issue, and I've been using aws-nuke (old repo & this fork) for almost a year now.
version: 3.24.0

Thanks @vinhltr I'll have to look into this more. Do you actually use S3Object on purpose. 99% of the time folks really just want S3Bucket. I'm inclined to disable S3Object by default as it's very problematic.

@ekristen My understanding is to nuke an s3 bucket, I have to wipe it first, which means deleting all s3objects, so yes, I'm using S3Object on purpose.

You aren't wrong, but S3Bucket wipes an entire bucket clean much more efficiently using bulk api calls. S3Object should really just always be disabled.
Exclude S3Object in your configuration. You'll end up with the same result and it will be much quicker.

noted, I'll make adjustment in my code, thanks @ekristen

I actually had the same. aws-nuke didn't nuke any resources. Then I excluded S3Object and resources were deleted. Weird :-/

Closing. S3Object will be disable by default in the 4.x release of the tool. #380


Ignore tokens between backticks in rule max line length (#1007)

Tokens starting and ending with a backtick should be ignored entirely when validating whether a line exceeds the maximum length of a line. Such tokens can not be spit into multiple lines. For example when writing JUnit test it is a common pattern to write the function names between back ticks instead of using the DisplayName annotation.
Currently I just ignore all ASTNodes starting and ending with a back tick. Such a node no longer counts in the calculation of the length of the line. This is not explicitly limited to method names neither to unit test only. However I do think this approach is valid. Tokens can only contain back ticked values whenever this is allowed by Kotlin. Such tokens can never be split in multiple lines.

The identifiers between back ticks can now optionally be ignored. By default this option is disabled so the behaviour is not changed for existing users.

@Tapchicoma Sorry that I reach out to you in this way but I have found no other way to do so. I am wondering what else I can do to get my PR's merged. I am aware that you are volunteer on this project. I am willingly to give a long term commitment on the project if you would appreciate that. But for that I need to know how my contributions will be merged more smoothly.

@Tapchicoma Sorry that I reach out to you in this way but I have found no other way to do so. I am wondering what else I can do to get my PR's merged. I am aware that you are volunteer on this project. I am willingly to give a long term commitment on the project if you would appreciate that. But for that I need to know how my contributions will be merged more smoothly.

hi @paul-dingemans, sorry for long-awaited review, I've just changed 3 things:

Changed how we use editorconfig properties (see #701 and associated PRs for the new API - we shouldn't introduce new fields for the EditorConfig interface from now on)
Renamed the custom property to start with ktlint_ following your own suggestion in #1033, jus
Changed README a bit, so we don't have a new section (which is already quite bloated)

I will take your frustration on me, as I planned to do the aforementioned changes way earlier, but then life happened. Your PRs are of course appreciated, just one wish would be to make your PRs smaller and target one specific issue/thing (I'm referring to your other PRs, this one looks good). thanks for the contribution!


Support reading settings from a config file

At my hosting service, I cannot control the environment variables so need an alternative way to configure settings.

@capncrunch Regarding this and #39, I'd be happy to review a PR if you want to implement these features, but don't have time currently to work on them myself.

I'll give it a try.


IndexError: list index out of range

from twitter.search import Search

email, username, password = "myEmail", "myUsername", "MyPassword"
# default output directory is `data/search_results` if save=True
search = Search(email, username, password, save=True, debug=1)

res = search.run(
    limit=37,
    retries=5,
    queries=[
        {
            'category': 'Latest',
            'query': 'paperswithcode -tensorflow -tf'
        }
    ],
)

getTwitterAccounts
    url = f"https://twitter.com/i/api/2/search/adaptive.json?include_profile_interstitial_type=1&include_blocking=1&include_blocked_by=1&include_followed_by=1&include_want_retweets=1&include_mute_edge=1&include_can_dm=1&include_can_media_tag=1&include_ext_has_nft_avatar=1&skip_status=1&cards_platform=Web-12&include_cards=1&include_ext_alt_text=true&include_quote_count=true&include_reply_count=1&tweet_mode=extended&include_entities=true&include_user_entities=true&include_ext_media_color=true&include_ext_media_availability=true&include_ext_sensitive_media_warning=true&include_ext_trusted_friends_metadata=true&send_error_codes=true&simple_quoted_tweet=true&q={sys.argv[1]}&result_filter=user&count=20&query_source=typed_query"
IndexError: list index out of range

You'll need to update to the latest version

I did pip install --upgrade twitter-api-client and I get the same error.
Requirement already satisfied: twitter-api-client in /Users/me/Documents/Git/env/lib/python3.10/site-packages (0.10.8)
Requirement already satisfied: aiofiles in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from twitter-api-client) (23.1.0)
Requirement already satisfied: websockets in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from twitter-api-client) (11.0.3)
Requirement already satisfied: nest-asyncio in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from twitter-api-client) (1.5.6)
Requirement already satisfied: httpx in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from twitter-api-client) (0.24.0)
Requirement already satisfied: tqdm in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from twitter-api-client) (4.65.0)
Requirement already satisfied: orjson in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from twitter-api-client) (3.9.1)
Requirement already satisfied: uvloop in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from twitter-api-client) (0.17.0)
Requirement already satisfied: certifi in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from httpx->twitter-api-client) (2023.5.7)
Requirement already satisfied: httpcore<0.18.0,>=0.15.0 in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from httpx->twitter-api-client) (0.17.2)
Requirement already satisfied: idna in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from httpx->twitter-api-client) (3.4)
Requirement already satisfied: sniffio in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from httpx->twitter-api-client) (1.3.0)
Requirement already satisfied: h11<0.15,>=0.13 in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from httpcore<0.18.0,>=0.15.0->httpx->twitter-api-client) (0.14.0)
Requirement already satisfied: anyio<5.0,>=3.0 in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from httpcore<0.18.0,>=0.15.0->httpx->twitter-api-client) (3.7.0)
Requirement already satisfied: exceptiongroup in /Users/me/Documents/Git/env/lib/python3.10/site-packages (from anyio<5.0,>=3.0->httpcore<0.18.0,>=0.15.0->httpx->twitter-api-client) (1.1.1)


Support for generic messages

Addresses lingering issues with generic message types discussed @ #278.
As mentioned there, the problem seems to lie with bits of code that stringify types using Type.Name, which loses information about the instance type's generic parameters. An added complication is that the Subject of SQS/SNS messages gets populated with this value;  changing that could break existing applications.
Here, I've attempted to remove all usages of Type.Name from the codebase in a way that won't break existing applications:

For purely internal stuff, I've just replaced uses of Type.Name with something that preserves information about generic type parameters.

For the message Subject, I've introduced an IMessageSubjectProvider. The default implementation preserves the current behaviour and compatibility, but has the existing problems with generics. An optional GenericMessageSubjectProvider breaks compatibility but supports generics (or users are free to supply their own impelmentation).

Is this PR separate to #359, or does it replace #359 ?

It's separate. The topic name stuff #359 is involved with already supports generics.

Needs unit tests on GenericMessageSubjectProvider and NonGenericMessageSubjectProvider.
After review, we will merge this to a 6.0 beta unless there's a good reason to lock down 6.0 beforehand.

Requested subject provider unit tests added

Not sure why that test is failing on travis... passes locally and in appveyor, and I don't think anything I've done around the bit that's failing. Flaky test?

Must be a flakey test, it's green after I re-ran it. 🤷♂


fix: Remove '.' from sanitized type names

Before this PR
Types fail when they include . in their import path (e.g. gopkg.in/inf.v0) and require namespacing due to a similarly named type in a different package.
After this PR

==COMMIT_MSG==
Remove '.' from sanitized type names
==COMMIT_MSG==
Possible downsides?

Released 0.60.0


Simulate various DiffAdjDivisor values to determine the time required to increase the difficulty level to the specified target

Simulation env parameters:

init diff: 10 replicas
target diff: 20 replicas
mining power: 20 replicas
ending check: current diff == target diff
simulation rounds: 1000

DiffAdjDivisor
duration (mean value)

1024
11418 hrs

128
1078 hrs

64
505 hrs

32
225 hrs

DiffAdjDivisor = 32 (around 10 days) seems to be more reasonable?

DiffAdjDivisor  == 1024

DiffAdjDivisor  == 128

DiffAdjDivisor  == 64

DiffAdjDivisor  == 32

Iterations: python es_mc.py 1024 iterations

init diff: 20 replicas
Iterations: 1000
mining power: 20 replicas
simulation rounds: 100

DiffAdjDivisor	Block time mean	Block time standard variance	Coefficient of variation
1024	10732 hrs	11479 hrs	1.07
32	10192 hrs	10187 hrs	0.99
Conclusion: No big differences in standard variance


[Bug]: Alarm Status unknown after HA restart

Client version
6.2.0
Node version
??
Operating System type
Linux
Operating system version
??
Describe the bug
After a restart of HA the alarm state is lost/unknown. I manually have to change the state to update the Alarm state
To reproduce

Set the Alarm to "Home"
Restart HA
Check Alarm (entity: alarm_control_panel.eufy_homebase)

Screenshots & Logfiles
No response
Additional context
No response

Wrong repo


Docker / docker-compose support

Docker can make deploying easier. This PR creates a Dockerfile and docker-compose_example.yml
Now, you can write install manual like below
git clone https://github.com/lewisakura/webhook-proxy.git
cd webhook-proxy
cp docker-compose_example.yml docker-compose.yml
vim docker-compose.yml # Edit docker-compose file with your editor, you want
docker compose up -d

A docker composer should really be added @lewisakura :)

Any updates on this @lewisakura


decent-sampler: 1.10.0 -> 1.12.1

Added myself to maintainers
Formatted with nixfmt
Removed reliance on archive.org. Download assets from upstream instead
Updated 1.10.0 -> 1.12.1

Closes https://github.com/NixOS/nixpkgs/issues/349256
Things done

Built on platform(s)

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

I was just giving @adam248 some time to respond.
Feel free to ping eagerly next time; ~a week should be long enough of a timeout.
Please also see https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#committers-work-on-a-push-basis


chore(npm): remove shrinkwrap file

What & Why
Usually modules that are used by other modules shouldn't have a shrinkwrap.

LGTM


Policy engine workflow for building and testing 2nd party plugins

TODO

[ ] gen from codebase
[ ] beta attestation API
[ ] overlay support
[ ] test cases

https://github.com/search?q=org%3Aintel+path%3Apyproject.toml&type=code

These are existing intel repos which are pep-518 comparable, so they should build with the build package

Future

[ ] #1615
[ ] Make a single python script run

[ ] Leverage pin_command() with cached dag workflow context off SCITT

Test Cases

https://github.com/search?q=org%3Aintel+path%3Apyproject.toml&type=code

gh search code --filename pyproject.toml --owner $USER --json repository,path,sha,url

[
  {
    "path": "pyproject.toml",
    "repository": {
      "id": "MDEwOlJlcG9zaXRvcnk5ODQ2ODEzMw==",
      "isFork": false,
      "isPrivate": false,
      "nameWithOwner": "pdxjohnny/httptest",
      "url": "https://github.com/pdxjohnny/httptest"
    },
    "sha": "17b123594123d648e8a064fb0761a248ed0b312e",
    "url": "https://github.com/pdxjohnny/httptest/blob/2239666733f9e77221b01425c8cc71fb18062eb4/pyproject.toml"
  }
]


Bug 2042587: Apply ConfigMaps with Injected Keys

Add a general purpose function to apply ConfigMaps with data that can be
injected into a specified key. This allows operators to reconcile
ConfigMaps that can have data injected by other controllers. Injected
keys are used by components that require the cluster's global trust
bundle or require the Service CA certificate.
This change preserves the existing ability for the global trust bundle
to be injected into a ConfigMap via the
"config.openshift.io/inject-trusted-cabundle": "true" label, and then be
reconciled using ApplyConfigMap.

The new ApplyInjectableConfigMap method can be used by operators that need the Service CA injected into a ConfigMap. There are several CVO operators which do this - see https://docs.openshift.com/container-platform/4.9/security/certificate_types_descriptions/service-ca-certificates.html

/assign @mfojtik

/bugzilla refresh


“No such file or directory” Error

Running npm-license-crawler . in a directory with a package.json and installed node_modules results in this error:
env: node\r: No such file or directory

OS: OS X 10.11.2
NPM:  3.3.12
Node: 5.3.0

+1
Same OS, NPM and Node. Using NVM, changed to Node v4.2.4, same result

OK, I'll have a look at this asap.

Guys, I think the problem is solved with new release. The problem was the published command wrapper file contained CRLF line endings which causes problems specifically on OS X. Seems like a few other node projects had the same issue in the past. Originally, I developed on OS X, but I had to migrate my dev environment to Win 10, recently. On Windows, git will perform an autoconversion to CRLF by default on the local base - I wasn't aware of the consequences it has for OS X users. Sorry about that.
Please provide a short feedback. Thanks

@swashcap and @uglow As you did not get back to me I assume the issue has been solved with the new release. May be the force with you!

Hi Marcus,
Sorry for not getting back to you. I used the parent dependency of this package instead, which met my needs at the time. If you  reproduced the error, made changes and couldn't reproduce it anymore, then I agree that it's safe to close this.
Cheers,
Brett
Sent from my iPhone

On 20 Jan 2016, at 9:12 PM, Marcus Wittig<EMAIL_ADDRESS>wrote:
@swashcap and @uglow As you did not get back to me I assume the issue has been solved with the new release. May be the force with you!
—
Reply to this email directly or view it on GitHub.

Hi Brett,
Thanks for letting me know. If you only need to check licenses for a single package (which is the common case, I think) you'll be fine with license-checker.
Regards
Marcus


ESLint Error on create

Describe the bug
Let me start off by saying that this project is incredible. Really great work.
Its one of those FOSS projects that you look and think "Shit, that took me a month to build 6 months ago."
Pulumi was news to me, really liking it so far. I don't think I'll use this project wholesale, but there is a lot of good stuff in here I'm going to transplant into an existing fullstack TS / Hasura SaaS project I'm leading.
Unfortunately, it seems like there is a ESLint Error when running the create command.
Running
yarn create full-stack --backend hasura --authentication auth0 --cloud aws --web react --mobile react-native --cicd github-actions

Yields
yarn run v1.22.4
$ eslint packages/** --ext ts,tsx --fix

Oops! Something went wrong! :(

ESLint: 7.12.1

Error: Error while loading rule 'jest/no-deprecated-functions': Unable to detect Jest version - please ensure jest package is installed, or otherwise set version explicitly

Expected behavior
Painless setup that creates a unicorn with 0 effort.
Desktop (please complete the following information):

OS: Ubuntu 18

Additional context
Definitely going to be keeping an eye on this project.
I'm working on TS metadata generation that would be a good fit for this, I'll share once its ready.

yarn add jest -W --dev in the workspace root resolved the issue.

Thanks for the kind words! I couldn't have said why I built the project better myself. How'd you discover it?
Thanks for the bug report. I tried your proposed solution but the web tests fail for me.
% yarn test
[Web]
[Web] There might be a problem with the project dependency tree.
[Web] It is likely not a bug in Create React App, but something you need to fix locally.
[Web]
[Web] The react-scripts package provided by Create React App requires a dependency:
[Web]
[Web]   "jest": "26.6.0"
[Web]
[Web] Don't try to install it manually: your package manager does it automatically.
[Web] However, a different version of jest was detected higher up in the tree:
[Web]
[Web]   /Users/tiagobandeira/dev/apollo-server-express-no-auth/node_modules/jest (version: 26.6.1)
[Web]
[Web] Manually installing incompatible versions is known to cause hard-to-debug issues.
[Web]
[Web] If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
[Web] That will permanently disable this message but you might encounter other issues.
[Web]
[Web] To fix the dependency tree, try following the steps below in the exact order:
[Web]
[Web]   1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
[Web]   2. Delete node_modules in your project folder.
[Web]   3. Remove "jest" from dependencies and/or devDependencies in the package.json file in your project folder.
[Web]   4. Run npm install or yarn, depending on the package manager you use.
[Web]
[Web] In most cases, this should be enough to fix the problem.
[Web] If this has not helped, there are a few other things you can try:
[Web]
[Web]   5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
[Web]      This may help because npm has known issues with package hoisting which may get resolved in future versions.
[Web]
[Web]   6. Check if /Users/tiagobandeira/dev/apollo-server-express-no-auth/node_modules/jest is outside your project directory.
[Web]      For example, you might have accidentally installed something in your home folder.
[Web]
[Web]   7. Try running npm ls jest in your project folder.
[Web]      This will tell you which other package (apart from the expected react-scripts) installed jest.
[Web]
[Web] If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
[Web] That would permanently disable this preflight check in case you want to proceed anyway.
[Web]
[Web] P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
[Web]
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[Web] yarn --cwd packages/web test --ci --watchAll=false exited with code 1

Could either set the jest version at the root to 26.6.0 to match react-scripts or set the jest version in the eslint-plugin-create-full-stack. I'm going with the latter since that's one fewer dependency

heard about the project through the hasura newsletter, you were the featured project
I'd like to hear your thoughts on why you decided to include the eslint config through a package.
personally I like my dependencies to be a bit more declarative, even if it is more verbose. having to dig through an additional layer of dependencies to determine why eslint is acting weird (which happens all the time) is a little cumbersome.

Nice!
I did it to follow the CRA model:
https://github.com/facebook/create-react-app/tree/master/packages/eslint-config-react-app
It's a trade-off. CRA hides babel, webpack and eslint configs from you to make the project simpler to navigate while still allowing you to override a lot of the settings. It's one more layer to dig through but ideally if it works as it should then only experts need to dig into it and novices feel more comfortable.

fair enough, its a design choice, nothing wrong with it.
more recently I've been encouraging my devs to adhere to cra as closesly as possible, I tend to reject pr's that start messing with it because I like getting the free incremental improvements from the cra team.


[cPP ENHANCEMENT] Adding SHA3/SHAKE

SHA3 is not a viable option yet. SHA3 is required in order to permit SHAKE, which is required in order to support Ed448 (as per #325).  This request purposefully only adds SHA3 to the FCS_COP.1/Hash and does not affect FCS_COP.1/KeyedHash, FCS_RBG_EXT.1, or any cryptographic protocol SFR.  A new optional SFR is included, FCS_COP.1/XOF to cleanly separate the SHA family of hashing functions from the differences in the SHAKE XOFs while not creating too much differences in the normal FCS_COP.1/Hash we've come to get used to.
Recommend the following changes to the cPP:
FCS_COP.1/Hash
FCS_COP.1.1/Hash The TSF shall perform cryptographic hashing services in accordance with a specified cryptographic algorithm [selection: SHA-1, SHA2-256, SHA2-384, SHA2-512, SHA3-256, SHA3-384, SHA3-512] and cryptographic key sizes [assignment: cryptographic key sizes] and message digest sizes [selection: 160, 256, 384, 512] bits that meet the following: ISO/IEC 10118-3:2018.
[To be considered an optional SFR]
FCS_COP.1/XOF
FCS_COP.1.1/XOF The TSF shall perform cryptographic extendable-output functions in accordance with a specified cryptographic algorithm [selection: SHAKE128, SHAKE256] and cryptographic key sizes [assignment: cryptographic key sizes] and output sizes in the range of [assignment: lower to upper range] bits that meet the following: FIPS PUB 202.
Application Note: This SFR must be claimed when Ed448 is claimed from FCS_COP.1/SigGen.  It is permissible for the lower and upper range to be identical, such as defining a fixed output length.
For the SD, update the test AAs to include the following:
FCS_COP.1/Hash
Modify the existing test specifications to label the existing "Short Messages Test", "Selection Long Messages Test" and "Pseudorandomly Generated Messages" tests as applicable only to SHA and SHA2.  The preamble describing the modes the test cases can operate in is applicable to all SHA, SHA2 and SHA3 implementations.
[conditional: for SHA3 only]
Short Messages Test- Bit-oriented Mode
The evaluators devise an input set consisting of m+1 messages, where m is the rate of the hash algorithm. The length of the messages range sequentially from 0 to m bits (or 1 to m bits, if zero-length is not supported by the hash function). The message text shall be pseudorandomly generated. The evaluators compute the message digest for each of the messages and ensure that the correct result is produced when the messages are provided to the TSF.
Short Messages Test- Byte-oriented Mode
The evaluators devise an input set consisting of m/8+1 messages, where m is the rate of the hash algorithm. The length of the messages range sequentially from 0 to m/8 bytes (or 1 to m/8 bytes, if zero-length is not supported by the hash function), with each message being an integral number of bytes. The message text shall be pseudorandomly generated. The evaluators compute the message digest for each of the messages and ensure that the correct result is produced when the messages are provided to the TSF.
Selected Long Messages Test- Bit-oriented Mode
The evaluators devise an input set consisting of 100 messages. Each message ranges in Len size from rate+(rate+1) <= Len <= rate+(100*(rate+1) ) incrementing by rate+1. The evaluators compute the message digest for each of the messages and ensure that the correct result is produced when the messages are provided to the TSF.
Selected Long Messages Test- Byte-oriented Mode
The evaluators devise an input set consisting of 100 messages. Each message ranges in Len size from rate+(rate+8) <= Len <= rate+(100*(rate+8) ) incrementing by rate+8. The evaluators compute the message digest for each of the messages and ensure that the correct result is produced when the messages are provided to the TSF.
Pseudorandomly Generated Messages Test
This test is for byte-oriented implementations only. The evaluators randomly generate a seed that is n bits long. The seed is used as the initial input to the hashing function.  The evaluators then formulate a set of 100 messages and associated digests by following the algorithm provided in [SHA3MCT-ACVP]. The evaluators then ensure that the correct result is produced when the messages are provided to the TSF.
NOTE: Add https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.html#name-sha3-monte-carlo-test as the reference to [SHA3MCT-ACVP] in section 7 of the cPP as it defines an updated algorithm after SHA3VS was published.
Large Data Test
The evaluators devise an input set consisting of messages which are equal to or larger than 2^33 bits.  The message text can be generated psuedorandomly or use a repeating bit pattern.  The evaluators then ensure that the correct result is produced when the messages are provided to the TSF.
NOTE: Unfortunately, the SHA3VS document in https://csrc.nist.gov/CSRC/media/Projects/Cryptographic-Algorithm-Validation-Program/documents/sha3/sha3vs.pdf doesn't describe the large message test as this was added after the fact. The large message test is rationalized in https://eprint.iacr.org/2019/1421.pdf and instantiated using NIST's ACVP validation system.  Details were pulled from https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.html#name-large-data-tests-for-sha-3.
[To be considered an optional SFR]
FCS_COP.1/XOF
TSS
The evaluator shall check that the association of the XOF with other TSF cryptographic functions (for example, the digital signature verification function) is documented in the TSS.
AGD
The evaluator checks the AGD documents to determine that any configuration that is required to configure the required XOF output size is present.
Tests
The TSF XOF must be capable of fixed-length output and can be implemented in one of two modes. The first mode is the byte-oriented mode. In this mode the TSF processes messages that are an integral number of bytes in length; i.e., the length (in bits) of the message to be processed is divisible by 8. The second mode is the bit-oriented mode. In this mode the TSF processes messages of arbitrary length. As there are different tests for each mode, an indication is given in the following sections for the bit-oriented vs. the byte-oriented tests.  In all cases the length of the output must be the length of the security strength (128 bits for SHAKE128 and 256 bits for SHAKE256).
The evaluator shall perform all of the following tests for each XOF algorithm implemented by the TSF and used to satisfy the requirements of this PP.
Short Messages Test- Bit-oriented Mode
The evaluators devise an input set consisting of 2*m+1 messages, where m is the rate of the XOF algorithm. The length of the messages range sequentially from 0 to m bits (or 1 to m bits, if zero-length is not supported by the hash function). The message text shall be pseudorandomly generated. The evaluators compute the output for each of the messages and ensure that the correct result is produced when the messages are provided to the TSF.
Short Messages Test- Byte-oriented Mode
The evaluators devise an input set consisting of 2*m/8+1 messages, where m is the rate of the XOF algorithm. The length of the messages range sequentially from 0 to m/8 bytes (or 1 to m/8 bytes, if zero-length is not supported by the XOF), with each message being an integral number of bytes. The message text shall be pseudorandomly generated. The evaluators compute the output for each of the messages and ensure that the correct result is produced when the messages are provided to the TSF.
Selected Long Messages Test- Bit-oriented Mode
The evaluators devise an input set consisting of 100 messages. Each message ranges in Len size from rate+(rate+1) <= Len <= rate+(100*(rate+1) ) incrementing by rate+1. The evaluators compute the output for each of the messages and ensure that the correct result is produced when the messages are provided to the TSF.
Selected Long Messages Test- Byte-oriented Mode
The evaluators devise an input set consisting of 100 messages. Each message ranges in Len size from rate+(rate+8) <= Len <= rate+(100*(rate+8) ) incrementing by rate+8. The evaluators compute the output for each of the messages and ensure that the correct result is produced when the messages are provided to the TSF.
Pseudorandomly Generated Messages Test
This test is for byte-oriented implementations only. The evaluators randomly generate a seed that is 128 bits long. The seed is used as the initial input to the XOF.  The evaluators then formulate a set of 100 messages and associated digests by following the algorithm provided in [SHA3MCT-ACVP]. The evaluators then ensure that the correct result is produced when the messages are provided to the TSF.
NOTE: Add https://pages.nist.gov/ACVP/draft-celi-acvp-sha3.html#name-sha3-monte-carlo-test as the reference to [SHA3MCT-ACVP] in section 7 of the cPP.
Variable Output Test - Bit-oriented Mode
The evaluators will devise an input set consisting of messages corresponding to the security strength of the XOF, i.e., for SHAKE128, the input message length will be 128 bits; for SHAKE256, the input message length will be 256 bits.  Given an output bit range between MinRange and MaxRange bits, read the message into the XOF algorithm and generate the output of the given output length.
Variable Output Test - Byte-oriented Mode
The evaluators will devise an input set consisting of messages corresponding to the security strength of the XOF, i.e., for SHAKE128, the input message length will be 128 bits; for SHAKE256, the input message length will be 256 bits.  Given an output bit range between MinRange and MaxRange bits, such that the output is a multiple of 8 bits, read the message into the XOF algorithm and generate the output of the given output length.

I'd suggest the MINT obtain buy-in from NIAP before proceeding with this.  Neither SHA-3 nor SHAKE are approved for use in CNSA as a hash algorithm.


kitty: disable update check machanism

Motivation for this change
kitty has its own update notification mechanism which should probably be disabled when the package is managed by a package manager such as nix. See https://sw.kovidgoyal.net/kitty/build.html#note-for-linux-macos-packagers.
Things done

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

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

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

Notify maintainers
cc @tex @rvolosatovs @Ma27

Thanks! Backported as 2b2ab759327c4504506c342644374493496c3bbb.


Use 2017 in license header in the new files.

Happy new year!

Only new files should be updated. Existing files should retain the year that they were created.

Btw, the license check will fail if you do this...
I have a fix ready in a different PR, but I'll split it into another CL now so nobody else has to redo my work.

Is this taken care of now?

Yes, this should be fixed.


feat: add miracl as retrieval task

model
ndcg@10
evaluation_time (seconds)

multilingual-e5-base
80.22 %
17.13

multilingual-e5-large
82.01 %
52.19

we need to figure out how to handle the languages first
Totally agree

@guenthermi Regarding the multilinguality: The abstract AbsTaskRetrieval class in MTEB currently doesn't support multilingual retrieval datasets, but I did extend it in the long-douments fork to do that: https://github.com/jina-ai/mteb-long-documents/blob/0b6b00eca96b5d9f62a80eb35d7176a99e91306e/mteb/abstasks/AbsTaskRetrieval.py

No it's not merged. I added it for the code tasks, which have neither been merged into MTEB nor into the master branch of the long-documents fork.


Alert: updated in accordance to design review

By creating this pull request you agree to the terms in CONTRIBUTING.md.
https://github.com/Infineon/.github/blob/master/CONTRIBUTING.md
--- DO NOT DELETE ANYTHING ABOVE THIS LINE ---
Issue 1: The height was already 48px. Furthermore, the height is not fixed. It is adjusted to content. Height in Figma is not fixed either.
Issue 2: Removed the 'success' color variant.
Issue 3: Left for version 2.

📦 Published PR as canary version: 20.18.0--canary.498.c0079b2faebef6009d9dd7f947fb10b48c50bcdb.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

looks good (y)


Add Onivim to ECD Tools Adopters Page for Open VSX

The Eclipse Cloud Developer Tools (ECD Tools) adopters page is now live at https://ecdtools.eclipse.org/adopters/.
As an adopter of the Open VSX Registry, we would love to see Onivim listed there.
Instructions on how to get listed are at https://ecdtools.eclipse.org/adopters/how-to-be-listed-as-an-adopter/.

Hi @brianking ,
Thanks for reaching out, would be great to have Onivim listed there! I've opened a PR and signed the necessary agreements: https://github.com/EclipseFdn/eclipsefdn-project-adopters/pull/59
Let me know if there is anything else you need from me 👍

Hi @brianking ,
Thanks for reaching out, would be great to have Onivim listed there! I've opened a PR and signed the necessary agreements: https://github.com/EclipseFdn/eclipsefdn-project-adopters/pull/59
Let me know if there is anything else you need from me 👍

Excellent, thanks.

Excellent, thanks.


Support renter upload/download when client and server are separate systems

The following /renter APIs are difficult to use in scenarios where the renter application is not running on the same system as the siad server:

/renter/download/*siapath
/renter/downloadasync/*siapath
/renter/upload/*siapath

The problem is that the "local" paths in the API are the paths on the siad system rather than the API client system.
As an app developer, I'd like a /renter/upload API where I can give siad the file data and the siapath and Sia just processes the upload.
Possible workarounds I can think of for now:

Make sure siad and Sia client application share a filesystem and only upload/download files on that filesystem.
Add a layer on top of the Sia client that moves files between the siad system and the client system.

We have implemented limited support for streaming downloads over HTTP. Uploads are trickier because they force the renter to use a sequential upload algorithm. You also have the problem of resuming; how do you resume an upload that was initiated over HTTP? It's doable but there's a fair amount of logic involved.
But on the whole, streaming uploads/downloads is an important feature, and will likely only become more important as the network matures.

We could upload the entire file in an API request, and have the renter write the file out to disk and keep it locally until the upload is complete. This way, all of the renter's uploading and repair algorithms remain unchanged, the API client simply has to send all of the file data over HTTP to the backend, instead of supplying the path to the file.

Label "Feature Request"


Example in robyn.md does not work

When I start the code in https://github.com/psqlpy-python/psqlpy/blob/main/docs/usage/frameworks/robyn.md it does not serve

Hello!
I'll look into it, maybe robin was updated)


Move runners.core.fn to java-fn-execution

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Make sure there is a JIRA issue filed for the change (usually before you start working on it).  Trivial changes like typos do not require a JIRA issue.  Your pull request should address just this issue, without pulling in other changes.
[ ] Each commit in the pull request should have a meaningful subject line and body.
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Run mvn clean verify to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

This separates out utilities to interact with the Fn APIs, removing any
introduced dependency on the Beam Java SDK.

R: @kennknowles


How does the newly installed ionic interact with android?There is no exec () method?

**Ionic version:**  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use

[

[ ] @1.

](https://github.com/ionic-team/ionic-v1))
[ ] 2.x
[ ] 3.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Expected behavior:

Steps to reproduce:

Related code:
insert any relevant code here

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here

Hello! Thanks for opening an issue with us! As this seems like more of a support question I will urge that you ask this question on our forum or on our slack channel. Thanks for using Ionic!


Provide the dataset as a release

If we distribute the dataset (or model) as a release, we have a much bigger threshold for the file size (2 GB instead of 100 MB).

Each file included in a release must be under 2 GB. There is no limit on the total size of a release, nor bandwidth usage.

https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases#storage-and-bandwidth-quotas

The SNUSR dataset is released as a draft here:
https://github.com/mlcommons/mobile_models/releases/tag/untagged-adb45e94db8a258b27b7
After confirming that the files are ok I will make it public.

If I should put more information in the description, please advice.

these files looks good to me.

looks good to me!

Let's make this zip file publicly available.

Published


java.lang.Double cannot be cast to java.lang.String and evaluating TextRecognition.recognize

I created a clean react native project and i get this error when i use your package.
'java.lang.Double cannot be cast to java.lang.String'
I also got an error that says 'null is not an object ("evaluating TextRecognition.recognize'')'
App.js
import React, {useState, useEffect} from 'react';
import {SafeAreaView, StatusBar, Text, View} from 'react-native';
import TextRecognition from 'react-native-text-recognition';
import testImage from './src/assets/testImage.jpg';

const App = () => {
  const [text, setText] = useState('');

  useEffect(() => {
    (async () => {
      try {
        const result = await TextRecognition.recognize(testImage);

        setText(result);
      } catch (e) {
        console.log(e);
      }
    })();
  }, []);

  return (
    <SafeAreaView>
      <StatusBar />
      <View>
        <Text>Hello World</Text>
        <Text>{text}</Text>
      </View>
    </SafeAreaView>
  );
};

export default App;

Is this on the ML branch or the main branch?

I'm using the main branch, i'll check out the ml branch now to see if it will work.

I'm still getting the same error even on ML branch.

What is the image you are using and what Android version? I've only tested Android 10 and 11.

ext {
buildToolsVersion = "30.0.2"
minSdkVersion = 21
compileSdkVersion = 30
targetSdkVersion = 30
ndkVersion = "21.4.7075529"
}
The image is: https://ak.picdn.net/shutterstock/videos/1039447646/thumb/1.jpg
I think this is a version problem. Can you create a react native project that's working and i'll just fork it or something.

Oh i get it, I should be using an image directly from the filesystem right? That's why it causes this problem most likely.
Does this work with expo btw?

 What you should do is get an the file path from an actual image from your phone. Sorry for opening an issue for this, my bad.


[FLOC 3362] add context to Enabling control service doc

Fixes 3362
Adds an explanation of why you need to enable the control service.

Thanks.  Just one minor suggestion inline.  Address as you like and then merge when the doc builder is green.


npm run transform-tokens cant find "global" form figma plugin export

"Reference doesn't exist: global.color.primary-base.value tries to reference brand.accenture.primary-base, which is not defined"
Once the figma Plugin creates this "Global" key, the token-transformer can't find it, I'm including it manually

to this:

{
  "global": {
    "brand": {
      "accenture": {
        "primary-base": {
          "value": "#A100FF",
          "type": "color",
          "description": "Base Accenture Color"
        },
        "secondary": {
          "value": "#0041F0",
          "type": "color"
        }
      }
    },
    "color": {
      "primary-base": {
        "value": "{brand.accenture.primary-base}",
        "type": "color"
      }
    },
    "black": {
      "12": {
        "value": "rgba(0,0,0,0.12)",
        "type": "color"
      },
      "25": {
        "value": "rgba(0,0,0,0.25)",
        "type": "color"
      },
      "50": {
        "value": "rgba(0,0,0,0.5)",
        "type": "color"
      },
      "85": {
        "value": "rgba(0,0,0,0.85)",
        "type": "color"
      },
      "100": {
        "value": "#000",
        "type": "color"
      }
    }
  },
  "font": {},
  "$themes": [],
  "$metadata": {
    "tokenSetOrder": [
      "global",
      "font"
    ]
  }
}

Hey @TBrayner,
the plugin does not by itself include a global key. This must be your to level in figma. Is that correct?
You need to write the entire path out in the references. I hope that helps, otherwise please clarify the question.


Hook that fires after each cycle

I'd really like a hook cycle that is executed after each run cycle, supplied in the constructor just like the setup & teardown hooks. Some benchmarking code needs to reset state after the benchmarking test function itself is called.
const bench = new Bench({
  cycle: () => {
    [...]
  }
});

I can implement this myself if you give me the go-ahead.

Sure, I'd like you to implement it, but the thing is where it should be used. And could you give a strong example? The reason I'm asking this is that I want to put the minimum amount of features into tinylibs so they don't get out of the Minimal stage.
But from my side, I love this feature. We just need to discuss it more.

I need this feature because I'm benchmarking a database (more specifically, BlinkDB) where state must be reset after an insertMany, else the operation fails because of clashing primary keys.
In order to prevent duplicate primary keys, current code has to look like this:
...
let users: User[] = ...;

const bench = new Bench()
  .add("lokijs", () => {
    const newUsers = users.map(u => ({ ...u, id: 10000 * lokiIndex + u.id }));
    lokiIndex++;

    lokiUserTable.insert(newUsers);
  })
  .add("blinkdb", async () => {
    const newUsers = users.map(u => ({ ...u, id: 10000 * blinkIndex + u.id }));
    blinkIndex++;

    await insertMany(blinkUserTable, newUsers);
  });

This is brittle, obviously skews the results, and doesn't look all that great.
It'd be much cleaner with a simple cycle hook:
...
let users: User[] = ...;

const bench = new Bench({
  cycle: async () => {
    lokiUserTable.clear();
    await clear(blinkUserTable);
  }
})
  .add("lokijs", () => {
    lokiUserTable.insert(users);
  })
  .add("blinkdb", async () => {
    await insertMany(blinkUserTable, users);
  });

Nice, I see. The question is, does cycle run also before each case or only
after, and why?
On Mon, 20 Feb 2023, 10:49 Fröhlich A., @.***> wrote:

I need this feature because I'm benchmarking a database (more
specifically, BlinkDB https://github.com/blinkdb-js/blinkdb) where
state must be reset after an insertMany, else the operation fails because
of clashing primary keys.
In order to prevent duplicate primary keys, current code has to look like
this
https://github.com/blinkdb-js/blinkdb/blob/feature/benchmarking/packages/benchmarks/src/benchmarks/blinkdb/insert-many.ts
:
...let users: User[] = ...;
const bench = new Bench()
.add("lokijs", () => {
const newUsers = users.map(u => ({ ...u, id: 10000 * lokiIndex + u.id }));
lokiIndex++;
lokiUserTable.insert(newUsers);

})
.add("blinkdb", async () => {
const newUsers = users.map(u => ({ ...u, id: 10000 * blinkIndex + u.id }));
blinkIndex++;
await insertMany(blinkUserTable, newUsers);

});
This is brittle, obviously skews the results, and doesn't look all that
great.
It'd be much cleaner with a simple cycle hook:
...let users: User[] = ...;
const bench = new Bench({
cycle: async () => {
lokiUserTable.clear();
await clear(blinkUserTable);
}})
.add("lokijs", () => {
lokiUserTable.insert(users);
})
.add("blinkdb", async () => {
await insertMany(blinkUserTable, users);
});
—
Reply to this email directly, view it on GitHub
https://github.com/tinylibs/tinybench/issues/31#issuecomment-1436469079,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBMICCTX4FZ4HQMJTH232LWYMLH7ANCNFSM6AAAAAAUY3E4VQ
.
You are receiving this because you commented.Message ID:
@.***>

In my case, it doesn't matter - But I'd prefer after each cycle. If you have code that specifically needs to run before the first test case, you can just call it before starting the benchmark. Also, Benchmark.js handles it similarly.

Thank you so much for the reference, let's have a PR if you want to work on
it, and let's move the discussion there.
On Mon, 20 Feb 2023, 12:19 Fröhlich A., @.***> wrote:

In my case, it doesn't matter - But I'd prefer after each cycle. If you
have code that specifically needs to run before the first test case, you
can just call it before starting the benchmark. Also, Benchmark.js handles
it similarly https://benchmarkjs.com/docs/#options_onCycle.
—
Reply to this email directly, view it on GitHub
https://github.com/tinylibs/tinybench/issues/31#issuecomment-1436562476,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBMICFBIMVKB3BNJ75OZ5DWYMVZNANCNFSM6AAAAAAUY3E4VQ
.
You are receiving this because you commented.Message ID:
@.***>

@froehlichA See #33, it's not complete and i'll review it later. but we can have:
beforeAll: which fallbacks to setup
afterAll: which fallbacks to teardown
beforeEach: like vitest/jest beforeEach, which runs before each time a case starts
afterEach: like `cycle`, but with different name, and similar to beforeEach, but runs after each case

cc @achingbrain

Landed in #33, Let me know your opinion.


Update RIDs for uniformity, remove unsupported OS

Minor changes to update the RIDs and add convenience comments for users to better understand that the list is not exhaustive and there are potentially more targets available. Updated formatting to keep consistency.
I didn't update the Android section to include a Portable entry since I'm not sure if android is portable with the .NET Core 2.0 minimum requirement. The macOS section is more cluttered with the reformatting so I'd be open to compressing it again but it looks odd having a Portable option with indented RID and the others being at the Portable level. I also liked including the OS names which people typically remember more than they do the numeric representation.
For macOS 10.10 Yosemite I don't see it listed as supported or unsupported but it was in the original document and exists in the runtime.json file so I did not remove it but I wonder if it should be removed.
Summary
Updated the Using RIDs section and those below.

Removed comment about omitting some architectures so the linux-arm target could be included (for Raspberry Pi reference below).
Added a comment below each OS section to repeat the note that the list is not complete and includes a link to the JSON file with all targets.
Added a note below Linux RIDs to mention Raspberry Pi specifically since some users do not understand the distinction between OS and architecture as evidenced by issues and questions I get when doing presentations on .NET Core.
Alpha-sorted the Linux distributions as the list has gotten long and looked as though it was intended to be alpha-sorted. This improves discoverability of available targets. The sorting is based on the name, not the RID.
Removed Ubuntu 17.10 as it's marked as no longer supported.
Reformatted the macOS section to mirror the other sections including the addition of a Portable section.
All Portable sections got a note explicitly that they are supported in .NET Core 2.0 and later.

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

//cc @terrajobst

I think @richlander would be more qualified to review this.

@ErikNoren - @jkotas left some good feedback. Can share your plans to resolve that?

@richlander I saw the comments and can absolutely make the changes but they came just before I started international travel with severely limited access. I will review again when I return home the second week of December. I will check to see if anything is announced at Connect(); that would impact the changes at that time as well.

I've made the changes I understood and resolved the conversations on those (I hope that was right; I didn't find any documentation guidance on what to do with those) but left open 2 where I have a question or want review feedback. This is my first time doing a pull for such a large, active repository so I apologize for mistakes I might make.

All review items from @jkotas have been incorporated and committed.

Is there anything else I need to do? This is my first contribution and I'm not sure if I'm all done and this is waiting for some final approval to pull or if I was supposed to do something else.  @richlander

@jkotas do we need anyone else to review this?

@richlander may want to take a look.

Also, is the removal of rhel.7-x64 intentional?

Yes, we have kept only the common values that are likely to be used in practice:

rhel.7-x64 is equivalent to linux-x64. We recommend to use linux-x64 as much as possible, and not really use distro specific RIDs like rhel.7-x64.
rhel.6-x64 is not equivalent to linux-x64. It is why it was kept as common value.

Note that all the RIDs that have been removed from the list in this doc are still in the big .json file with the whole RID graph linked from the docs.

Cool. So I'll resolve the merge conflicts and update the metadata and merge this. Thanks everyone!


Vue 'watch' has different performance in SSR and SPA

When enter a page for the first time, SSR and SPA perform different.
I know, SSR will return a static HTML for the first time, then Hydrate(active) the page.
But still I can't figure out
For SSR:
export default {
  asyncData() {
    return {
      paramA: {}
    }
  },
  data() {
    return {
      paramB: {}
    }
  },
  watch: {
    paramA: function(newValue) {
       console.log('paramA', newValue) // won't print unless 'immediate: true'
    },
    paramB: function(newValue) {
       // Here is what i'm confusing
       // will print whether 'immediate: true' or not, **Why?**
       console.log('paramB', newValue)
    }
  }
}

For Pure Vue SPA:
export default {
  data() {
    return {
      paramC: {}
    }
  },
  watch: {
    paramC: function(newValue) {
       console.log('paramC', newValue) // won't print unless 'immediate: true'
    }
  }
}

This question is available on Nuxt.js community (#c2673)

@fxxjdedd I believe that's because when paramB is merged into the object in SSR, the watcher is already set up.

I think because in SSR there's a state object sent from the server, which is then applied (causing the watcher to fire)
SPA:

data()
render on client
done

SSR:

asyncData() on server
data() on server
render on server
state payload serialized
skipped asyncData on client (?)
data() on client
state payload applied <- THIS IS YOUR PRINT
render on client
hydrating the html

so we can not watch data in ssr?

@hitao123 Of course you can. With all normal Vue usage there won't be any difference.


Swift3

Added estonian.

Has conflicts. If someone fixes I'll auto-merge.

@MaeseppTarvo could you resolve conflicts for swift 3 branch please? Thanks

@kgn I resloved conflicts and created one pull request to your fork and one here... please merge yours and then this pull request wont have any merge conflicts, or @kevinlawler please merge my new Swift 3 pull request and then this one can be closed, thanks


Investigate sphinx-autoapi warning

We keep getting this warning:
/home/docs/checkouts/readthedocs.org/user_builds/poliastro/envs/1073/lib/python3.7/site-packages/autoapi/extension.py:137: RemovedInAutoAPI2Warning: autoapi_template_dir will be expected to be  relative to conf.py instead of relative to where sphinx-build is run

This warning is evident as the Search functionality of the documentation doesn't work. I am trying to find out how we can overcome this & will update the same :smile:

This warning is evident as the Search functionality of the documentation doesn't work. I am trying to find out how we can overcome this & will update the same :smile:

This has been fixed via #1090

This has been fixed via #1090

Indeed!

Indeed!


reduce dependence on external data servers

Describe the bug
We download some of our data directly from external servers every time we run a simulation. This causes problems, e.g. when those servers are down we can't download data and can't run our simulations. We can address this by fully switching to use ClimaArtifacts.
SNOTEL data bug description
Suddenly I get a docs failure on two separate branches that don't make any changes in docs/. It comes from docs/tutorials/standalone/Snow/data_tutorial.jl and seems to be due to a dimension mismatch when creating a dataframe.
ERROR: LoadError: LoadError: DimensionMismatch: Length of nms doesn't match length of x.
in expression starting at /home/runner/work/ClimaLand.jl/ClimaLand.jl/docs/src/generated/standalone/Snow/data_tutorial.md:2
when executing the following code block from inputfile `~/work/ClimaLand.jl/ClimaLand.jl/docs/tutorials/standalone/Snow/data_tutorial.jl`

metadata = DataTools.snotel_metadata();
metacols = ["id", "state", "elev", "lat", "lon"]
DataFrames.rename!(metadata, Symbol.(metacols));

Failing Github actions:

on js/regridder_type
on js/imp-interface

To Reproduce
Ideally a minimal reproducible example:
# some code here

Or even better, add it as a unit test, and open pull request.
Project

If not using the `examples` project:
```
paste your Project.toml here.
```
```
paste your Manifest.toml here.
```

System details
Any relevant system information:

Julia version
operating system
modules loaded on cluster (module list)

Related issues / PRs
Please add any relevant links.

There were probably server issues. I meged the PR.
I think that the real issue is that we should try to avoid depending on an external server if the data we use is always the same.

There were probably server issues. I meged the PR.
I think that the real issue is that we should try to avoid depending on an external server if the data we use is always the same.

Agreed, I updated this issue to highlight that

will be resolved as we move to ClimaArtifacts - see #580

My understanding is that part of the Snow code is supposed to grab and process whatever data the user from Snotel wants.
I also think that we had issues with the MODIS servers at some point. I am not sure where we access them.


Rename submodule under cupy.fft package

Rel #3420.
This PR renames cupy.fft.fft submodule to cupy.fft._fft to indicate that it is CuPy's private submodule and not intended to be used by users.

Need to merge with master 🙂 btw this PR blocks #3896.

Merged with master!

Thanks! There seems to be a few flake8 errors 🙂

@takagi Could you check Travis failure?

cupy.fft.config should be a public submodule? Numpy does not have its counterpart, butv it is used by users to control the behavior of cupy.fft features.

@takagi Yes, it is a public submodule. There is a helper function documented in https://docs.cupy.dev/en/latest/reference/generated/cupy.fft.config.set_cufft_gpus.html.

Yeah, and there's also an enable_nd_planning flag.

I also plan to expose a few cache-related APIs to the confit module in #3730.

Jenkins, test this please

Jenkins CI test (for commit 7866df640329fad25fd2d2446699eaf20079fa9a, target branch master) failed with status FAILURE.

I'll fix the CI failure.

pfnCI, test this please.

Jenkins CI test (for commit 9bf59cb305ac81f581b6e7dc8ee7a14d7ccdaa9c, target branch master) succeeded!

@takagi Could you resolve conflicts?

pfnCI, test this please.

Jenkins CI test (for commit f003df3f684829530ede2635f22f057bd03abd34, target branch master) succeeded!

LGTM.


External vision XY initialization and tracking

At initialization LPOS.X and LPOS.Y take way too long to converge to values sent by external vision. (Probably because aircraft is stationary but not at origin when EKF2 starts, so external vision is sending in non zero values.)

And they oscillate on external vision reset to new value:

External vision data is fused with 1cm variance.

Full log file can be found at http://wikisend.com/download/174296/log001.px4log

Fixed in master


Fix #58: LANG issue

With this PR, TP.jl should work for all LANG values at the expense of only supporting the online/offline CPUs feature for LANG=en systems. Seems like a reasonable tradeoff, at least for now.
Closes #58

Merge after CI


Invalid Content-Length header when using form data with custom stream

Summary
When providing a custom stream to the formData option, the  Content-Length header of the post request is not computed properly which leads to incorrect interpretation by the target server.
Granted, this is mostly an issue with form-data, but I believe request should at least warn its users about this potential pitfall.
Similar to https://github.com/request/request/issues/446 but I believe using a file stream works properly in form-data now.
Simplest Example to Reproduce
Probably not the simplest, but here's one example with ffmpeg-stream:
const { Converter } = require('ffmpeg-stream');
const request = require('request');

const audioConverter = new Converter();
const converterInput = audioConverter.createInputFromFile('./test.wav');
const converterOutput = audioConverter.createOutputStream({f: 'mp3'});

audioConverter.run(); // Not waiting for it to complete since it expects someone to read the stream, which we do after
request({
  method: 'POST',
  url: 'http://<IP_ADDRESS>:7777',
  formData: {
    audio: {
       value:converterOutput,
       options:{filename:'aa.mp3', contentType:'audio/mp3'}
    }
  }
});

In another terminal, start netcat -l -p 7777 to see the raw request:
POST / HTTP/1.1
host: <IP_ADDRESS>:7777
content-type: multipart/form-data; boundary=--------------------------111914189062304585333080
content-length: 204
Connection: close

----------------------------111914189062304585333080
Content-Disposition: form-data; name="audio"; filename="aa.mp3"
Content-Type: audio/mp3

.... file content.....
----------------------------111914189062304585333080--

Expected Behavior
The Content-length header shall be set properly, or not set at all. One can achieve this by setting knownLength manually, but that's cumbersome. In my case it requires me to use a buffered stream:
const converterOutput = audioConverter.createBufferedOutputStream({f: 'mp3'});

Then set the property:
knownLength: converterOutput.readableLength,

Current Behavior
The Content-Length header is computed as if the file length was 0.
Possible Solution
A few ideas:

Don't set the content-length header (see https://github.com/form-data/form-data/pull/382/files)
Buffer the whole stream then compute the content-length header properly
Mention in the readme that value should be either a request object or a fs stream. When using a custom stream, options.knownLength should be set.

Context
Trying to send a file converted on the fly in a POST request.
Your Environment

software
version

request
2.88.0

node
13.6.0

npm
6.13.4

Operating System
Mac OS Catalina 10.15.2

I'd like this issue to remain open since it pinpoints unexpected behaviour


21k Pretrain weight

Could you please release the ResNet101 pretrained weights with ImageNet21K or tell us where can we find it?
Thank you!

Hi I think the ViT paper does provide those weights.

Hi @lzrobots
Sorry for bothering you, I have searched the official ViT repo, but I can't find the weights..
https://github.com/google-research/vision_transformer/issues/36
https://github.com/google-research/big_transfer/issues/21
Could you please provide a link?

you might get the weights from the readme file of the BiT repo you mentioned above.


WIP: add catalog-info for backstage

related to https://github.com/DiamondLightSource/blueapi/issues/113

This should not be merged until https://github.com/DiamondLightSource/blueapi/pull/135 is merged.

AsyncAPI yaml file has now been added at docs/user/reference/asyncapi.yaml, so please add a reference to this to the cataloginfo file. Also please put your openAPI file in the same folder and update the reference to it accordingly.

Be nice to have this validator for the catalog-info, but I'm happy to add it once this is over the line

Also be good to add
annotations:
    github.com/project-slug: DiamondLightSouce/blueapi

to the component>metadata section so that the CI and other stuff is visble in backstage


Getting a deprecation message when running Postgraphile

I'm running Postgraphile as a Docker container, and checking its log I get this:
Attaching to my-graphql
my-graphql | 2021-09-19T16:50:59.220839688Z
my-graphql | 2021-09-19T16:50:59.221256604Z PostGraphile v4.11.0 server listening on port 5000 🚀
my-graphql | 2021-09-19T16:50:59.221295437Z
my-graphql | 2021-09-19T16:50:59.221591887Z   ‣ GraphQL API:         http://<IP_ADDRESS>:5000/graphql (subscriptions enabled)
my-graphql | 2021-09-19T16:50:59.221601435Z   ‣ GraphiQL GUI/IDE:    http://<IP_ADDRESS>:5000/graphiql
my-graphql | 2021-09-19T16:50:59.221605432Z   ‣ Postgres connection<EMAIL_ADDRESS>(watching)
my-graphql | 2021-09-19T16:50:59.221612966Z   ‣ Postgres schema(s):  business
my-graphql | 2021-09-19T16:50:59.221616172Z   ‣ Documentation:       https://graphile.org/postgraphile/introduction/
my-graphql | 2021-09-19T16:50:59.221619258Z   ‣ Node.js version:     v12.20.1 on linux x64
my-graphql | 2021-09-19T16:50:59.221622244Z   ‣ Join innovation.rocks in supporting PostGraphile development: https://graphile.org/sponsor/
my-graphql | 2021-09-19T16:50:59.221625280Z
my-graphql | 2021-09-19T16:50:59.221663692Z * * *
my-graphql | 2021-09-19T16:50:59.221692126Z
my-graphql | 2021-09-19T16:51:01.586186659Z (node:1) [DEP0001] DeprecationWarning: OutgoingMessage.flush is deprecated. Use flushHeaders instead.
my-graphql | 2021-09-19T16:51:01.730630742Z 0 error(s) as anonymous_group in 127.78ms :: query IntrospectionQuery { __schema { queryType { name } mutationType { name } subscriptionType { name } types { ...FullType } directives { name description locations args { ...InputValue } } } } fragment FullType on __Type { kind name description fields(includeDeprecated: true) { name description args { ...InputValue } type { ...TypeRef } isDeprecated deprecationReason } inputFields { ...InputValue } interfaces { ...TypeRef } enumValues(includeDeprecated: true) { name description isDeprecated deprecationReason } possibleTypes { ...TypeRef } } fragment InputValue on __InputValue { name description type { ...TypeRef } defaultValue } fragment TypeRef on __Type { kind name ofType { kind name ofType { kind name ofType { kind name ofType { kind name ofType { kind name ofType { kind name ofType { kind name } } } } } } } }

There is this deprecation message [DEP0001] DeprecationWarning.
I'm using these options for Postgraphile in my docker-compose.yml:
      "--watch",
      "--jwt-secret", "keyboard_kitten",
      "--jwt-token-identifier", "business.jwt_token",
      "--dynamic-json",
      "--subscriptions",
      "--no-setof-functions-contain-nulls",
#      "--no-ignore-rbac",
#      "--no-ignore-indexes",
      "--show-error-stack=json",
      "--extended-errors", "hint,detail,errcode",
      "--enable-query-batching",
      "--legacy-relations", "omit",
      "--export-schema-graphql", "cyp_schema.graphql",
      "--enhance-graphiql"

Should I take any action for this deprecation message?

Sounds like something you should ask of postgraphile.
Closing since this is unrelated to ferry


Voyager Create new product

Version information

Laravel: v5.7
Voyager: v1.1.9
PHP: 7.2
Database: MySQL 5.7

Description

Not show user_id input when create new product use relationship with users table.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
Products Bread

products table

Result when create new product

Additional context
Add any other context about the problem here.

This is expected behavior.  When you add a relationship, it will show the defined relationship.  If that relationship depends on another field on that table (i.e. your user_id field), then it will hide that field as it is redundant.

In products list why show users?


Refs #29713 -- Improved error message from translation system check.

Ticket #29713, follow up to PR #10340.
There were a number of issues that I think needed addressing:

Some of the documentation was sorted alphabetically as requested, some of it wasn't.
The documentation for the check should have linked to the LANGUAGE_CODE documentation.
The error message was far too complicated and incorrect:

Language tags are not solely formatted as ll or ll-cc. Django supports zh-Hans, for example.
Outputting a URL is not nice - using the LANGUAGE_CODE documentation is better.
A better link would have been: https://www.w3.org/International/articles/language-tags/

The tests had some problems:

It looks as though subTest() was being used and then got removed before the push.
Not enough valid and invalid values were being tested.

This check should probably only be applied if USE_I18N = True?

See the fixup! commit. We can squash it in or scrap it if we always want to check.

I think that there are generally other problems in Django where language code (or tag) is confused with locale, a point made here. For example, I think ticket #24063 was implemented incorrectly - it should have extended to_locale(). LANGUAGE_CODE should follow BCP 47 which is what Django's documentation effectively asks for. I'll see if I can resolve some of these issues later.

Thanks for this @pope1ni. Looks great.

This check should probably only be applied if USE_I18N = True?

See the fixup! commit. We can squash it in or scrap it if we always want to check.

What's your thought? Seems reasonable to me.

So IIRC, the documentation for the LANGUAGE_CODE setting mentions that it requires USE_I18N. But looking at django.utils.translation.trans_null.get_language() it looks like the value of the setting is still returned. The question is whether this value is used outside of translations somewhere when USE_I18N = False and, if so, maybe we still want to check the value is correct?
I've not dug into this thoroughly, but I'm sure it is used for the html[lang] attribute in the admin site base template. If that is applied irrespective of the value of USE_I18N, then we should still check (and update the documentation). I plan to look into the whole language tag vs locale thing at some point...

OK. Good follow-up. 🙂
I’ll have a little look in the morning to see if I can one up with a sensible answer.

Ok. So I think that I'll drop the check for USE_I18N and I'll have a stab this evening at sorting out the rest.

I'll have a stab this evening at sorting out the rest.

Hey @pope1ni: I can't quite work out if you mean that for here, or a separate PR? (This seems a good atomic improvement so I can just merge 36c5c11eb0ebd4b779ab6ab807292635c61d4961 if you're happy.)

I meant that I'd look into other issues related to language codes/tags vs locales, etc. separately.
Have dropped the fixup! commit that introduced the USE_I18N check for now.
Otherwise this should be good to go.


Remove redundant HostUtils substitutions

This was probably required in the distant past but is likely no longer required. Lets see...

uncommitted changes in group_01, probably need a regen


"Other options" button missing???

[Enter feedback here]
Hi there,
I'm trying to create a Wiki Enterprise but the "Other Options" button isn't appearing under my "Team Site" and "Communications Site" buttons. Why is it missing?
Thanks,
Stephen G

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

ID: 0419db4c-9918-fcbe-53b3-4aca315e7703
Version Independent ID: 0eca18cd-d073-8a6c-47ba-3e3330d63167
Content: Create a site - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/create-site-collection.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Broken Extend Proxy SSLHandling  - Correct Server SSL Certificate fail with RemoteCertificateNameMismatch

Description
The SSL Handshake between Extend-Client and an SSL secured Extend-Proxy fails with RemoteCertificateNameMismatch when Certificate is correctly generated to match extend proxy host name.
Reproduce

Generate a valid SSL Certificate with a CN matching the host on which the extend proxy is running.
Secure the Extend Proxy with the SSL certificate
Configure Extend Client to connect to SSL Secured Extend Proxy
Configure Extend Client Configuration to use Tangosol.Net.SslStreamProvider.StrictCertificateValidation as the remote-certificate-validator (or write one which does not allow SSL Handshake errors)
Attempt to establish a connection between the client and proxy

The SSL handshake will fail with RemoteCertificateNameMismatch.
Expected Behaviour
The SSL handshake should succeed.
Cause
The cause of this error is due to the parameters passed to the System.Net.Security.SslStream.AuthenticateAsClient method.
In Tangosol.net.SslStreamProvider:182, the serverName is always the IP Address of the targetHost and not the Fully Qualified Domain Name of the host.
This goes back to Tangosol.net.SslStreamProvider:172 where SslStreamProvider.ServerName is not correctly initialised  at the point of creating the SslStreamProvider and is always null.
Correctly initialising the serverName with the FQDN of the remote endpoint would resolve this issue
I'm not sure about the correct place SslStreamProvider.ServerName should be initialised but a quick fix would be to replace SslStreamProvider:172
                string serverName = string.IsNullOrEmpty(ServerName)
                        ? ((IPEndPoint)client.Client.RemoteEndPoint).Address.ToString()
                        : ServerName;

with
string serverName ;
try {
   // try to get FQDN
   IPHostEntry host = Dns.GetHostEntry(((IPEndPoint)client.Client.RemoteEndPoint).Address);
   serverName = host.HostName ;
} catch (Exception x)
{
   // failed - revert to IP Address
   serverName = ((IPEndPoint)client.Client.RemoteEndPoint).Address.ToString();
   CacheFactory.Log("Failed to get FQDN for address " + serverName + " due to " + x.GetType().Name + " - " x.Message, CacheFactory.LogLevel.Warn);
}

Environment
Not Applicable.

As you mentioned in cause description the real cause is SslStreamProvider.ServerName is not initialized and to initialize ServerName correctly, you need to specify  element which was missing in the schema.
So with the recent fix in commit 5a98ec8ea17fa0b3d8cb1db3fb3d16c9fdea7fb0, now you can set the  to correctly initialized SslStreamProvider.ServerName.

Hi @chpatel3,
Looking over the fix - I'm not quite following why a new config element was needed here.  The  element allows for the specification of the  and a list of .    What should happen is that the code should go through the remote-addresses and connect to whichever one is available or the load-balancing stipulates.  If SSL is specified for the  then the X509 Certificate returned should be validated.
The validation should check the host we ended up connecting with appears in the SAN of the certificate it has supplied and that cert chain path / revocation list are trusted.  All that is needed is for the code to do a resolve the IP to it's Fully Qualified domain name.
By adding a single serverName element to the SSL aren't we limiting / complicating the configuration?  Please let me know if I've got my wires crossed here but in our use case we have multiple addresses and we won't know ahead of time which one (which serverName) we will connect to.
please let me have your thoughts.
thanks in advance + kind regards,
Kaveh.

Hi @kmgoudarzi,
So the config change that was done is for correctly initializing SslStreamProvider.ServerName.
Please look SslStreamProvider.Config.set where there was already code exists to initialize SslStreamProvider.ServerName from the config but actually that configuration part was missing in the schema.
216:                IXmlElement xmlSub = xml.GetElement("server");
217:                // configure the target server
218:                if (xmlSub != null)
219:                {
220:                    ServerName = xmlSub.GetString();
221:                }
So specifying the  in ssl config should have resolve your original issue of RemoteCertificateNameMismatch as in your original description for this issue you've mentioned correctly initialising the SslStreamProvider.serverName with the FQDN of the remote endpoint would resolve this issue.
But now the new valid use case that you bring up of having multiple addresses and don't know ahead of time which one (which serverName) we will connect to.
So here when you say multiple addresses then do you mean you've certificate with multiple identities/dns name?
Didn't specifying the  element with the wildcard e.g "*.example.com" work for you? I believe specifying the target name similar to that should have matched with SAN of the certificate.
I tried to confirm that but microsoft .NET documentation is not clear about that so could you please file the separate SR (would prefer internal one) if specifying target serverName using wildcard does not work for you.
Thanks!


The category of groupoids

Another slice of #40: the category of groupoids.
This is the "weak" version of said category, using natural iso as functor equality, just as Categories.Category.Instance.Cats. A strict version (akin to StrictCats) will follow in a separate PR.
The reason for also including the change to Categories.Morphism.IsoEquiv in this PR is that the proof of F-resp-⁻¹ uses to-unique.

This PR has been open for a while. Is there anything problematic about it?
If so, please let me know how I can improve it.

It came in when I was super-busy, and I haven't been systematic enough to go back to look at it. Thanks for the ping, I'll look at it in detail now.

I refactored the PR further, as requested by @JacquesCarette.
It now depends on #51 and #55 (see above for details).

In the latest version, Groupid and IsGroupoid are now both in Categories.Category.Groupoid, while the actual category of groupoids is in Categories.Category.Instance.Groupoids.
The reason so many files are changed is that the Categories.Category.IsGroupoid module disappeared.


[WFCORE-3801] Reorder elytron authentication factories to eliminate m…

…eaningless diffs to the galleon build
https://issues.jboss.org/browse/WFCORE-3801
@darranl FYI

Core - Full Integration Build 7286 outcome was FAILURE using a merge of 45a05692a8ec2684871214718dfa227d8c4ea99c
Summary: Execution timeout (new); tests passed: 4125, ignored: 136 Build time: 02:30:50

retest this please

Normally the re-ordering would happen in case there are dependencies that require certain resources to be added before others. Otherwise the user-defined order is preserved.