LCFS - Recommend Record and Recommend Refuse visible to Director

Log in as director
View a transfer in the submitted status that has not been recommended

Expected:
Director cannot take any actions on the report until is is recommended
Actual:
Director can see radio buttons for recommend / refuse, but no save button and buttons do nothing

When signed in as a director, I can still see the radios buttons for "Recommend record" and "Recommend refuse". This should not be the case. For transfer in "Submitted" status, the director should have no action available. Currently in the Portal, the director sees this:

In TFRS, the director can view a submitted transfer, but take no action until an analyst has recommended recording the transfer. This is what the director screen of a submitted transfer looks like in TFRS:


How about using a expo router?

We had the chance to try the Expo Router with some of our internal projects, and it seems very promising, especially since it comes with deep linking and web support by default.
If everything goes as expected, we plan to include it in the next major version.


Feature parser scenario outline with no examples

Fix for IndexOutOfBoundsException when feature parser tries to build Table object while there are no Examples:  table row available for the scenario outline.
The approach is to skip table object creation when there is no example table row available and let the feature parser error listener throw exception afterward.
sample feature to replicate this Exception: invalidScenarioOutline.zip

Relevant Issues : (compulsory)
Relevant PRs : (optional)
Type of change :

[ ] New feature
[ ✓] Bug fix for existing feature
[ ] Code quality improvement
[ ] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

@babusekaran thanks ! but can you re-do this against the "cukexit" branch.

Sorry, my bad. changed the same from master to cukexit.


Code Integration

https://github.com/AnandSingh-0619/home-robot/blob/f3f8207f8a0689f4bdad21c6715f9bed1400eab3/projects/habitat_uncertainity/sensors.py#L75C1-L83C35
The model and wts are called in the YOLO_pred file where the predict function returns the new observations. A new YOLO_ObjectSegmentationSensor which should be replaced with original for object segmentation. I need steps to integrate this to the main code.
@yusufali98

You need to follow the OVON codebase structure. This is how you should achieve this:

Look closely as to how the custom sensors are created within the ovon directory. Sensors are defined in the tasks/ folder in sensors.py
Consider the ClipObjectGoalSensor. once the sensor is defined you need to create a hydra config for the same as is done here
Then you need to register the config data class with the hydra config store as is done here
You also need to create the search path plugin and need to register the plugin in the run.py file that you will use to run any experiments.
The DDPPO training in home-robot uses the built-in habitat_baselines run.py file. So as done in the OVON codebase, you need to create a new run.py within habitat_uncertainty project folder in which you will just register the hydra plugin (step 4) and basically import the execute_exp function from the habitat_baselines run.py (this and this)

Basically, you need to exactly replicate the OVON code structure and make sure you never make any changes in the habitat-lab/habitat-baselines codebase.
Regarding your question of the custom OVON trainers, they will only be used if specified in the config as is done here to use this particular custom trainer. We dont need to do all this because you will just use the standard habitat_baselines trainer that is specified in the rl_skill.yaml

Also, please make sure you link the correct branch in the GitHub issue. Linking incorrect branches can cause issues.
Right now you have linked this branch
But I am guessing you wanted to link your dev branch


Update README to note the charm is deprecated

Note that the markdown used is GH-specific: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts


SQL File missing

Hi,
I just downloaded your script. and want to know can you share your database sql file for this site?
Thanks

Hi,
Thanks for spotting that. Will add it soonest

Thanks.
I am using it for one of my project.
It is great but missing basic thing.
On Thursday 6 October 2016, Trevor SIbanda<EMAIL_ADDRESS>wrote:

Hi,
Thanks for spotting that. Will add it soonest
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/trevorsibanda/oneshop/issues/1#issuecomment-251894240,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALb0XT2YfowXbo1nMJsRLJqqk35chSa8ks5qxKvmgaJpZM4KLuzz
.

Hi,
Can you share SQL file for this site?
Thank you


Handle 'referenced' in EnumConstantDecl

I'm not sure why, but the ctype.c integration test fails for me on my clang v3.8.0 due to "referenced" showing up in the EnumConstantDecl AST nodes. Updated the regex to handle it and added a test.

This change is

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

ast/enum_constant_decl.go, line 33 at r1 (raw file):

		Position2: groups["position2"],
		Name:      groups["name"],
		Type:      groups["type"],

Also add the following line:
Referenced: len(groups["referenced"]) > 0,

ast/enum_constant_decl_test.go, line 17 at r1 (raw file):

			Children:  []Node{},
		},
		`0x3c77ba8 <line:59:3, col:65> col:3 referenced _ISalnum 'int'`: &EnumConstantDecl{

Please add Referenced bool to EnumConstantDecl.

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 2 unresolved discussions.

ast/enum_constant_decl.go, line 33 at r1 (raw file):
Previously, elliotchance (Elliot Chance) wrote…
Also add the following line:
Referenced: len(groups["referenced"]) > 0,

Done.

ast/enum_constant_decl_test.go, line 17 at r1 (raw file):
Previously, elliotchance (Elliot Chance) wrote…
Please add Referenced bool to EnumConstantDecl.

Done.

Comments from Reviewable

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Start Virtual Machine Fail

When I open the virtual machine, it always says “qemu exited from an error”.

Your settings are wrong. There is a future plan for a more detailed error message. For now, you can run it attached to Xcode debugger to see the full error message in the console.

Your settings are wrong. There is a future plan for a more detailed error message. For now, you can run it attached to Xcode debugger to see the full error message in the console.

Thanks, I reinstalled  the app, and this problem was work out. But when I want to start the VM, It will crash, and you have to shut down the process in the background or restart the iPad.


hyphen missing in pip index argument

The index argument was not being parsed because of the missing hyphen.

thanks!


How can hide circlemenu button in bottom viewcontroller?

how i hide circle button in bottom viewcontroller?
I want hide circle button in some viewcontroller in MatchTabs ( don't show all viewcontroller)
Thanks you

Hi @unamekkk! Just don't set popover view controller


Added A line for copyright section

Related Issue
closes #446
Description
Added A line for copyright section which makes the website look neat
Type of PR

[ ] Bug fix
[x ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[x ] I have performed a self-review of my code
[x ] I have read and followed the Contribution Guidelines.
[x ] I have tested the changes thoroughly before submitting this pull request.
[x ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x ] I have commented my code, particularly in hard-to-understand areas.

@CSEdgeOff  please review the pull request soon so that i can work on the another

@Saipradyumnagoud We're getting Conflicts Kindly update your PR with the new changes in the repo

@CSEdgeOff  yes i have made changes for the merge conficts now you can review  the pull request .


Update play.js

Updated the code to run with latest versions

Looks good to me to reflect discord.js v13 changes

Thanks!

@Grayson-code can you make changes in different files too, I am sure they are more basically for example index.js which contains requirements of passing intents too.

@Grayson-code can you make changes in different files too, I am sure they are more basically for example index.js which contains requirements of passing intents too.
Because they are also required and equally important,you can go about changing the pull request name to reflect v13 changes.

yeeee am looking into more files now only so yeajh

i believe I have made changes to example/* to work with discord.js v13

Could you follow the code style, more information here : https://app.codacy.com/gh/MenuDocs/erela.js/pullRequest?prid=8793096
If you feel if it's a mistake at some situations please disable eslint rules

Could you follow the code style, more information here : https://app.codacy.com/gh/MenuDocs/erela.js/pullRequest?prid=8793096 If you feel if it's a mistake at some situations please disable eslint rules

sure gotcha

i worked with the code style but has left the issues that were there before PR

Also about the https://solaris.codes domain in the repo as its expired would you like to replace all of em with like the current netlify link?

superseded by #184


Avoid compat.py, to make _in_process.py fully zip-safe (on Py3.7+).

The relevant part of compat.py is simply included in _in_process.py.
See the recent discussion in https://github.com/pypa/pep517/pull/55#issuecomment-606791307 for context.
cc @lazka @kitterma @dstufft @pfmoore @takluyver

Thanks for the quick response.  I took the modified version, rebuilt the Debian pep517 package and then used it to rebuild our pip package with pep517 unbundled as a wheel (as discussed in the other thread).  Then I went through the reproducer provided in Debian Bug #954256 [1].
I can confirm that it works correctly now, so this change solves the problem we were having.
@pfmoore Would it be possible to get a new release with this change in it?  If it's not convenient, just let me know and I'll add it as a distro patch until after the next release.  Thanks.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954256

@kitterma Thanks for confirming the fix, I have merged it but I can't do a release myself (it's possible I have the rights, but I don't know the process, and I don't consider myself a release admin on this project). So I'll defer to @takluyver to make a release.

Thanks.

@jaraco did some automation so it should just be a matter of making a tag and watching the wheels turn, though I've been forgetting to use it since then. I'll try to see if it works.

Released as 0.8.2

Excellent.  Thanks.


ghuser profile is not Updating on updating github profile

I recently got my ghuser profile Aditya. I update my profile bio on github but it didn't updated on ghuser profile.

Your ghuser profile updates every day. Wait a day and it will get updated


Add session exchanges: Chi-X (Europe, Japan), Bm&fBovespa

I made some changes. Please review.

Thanks, Dmitry. Merged this one.


Configure the API authentication in WebSecurityConfig

It would avoid managing the auth token in the ApiController and allow usage of Pre/PostAuthorize to check for international search permission. There might be some additional security benefits provided by Spring in how the token is handled.

[x] make sure the auth param is specific to the API access (under /api/*)
[ ] strip the auth param from the request to avoid potential leaks

It might be interesting to setup a OAuth 2.0 authentication scheme so that registries would explicitly request permission to act on behalf of a user registered in another registry.

each registry would have an "account" in each partner registries
permission to query remote data would be given by a generated OAuth token
no need for hard coded user-id, search-token or auth-token in the configuration
permission can be obtained or revoked at any moment

The authentication protocol would look like the following:

admin from registry A creates a user account at registry B
admin from registry A request permission to access registry B on behalf of the created user account
OAuth credentials are stored in registry A database
registry B decides whether or not to promote the created user account with administrative priviledges

It's not possible nor desirable to strip credentials from the request.

I'll open a separate issue for the OAuth 2.0 authentication between registries.


When reproducting the paper, result on IJB-B, IJB-C,Tinyface are lower than reported

I trained the model on MS1MV2, on high-quality datasets, and I got a similar result. Average 97.18(reported 97.19)
But when testing on IJB-B, IJB-C, and Tinyface, the results are lower.

Dataset
Avg on high quality
IJB-B
IJB-C
Tinyface-Rank1
Tinyface-Rank5

Reported in the paper
97.19
95.67
96.89
68.21
71.54

Reproducted
97.18
95.37
96.62
67.03
70.52

I followed the code provided and trained on 8-GPUs. And I wonder if there are some special tricks when evaluating on mixed and low-quality datasets?
And I found in the paper, Table3, (b), AdaFace trained on MS1MV2 has a better result on TinyFace than the model trained on MS1MV3. This is quite strange, MS1MV3 dataset is larger than MS1MV2, and the result should be better, but it shows a reverse result on TinyFace. Table 3 shows the trend, the model trained on MS1MV3 has better performance than the model trained on MS1MV2, but only in TinyFace, it's different.
I wonder if it's a small mistake that the result on TinyFace is reversed on MS1MV3 and MS1MV2 ?
Hope to get your reply.

Hi yyyujintang
The code released should work as it is without modification.
This is the setting I used for ms1mv2. I used 2 A100 GPUs.


Can`t install on linux ubuntu 14.04

UNMET PEER DEPENDENCY<EMAIL_ADDRESS><1.0.0
notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS><EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><1.0.0 but none was installed.

@chumack, sorry for being late, did you fixed it?
I recently merged #34 which may be related to it.


[outreachy] Registry: web accessibility review and improvements

Outreachy task for @FatumaA
Based on your user experience report, please provide the following suggested improvement via a PR:

The submit button's hover effect does not meet web accessibility guidelines on color contrast (WCAG 2.0 at Level AAA) but they meet Level AA. And the language and type filter buttons have the same styling even though they represent different things. This gives the visual impression that they do the same thing.

Please use a automated accessibility auditing tools to identify existing issues and share the list of issues as a comment to this thread (in textual form or as screenshots). We can then select the issue(s) for you to work on in a PR.
Note: This is an assigned issue for a participant that has completed the user experience report, if you are an outreachy participant as well, find instructions here: #5290

I used pa11y CLI against the registry section of the website on the standard setting (WCAG 2.1 AA),  and this was the output:
pa11y http://localhost:1313/ecosystem/registry/

Welcome to Pa11y

 > Running Pa11y on URL http://localhost:1313/ecosystem/registry/

Results for URL: http://localhost:1313/ecosystem/registry/

 • Error: This form does not contain a submit button, which creates issues for those who cannot submit the form using the keyboard. Submit buttons are INPUT elements with type attribute "submit" or "image", or BUTTON elements with type "submit" or omitted/invalid.
   ├── WCAG2AA.Principle3.Guideline3_2.3_2_2.H32.2
   ├── #searchForm
   └── <form action="/ecosystem/registry" id="searchForm">
<span ...</form>

 • Error: This element has insufficient contrast at this conformance level. Expected a contrast ratio of at least 4.5:1, but text in this element has a contrast ratio of 3.68:1. Recommendation:  change background to #0d1115.
   ├── WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail
   ├── #searchForm > div > button:nth-child(6)
   └── <button type="button" class="btn btn-outline-success" onclick="document.getElementById("searchForm").submit()">Submit</button>

2 Errors

It produces a lot more errors on the highest setting but it seems more reasonable to meet the acceptable level (AA) first before aiming for full compliance

Hey @FatumaA, thanks for running the report. Can you run the report on the highest level nevertheless? This way we can choose to resolve the AA issues and then cherry pick from the AAA issues that are reasonable to be solved. I assume that a lot of them are just repetition of the same issue, so we might be able to solve many of them with only a few changes. If you think that the output of the report is too long to be posted in a comment here you can use https://gist.github.com/ to create a place to store it outside.

Ok, here is the gist with the full report at the highest setting

Thanks! As suspected there are many issues of the same kind:
$ grep "WCAG2" gistfile1.txt | sort | uniq -c
 397    ├── WCAG2AAA.Principle1.Guideline1_3.1_3_1_AAA.G141
3368    ├── WCAG2AAA.Principle1.Guideline1_4.1_4_6.G17.Fail
   1    ├── WCAG2AAA.Principle3.Guideline3_2.3_2_2.H32.2

You listed WCAG2AAA.Principle3.Guideline3_2.3_2_2.H32.2 already, which is the issue with the missing button.
Then, we have WCAG2AAA.Principle1.Guideline1_3.1_3_1_AAA.G141 as an issue with heading structure (h6 in h4, not h5), etc. I assume most of them are for the same thing just in a repeated manner, since most of them are of the following structure:
 • Error: The heading structure is not logically nested. This h6 element should be an h5 to be properly nested.
   ├── WCAG2AAA.Principle1.Guideline1_3.1_3_1_AAA.G141
   ├── #default-body > li:nth-child(47) > div > div:nth-child(3) > div:nth-child(1) > h6
   └──
...

The one where we should keep the AA level is WCAG2AAA.Principle1.Guideline1_4.1_4_6.G17.Fail vs WCAG2AA.Principle1.Guideline1_4.1_4_3.G18.Fail, let's try to accomplish at least a 4.5:1 ratio, which should lower that number significantly (I hope)
Can you take a look into these issues and see how feasible it is to solve them and raise a PR accordingly? Thanks

It seems that the errros are in 3 categories:

Color contrasts issue
Header hierarchy
Form missing submit button

I think they can be handled in one PR

Yes, one PR is just fine.

hey @FatumaA, I have not received a PR for this issue from you, please let me know if you plan to do anything today? I will be not available to help after my work day ends

hey @FatumaA, I have not received a PR for this issue from you, please let me know if you plan to do anything today? I will be not available to help after my work day ends

Hi,
Apologies for the delays on this, I have linked a draft PR for what I've adjusted so far.
I've also used this tool along with pa11y to help make sense of the issues.

All the issues seem to be fixed except for the code blocks, which I'm not sure how to go about, and the nav shared across the website.
I think I will push commits for the nav, then mark it as ready for review.
I will send timeline in about an hour.
Thank you!

for the hierarchy issue you might need to go here:
https://github.com/open-telemetry/opentelemetry.io/blob/1ac2f27190c8bc0064beed51e2b5d87bb87e5f07/layouts/partials/ecosystem/registry/entry.html#L90


Need jaxb-api dependency for java 8+ version

Got jaxb exception when used java 8+ version
Why need jaxb-api in java 8+ ?
https://stackoverflow.com/questions/43574426/how-to-resolve-java-lang-noclassdeffounderror-javax-xml-bind-jaxbexception-in-j
I faced exception with following java and maven version
C:\Users>java -version
java version "10.0.1" 2018-04-17
Java(TM) SE Runtime Environment 18.3 (build 10.0.1+10)
Java HotSpot(TM) 64-Bit Server VM 18.3 (build 10.0.1+10, mixed mode)
C:\Users>mvn -v
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-25T01:19:0
5+05:30)
Maven home: C:\Program Files\apache-maven-3.5.3\bin..
Java version: 1.8.0_172, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_172\jre
Default locale: en_IN, platform encoding: Cp1252
OS name: "windows 8.1", version: "6.3", arch: "amd64", family: "windows"
After adding jaxb api, I am able to run application.

Your welcome.
On Sat, Aug 25, 2018, 11:50 AM Mrinmoy<EMAIL_ADDRESS>wrote:

Thanks for your contribution
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrin9/Angular-SpringBoot-REST-JWT/pull/36#issuecomment-415943213,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALWrL1Gwj9LE9wwBJQXC4J78nVfvvGQks5uUOy0gaJpZM4VZuWM
.


ALT responds 200 even without configured to ES

It is expected that GET /core-model-1-4:control-construct responds 500 Internal server error when configuration to ElasticSearch (ES) fails. Currently, in server/controllers/Core.js getControlConstruct(), response to be updated as below
response['application/json'] = {
        "core-model-1-4:control-construct": await elasticsearchService.updateControlConstructWithServicePolicy(value)
      };

instead of
response['application/json'] = {
        "core-model-1-4:control-construct": value
      };

As , ApplicationLayerTopology is not having any service record policy we are not updating the controlconstruct with service record policy .


multicore cup

Is nact ability to take full advantage of multicore cup resources ?
or all atcors run only on a single cup?

Each actor system runs on a single core. You could use node's multi
processing features to create more than one system, and then create actors
which would bridge the different systems.
We've taken a similar approach to allow for communication between different
services in our kubernetes cluster.
On Wed, 25 Dec 2019, 10:33 yunmin<EMAIL_ADDRESS>wrote:

Is nact ability to take full advantage of multicore cup resources ?
or all atcors run only on a single cup?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ncthbrt/nact/issues/74?email_source=notifications&email_token=ACCJEWIDV4ZT75K3JYXZW6LQ2MLDXA5CNFSM4J7DODN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4ICSXISA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACCJEWJYHP62DEQ4MN2SQ7DQ2MLDXANCNFSM4J7DODNQ
.

sorry I'm not sure..

How do actors on system A communicate with actors on system B?
dispatch(A-actor, 'communicate between A&B system', B-actor);  does this work?
or i must use process.send({ msg: 'word to A-system' }) to deal with the communication between two processes(systems)?


Adds partner token endpoints

Adds 3 partner token endpoints and their related resources.

Looks good :shipit:


Starship not working on mac

Enabling starship doesn't work. I see the following error on the console when starting devenv (through direnv):

/dev/stdin:69: preexec_functions: unbound variable

To Reproduce
Set starship.enable = true; in devenv.nix
Version
devenv: 0.6.2

It works for me.
devenv 0.6.2
nix 2.13.3 (via alternative installer from Determinate Systems)
macOS 13.3.1 aarch64
If anyone has any ideas how to get to the bottom of this....

Confirmed working.

aarch64-darwin
devenv 0.6.2
nixpkgs@9f7d9a55cc9960c029b006444e64e8dfa54a578e

@mrfelton, are you using https://github.com/rcaloras/bash-preexec by any chance? The variable preexec_functions is related to that project.

I am using iterm2 which according to the link you sent, implies that I may be using that.

Reported as it works, please report if anyone else has issues with it.

Not working on macOS
I do have iTerm but failed on Terminal.apop and iTerm.app
aarch64-darwin
devenv 0.6.2
nix 2.18.1 (via alternative installer from Determinate Systems)


Google cloud storage does not work

Distro: Ubuntu 16
chris@pghoard-test-ubuntu# sudo pghoard --config pghoard.json
2016-06-14 22:17:10,162 pghoard MainThread  DEBUG   Loading JSON config from: 'pghoard.json', signal: None
2016-06-14 22:17:10,326 pghoard MainThread  INFO    pghoard initialized, own_hostname: 'pghoard-test-ubuntu', cwd: '/home/chris'
2016-06-14 22:17:10,339 pghoard MainThread  WARNING OperationalError (fe_sendauth: no password supplied
) connecting to DB at: "dbname='replication' host='x.x.x.x' port='5432' replication='true' user='pghoard'"
2016-06-14 22:17:10,339 pghoard.common  MainThread  WARNING Creating alert file: '/var/lib/pghoard/configuration_error'
2016-06-14 22:17:10,343 root    MainThread  WARNING No module named 'oauth2client.locked_file'
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/googleapiclient/discovery_cache/init.py", line 33, in autodetect
from google.appengine.api import memcache
ImportError: No module named 'google.appengine'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/googleapiclient/discovery_cache/init.py", line 38, in autodetect
from . import file_cache
File "/usr/lib/python3/dist-packages/googleapiclient/discovery_cache/file_cache.py", line 32, in
from oauth2client.locked_file import LockedFile
ImportError: No module named 'oauth2client.locked_file'
2016-06-14 22:17:10,545 pghoard MainThread  ERROR   Unexpected exception in PGHoard main loop
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pghoard/rohmu/object_storage/google.py", line 227, in get_or_create_bucket
gs_buckets.get(bucket=bucket_name).execute()
File "/usr/lib/python3/dist-packages/oauth2client/util.py", line 137, in positional_wrapper
return wrapped(_args, *_kwargs)
File "/usr/lib/python3/dist-packages/googleapiclient/http.py", line 729, in execute
raise HttpError(resp, content, uri=self.uri)
googleapiclient.errors.HttpError: <HttpError 403 when requesting https://www.googleapis.com/storage/v1/b/xxxxx-pghoard-test?alt=json returned "Forbidden">
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pghoard/pghoard.py", line 405, in run
self.handle_site(site, site_config)
File "/usr/lib/python3/dist-packages/pghoard/pghoard.py", line 359, in handle_site
self.time_of_last_backup[site] = self.check_backup_count_and_state(site)
File "/usr/lib/python3/dist-packages/pghoard/pghoard.py", line 257, in check_backup_count_and_state
basebackups = self.get_remote_basebackups_info(site)
File "/usr/lib/python3/dist-packages/pghoard/pghoard.py", line 242, in get_remote_basebackups_info
storage = get_transfer(storage_config)
File "/usr/lib/python3/dist-packages/pghoard/rohmu/init.py", line 40, in get_transfer
return storage_class(**storage_config)
File "/usr/lib/python3/dist-packages/pghoard/rohmu/object_storage/google.py", line 83, in init
self.bucket_name = self.get_or_create_bucket(bucket_name)
File "/usr/lib/python3/dist-packages/pghoard/rohmu/object_storage/google.py", line 233, in get_or_create_bucket
raise InvalidConfigurationError("Bucket {0!r} exists but isn't accessible".format(bucket_name))
pghoard.rohmu.errors.InvalidConfigurationError: Bucket 'xxxxx-pghoard-test' exists but isn't accessible
^C2016-06-14 22:17:11,303   pghoard MainThread  WARNING Quitting, signal: 2
^C2016-06-14 22:17:11,833   pghoard MainThread  WARNING Quitting, signal: 2
^C2016-06-14 22:17:12,330   pghoard MainThread  WARNING Quitting, signal: 2
^C2016-06-14 22:17:12,608   pghoard MainThread  WARNING Quitting, signal: 2
^C2016-06-14 22:17:13,257   pghoard MainThread  WARNING Quitting, signal: 2
^C2016-06-14 22:17:13,438   pghoard MainThread  WARNING Quitting, signal: 2

It looks like your system is missing the oauth2client package which is a dependency of googleapiclient. I don't know how these are packaged on Ubuntu, but at least on Fedora oauth2client is a direct dependency of googleapiclient.
Please let me know if installing python3-oauth2client fixes the issue for you.
Also, not quite related to this, but you should run pghoard as the postgres user, not as root.

I checked the python3-googleclient and python3-oauth2client packages on Debian Jessie, and the packages in the main repository are not really Python 3 compliant. The ones in Debian backports work in Jessie, but I noticed the oauth2client.locked_file module has moved to oauth2client.contrib.locked_file in recent versions of oauth2client, and for example mixing the non-backports version of python3-googleclient with the backports version of python3-oauth2client would cause an error like that.

I'm closing this - it looks like it's packaging issue on Ubuntu.  Please reopen if there are more issues.

Just FYI: Same happened to me when installing google-api-python-client via pip which is suppose to define a dependency on oauth2client but somehow that doesn't work.

It took me quite some time btw to figure out this was just a warning because error reporting is a bit misleading. On the other hand, now it's returning a configuration error with the severity warning which looks critical to me:
2017-07-10 16:49:10,025	pghoard.common	MainThread	WARNING	Creating alert file: '/data/backups/configuration_error'
2017-07-10 16:49:10,026	pghoard	MainThread	INFO	Creating a new basebackup for 'default' because there are currently none
2017-07-10 16:49:10,028	pghoard	MainThread	WARNING	OperationalError (fe_sendauth: no password supplied
) connecting to DB at: "dbname='replication' host='<IP_ADDRESS>' port='5432' replication='true' user='replication'"

The next question is why it's not using a password even though I've set one... But will investigate that further and open an issue if it looks like a bug.


Unwanted behaviour getCheckboxCheckedState

Say I have the following code:
@foreach ( Permission::all() as $permission )
	@if ( $role->permissions->contains($permission->id) )
	{{ Form::checkbox('permissions[]', $permission->id, false ) }} {{ $permission->label }}
	@else
	{{ Form::checkbox('permissions[]', $permission->id, false ) }} {{ $permission->label }}
	@endif
@endforeach

But my model being parsed has the permissions() array. The false will be ignored and the checkbox will be shown checked. Even if the $permission->id is not related to the Role.
FormBuilder@getCheckboxCheckedState
return is_array($posted) ? in_array($value, $posted) : (bool) $posted;

this line will return true, even if the $permission->id is set. Or the 'checked state' parameter is given.
Perosnally I think that all those isChecked checks should only be performed if $checked is_null.
FormBuilder@checkable()
$checked = $this->getCheckedState($type, $name, $value, $checked);

should be
if ( is_null($checked) ) $checked = $this->getCheckedState($type, $name, $value, $checked);

I believe this topic should remain open if FormBuilder is still being actively developed. In @devinfd 's  PR, he suggests that the explicitly passed value should override 'old input' as well as 'model value'. That was correctly rejected, but my issue is with explicitly passed value not overriding model value as it should. Thanks.

I agree. It should have the same cascade as the other input fields: Input > Explicit > Model

I too feel this bug should be fixed. I know the HTML helper has been taken out of core but the repo at illuminate/html is labelled as read-only so I assume PRs are ignored as none have been merged/closed. Also there is no way to submit issues. How can we contribute to the HTML helper? @GrahamCampbell any thing you can do here?

Alternatively you can use https://github.com/LaravelCollective/html

Hello, I just ran into this issue too.
Adding the array key to the field name seems to resolve it so far.
@foreach ( Permission::all() as $key => $permission )
    {{ Form::checkbox('permissions[' . $key . ']', $permission->id, false ) }} {{ $permission->label }}
@endforeach

I hope it helps and saves your time.


[INFO REQUEST] Provide an overview of improvements and changes between major versions 5 and 6

Release version
APIOps Toolkit for Azure APIM v6.0.1
Question Details
Good morning,
I just wanted to request an easily readable overview of what has changed between the major versions 5 and 6 and if there are migration steps available or even required.
Currently the information is spread across dozens of release candidates and might not even apply anymore.
Thanks for the great work!
Expected behavior
.
Actual behavior
.
Reproduction Steps
.

Please got through the release notes of the different versions for now. When we get some time, we will be updating the associated GitHub page.


Man page fixes found by https://pagure.io/ManualPageScan

Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

LGTM

LGTM, nice and simple

@rh-atomic-bot r=mheon

@rh-atomic-bot r=TomSweeneyRedHat

Merging Manually.  Since Homu is not responding.


shared_example_group edge case

Failure/Error: Unable to find matching line from backtrace
 LocalJumpError:
   no block given

This is where I started, while working on rspec-console. And falling down the rabbit hole, I saw that:
 class Registry
    def add(context, name, *metadata_args, &block)
      [snip]
      return if metadata_args.empty?
      RSpec.configuration.include SharedExampleGroupModule.new(name, block), *metadata_args
    end

If return if metadata_args.empty? is called on [nil] by accident, it will return false and
class SharedExampleGroupModule < Module
  def initialize(description, definition)

will fail to be properly defined. Causing a failure further down when @description is called as a block, and is empty.
Don't ask me why I was able to pass [nil] in there -- I'm trying to work with rspec_console and my spec suite for it creates weird cases. But if you slap good ol' compact in ala return if metadata_args.compact.empty? you can prevent the edge case I am seeing.

Can you provide a code snippet that calls a public RSpec API to get [nil] to reach there?  If so, we'll happily address this (or we'll be happy to merge a PR from you addressing it).  Although, there might be a different location before it gets here from the public API that is a more appropriate place to fix it.
If there's no way to get here with [nil] via a call to a public RSpec API then I'd recommend sticking to just public APIs :).  We can always add additional APIs that you may need.

@myronmarston FWIW, this is where I managed to do it:
::RSpec.world.shared_example_group_registry.add()
You can see why I'm doing this nonsense if you want here: https://github.com/mooreniemi/rspec-console/blob/rspec_3_support/lib/rspec-console/config_cache.rb

So if you're calling that method would a group then we should error at you there, I wouldn't recommend we no op on nil, that method expects a shared example group so...

I'd say you should run a compact on your array before checking it's empty... or just avoid adding nils to it in the first place if possible...

@JonRowe I've already resolved my issue on my end. (Without doing anything to RSpec core.) This was just a heads up to you, in case you wanted to do anything with it.

 Thanks for the heads up :)


typescript support

It would be nice to have types applied to the data we are getting each frame

I wrote some typings and am evaluating them right now, feel free to test and use them as you like.
if you find errors please let me know.
https://gist.github.com/peanutbother/af907b7cb9ec27baaebfaf2952fb2b53


Migrate v2 MPI operator to the unified operator

Now that v1 MPI operator has been migrated to this repo https://github.com/kubeflow/training-operator/pull/1457. Let's use this issue to track the progress on v2.
https://github.com/kubeflow/mpi-operator/tree/master/v2
cc @hackerboy01 @zw0610 @alculquicondor @kubeflow/wg-training-leads

@alculquicondor What is the status for MPI Operator v2 ?
Do we have plans to deliver MPI Operator v2 as part of Universal Training Operator in Kubeflow 1.5 ?
The Kubeflow 1.5 release deadline is January 15th.

We need a contributor to do it. I don't currently have capacity to handle it. That means that likely it wouldn't be possible for January 15th. But I don't think the v1 operator is ready either.

cc @ArangoGutierrez

I want to resurrect this thread.  There have been many asks from the community to have v2 mpi operator in training operator.  Currently, newer features are merged into v2 mpi.  What is our plan here regarding migration?  What are the road blocks here?  There is confusion in the community the future of v1 mpi as well.
Can we prioritise this?  @alculquicondor @terrytangyuan @tenzen-y

IIRC, we are planning to donate mpi-operator v2 to kubernetes-sigs. So we should decide whether donate the kubernetes-sigs or merge the v2 operator to the training-operator to avoid double management.
https://github.com/kubeflow/community/pull/557
cc: @ArangoGutierrez @denkensk @ahg-g

Do have any new plan here ? Since donate mpi-operator v2 to kubernetes-sigs is seems aborted, should we merge mpi-operator v2 to training-operator ?

There's also discussion around donating Spark-on-K8s project to Kubeflow. I personally think that project is similar to MPI Operator which not just focus on training. So I am not sure if MPI Operator would be a good fit for training-operator.


typescriptify

I don't know if this is of interest, but I started to write some classes in TS, which should give better types in the d.ts files.

Hi, Thanks for your effort on this.
Can you please explain what this does. It is hard to accept a pull request that does a complete change of several files. Much better to have a detailed explanation of each change and/or a more surgical pull request with diffs that we can analyze.

Hi,
I guess that's the problem when moving from one filetype to another: git does not see this as a move, so it's a remove and a add, so there's no diff comparison for it.
In Dynamo.ts the main changes are:

Added Types for the params
Added input and return types for the methods
The public instance variables are clear to see before the constructor
Remove the send and used this.client.send directly because I could not come up with clever types for send.

In ULID.ts the main changes are:

Added input and return types for the methods, still some any (sorry)
Tried to figure out via the unit tests what allowed types for the when parameter are

The only idea I can come up with, is to use githubs markdown diff feature:
git diff main:src/Dynamo.js src/Dynamo.ts
diff --git a/src/Dynamo.js b/src/Dynamo.ts
index 856fe59..24d2e89 100644
--- a/src/Dynamo.js
+++ b/src/Dynamo.ts
@@ -1,8 +1,7 @@
 /*
-    Dynamo.js -- AWS V3 SDK API
+    Dynamo.ts -- AWS V3 SDK API

     This module provides a wrapper and convenience API over the AWS V3 SDK.
-    It is used by OneTable internally and is not a public API.

     Use:
         import {Model, Table} from 'dynamodb-onetable'
@@ -14,26 +13,82 @@
     */

 import {
+    AttributeValue,
     BatchGetItemCommand,
+    BatchGetItemCommandInput,
     BatchWriteItemCommand,
+    BatchWriteItemCommandInput,
     CreateTableCommand,
+    CreateTableCommandInput,
     DeleteItemCommand,
+    DeleteItemCommandInput,
     DeleteTableCommand,
+    DeleteTableCommandInput,
     DescribeTableCommand,
+    DescribeTableCommandInput,
+    DynamoDBClient,
     GetItemCommand,
+    GetItemCommandInput,
     ListTablesCommand,
+    ListTablesCommandInput,
     PutItemCommand,
+    PutItemCommandInput,
     QueryCommand,
+    QueryCommandInput,
     ScanCommand,
+    ScanCommandInput,
     TransactGetItemsCommand,
+    TransactGetItemsCommandInput,
     TransactWriteItemsCommand,
+    TransactWriteItemsCommandInput,
     UpdateItemCommand,
+    UpdateItemCommandInput
 } from '@aws-sdk/client-dynamodb'
-
-import {marshall, unmarshall} from '@aws-sdk/util-dynamodb'
+import {
+    marshall,
+    marshallOptions,
+    unmarshall,
+    unmarshallOptions
+} from '@aws-sdk/util-dynamodb'
+
+interface DynamoParams {
+    client?: DynamoDBClient
+    marshall?: <T extends { [K in keyof T]: any }>(
+        data: T,
+        options?: marshallOptions | undefined
+    ) => {
+        [key: string]: AttributeValue
+    }
+    unmarshall?: (
+        data: {
+            [key: string]: AttributeValue
+        },
+        options?: unmarshallOptions | undefined
+    ) => {
+        [key: string]: any
+    }
+}

 export class Dynamo {
-    constructor(params = {}) {
+    client: DynamoDBClient
+    params: any
+    V3: boolean
+    marshall: <T extends { [K in keyof T]: any }>(
+        data: T,
+        options?: marshallOptions | undefined
+    ) => {
+        [key: string]: AttributeValue
+    }
+    unmarshall: (
+        data: {
+            [key: string]: AttributeValue
+        },
+        options?: unmarshallOptions | undefined
+    ) => {
+        [key: string]: any
+    }
+
+    constructor(params: DynamoParams = {}) {
         this.client = params.client
         this.params = params
         this.marshall = marshall
@@ -41,78 +96,74 @@ export class Dynamo {
         this.V3 = true
     }

-    async createTable(params) {
+    async createTable(params: CreateTableCommandInput) {
         let command = new CreateTableCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async deleteTable(params) {
+    async deleteTable(params: DeleteTableCommandInput) {
         let command = new DeleteTableCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async delete(params) {
+    async delete(params: DeleteItemCommandInput) {
         let command = new DeleteItemCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async describeTable(params) {
+    async describeTable(params: DescribeTableCommandInput) {
         let command = new DescribeTableCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async get(params) {
+    async get(params: GetItemCommandInput) {
         let command = new GetItemCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async find(params) {
+    async find(params: QueryCommandInput) {
         let command = new QueryCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async listTables(params) {
+    async listTables(params: ListTablesCommandInput) {
         let command = new ListTablesCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async put(params) {
+    async put(params: PutItemCommandInput) {
         let command = new PutItemCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async scan(params) {
+    async scan(params: ScanCommandInput) {
         let command = new ScanCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async update(params) {
+    async update(params: UpdateItemCommandInput) {
         let command = new UpdateItemCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async batchGet(params) {
+    async batchGet(params: BatchGetItemCommandInput) {
         let command = new BatchGetItemCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async batchWrite(params) {
+    async batchWrite(params: BatchWriteItemCommandInput) {
         let command = new BatchWriteItemCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async transactGet(params) {
+    async transactGet(params: TransactGetItemsCommandInput) {
         let command = new TransactGetItemsCommand(params)
-        return await this.send(command)
+        return await this.client.send(command)
     }

-    async transactWrite(params) {
+    async transactWrite(params: TransactWriteItemsCommandInput) {
         let command = new TransactWriteItemsCommand(params)
-        return await this.send(command)
-    }
-
-    async send(cmd) {
-        return await this.client.send(cmd)
+        return await this.client.send(command)
     }
 }

git diff main:src/ULID.js src/ULID.ts
diff --git a/src/ULID.js b/src/ULID.ts
index 408e5a6..c237ade 100644
--- a/src/ULID.js
+++ b/src/ULID.ts
@@ -1,5 +1,5 @@
 /*
-    ULID.js -- Universal Unique Lexicographically Sortable Identifier
+    ULID.ts -- Universal Unique Lexicographically Sortable Identifier
     https://github.com/ulid/spec
  */
 import Crypto from 'crypto'
@@ -11,20 +11,25 @@ const RandomLength = 16
 const TimeLen = 10

 export default class ULID {
-    constructor(when) {
-        this.when = isNaN(when) ? when = new Date() : new Date(when)
+    when: Date
+    constructor(when?: Date | undefined) {
+        if (when === undefined) {
+            this.when = new Date()
+        } else {
+            this.when = when
+        }
     }

-    toString() {
+    toString(): string {
         return this.getTime(this.when) + this.getRandom()
     }

-    decode(ulid) {
-        ulid = ulid.toString()
-        if (ulid.length !== (TimeLen + RandomLength)) {
+    decode(ulid: any) {
+        const ulidStr: string = ulid.toString()
+        if (ulidStr.length !== TimeLen + RandomLength) {
             throw new Error('Invalid ULID')
         }
-        let letters = ulid.substr(0, TimeLen).split('').reverse()
+        let letters = ulidStr.substr(0, TimeLen).split('').reverse()
         return letters.reduce((accum, c, index) => {
             let i = Letters.indexOf(c)
             if (i < 0) {
@@ -35,17 +40,17 @@ export default class ULID {
         }, 0)
     }

-    getRandom() {
+    getRandom(): string {
         let bytes = []
         let buffer = Crypto.randomBytes(RandomLength)
         for (let i = 0; i < RandomLength; i++) {
             //  Letters is one longer than LettersLen
-            bytes[i] = Letters[Math.floor(buffer.readUInt8(i) / 0xFF * LettersLen)]
+            bytes[i] = Letters[Math.floor((buffer.readUInt8(i) / 0xff) * LettersLen)]
         }
         return bytes.join('')
     }

-    getTime(now) {
+    getTime(now: any): string {
         let bytes = []
         for (let i = 0; i < TimeLen; i++) {
             let mod = now % LettersLen

Hi Christian,  Thanks for the extra details that helps.
I'd love to have better .d.ts files, but don't really want to switch to TS files, especially not for just a couple of files. If we did switch, we'd do all the source.
Would it be possible to make improvements from your prototyping ts files to the original .d.ts files? Especially the Dynamod.d.ts is pretty bare (which I guess is what prompted your efforts).
Other comments:

Don't want to import everything in Dynamo from '@aws-sdk/client-dynamodb. We only want to import the commands we actually use. That helps tree shaking for minimal footprint.

Hi,

I'd love to have better .d.ts files, but don't really want to switch to TS files, especially not for just a couple of files. If we did switch, we'd do all the source.

From my perspective/experience I would always do it step by step and not in one big rewrite. Especially because tsc supports that mixed JS/TS mode.

Would it be possible to make improvements from your prototyping ts files to the original .d.ts files? Especially the Dynamod.d.ts is pretty bare (which I guess is what prompted your efforts).

Sure, feel free to pick whatever makes the existing typings better.

Don't want to import everything in Dynamo from '@aws-sdk/client-dynamodb. We only want to import the commands we actually use. That helps tree shaking for minimal footprint.

Not sure if I understand you 100%. The generated code in mjs only imports what's needed (the commands), the cjs imports everything (as before).

Agree on step, by step changing. But we've not yet decided to take those steps.
I'd love to manually apply your changes to Dynamo, Ulid etc and strengthen our typings.
If we do switch to TS, will dig up this pull request and it will save time.
Some shakers do a better job than others. Doing an import in Dynamo of the full API may not get removed. E.g. AttributeValue which we don't use.  Not a big deal given the direction we're taking.
Lastly, thank you very much for your effort on this. We will update the .d.ts over the weekend and hopefully that will help your use-cases. Please feel free to suggest and propose pull requests for any other features or issue you identify.

Lastly, thank you very much for your effort on this. We will update the .d.ts over the weekend and hopefully that will help your use-cases. Please feel free to suggest and propose pull requests for any other features or issue you identify.

Thanks, will do. And thank you for the library.

I've cherry picked some fixes for ULID.d.ts and Dynamo.d.ts -- but pretty minimal.
Please feel free to suggest surgical changes to any *.d.ts file where we can improve our typescript definitions.
My goal is to keep it simple, readable and yet offer good TS support.


StrategyHandler.doneWaiting may result in unhandled promise rejections

Library Affected:
workbox-strategies
Browser & Platform:
all browsers
Issue or Feature Request Description:
While investigating some unhandled rejection errors in our application, I found that StrategyHandler.doneWaiting throws on the first rejected promise that it encounters. This means that subsequent rejected promises may result in unhandled rejection errors.

Hi there,
Workbox is moving to a new engineering team within Google. As part of this move, we're declaring a partial bug bankruptcy to allow the new team to start fresh. We realize this isn't optimal, but realistically, this is the only way we see it working. For transparency, here're the criteria we applied:

For PRs, we closed everything that doesn't target the current v7 branch.
For Issues, we closed everything that was created before 2024.

Thanks, and we hope for your understanding!
The Workbox team


Include directory from resources while compiling native Image via gluon client maven plugin

I wrote a custom alert/combobox implementation for my project. Could not
use Gluon Mobile because its integrated tightly with our custom Theme
API. It works now!!
However, I have a small issue. My project root currently looks like this
root
 - src

 - resources

     - default/

         - config.xml

         - Themes/

         - Profiles/

         - Icons/

     - style.css

     - Roboto.ttf

When the config.xml file isnt found on local disk, the program just
copies all the contents of the default directory to the disk.
However, when i try to get Main.class.getResource("default/").toURI()
it returns a nullpointer. i added -H:IncludeResources='*/*.*' to
<nativeImageArgs> but it doesnt work. I also tried adding that under
<resourcesList> but that too did not work.
Any leads on how I can embed all the directories/files/ everything from
the resources folder onto the native image
StreamPi is going to be a real nice demonstration of how powerful
graalvm, gluon can be. I love your work!

This is a graalvm issue. Class.getResource() returns resource:/<file location within the project> which isn't usable in most cases.
In order to get a file though, Class.getResourceAsStream() works perfectly!
My workaround was to zip the entire directory, put it inside the resources directory and then extract it.

This is a graalvm issue. Class.getResource() returns resource:/<file location within the project> which isn't usable in most cases.
In order to get a file though, Class.getResourceAsStream() works perfectly!
My workaround was to zip the entire directory, put it inside the resources directory and then extract it.

Yes, Main.class.getResource("default/") doesn't return a "directory", from which you can list files.
You have to either use a FileSystem or Class.getResourceAsStream().

Yes, Main.class.getResource("default/") doesn't return a "directory", from which you can list files.
You have to either use a FileSystem or Class.getResourceAsStream().


Extensions

@Knagis,
So I've had some solid progress on enabling extensions. Now I'd appreciate your feedback on pre-existing features in this regard.

[x] Strikeout
seems to me as an obvious candidate.

[x] Line breaks
I believe this one should also be an extension.

[x] Unicode bullet
I didn't see it mentioned anywhere in the spec. Extension?

[x] HtmlFormatter + OutputDelegate
Are two different formatters really required? AFAIK one of these was added as a means to enable customizations. Since we now have a modular design, no modifications to the bulk formatters should be required.

[x] TrackSourcePosition
The implementation would obviously remain deeply integrated, just the API would be a little cleaner, similarly to the reference label case extension.

[ ] UriResolver
Need I say more?

[ ] Anything else?

Thanks
Edit: Added omissions and turned into checklist.

Strikeout can be an extension, line breaks could be as well. The problem is though that currently it is very easy for the developer to discover these additional features that are supported by default (through the switch). It would be nice that the discovery could be made just as easy.
Unicode bullet is not in the spec (I haven't heard any good arguments against supporting it and I actually made a PR at one point that added it both to the spec and both reference implementations, the PR is still open). It could be an extension though it is a question of does it really have to be - maybe it is easier to just leave it as is.
HtmlFormatter was mainly created because people wanted to do things like
foo
 with as little code as possible.

All valid points. Let me address each separately (these could easily become own issues).

Strikeout can be an extension, line breaks could be as well. The problem is though that currently it is very easy for the developer to discover these additional features that are supported by default (through the switch). It would be nice that the discovery could be made just as easy.

Sure, it's easy to discover Strikethrough when it's the only available additional feature ;)
Admittedly I didn't dedicate much thought to extension discoverability. All extensions currently reside in the Extension namespace, which may quickly become bloated as settings and features are added.
So, for example, there is a FancyLists extension with FancyListsSettings, which in turn has FancyListsFeatures, NumericListStyles and AdditiveListStyles.
One possible solution would be to use type nesting (FancyLists.Features etc.), although I'm personally leaning against it.
There's always the option of restricting customizability ( Yes, I might have gotten carried away with the multitude of settings and features). That doesn't seem to work in the above case, however, as most scenarios won't require UpperLatin, ArabicIndic and Hebrew always on.
The path of the least resistance (and my personal favorite) would be to leave things as are and refer users to documentation (once that's available).

Unicode bullet is not in the spec (I haven't heard any good arguments against supporting it and I actually made a PR at one point that added it both to the spec and both reference implementations, the PR is still open).

I'm sorry to hear that your PR didn't get through.
There is indeed no reason why it shouldn't be added to the spec. However, I'm not sure having an always-on feature that isn't in the spec (yet?) is such a good idea.
FancyLists have 4 bullet list types (I used a different code point for disc), all off by default (although that itself is subject to a separate discussion).

In the proposed design one would

create a custom formatter that extends HeaderFormatter
override WriteOpening()
create a custom extension that initializes the formatter
register the extension in settings.Extensions.

No changes to the library code are necessary.

About the extension visibility - one idea I had - each extension would expose an extension method on the CommonMark namespace, so one could write something like:
using CommonMark;

var settings = CommonMarkSettings.Default.Clone();
settings.EnableFancyLists(some settings here as arguments);

This approach would enable other developers to write extensions that are external but for a developer those could be added the same way.
This would also enable you to separate the extension classes in separate namespaces for code clarity since the additional level would not add any extra work to the developer.

P.S. How much a performance gain did you get with the delegate array trick? I didn't apply to formatters yet, but I suspect that it would also be somewhat faster than a virtual method call for each element (especially inline).

The original code was something like
if (c == '*' || c == '_') HandleEmphasis();
else if (c == '!') HandleExclamation();
etc...

The delegate array approach resulted in the same performance but with the added flexibility of changing the handle methods on the fly and without the need to hardcode settings checks in the parser method.

However, I'm not sure having an always-on feature that isn't in the spec (yet?) is such a good idea.

It's not. I was always hoping that it would get to the spec sooner than later.

HtmlFormatter

HtmlFormatter could go if the same can be achieved with different means. What I would like to keep is HtmlFormatterSlim since that produces the best performance.
What performance are you seeing with the extension model?

Extension methods could be nice, but I see two problems with these:

won't work in .NET 2.0
would make the extension code less pretty.

I have found a workaround for 1, and 2 may be just my distorted point of view, but still.

What I would like to keep is HtmlFormatterSlim since that produces the best performance.

I assumed as much. I'll then remove HtmlFormatter and rename HtmlFormatterSlim.

What performance are you seeing with the extension model?

I didn't measure yet, but I'm expecting that to be at least as good as that of the monolithic design (I applied the same trick to all parser methods, so instead of an if/else forest it's just a couple of delegate invocations - alright, more than a couple, but those should still perform much better than virtual calls.).

More extension candidates:

PositionTracking
The implementation would obviously remain deeply integrated, just the API would be a little cleaner, similarly to the reference label case extension.

UriResolver
Need I say more?

CustomFormatter
seems like an actual candidate for removal. My understanding is that it's a relic of the pre-Parse() age.

Anything else?

The following exist in cmark:

Safe (a.k.a. HTML Sanitization)
Am I correct in my presuming that this wasn't ported yet?

Smart (a.k.a Smart Punctuation)
I am aware of the potential performance hit this might incur. Yet it's something that many users see as basic Markdown functionality (Smarty Pants has been around almost since the beginning).

won't work in .NET 2.0
would make the extension code less pretty.

I don't think 1. is an issue - since most people even if they are forced to target .NET 2.0 will be using newer compilers that do support extension methods.
Why would it make it less pretty? In my mind the extension method was simply a shortcut for enabling the shortcut - if the dev wants he can still instantiate the extension and add it manually to the settings instance.
A similar approach is used with Owin in ASP.NET - the various frameworks add extension methods for IAppBuilder interface, so you end up simply calling app.MapSignalR().

PositionTracking

Perhaps, if that is indeed possible. Note #21 - if the implementation is changed drastically, this should be kept in mind - even if the implementation is not updated but at least to not make it harder to implement that down the road.

CustomFormatter

?

Safe (a.k.a. HTML Sanitization)

The implementation in cmark is not really HTML sanitization but rather disabling of HTML and unsafe URI schemes. I would prefer to use a separate external sanitization library that would actually process the HTML instead of prohibiting it. The problem is that the last time I looked, I could not find anything in the .NET world (MS had made one but deprecated it).

Smart

Yes, this one should be implemented. I once almost started but only almost.

Tree

It could be added and should be pretty easy to. Though I think I still prefer the plain text output in case I have to debug something. But there was at least one who was actually using that XML output in cmark for further processing.

Why would it make it less pretty?

I was actually thinking about built-in extensions. Those would either need to open a separate namespace declaration, e.g.
namespace CommonMark
{
    public static partial class CommonMarkSettingsExtensions
    {
        public static void RegisterMathDollars(this CommonMarkSettings settings)
        {
            settings.Extensions.Register(new Extension.MathDollars(settings));
        }
    }
}

or a single file with a CommonMarkSettingsExtensions class would need to reference all built-in extensions at once (which is slightly prettier since I already have a RegisterAll() method that does the same).

I don't think 1. is an issue - since most people even if they are forced to target .NET 2.0 will be using newer compilers that do support extension methods.

This is a runtime issue rather than a compiler one. Trying to compile the above for .NET 2.0 results in
error CS1110: Cannot define a new extension method because the compiler required type 'System.Runtime.CompilerServices.ExtensionAttribute' cannot be found. Are you missing a reference to System.Core.dll?

As already mentioned, this is magically solved with a reference to LinqBridge. However, this begs the question: How many people actually use the .NET 2.0 version? Perhaps 2016 is the year it finally gets to retire?

By CustomFormatter I meant OutputFormat.CustomDelegate. Sorry about the misnomer.

The implementation in cmark is not really HTML sanitization but rather disabling of HTML and unsafe URI schemes. I would prefer to use a separate external sanitization library that would actually process the HTML instead of prohibiting it.

Yes, I noticed that after-the-factly. I think it's a matter of cmark compatibility. Surely CommonMark.NET is CommonMark-compliant, but it might look bad if it lacks an option some would consider a critical one. Maybe it just should ape cmark until a proper solution is found.

The only reason I see to keep the 2.0 version is if someone somewhere wants to use it in an environment like SQL Server 2005 that allows to run managed code in its own process but only supports .NET 2.0. From what I read, we could add the attribute to the code the same as Lazy and Func.
There could be other reasons why for example JSON.NET still supports .NET 2.0.

OutputFormat.CustomDelegate

That is the current option (though ugly) to use custom formatters - the idea is that you could modify CommonMarkSettings.Default and thus change how another library that wraps commonmark.net is generating the output. It can go away as soon as there is a better way of specifying the formatter.

HTML sanitization

Yes, since there is no better solution for now, the simple disable-html flag could be the answer.

From what I read, we could add the attribute to the code the same as Lazy and Func.

I tried that, it didn't work (although I might have done something wrong).

There could be other reasons why for example JSON.NET still supports .NET 2.0.

Sentimental value? :stuck_out_tongue:
Unlike JSON.NET, CommonMark.NET has the luxury of being in pre-release, which means it has much greater freedom in this regard.
Although I managed to work around missing .NET features so far, it feels like coding with one hand tied behind one's back. I recall at least four occurrences of adding/removing/adding/removing Func flavors.

It can go away as soon as there is a better way of specifying the formatter.

Gone :sunglasses:

Any chance you could add image size extensions?
https://github.com/jgm/CommonMark/wiki/Deployed-Extensions#image-size

These are common requests I get in Markdown Edit for extensions:

Language specification in fenced code blocks for syntax highlighting
  ```C#

Generate header/image identifiiers for later styling

Checkboxes similar to GitHub

Tables

Math formulas for Math Jax?

TABLES

[x] I'd love to have checkboxes!

Sorry for the late response. Overall my intention for a while now has been to update the readme to say that this package is deprecated and instead recommend to use https://github.com/lunet-io/markdig
The reason is that when I started work on porting cmark to .net I was under the impression that the standard will be constantly improved and things like tables will be added to it so that there would not be such a significant need for extensions. Unfortunately that did not turn out to be true, so the design of markdig that enables extensions is much more suitable for the current situation.


Added focused element type

Extension now returns the focused element type. Currently limited to text editor, terminal or undefined.
Added new command command-server.getFocusedElementType

I've done some clean up now


Add tests for fp12 arithmetics

Add tests and test vectors for fp12 arithmetics
Add some missing fp4 tests

Coverage increased (+0.7%) to 89.692% when pulling 94f902205119997ab85cbbe0f92d747632f678b8 on add-fp12-tv into a89393bd9fb81d01df90a5a24fcab30a2a817755 on master.


Packed 2101010 Vertex Attribute Support

Hello, does bgfx also support packed 2101010 vertex attributes? It's quite handy for storing normals and tangents and is available on D3D10/OGL3 hardware.

Nope, but I can add it.

It will be great, thanks! :) Oh another question, what will bgfx do if it isn't supported by the target hardware? Will it decode and convert them to raw floats silently, or does it require me to decide? (for example if I want to fallback to the uint16 for every normal/tangent component)

It will be handled with caps, like this:
https://github.com/bkaradzic/bgfx/blob/master/include/bgfx.h#L103
You'll be responsible to handle that case.

Sounds great, thanks!

@siavashserver I added AttribType::Uint10 https://github.com/bkaradzic/bgfx/commit/8da579ff99a62318682f1e913f5e0d9f6b8f8b2c
Can you try it?

@bkaradzic I'll setup a quick test, I wasn't expecting to see it baked for this summer :-D
It's surprising that D3D doesn't support the signed variant like OGL, so an extra -0.5 is necessary on shader side.
Thanks again!

I didn't update docs, but you probably already know, that limitation is that Uint10 makes sense only as 3 components. A2 should be ignored due to D3D9 limitation. And less than 3 components will still take 32-bits at which point other types are better.

Yes, the 4th component (A2) should be ignored for portability reason. OGL3.x doesn't use same normalization formula as OGL4.x and D3D10+, and for example 0 might endup as 0.3 (or 0.6?) in vertex shader if I remember correctly.

Sorry for being late, I tried to modify example-01-cubes and use the new packed format to store the vertex colors as a 4 component normalized Uint10, but cubes do appear as black. (no modifications performed on shaders)
Here is the modified file: https://gist.github.com/siavashserver/6566b3099b32bde3fa16

Currently, I'm working on the option that allows packing normals into unsigned ints (both 8 8 8 8 or 10 10 10 2 formats). I ran into the issue. When bgfx is binding vertex attributes, it uses GL_UNSIGNED_INT_10_10_10_2. It produces OpenGL error "invalid enum" on glVertexAttribPointer call:
GL_CHECK(glVertexAttribPointer(loc
        , num
        // According to docs this function accepts GL_BGRA
        // works ok but the normal components must be reordered in the shader.
        // The value 4 returned by vertexDecl.decode(...) also works ok.
        //, 1 == type ? GL_BGRA : num
        , s_attribType[type]
        , normalized
        , _vertexDecl.m_stride
        , (void*)(uintptr_t)baseVertex)
        );

This problem can be fixed by using GL_UNSIGNED_INT_2_10_10_10_REV instead of GL_UNSIGNED_INT_10_10_10_2:
static const GLenum s_attribType[] =
{
    GL_UNSIGNED_BYTE,            // Uint8
    GL_UNSIGNED_INT_2_10_10_10_REV,  // Uint10, works with this one just fine
    //GL_UNSIGNED_INT_10_10_10_2,  // Uint10
    GL_SHORT,                    // Int16
    GL_HALF_FLOAT,           // Half
    GL_FLOAT,                    // Float
};

Also, I noticed that geometryc  uses Uint8 packing, while Uint10 can provide better precision.
Unless the usage of Uint8 packing was chosen on purpose, maybe that is the reason why the Uint10 did not work at the moment of implementing the tool.
My version of packing works this way (https://github.com/VladSerhiienko/FbxPipeline/blob/master/FbxPipeline/FbxPipeline/fbxpmesh.cpp):
union UIntPack_aaa2 {
    uint32_t u;
    struct {
        uint32_t x : 10;
        uint32_t y : 10;
        uint32_t z : 10;
        uint32_t w : 2;
    } q;
};

template < bool tangent >
uint32_t PackNormal_aaa2( const float* v ) {
    UIntPack_aaa2 packed;
    packed.q.x = ( uint32_t )( mathfu::Clamp( v[ 0 ], -1.0f, 1.0f ) * 511.0f + 512.0f );
    packed.q.y = ( uint32_t )( mathfu::Clamp( v[ 1 ], -1.0f, 1.0f ) * 511.0f + 512.0f );
    packed.q.z = ( uint32_t )( mathfu::Clamp( v[ 2 ], -1.0f, 1.0f ) * 511.0f + 512.0f );
    packed.q.w = tangent ? ( uint32_t )( mathfu::Clamp( v[ 3 ], -1.0f, 1.0f ) * 1.0f + 2.0f ) : 0;
    return packed.u;
}

@VladSerhiienko Cool! It wasn't implemented because once I added feature didn't go back to geometryc to add it there too.
GL_UNSIGNED_INT_10_10_10_2 vs GL_UNSIGNED_INT_2_10_10_10_REV, not sure, have to check if it matches D3D.
packed.q.w = tangent ? ( uint32_t )( mathfu::Clamp( v[ 3 ], -1.0f, 1.0f ) * 1.0f + 2.0f ) : 0;

Shouldn't you do some rounding here because you only have space to represent values 0-3.

@VladSerhiienko I was just looking at your FbxPipeline project, and noticed you're using vcache_optimizer, see this instead: https://github.com/zeux/meshoptimizer.

@bkaradzic Thanks for the answers! I'll take a look at zeux`s meshoptmizer soon, looks very promising at first glance. Yeah, you're right, the w component scaling looks incorrect, thanks for that! I think it is up to a developer to check if it matches. The shader has a macro, that defines its type, so he can do some reordering in the shader if needed. It looks like that for OpenGL there are not some many options.
ES 2 requires some extensions to use this format, ES 3 (https://www.khronos.org/registry/OpenGL-Refpages/es3.0/html/glVertexAttribPointer.xhtml) expects only GL_UNSIGNED_INT_2_10_10_10_REV (or signed), there is no GL_UNSIGNED_INT_10_10_10_2 format in the docs. There is a page (http://www.informit.com/articles/article.aspx?p=2033340&seqNum=3) that has nice imgs of format layout.

Looks like GL_UNSIGNED_INT_2_10_10_10_REV (without GL_BGRA) will decode the uint as expected + I can see correct results with that function in FbxPipeline.

@bkaradzic I checked and A2 seems to be supported on GLES3, Metal, Vulkan, D3D11 and D3D12. So I would say on most platforms.

So maybe uint10 chould also have a2, and caps could be false on gles2/d3d9.
Or have a new format with added a2.

I would like to use it to store tangent+(handedness in w) vectors in geometry file. My assumption is that 0.0 and 1.0 is coded perfectly even on 2 bits. It would be higher precision for the same number of bits. If A2 isn't supported runtime, one can convert it to Uint8.


replace @octokit/rest with @octokit/core

Hey friends,
@octokit maintainer here 👋
It looks like you only use the octokit.request method
https://github.com/cypress-io/github-action/blob/345747a85e46d21addb1f8bc23116b9eefdcf41a/index.js#L386-L410
In that case, I would recommend to use @octokit/core instead of @octokit/rest - the latter just adds ~600 convenience methods for every REST API endpoint. There will also be fewer deprecations & breaking changes with @octokit/core. None of your could would need to change is
- const { Octokit } = require('@octokit/rest')
+ const { Octokit } = require('@octokit/core')

I'd be happy to send a pull request myself

@gr2m That'd be great! We would welcome a PR.


Typo correction and added a compiler link

Typo correction of veriloggen: verilogger -> veriloggen
Added NNgen: https://github.com/NNgen/nngen

Thanks! I had seen this project in the past, but it disappeared from my radar. Great to see it going still.


Add support for DSCP markings for QoD sessions

Problem description
A user may want to apply a QoS Profile to a class of traffic based on the DSCP value according to RFC4594 in the IP header.  This would be traffic from the user device to / from any network and would not necessarily be restricted to a specific application server.
This aligns with traffic classification as defined in the Home Devices QoD API
Possible evolution
Instead of requiring the application server in the create session schema, add a flow identifier schema that includes application server, DSCP and can contain other attributes which could be used to classify the traffic.
Alternative solution

Additional context

The application server schema supports subnets, so you can already specify <IP_ADDRESS>/0 or ::/0 if you want the profile to apply to any flow to/from the device.
DSCP values can be implicitly associated with a given QoS profile, in the same way that 3GPP QCI/5QI values can be implicitly associated with a given QoS profile. The API consumer should not have to select more than the profile name from the available options to specify the QoS they would like. CAMARA APIs are intended to be used by developers who do not have the first clue about telco networking, but do understand their throughput, latency and jitter requirements.
If you think it is important that the typical QoD API consumer knows exactly what DSCP they will get for the fixed network part of the route, and that cannot be captured in either the profile name or description, then it could be considered to add this as an additional optional property of a QoS profile.
But I am strongly against giving API consumers the ability to "pick and mix" QoS profile parameters so as to build their own custom profile.

The application server schema supports subnets, so you can already specify <IP_ADDRESS>/0 or ::/0 if you want the profile to apply to any flow to/from the device.

Excellent.  That works.

CAMARA APIs are intended to be used by developers who do not have the first clue about telco networking, but do understand their throughput, latency and jitter requirements.

DSCP and L4S are not limited to the telecommunications space.  To date, all of the application developers that I've spoken with are very familiar with marking using DSCP since it also helps with Wi-Fi networks.  The Wi-Fi improvements are arguably more impactful than the access networks ones for wireline networks.
I've spoken with gaming, streaming application and other related developers on this subject.
The primary downside that we've encountered with DSCP values is that they are frequently bleached at different points in the network.

QoD API consumer knows exactly what DSCP they will get for the fixed network part of the route, and that cannot be captured in either the profile name or description, then it could be considered to add this as an additional optional property of a QoS profile.

This approach would work.  It overloads functionality the QoS profile more than I like, but it would solve this in a way to enable server providers flexibility.
Does anyone else have thoughts on this?

I agree with @eric-murray's comment. DSCP is implicitly a part of QoS profile that captures the application intent. Additionally, operator's have their own DSCP schema implementation which could be quite different than the standards. Also, it would be confusing to the developers who may not have deep knowledge of the protocol.

I appreciate that not all networks will have support for DSCP header markings for traffic classification.  However, I don't think that is a reason to not include it in the session creation, since this includes all of the information necessarily for identifying the traffic which will be managed by the QoD flow.
Some of the device attributes in the create session schema are not supported by wireline networks.  There is a president for including attributes in the create session schema which are not supported by all underly networks.

phoneNumber
networkAccessIdentifier

While collecting feedback on this topic, I've found that explaining why the DSCP would be in the QoS Profile to be quite confusing.  Since the DSCP is a packet marking and not an actual QoS attribute.
I would like to modify the proposal to add a new optional property diffServe to the createSession schema.
If the diffServe classification is requested, but is not supported, then the server can return 400 with an appropriate error message.
The alternate approach is to add a diffServe or preserveDiffServe property to the QoSProfile.  This has the advantage of allowing the operator to specify if they support this.  Unlike the other attribute in the QoS Profile schema, this is a packet marking and not an attribute of the actual quality of service.  This could be used to preserve the diffServe packet markings, since they are frequently bleach by default.  Since this isn't a part of the session, it would be confusing to use a specific attribute in the QoS Profile identifying the traffic.  But other elements and mechanisms in the network would have access to these fields.

Hi @RandyLevensalor
I think including dscp in the QoS profile is no more confusing than including priority. Neither are QoS metrics in themselves, but rather are technical means to achieving specified QoS metrics, particularly latency. If end users only cared about the QoS of their traffic, they would not care what priority their traffic is given. Indeed, they should not care.
But we recognise that there are end users who understand such details and would like to know or even specify how their traffic is managed. As network operators, this works to our advantage because setting priority is one thing that we can control with absolute certainty. If that doesn't give the end user the QoS that they expected (because other traffic has an even higher priority), well, we still gave them what they asked for, so can charge them anyway.
Can you clarify the following points about your proposal:

Why can the existing priority field of the QoS profile not be used for this? It's an integer, so can easily be interpreted as a DSCP value. How will fixed networks otherwise use the priority field?
If the API consumer directly specifies a diffServe value when creating a QoS session, what are the allowed values? Is it boolean (diffServe will / will not be preserved), or are they actually specifying a required DSCP value, or something more?
If diffServe is a DSCP value, what does the network accepting this actually mean? Does it mean that any traffic accepted by the network that has the DSCP field set to that value is guaranteed to leave the network with that value preserved? Or does it mean more than that? What exactly is the API consumer expecting if the network accepts their diffServe requirement?

Why can the existing priority field of the QoS profile not be used for this? It's an integer, so can easily be interpreted as a DSCP value. How will fixed networks otherwise use the priority field?

Priority is a QoS setting at the MAC layer based on a policy in the access network.  DSCP and DiffServe is an L3 / IP header that can be set by the application.  It's possible to create a policy to set any priority for a given DSCP value across all access network types.
There are conventions to map different DSCP values to specific priorities. However, there is no guarantee that the a specific DSCP value be mapped to a given priority.  Allowing developers to map traffic with a DSCP value to specific priority is one of the primary goals of this enhancement.

Priority is a QoS setting at the MAC layer based on a policy in the access network.

I think that should be documented if that is the case for fixed networks, as my expectation would otherwise be that QoS profile parameters apply to the defined flow, which is a layer 3 flow between the two specified IP addresses.

Priority is a QoS setting at the MAC layer based on a policy in the access network.

I think that should be documented if that is the case for fixed networks, as my expectation would otherwise be that QoS profile parameters apply to the defined flow, which is a layer 3 flow between the two specified IP addresses.

I think that I wasn't clear.  That flow is an L3 flow.  However, none of the QoS attributes are defined in the L3 header.  There is L3 priority field.

From QoD Call Feb 9th: Related to #243, also move to backlog until use cases are described.

Slides presented on November 15th.
qos-profile-l4s.pptx


JavaScript Formatting

I can't seem to get the

how are you configuring your prettier?

In .vscode/settings.json
"prettier.semi": false,
"prettier.printWidth": 180,

ah, that will only set it for the vscode prettier extension which this bypasses. you'll need to set up your config following https://prettier.io/docs/en/configuration.html

You made my day! That got it working, but I had to uninstall prettier and install prettier-vscode.
I hope this helps others with the same problems.

ah, that will only set it for the vscode prettier extension which this bypasses. you'll need to set up your config following https://prettier.io/docs/en/configuration.html

Hey man, how did you make it work? I created a .prettierrc file like it suggested in @stevesob 's link, but it did not override svelte's formatting.

Nevermind, I made it work by adding a .prettierrc and installing prettier-vscode too. The problem was caused by another vscode plugin, beutify. I disabled it, and it worked!


Sample code for ASP.NET MVC5 OAuth

Heya,
https://github.com/ysinjab/InstagramCSharp/blob/master/Samples/OAuth/ASP.net MVC5/InstagramOAuthController.cs#L35
Line 35 in the controller sample is:
AuthUser authenticatedUser = JsonConvert.DeserializeObject<AuthUser>(responseContent);
I believe it should be:
AuthenticatedUser authenticatedUser = JsonConvert.DeserializeObject<AuthenticatedUser>(responseContent);
Not a big issue for the lib itself, as this is sample code only, but would make it easier for whomever wants to use the sample for quick code that works.
Thanks for a great lib!

Many Thanks justabuzz ;)
I updated the samples


HOWTO: Per example gradient

This howto exemplifies how per-example gradients can be retrieved using jax.vmap.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #306   +/-   ##
=======================================
  Coverage   79.33%   79.33%
=======================================
  Files          34       34
  Lines        2255     2255
=======================================
  Hits         1789     1789
  Misses        466      466

Continue to review full report at Codecov.

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

We've redone our HOWTO system. Here's an example of the new format:
Rendered in ReadTheDocs: https://flax.readthedocs.io/en/latest/howtos/ensembling.html
Document source: https://github.com/google/flax/blob/master/docs/howtos/ensembling.rst (see the :testsetup, :testcode and :codediff directives)
We'd happy take pull requests revamping this HOWTO to the new system.

Looks like this PR is inactive, so I'll close it. We're tracking the HOWTO request here: #858


Custom data

If I have set of label and image. Whether I have to convert to bin and label in format of KITTI dataset or not ?

You can just follow the official instruction of each dataset to prepare the data.


Remove unused assignment in ExpectationsTestRunner

I noticed this in the warnings when running on CI (repeated 14 times).
/Users/runner/work/ruby-lsp/ruby-lsp/test/expectations/expectations_test_runner.rb:15: warning: assigned but unused variable - params

I added a raise in run_expectations and everything still passes. We're must be overriding it in every class that inherits from ExpectationsTestRunner, so should we just remove the body and mark it as abstract?


Fixing aXe spelling

@aarongustafson Can you sign the CLA? Thanks!

@aarongustafson I just realized this PR needs to be done against: https://github.com/sonarwhal/sonar/blob/master/docs/about/FAQ.md.  Can you open it in the other repository? Thanks!

@aarongustafson Fixed in https://github.com/sonarwhal/sonar/commit/22f2e1816e8d200fa3ccaf0871c1f260ecbcc316.

Note: You should update the content from your repository.

Signed.


Expose diagnostic error codes

PR to parse UR10 error codes from diagnostic logs that are streamed on the Primary Interface port 30001

Thank you very much for your contribution! I've wanted to extract parts of #186 since a long time, since that one got too big at some point. I'll have a deeper look at this ASAP.

@urfeex Any updates on this?


Allow custom tag name and id attribute

Hi @listrophy,
can you merge the actual master into your branch, resolve the conflicts and make a new build? Then I will test and accept your PR.
Thanks


Added a Simplified Chinese translation of the README

Added a Simplified Chinese translation of the README, zh_CN

cc @codegangsta

@meatballhat : Excuse me,why do we not see Simplified Chinese translation of the README?

Hi @panjunjie,
It is merged, but I see that there wasn't a link included on the English README file. I will add it now.
Thank you!

Added the link in https://github.com/codegangsta/negroni/commit/41253136e3592bb8f1654186033bcc0c57a5ad70

Thank you for your reply. I like the project very much


py.run has import issues on 3.8

The following code crashes on 3.8:
 test_write_unraisable() {
     #[pyfunction]
     fn report_unraisable(py: Python<'_>) {
         use pyo3::exceptions::PyRuntimeError;
         let err = PyRuntimeError::new_err("foo");
         err.write_unraisable(py, None);

         let err = PyRuntimeError::new_err("bar");
         err.write_unraisable(py, Some(py.NotImplemented().as_ref(py)));
     }

     Python::with_gil(|py| {
         let report_unraisable = wrap_pyfunction!(report_unraisable, py).unwrap();
         let locals = PyDict::new(py);
         locals
             .set_item("report_unraisable", report_unraisable)
             .unwrap();

         let source = r#"if True:
         import sys

         captured = []
         def report(data):
             captured.append(list(data))

         original_hook = sys.unraisablehook
         try:
             sys.unraisablehook = report
             report_unraisable()

             assert len(captured) == 2

             assert captured[0][0] is RuntimeError
             assert str(captured[0][1]) == 'foo'
             assert captured[0][4] is None

             assert captured[1][0] is RuntimeError
             assert str(captured[1][1]) == 'bar'
             assert captured[1][4] is NotImplemented
         finally:
             sys.unraisablehook = original_hook
         "#;

         py.run(source, Some(locals), None).unwrap();
     });
 }

(From #2889)
I'm not yet sure what's going on here. Probably worth investigating sometime.

No longer reproduces on main. Probably was fixed by #3378 (thanks @GoldsteinE!)


Can i cleanup old logs?

I want to cleanup old logs from S3.
There is option for do it? Or can I do it manually?

Hello, @alu
I'm not sure how to do it with digdag itself.
(IIUC, It's not implemented yet. )
An alternative idea, Have you ever tried S3 Object lifecycle management?
http://docs.aws.amazon.com/AmazonS3/latest/dev/object-lifecycle-mgmt.html
Ref: Twitter in Japanese.

Right. Old logs need to be deleted manually for now. As @hiroyuki-sato suggested, using lifecycle management would make it easy.

@hiroyuki-sato @komamitsu
Thank you for response.
Our storage is S3 LIKE private storage so we can't use lifecycle management because not implemented yet on the storage.
So i think delete logs from /log/YYYY-MM-DD after a certain period of time.
It's not problem?
Thanks.

Hello, @alu
Another user removed old logs.
It seems work well.
The user used log-server.type = local and added cleanup task like the below.
find /dir -mtime +180 -exec rm {} \;
Ref: Twitter (Japanese text)

@hiroyuki-sato
Thanks :)


Fix UnitTests failing while building in linux environment

#175
I have changed file path definition cause there are some differences between Linux&Windows path declaration that's why the bug appeared.
Now they are defined in correct way regardless of the system

Thank you :) Looks ok.


[#1318] proper logout for intercepted 401s

:nut_and_bolt: Description: What code changed, and why?
When a 401 was intercepted by the auth interceptor, and not the periodic call in chef-session, the interceptor would call logout() without arguments. This used to have two effects:

the user is sent back to / (or rather, /dashboards/event-feed) after re-signin, regardless of where they were before
the user has to select their signin method.

This became apparent most obviously when using IAMv2.1, because it has another peridoc call: checking project rules' apply status. So those calls, when failing, would cause no automatic re-login for SAML users, as desired in #1246.
Now, the logic is inverted: If nothing is passed, the signin happens as if it was a re-signin: including the proper state for going back to the page, and skipping signin method selection if possible.
⚠ The way chef-session figures out "which page we're on" is hacky IMHO; it should rather subscribe to something in ngrx store, instead of reading a window global. (I might be wrong.)
:chains: Related Resources

#1246
Fixes #1318

:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change

start_all_services, setup automate-ui in your preferred way
chef-automate iam upgrade-to-v2 --beta2.1
change the dex config template as outlined in #1246
sign in locally using SAML, go to https://a2-dev.test/settings

you will see nothing, but it's the test to verify we end up on the same page after re-signin

wait for a minute
notice that there's a few requests, and a roundtrip through dex and okta, and you'll end up on the same page again

:white_check_mark: Checklist

[X] Tests added/updated?
[ ] Docs added/updated?

@msorens thanks for playing with this. I'm afraid I don't follow here:

(different URL params and on screen param, of course)

Re: the videos of your attempts,
Attempt 4
The network tab shows

which is what we'd expect with this PR -- the failing request is the periodic one (GET /apply-rules: 401), and the browser then goes to /session/new?state=/settings&id_token_hint=YOURIDTOKEN. As far as automate-ui and this PR is concerned, that's what we want to see happen.
The question then is: why did you see the local user login? I can't tell from the video alone: Did you use a SAML user? What's the id_token? Anything in the logs of session-service? What are the query parameters of the request to /dex/auth?
The fact that the request to dex's /auth endpoint redirects you to /auth/local

means one of two things:

there was a connector_id=local query parameter to /dex/auth -- which would mean your id_token wasn't the one of a SAML user, but a local one
there was only one dex connector set up -- so it would automatically send to you the one and only. This is unlikely, because then, we shouldn't see the Back link in the top left.

I'd conclude that your id_token must not be the one of a SAML user. I suppose it wasn't, since you've been testing this PR 😄
👉 Can you reproduce this?
Attempt 1 and 7
There's no data to attempt 1, making it hard to assess; however, this error has -- unfortunately! -- nothing to do with the change in this PR: it's related to session-service and its cookies. (Those cookies are http-only, which means that our UI code in automate-ui can never see them. 🙈)
However, there are multiple tabs involved -- one logging out, which starts one session dance, and a fresh one, which starts a second session dance. I would have thought that this set of issues had been resolved in #716. This is something to investigate more throughly. We'd need the database contents to see what had happened here; I'll try to reproduce this on my end.

So, letting this one some more, I've noticed that it's racy 😞
There's two requests getting a 401 when the token is expired, and they cause a call to logout():

However, only one includes the id_token_hint, and the second one of them is canceling the first. So depending on their order, the right thing happens, or doesn't. (In the screenshot, the order was the lucky one, but it seems just as likely that the order is reversed.)
I'm looking into how to fix this. We might have to push this down the road for the chef-session refactor after all... 🤔

ℹ the last commit resolves the last comment I've posted above ☝
@msorens I'm still unsure about your relay state issues, and I haven't been able to reproduce these...


Added section on Pastafarianism, Fixes issue #13

attempt 2

There are now merge conflicts. Could you update with the latest version from upstream?


How fine-tune the model?

Very nice work,
do you have a sample of code for fine-tuning the model for a task?
Could be possible to fine tune as it was a model from the torch hub?

Yes, you should be able to fine-tune a torch hub model like normal.
As for how to fine-tune the models, I'd suggest taking a look at the finetuning script in the mae repo. It should be fairly similar to what we did, but you might have to tweak "drop path" and "layer decay" to your specific task.
We will eventually release training code in this repo as well, but we're currently fairly busy so it might take a while.


Reland "Speed up first asset load by encoding asset manifest in binary rather than JSON (#116662)"

Relands #113637, which was reverted by #116662.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

Due to difficult to debug issues in g3, I'll be taking a different strategy to landing this change.
Instead of one change that 1) generates the new asset manifest and 2) also uses it for image resolution (with code to fallback to AssetManifest.json to prevent g3 breakages), two separate changes will be made. This way, in between these two changes, g3 tooling can be changed to produce the new asset manifest. The result is that we don't need the complicated AssetManifest.json fallback logic that is difficult to get working in g3 tests.
Development is being tracked with https://github.com/flutter/flutter/issues/117228


Allow a variable number of ResponseGroup arguments

PR for #2

Hi,
when only add the [Flag] to the AmazonResponseGroup we have the same functionality.
I prefer the flag.
//params
wrapper.Search(search, AmazonSearchIndex.Automotive, AmazonResponseGroup.ItemIds, AmazonResponseGroup.Offers, AmazonResponseGroup.Images);

//flag
wrapper.Search(search, AmazonSearchIndex.Automotive, AmazonResponseGroup.ItemIds | AmazonResponseGroup.Offers | AmazonResponseGroup.Images);

yep, it is much less change


Create Entity "Position" #11

Description
Create Entity 'Position'

Expected outcome
Fields: Name, Description

Actual outcome

Steps to reproduce

Client environment

Resolved by #16


[AutoRelease] t2-cognitiveservices-2024-11-12-24074(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/5716
Recording test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=976
BuildTargetingString
azure-mgmt-cognitiveservices
Skip.CreateApiReview

issue link:https://github.com/Azure/sdk-release-request/issues/5716


Use mapbox/polyline for polyline/polygon URI param encoding

Hi,
Looking at https://github.com/nrenner/brouter-web/issues/220, it seems that mapbox/polyline encoding is indeed enough to get past the URI length issue. Here is a first draft, not yet functional. :/

Just saw this one again - don't know what to comment on if it's not functional yet. But if it seems to solve the issue we should go for it?

Hi,
Sure, I was working on the profile tweaking ui lately and let this one drift a bit aside. I'll try to fix it and have a working mapbox/polyline implementation soon.
Still a WIP then.

@Phyks FYI we are talking about too-big nogos limitation on #405 - maybe it can add extra motivation on that PR that should address that :). Or maybe you do not plan to work on it anymore?

Hi @bagage, thanks for the heads up, this one completely slipped out of my sight...
I'm not sure to have much free time to commit into this one soon. If anyone is interested in taking over, please feel free to do so!

Continuing on #417 then, thanks @Phyks!