Still Not Working?

Is anyone actually using this on a live store? There are still ToDo's in the code and incomplete order status functionality.
I can find no examples of any live magento sites using or any developers who have (successfully) installed. Bitpay why do you let this languish for so long? This will be 2 holiday seasons in a row you missed.

Last I checked the plugin release works without a problem with Magento 1.8, 1.8.1, and 1.9
See releases here:
https://github.com/bitpay/magento-plugin/releases/tag/v2.1.10
http://www.magentocommerce.com/magento-connect/bitpay-bitcoin-payment-method.html

@aleitner So does that mean you have seen this actually working on a real store taking real order and updating order status in magento admin correctly when payments are completed?
That has not been my experience the last 2 times I've checked the code; a year apart. Nothing in change logs indicates this was addressed since then as most commits are 2 years old.
No budget left to check this another time as most clients went with Coinbase (and their working extension). 1 client still has bitpay but gave up on bitcoin in general when Bitpay failed to address anything for 2 holidays in a row.
Tell me it actually works in real life with a real merchant and real customers and I'll check it again

Yes, this plugin works just fine and real customers use it.
No, I am not going to provide a customer by name (this is not BitPay's policy). The best I can provide is public data that Magento Connect provides which you can view within your Magento Connect account.

Not asking for an example. Just that you understand the issues in past with no mechanism for changing order status on payment (literally a To Do in the code) and that this has since been finished. You, @kleetus, can say without hesitation that professional merchants have been able to use it in a production environment without issue.
I can't charge to review/test this extension again so appreciate not wasting my time if this is not the case.


Remove various columns from organ_data

🗑 Data to Remove
Remove the following columns from the table organ_data:

sensitivity_min
sensitivity_max
sensitivity_comment
specificity_min
specificity_max
specificity_comment
npv_min
npv_max
npv_comment
ppv_min
ppv_max
ppv_comment

Discreet values for sensitivity, specificity, NPV, etc., are recorded at the biomarker-organ-study level. This may have once been used to aggregate the minimum and maximum values seen for each characteristic, however there is no longer any mention of these characteristics in the BMDB code.
The RDF generator has never used any of these columns.
📝 Code Modification?

Biomarker database: no
RDF generator: no

Recommend batch №2
Note: modifications to portal are not allowed; that means this information is in fact used and this table/column should be preserved.
💽 SQL
ALTER TABLE `organ_data`
    DROP COLUMN `sensitivity_min`,
    DROP COLUMN `sensitivity_max`,
    DROP COLUMN `sensitivity_comment`,
    DROP COLUMN `specificity_min`,
    DROP COLUMN `specificity_max`,
    DROP COLUMN `specificity_comment`,
    DROP COLUMN `npv_min`,
    DROP COLUMN `npv_max`,
    DROP COLUMN `npv_comment`,
    DROP COLUMN `ppv_min`,
    DROP COLUMN `ppv_max`,
    DROP COLUMN `ppv_comment`;

🩺 Testing Methodology

RDF before/after comparison: yes
In-app testing: yes
Other: N/A

🧘 Acceptance
Sign off by @mryan4 by closing this issue

No errors found during testing. This issue is closed.


feat: chips

You can just start the style guide's docs and see the documentation. The code is not perfect, however we can refactor, when we figure out more common pieces between the different components.

@jkettmann can you check again if you see the tooth on the bubble's background? :)
Regarding variables / darken / lighten and other functions. My idea is to have those done after we are at least more confident what can be reused for other components. It is really ugly to have this huge configuration file, but everything else before we have at least the common pieces together would be Premature optimisation. So let's leave that for another time.
Regarding the focus state I completely ignored it for now. Will discuss further with @skreutzberger how to proceed on that topic in a future ticket.
References :
https://www.tjvantoll.com/2013/01/28/stop-messing-with-the-browsers-default-focus-outline/

Looks good now


Add document for node conformance test.

This PR added a document for the node conformance test to Creating a Cluster/Running Kubernetes on Custom Solutions/Validate Node Setup
@dchen1107
/cc @kubernetes/sig-node

This change"s

Does this mean the node e2e tests have to be 100% non-flaky? Or will node conformance test retry a few times on failure?

@davidopp By default, the node conformance test only runs the node e2e test with "[conformance]" label, which should be stable (or else we should fix it or remove the conformance tag)
However, add flake retry is a good idea for better user experience.

Docs LGTM. Needs a Tech LGTM.

@dchen1107 PTAL.

LGTM


change *TintColor props to *Style for more freedom

This allows full styling of the indicators, not just tint color (I needed a border).
Eg: indicatorStyle={{backgroundColor:'none', borderColor: 'grey', borderStyle: 'solid', borderWidth: 1}}currentIndicatorStyle={{backgroundColor:'white'}}

Perhaps the old style should be allowed too, for backwards compatibility?

@jakecr  Good idea. I will update later


Remove errcheck to fix CI builds.

I don't know if the author want to fix it:
See https://github.com/kisielk/errcheck/issues/89
We can always re-add it in a year, when 1.4 is long gone, or we can fork it in the meantime, if it is that important.

It would be nice not to remove this completely - could we skip for go < 1.5 builds?

Agree, but I have no good idea on how to do that ATM, so I would just remove it until we find a good solution.

Something like this (lightly tested only) which won't run errcheck for go version 1.4 or earlier might work...
diff --git a/Makefile b/Makefile
index f1f585d..d218135 100644
--- a/Makefile
+++ b/Makefile
@@ -13,7 +13,7 @@ test:	rclone

 check:	rclone
 	go vet ./...
-	errcheck ./...
+	[[ `go version` =~ go1.[0-4][^0-9] ]] || errcheck -verbose ./...
 	goimports -d . | grep . ; test $$? -eq 1
 	golint ./... | grep -E -v '(StorageUrl|CdnUrl)' ; test $$? -eq 1

(Sorry, my bash foo isn't the best ;)
We also need something similar to avoid "go get"-ing the package in the first place, since that is what is actually failing.

I have fixed this in c245183101f94afcd87cea0a0274412bfa8bd00f with lashings of horrendous bash foo ;-)


Revert typescript bump.

The current version seems to be building broken typescript. Specifically, the error I'm seeing is
node_modules/mobx-quick-tree/dist/src/index.d.ts:15:250 - error TS1005: '?' expected.

And that line refers to the generated type for types.compose, which is quite
large. Although I tested this and it seemed to work, I must have not been using
the built version locally.
I'll unpublish 0.3.1. Even with the version currently specified (4.7.4) the file was considered ill-formatted. Really bizarre 😕

Successful typechecking on another project 🚀
If I see this again, I'll try to find a way to validate the generated code and add that to our CI.


Inconsistent text

It would be looking better if you make the text description consistent with the left vertical line (which all other elements respect):

Legit don't know how to feel about that. Sometimes I like the indentation and some times I don't. I will think about this.
In the mean time add this:
.layout-desktop .detailSectionContent {
	padding: 0vw 0vw 0.25vw 0vw !important;
}

I ended up making the change. Thanks for the feed back. Give it a day or two for the changes to show up on your Jellyfin.

Thanks, now it looks nice on mt desktop in Firefox. Also on my smartphone (in the app) is the description text ok, but there is now indentation for the title...


(1password) Update 1Password name

Description
Updated the 1Password name in the description to match the spelling of the name on the official website.
Motivation and Context
So that the name in the description on Chocolatey Community matches the official name.
How Has this Been Tested?
I haven't tested it in any way, but my changes concern only the description, so there should be no problems.
Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[x] My change requires a change to documentation (this usually means the notes in the description of a package).
[x] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review

Awesome work @rakleed! Thanks for your contribution!


Validate custom Docker images

Fixes #398 .
Changes proposed in this PR:

validate docker hub images ( the get req to the docker hub is blocked by CORS when running locally)
validate 3rd party images (just a options request to the provided url and checked response status)

Regarding the docker image validation there are at least 2 thing that we need to decide on:

what text imput we provide to the end user. As it is now we have separate fields for the image url and container tag.

we can opt for image and tag combined but it will get more trickier to handle the the docker hub images (we will have to parse the input and then validate and set algorithm object values) and harder for the user to figure out what to fill in in that input field. The input should probably look like this oceanprotocol/aquarius:v2.1.12 (this is how docker hub displays them within their website)
if we decide to stick with both input fields the tag is somehow useless for the 3'rd party images because it's probably already in the url. On the other hand it will be much easier and maybe more clear for the user that is using public docker hub images to fill in the publish form.

the other thing would be the validation step. As it is implemented in this PR the validation takes place after hitting publish

we could stick with this approach
or we can have a validate button similar to the file input field, but if we stick with having separate field for image url and image tag this button should cover both input fields

as for 1.: while it would be nicer for user to just have one field Docker Image which accepts image name + tag or image URL and we figure out the required values in background, this could get tricky and I think for image URLs the tag is usually not part of URL. So think having image name/url & tag individually is good enough. We could try to detect tag name if it is added when user adds imagename:tag to input, and auto-populate the Docker Image Tag field. But then again, we expect this not be used by majority of our users so we do not need to bother too much with it for now.
as for 2.: also think it's fine for now validating on hitting publish, showing the toast as the warning is not ideal (validation error as part of error messages shown on respective input field would be), but also good enough

as for 1.: while it would be nicer for user to just have one field Docker Image which accepts image name + tag or image URL and we figure out the required values in background, this could get tricky and I think for image URLs the tag is usually not part of URL. So think having image name/url & tag individually is good enough. We could try to detect tag name if it is added when user adds imagename:tag to input, and auto-populate the Docker Image Tag field. But then again, we expect this not be used by majority of our users so we do not need to bother too much with it for now.
as for 2.: also think it's fine for now validating on hitting publish, showing the toast as the warning is not ideal (validation error as part of error messages shown on respective input field would be), but also good enough

I agree that showing the toast is not ideal, I took a look over manually setting a validate error to a specific formik input, that's not really easy with our implementation but also in our case it a little bit trickier because we cannot know for sure witch input is wrong or causing the error (image url or image tag) and on witch to place the validation error. So for the moment I think we can display the error as a toast and it will be similar with the validation of the algorithm file or we can display the error using setError method from the publish page index. I would personally opt for the the toast 😄

All good, let's merge. Looks like that failing Windows test happens pretty often but can be ignored for now

All good, let's merge. Looks like that failing Windows test happens pretty often but can be ignored for now

Yeah that Windows test is becoming annoying.


fix: includes/notification-hubs-android-studio-add-google-play-services.md

Replace "text" for "gradle" language fence

@nschonni : Thanks for your contribution! The author, @spelluru, has been notified to review your proposed change.

@nschonni - Thank you.
#sign-off


Documentation build is failing

See: https://readthedocs.org/projects/pinecone/builds/3479574/

@audreyr ping


feat: launch modules from docker images

Adds the ability to also launch a module by creating and starting a container by a docker image provided for that module.
The config.example.toml is modified to launch an example replica of da_commit which has been dockerized. From the viewpoint of CB, it simply expects a docker image da_commit in the local registry. However, the dockerized version of the example module da_commit is not defined in this repo, but is available here.
Before you launch CB, build the da_commit image locally. Keep in mind that you'll have to modify Cargo.toml to point to the accurate current version of CB before you build the image.

Merged in the upstream.


Sum of Digit

Describe the project
Sum of digit a very simple project in HTML, CSS , JS that has functionalty like enter the any number and click calcaluate button and you will have the sum of digit contain in number.
Issue Type:

[x] New Project

Screenshots

If applicable, add screenshots to help explain your problem.

Hey @Kumar-Ankit56 Calculator project is already present in the repo.

@Vanshiii203 calculator is there but this something different please consider this.


Fix mismatched types in panic_handler in no_std

Change
Fix mismatched types in panic_handler in no_std.

Reason
To resolve errors in GHA checks and properly pass CI.
TEST
The GHA checks of this PR were properly passed.

Supplement
https://ferrous-systems.com/blog/probe-run/

Closed as fixed in another commit.
8bd6b492df7a636814275f70bccdda66514ceb02


Rapid token movement via keyboard scrambles teleportation position

As the title says - when moving a token through a teleportation point via arrow keys, "rapid" movement (repeatedly tapping the arrow key) appears to cause strange errors in token positioning.
Some behavior I've seen:

A token teleports ok, but after moving to some arbitrary point on the map, gets teleported back to a point near the original "teleport in" spot.
A token teleports, and is moved several (10 or more) squares up/down/left/right of the teleport destination, ignoring walls.

This can definitely be an issue, and I will try to look into seeing if there's anything that can be done, but it might be difficult to do anything about due to the way foundry handles user input / token movement.


killed when i try to push blocks into database geth/infura

Describe the bug
killed
To Reproduce
run ether_sql --settings='PersonalGethSettings' scrape_block_range --start_block_number 6305955 , my eth light geth node is syncing and it's over block 6305955

but, i get killed when i try to push data in database

i get killed too if i use same command with infura: ether_sql --settings='PersonalInfuraSettings' scrape_block_range --start_block_number 6305955

i've modified settings.py like that:

but, if i do ether_sql scrape_block --block_number 6305955 it also connect to DefaultSettings(infura, not my api ) and it works

Expected behavior
to not get killed and to push blocks into database
Desktop (please complete the following information):

OS: Ubuntu 16.04
Node Geth

my eth light geth node is syncing and it's over block 6305955

I have never tried pushing blocks using light geth blocks.
I will try it and update this issue.

but, if i do ether_sql scrape_block --block_number 6305955 it also connect to DefaultSettings(infura, not my api ) and it works

To use your personal infura setting use this command:
ether_sql --settings='PersonalInfuraSettings' scrape_block_range --start_block_number 6305955
PS: Thanks a lot for stres testing the library
PPS: refrain from posting your private infura key on a public forum like this.

that's how i've used it: ether_sql --settings='PersonalInfuraSettings' scrape_block_range --start_block_number 6307820, but no luck

anytime, i'm glad i can help a  little
it's for test, no worry, if people are lazy to create an account on infura they can use it

Strange, I tried the command and it works for me:
$ ether_sql --settings=PersonalInfuraSettings scrape_block --block_number=6307820
[2018-09-10 22:14:30,229][INFO][ether_sql.session] Connected to the db ether_sql
[2018-09-10 22:14:30,231][INFO][ether_sql.session] Connected to Infura node
[2018-09-10 22:14:30,231][INFO][ether_sql.globals] Pushing the session PersonalInfuraSettings in local thread
[2018-09-10 22:15:01,746][INFO][ether_sql.tasks.scrapper] Commiting block: 6307820 to sql

More, stranger thing is that the above command works for you when using DefaultSettings but does not work with PersonalInfuraSettings
Can you add the line LOG_LEVEL = "DEBUG" in your class PersonalInfuraSettings to see where is the process actually being killed, and copy paste the output?

(envname) [20:45 ubuntu@ip-172-26-15-152 ether_sql] > ether_sql --settings='PersonalInfuraSettings' scrape_block_range --start_block_number 6307821
[2018-09-10 20:45:16,099][DEBUG][ether_sql.session] DEBUG
[2018-09-10 20:45:16,164][INFO][ether_sql.session] Connected to the db ether_sql
[2018-09-10 20:45:16,165][INFO][ether_sql.session] Connected to Infura node
[2018-09-10 20:45:16,165][INFO][ether_sql.globals] Pushing the session PersonalInfuraSettings in local thread
[2018-09-10 20:45:16,224][DEBUG][web3.RequestManager] Making request. Method: eth_blockNumber
[2018-09-10 20:45:16,225][DEBUG][web3.providers.HTTPProvider] Making request HTTP. URI: https://mainnet.infura.io/HcekpL4KhjR4L0pCa4o8, Method: eth_blockNumber
[2018-09-10 20:45:16,230][DEBUG][urllib3.connectionpool] Starting new HTTPS connection (1): mainnet.infura.io:443
[2018-09-10 20:45:16,617][DEBUG][urllib3.connectionpool] https://mainnet.infura.io:443 "POST /HcekpL4KhjR4L0pCa4o8 HTTP/1.1" 200 44
[2018-09-10 20:45:16,617][DEBUG][web3.providers.HTTPProvider] Getting response HTTP. URI: https://mainnet.infura.io/HcekpL4KhjR4L0pCa4o8, Method: eth_blockNumber, Response: {'jsonrpc': '2.0', 'id': 0, 'result': '0x604106'}
[2018-09-10 20:45:16,618][DEBUG][ether_sql.cli] 6308102
[2018-09-10 20:45:16,618][DEBUG][ether_sql.cli] 6307821
[2018-09-10 20:45:16,618][DEBUG][ether_sql.models.blocks] 6305957
Killed

Response: {'jsonrpc': '2.0', 'id': 0, 'result': '0x604106'}, there should be 'id':1 right?

I think I got the reason why the process is being killed. The command first checks for missing blocks in the sql i.e. number of blocks which are missing between start_block_number and block 0, this is a heavy task and might be the reason for Killedcommand.

[2018-09-10 20:45:16,618][DEBUG][ether_sql.models.blocks] 6305957

This log is returned at line below and the process is being killed after that.
https://github.com/analyseether/ether_sql/blob/0ce3a74c7ce802d6db721b7066826dd873b98f07/ether_sql/models/blocks.py#L111
Try running the above command with setting --no-fill_gaps
$ ether_sql --settings=PersonalInfuraSettings scrape_block_range --start_block_number=6000000 --no-fill_gaps

Response: {'jsonrpc': '2.0', 'id': 0, 'result': '0x604106'}, there should be 'id':1 right?

Yes the id should be 1 but we are not using the id in any way it to kill our process.

yes, u're right, i got it now.
--no-fill_gaps work as workaround with infura
running same command with Geth: ether_sql --settings='PersonalGethSettings' scrape_block_range --start_block_number 6308345 --no-fill_gaps
(envname) [21:50 ubuntu@ip-172-26-15-152 ether_sql] > ether_sql --settings=PersonalGethSettings scrape_block_range --start_block_number=6000048 --no-fill_gaps
[2018-09-10 21:51:13,389][INFO][ether_sql.session] Connected to the db ether_sql
[2018-09-10 21:51:13,390][INFO][ether_sql.session] Connected to Geth node
[2018-09-10 21:51:13,390][INFO][ether_sql.globals] Pushing the session PersonalGethSettings in local thread
Traceback (most recent call last):
  File "/home/ubuntu/ether_sql/envname/bin/ether_sql", line 11, in <module>
    load_entry_point('ether-sql', 'console_scripts', 'ether_sql')()
  File "/home/ubuntu/ether_sql/envname/lib/python3.6/site-packages/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/home/ubuntu/ether_sql/envname/lib/python3.6/site-packages/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/home/ubuntu/ether_sql/envname/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/ubuntu/ether_sql/envname/lib/python3.6/site-packages/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/ubuntu/ether_sql/envname/lib/python3.6/site-packages/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/home/ubuntu/ether_sql/envname/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/home/ubuntu/ether_sql/ether_sql/cli/__init__.py", line 91, in scrape_block_range
    mode=mode)
  File "/home/ubuntu/ether_sql/ether_sql/tasks/scrapper.py", line 66, in scrape_blocks
    add_block_number(block_number)
  File "/home/ubuntu/ether_sql/envname/lib/python3.6/site-packages/celery/local.py", line 193, in __call__
    return self._get_current_object()(*a, **kw)
  File "/home/ubuntu/ether_sql/envname/lib/python3.6/site-packages/celery/app/task.py", line 379, in __call__
    return self.run(*args, **kwargs)
  File "/home/ubuntu/ether_sql/ether_sql/tasks/scrapper.py", line 143, in add_block_number
    timestamp=iso_timestamp)
  File "/home/ubuntu/ether_sql/ether_sql/models/receipts.py", line 60, in add_receipt
    status = bool(to_int(receipt_data['status']))
TypeError: 'NoneType' object is not subscriptable

same command  should work with geth or is not yet enabled?


[FEATURE REQ] Add ability to set Redirect URI on Interactive Browser Credential

Library or service name.
What library or service is this request related to?
Identity SDK.
Is your feature request related to a problem? Please describe.
What feature would you like to get added? What problem is it solving?
Add the ability to set Redirect URI/URL  on Interactive Browser Credential.
This is required to support Interactive Browser Credential auth flow against Azure Stack as the Redirect URI needs to match the registered URI for the public client application.

This feature is available in azure-identity:1.2.0-beta.1 release.


samples: threads: Rewrite misleading sample

The basic/threads sample is printing a log that looks like this:
Toggle USR0 LED: Counter = 0
Toggle USR1 LED: Counter = 0
Toggle USR0 LED: Counter = 1
Toggle USR0 LED: Counter = 2
Toggle USR0 LED: Counter = 3
Toggle USR0 LED: Counter = 4
From that log you would think that it was logging when leds were
blinking, but actually the led-threads might have crashed, and it
would just continue logging anyway. All it's doing is executing
printk's at roughly the same frequency as the LED's are blinking.
This patch rewrites the sample to use a FIFO so that the printk's only
trigger if the LEDs are actually blinking.
Signed-off-by: Sebastian Bøe<EMAIL_ADDRESS>

Why not add the original author to the review? @ric96 : Ping. (The sample comes from https://github.com/zephyrproject-rtos/zephyr/pull/4489 & https://github.com/zephyrproject-rtos/zephyr/pull/4573).

Why not add the original author to the review?
I was not able to find him based on the git blame.

Thanks.

why not just use  gpio_pin_read in the uart function?

Not sure what you mean, then we would have to introduce the ISR concept to wake up the UART
thread wouldn't we? I would prefer not to do that in the sample named basic/threads.


Downgrade auditwheel due to inability to exclude libraries for L-GPU

Before submitting
Please complete the following checklist when submitting a PR:

[ ] All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
tests directory!

[ ] All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running make docs.

[ ] Ensure that the test suite passes, by running make test.

[ ] Add a new entry to the .github/CHANGELOG.md file, summarizing the
change, and including a link back to the PR.

[ ] Ensure that code is properly formatted by running make format.

When all the above are checked, delete everything above the dashed
line and fill in the pull request template.

Context: The wheel-build process for L-GPU requires excluding licensed libraries from the shippable wheels. A recent update to auditwheel changed the procedure for how to achieve this, and the exclusion functionality cannot be easily replicated with the new design. This PR downgrades auditwheel to the working version, and restores the older override file.
Description of the Change: As above. Also ensure versioning of the CUDA toolkit to 12 explicitly.
Benefits:
Possible Drawbacks:
Related GitHub Issues:

Could you please update the changelog?

I can confirm the built wheels are free of any unneeded libraries.


[User story proposal] Xarray for Bayesian modeling (PyMC, ArviZ)

This is a proposal for a bayesian modeling use case story for Xarray. The story will be published on Xarray's blog (https://xarray.dev/blog).
Why?
Xarray is used as the underlying data structure in ArviZ (and PyMC?) today. A user story blog post showing how Xarray is used used to represent and analyze bayesian model data would help socialize the concept across the Xarray developer and broader Bayesian modeling communities.
What?
We are targeting a short and non-technical post that illustrates how Xarray is used in the ArviZ context. Below is a template outline that you should feel free to modify:

Who am I?
What problem am I trying to solve?
How does Xarray help?
Why did I choose Xarray?
Current pain points (or ways that Xarray could better serve your use case)
Technology I use around Xarray
Anything else to know?
Links and references

Feel free to insert images or short code blocks if they help you tell your story.
How?
Xarray's blog using Markdown with some front-matter. You can copy one of the existing posts to get started or you can write in a google-doc-like-thing and ask us to do the markdown formatting. If you copy a previous post, use a name like user-story-arviz or whatever makes sense for your application.
xref: https://github.com/xarray-contrib/xarray.dev/issues/272

@OriolAbril and/or @canyon289 - would either (or both) of you be up for contributing a blog post here?

@canyon289 - Circling back here. Are you still up for writing a post? We're ready to help get it on the site whenever you are ready.

@jhamman dont want to lose track of this. Should I just copy the template from say this post and make a PR?
https://github.com/xarray-contrib/xarray.dev/tree/main/src/posts/introducing-pint-xarray

@canyon289 - that would be great!

@jhamman Sorry for the delay. I am actively working on this. looking to get you a draft in the next week
https://github.com/canyon289/xarray.dev/blob/inf_data/src/posts/introducing-inference-data/index.md


Add global error handler.

Currently, repetative errors such as NoPrivateMessage are being handled individually and repetatively. A global error handler should be added to handle these common errors.

Useful links:

Real bot error handler
Tutorial example

Useful links:

Real bot error handler
Tutorial example


Is there any way to run this on Microsoft Azure?

As this starts with ts-node, is there any way to run this as an Azure web app?

Sure, you could put it on a VM.


alertMessages not found

Hi, cant find these methods
        self.alertNoPermissionToAccess(photos)
       showProposeMessageIfNeedFor(photos, andTryPropose: propose)

am I supposed to write them myself ?

Yes, it needs show some localized string.
The demo project has the extension, you can copy and modify it for your needs.


Trouble with stack-chain module

Hey,
I'm having trouble using https://github.com/AndreasMadsen/stack-chain in a project with Error objects that are created using this module.
This is the error I'm getting:
TypeError: Cannot define property:callSite, object is not extensible.
    at Function.defineProperty (native)
    at ValidationError.Object.defineProperty.set (node_modules/stack-chain/stack-chain.js:177:12)
    at Function.prepareStackTrace (node_modules/stack-chain/stack-chain.js:123:20)

So I'm thinking it might be something in the way error-create builds the Error objects?
Any ideas appreciated!

@raine thanks for report, still I think it may not be related to this module. At least there's nothing done within logic of error-create that will make created error instances non-extensible.
It'll be great if you can narrow it down to some simple test case, then we'll be able to say something more.
I'm closing it now, but let's keep discussion open, if it would appear as indeed bug in error-create we'll reopen it.

For what it's worth, I have a similar issue if I just require error-callsites anywhere in the project (no stack-chain).
TypeError: Cannot define property:__error_callsites, object is not extensible.
    at Function.defineProperty (native)
    at Function.Error.prepareStackTrace (node_modules/error-callsites/index.js:7:10)

@raine as I mentioned, best if you prepare smallest possible test case that reproduces that, and that proves it's related to error-create being involved, then we'll go from there


Demonstrate connectivity to MediaFlux in the UI

List the files in a namespace from MediaFlux into the UI.  The namespace can be hard-coded at this time, for the purposes of demonstrating our ability for the Rails application to communicate with the MediaFlux server.

Ideally we'd love to demo this during the stakeholder retreat (March 13).

I apologize, I have progressed with https://github.com/pulibrary/tiger-data-app/compare/jrgriffiniii-mflux-collection-query?expand=1 thus far. I am sorry for the absence of test coverage, I can look to address this following a meeting this afternoon.


Adds a script that outputs file with invocations of createBadge for copy paste

Hi Simon - the script is all set. A few things to note:

Most importantly, I'd like to have a fresh pair of eyes on Monday to double check everything is right before actually executing this script (quadruple checking the order of the createBadge args, cross-checking with etherscan to verify these transactions...etc). Would def appreciate your second pair of eyes as well.

To run the script, go to the root directory of this repo and run npm run initialize-badges. If all goes smoothly you should see a new txt file appear in the initializeBadges directory.

Wasn't totally sure of the exact JSON we want in IPFS (thus for computing the nftCid), currently the nftCID is based off a JSON that looks like:

{
  "beneficiaryOfBadge": "0x1875e398cD7FdcE8fF5C9d4ce1Ec904caE51692c",
  "buyer": "0x374Bd185Ee19fD9f8682Eb875E5D0546A8D58CdD",
  "mgCid": "zdpuAs4oSTUXz9wJX8mY7LTztmrG6i6p1hjmMELgBV9iS1KdG",
  "usdCostOfBadge": "5"
}

It will be very easy to change this to whatever we want and include any other properties that are in the event logs, so just let me know. Although these are the only 4 arguments other than nftCid that are in the createBadge func.

I implemented the pinToInfura func recursively because it makes it much easier for us to simply setTimeout on our calls to infura if we end up reaching their rate limit (which happens at a very number of requests). If your script fails because of this error I'll throw back in the setTimeout, so just let me know.

Interesting aside about decoding params/logs: my first path was to imitate the event getter we created for the portal, but I had a crazy wrestling with web3 when trying to replicate it - the event filter wouldn't return ANYTHING - not an error or a result. I ended up using hardcoded data to unblock myself. Using the hardcoded data I was able to finish the script using decode logs / decode params like you shared with me, it worked great. Unfortunately, the decoding funcs ended up being totally useless because I changed the event getting strategy. However, I left the code from the original script in the hardCodedData file in case you're interested in seeing it semi-working. Happy to delete it when we merge this in.

The web3 filter issue ended up being a weird bug that I spoke with some fellas from MetaMask and Infura about - it seems that we were trying to filter too many blocks in one request and it timed out. Conversation below in case you're interested:
https://consensys.slack.com/archives/G180E35GB/p1535130922000100
https://consensys.slack.com/archives/G180E35GB/p1535134448000100

Wasn't totally sure of the exact JSON we want in IPFS

I think we're trying to only push COALAIP objects to IPFS. Maybe we want to look at adding a new object using this a reference —> https://schema.org/BuyAction.

@thomasbeta https://github.com/UjoTeam/contracts-badges/pull/19 has a couple comments that might help clarify why/how we're using IPFS here

@Schwartz10 not sure if we're on the same page. Why couldn't we make a new COALAIP object for this?

I see what you're saying, my bad. I definitely think it's better to use a coalaip object because it will enforce a standard that's easier to follow. Not sure how it plays into parsing the metadata from a token exchange's POV, but I'm sure Simon has insight into that

hey @simondlr this is all set - I've confirmed 2 of the tx's on etherscan and they generally match what the script outputs (see below for why "generally").
If you go into the event logs on etherscan for a given transaction, the individual params in the data field are in a different order than when it comes back from a programmatic event getter. Additionally, the cid field is cut off after a certain amount of characters. Regardless, I can still verify an individual transaction by looking at the buyer, beneficiary, and the first x number of characters of the music group cid - as long as they all match I think we're good.
Example:

Should output badge script (notice the cutoff of mgcid from etherscan):
createBadge("0x374Bd185Ee19fD9f8682Eb875E5D0546A8D58CdD", "zdpuAs4oSTUXz9wJX8mY7LTztmrG6i6p1hjmMELgBV9iS1KdG", "zdpuB2o9vYZX7wmcm4tE43HUntsbm1uokD3rw5Vk4G2kP16oC", "0x1875e398cD7FdcE8fF5C9d4ce1Ec904caE51692c", 5);

Regardless, if you navigate to https://ipfs.infura.io:5001/api/v0/dag/get?arg=zdpuAs4oSTUXz9wJX8mY7LTztmrG6i6p1hjmMELgBV9iS1KdG (using the mgcid from the badge script), you will get a mg.
The last thing we need to discuss is the relationship between a single badge in IPFS and COALAIP.

The nftCID needs to conform to the EIP721 metadata scheme. https://github.com/ethereum/EIPs/blob/master/EIPS/eip-721.md. That's how other sites/properties are pulling out data from NFTs atm.
The scheme is:
{
    "title": "Asset Metadata",
    "type": "object",
    "properties": {
        "name": {
            "type": "string",
            "description": "Identifies the asset to which this NFT represents",
        },
        "description": {
            "type": "string",
            "description": "Describes the asset to which this NFT represents",
        },
        "image": {
            "type": "string",
            "description": "A URI pointing to a resource with mime type image/* representing the asset to which this NFT represents. Consider making any images at a width between 320 and 1080 pixels and aspect ratio between 1.91:1 and 4:5 inclusive.",
        }
    }
}

Note: this is a schema. Adding the extra fields is optional and I think we should add them. Perhaps adding "dateCreated" would also be useful? The official fields will be readily re-used. The others might be more important for Ujo-specific apps, not generic NFT/collectible apps.
So, something like this would be the end-result:
{
    "name": "Sunset Simon Patronage Badge",
    "description": "<some description>",
    "image": "<image_uri>",
    "beneficiaryOfBadge": "0x1875e398cD7FdcE8fF5C9d4ce1Ec904caE51692c",
    "MusicGroup": "zdpuAs4oSTUXz9wJX8mY7LTztmrG6i6p1hjmMELgBV9iS1KdG",
    "usdCostOfBadge": "5",
    "dateCreated": "<timestamp>"
}

The rest LGTM. Glad getPastEvents is working so well!

Cool, makes sense. A few q's:

Do you think we should include the buyer's address in this data too?
Which image should we use for the MG? Should we use the one associated with the current MGCID? @oftenfrequent this goes back to the "retro-badges" concept.
Is the description generic or unique to each badge?

Do you think we should include the buyer's address in this data too?

I would say, no, because this doesn't make up the badge itself. It's only relevant at time of purchase.

Which image should we use for the MG?

Since this nftCID doesn't change, it should be the one at the time of minting imho: like we had with the MGCID.

Is the description generic or unique to each badge?

I would say it's generic, not like a band description. eg: "A collectible patronage badge for Sunset Simon."
Replacing "Sunset Simon" with the MG.

Ok, did you see my updated question?

Also, not sure this matters at the moment, but I'm wondering if this script is missing an edge case which is if a badge had been transferred after purchase. I'm filtering for LogBadgeMinted events, so if we initialize badges we're giving ownership back to the original purchaser.

Also, not sure this matters at the moment, but I'm wondering if this script is missing an edge case which is if a badge had been transferred after purchase. I'm filtering for LogBadgeMinted events, so if we initialize badges we're giving ownership back to the original purchaser.

Yes, we need to check for this, but we can see if there's been any transfers, which doesn't look like it. You can see all txes are badge mint txes. No transfers have occurred yet.
https://etherscan.io/address/0xc45e027f0f9d7e90e612be02d4e710a632a9dba9

{
  "beneficiaryOfBadge": "0x1875e398cD7FdcE8fF5C9d4ce1Ec904caE51692c",
  "dateCreated": "2018-07-30T22:42:05-04:00",
  "description": "A collectible patronage badge for Tom Finster",
  "image": "https://www.dev.ujomusic.com/image/600x600/https://ipfs.infura.io/ipfs/QmZnhUQ7Yr6XY86ERhkgHjQMQ8uqZ4hiMzmqPaZwLHNULA",
  "musicgroup": "zdpuAs4oSTUXz9wJX8mY7LTztmrG6i6p1hjmMELgBV9iS1KdG",
  "name": "Tom Finster Patronage Badge",
  "usdCostOfBadge": 5
}

This is all set, here's an example object from IPFS after running the script.

Hey @Schwartz10. Removed the timestamps and the hardcoded data, along with some small tidying.
You can see an example of the nftCID here: https://ipfs.infura.io:5001/api/v0/dag/get?arg=zdpuAnZ4nv6cQoCj7tVVSmavg45HB5Dy7HkD8ubMvyH3z1CWq.
I'm still wondering about 3 things:

Are all images being served dev URI? Don't we have a non-dev API up?
Should "musicgroup" field be linked in COALA IP style instead or perhaps just capitalise it? Or just keep lowercase as is?
-"https://www.dev.ujomusic.com/image/600x600/https://ipfs.infura.io/ipfs/QmZnhUQ7Yr6XY86ERhkgHjQMQ8uqZ4hiMzmqPaZwLHNULA". These URIs still worry me somewhat in terms of decentralization & future proofing. One can link straight to the IPFS URI. Would that be more future proof? In addition to that. Should we consider adding in a field that's "imageCID", that's just the IPFS hash? That keeps somewhat more future proof if any of the URIs go down.

Are all images being served dev URI? Don't we have a non-dev API up? decentralization & future proofing ?
Good catch, my latest commit changes this to live API. In terms of future proofing and decentralization, I see your point - the thoughts behind my decision here were that (1) The spec you posted has a description under image:

Consider making any images at a width between 320 and 1080 pixels and aspect ratio between 1.91:1 and 4:5 inclusive.",

the api provides us a 600x600 image and potential big-time performance boosts.
(2) future proofing - one could capture the image cid from the URI even if it starts with ujomusic.com/... - by scraping the URI down to just the ipfs.infura.io/ipfs/cid, one can infer the infura uri, and then by scraping that URI down to just the cid, one can access the image directly from IPFS in worst case scenario

Should "musicgroup" field be linked in COALA IP style instead or perhaps just capitalise it? Or just keep lowercase as is?
Latest commit changes this to correct capitalization - seems redundant for IPFS to store the entire nest of MG information but would be interested in @thomasbeta opinion

Agree on all counts. Feel its all "good enough" for now.

I'm going to merge.


unixPB: Update checksum for CentOS/RHEL docker repo

Signed-off-by: Stewart X Addison<EMAIL_ADDRESS>
Checklist

[x] commit message has one of the standard prefixes
[ ] FAQ.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access)
[ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

I'm still getting the old checksum when I wget the repo:
2021-02-16 07:37:45 (87.8 MB/s) - ‘docker-ce.repo’ saved [1919/1919]

will@will-XPS-13-9360:~/Documents/1883/ansible$ sha256sum docker-ce.repo
8ab5599eef0afcac10cbd3e8670873efee20fcceb5fb3526a62edeade603cec7  docker-ce.repo

Since you've got our can you attach the file with the old checksum to those PR please?

LGTM - I assume the linter is still borked.

Yes as per https://github.com/AdoptOpenJDK/openjdk-infrastructure/issues/1926

This is the contents of the docker-ce.repo that still has the old checksum:
[docker-ce-stable]
name=Docker CE Stable - $basearch
baseurl=https://download.docker.com/linux/centos/$releasever/$basearch/stable
enabled=1
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg

[docker-ce-stable-debuginfo]
name=Docker CE Stable - Debuginfo $basearch
baseurl=https://download.docker.com/linux/centos/$releasever/debug-$basearch/stable
enabled=0
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg

[docker-ce-stable-source]
name=Docker CE Stable - Sources
baseurl=https://download.docker.com/linux/centos/$releasever/source/stable
enabled=0
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg

[docker-ce-test]
name=Docker CE Test - $basearch
baseurl=https://download.docker.com/linux/centos/$releasever/$basearch/test
enabled=0
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg

[docker-ce-test-debuginfo]
name=Docker CE Test - Debuginfo $basearch
baseurl=https://download.docker.com/linux/centos/$releasever/debug-$basearch/test
enabled=0
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg

[docker-ce-test-source]
name=Docker CE Test - Sources
baseurl=https://download.docker.com/linux/centos/$releasever/source/test
enabled=0
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg

[docker-ce-nightly]
name=Docker CE Nightly - $basearch
baseurl=https://download.docker.com/linux/centos/$releasever/$basearch/nightly
enabled=0
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg

[docker-ce-nightly-debuginfo]
name=Docker CE Nightly - Debuginfo $basearch
baseurl=https://download.docker.com/linux/centos/$releasever/debug-$basearch/nightly
enabled=0
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg

[docker-ce-nightly-source]
name=Docker CE Nightly - Sources
baseurl=https://download.docker.com/linux/centos/$releasever/source/nightly
enabled=0
gpgcheck=1
gpgkey=https://download.docker.com/linux/centos/gpg

I was unable to attach it due to GitHub not supporting that file type

I was unable to attach it due to GitHub not supporting that file type

You can always add .txt or gzip it, but thanks - that worked well enough :-)

Maybe they did something and reverted it. Was definitely having issues with the checksum yesterday somewhere after downloading it to verify but it looks to be working today. Closing


Add google_compute_instance_group_manager

Q
A

🐛 Bug fix?
no

🚀 New feature?
yes

⚠ Deprecations?
no

❌ BC Break
no

🔗 Related issues
https://github.com/snyk/driftctl/issues/998

❓ Documentation
https://github.com/snyk/driftctl-docs/pull/226

Codecov Report

Merging #1379 (eec7eae) into main (5bc324f) will increase coverage by 7.75%.
The diff coverage is 76.19%.

@@            Coverage Diff             @@
##             main    #1379      +/-   ##
==========================================
+ Coverage   74.08%   81.83%   +7.75%
==========================================
  Files         487      417      -70
  Lines       18338    15236    -3102
==========================================
- Hits        13586    12469    -1117
+ Misses       4433     2457    -1976
+ Partials      319      310       -9

Impacted Files
Coverage Δ

pkg/remote/google/init.go
0.00% <0.00%> (-77.78%)
:arrow_down:

pkg/resource/resource_types.go
100.00% <ø> (ø)

...ce/google/google_compute_instance_group_manager.go
14.28% <14.28%> (ø)

...oogle_compute_instance_group_manager_enumerator.go
90.00% <90.00%> (ø)

pkg/remote/google/repository/asset.go
97.77% <100.00%> (+0.05%)
:arrow_up:

pkg/resource/google/metadatas.go
100.00% <100.00%> (ø)

pkg/terraform/plugin_client.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/remote/aws/client/s3_client_factory.go
0.00% <0.00%> (-100.00%)
:arrow_down:

pkg/remote/aws/init.go
0.00% <0.00%> (-95.74%)
:arrow_down:

pkg/resource/azurerm/azurerm_image.go
12.50% <0.00%> (-87.50%)
:arrow_down:

... and 151 more


gitleaks still scanning node_modules and dist folder even ignoring them in gitleaks.toml in docker mode

Describe the bug
Hello dear friends!
My name is Jan Palach. I am facing an weird issue with gitleaks in docker mode. While using it in native executable mode nothing wrong seems to happen. The problem is, while running in docker mapping the target project to scan, gitleaks tell us that it has found the config file,but it still scanning node_modules and dist folders tooking to long to finish because my node_modules is huge.
To Reproduce
1 - Follow the docker mode from the documentation
2 - put the following configfile  in a path mapped path to expose to the docker image:
`title = "Gitleaks Config File"
[extend]
useDefault = true
[allowlist]
description = "global allow lists"
paths = [
'''.gitleaks.toml''',
'''(.?)(jpg|gif|doc|docx|zip|xls|pdf|bin|svg|socket|vsidx|v2|suo|wsuo|.dll|pdb|exe)$''',
'''(go.mod|go.sum)$''',
'''gradle.lockfile''',
'''yarn.lock''',
'''package-lock.json''',
'''package.json''',
'''pnpm-lock.yaml''',
'''Database.refactorlog''',
'''vendor''',
'''..test.''',
'''..swagger.''',
'''..error.*''',
'''docs''',
'''errors''',
'''messages''',
'''gitleaks_findings.json''',
'''pre-commit''',
'''README.md''',
'''dist''',
'''node_modules'''
]
`
3 - Then run the docker image pointing to the config file listed above:
docker run -v project root path:/app zricethezav/gitleaks:latest detect -l debug --no-git --source /app --verbose --no-banner --redact --config=/app/devsecops-secrets-detection/.gitleaks.toml
Result:
Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
2:48PM DBG using gitleaks config /app/devsecops-secrets-detection/.gitleaks.toml from --config
2:48PM DBG extending config with default config
2:50PM INF scan completed in 1m51s
2:50PM WRN leaks found: 1
Finding:     const fooAwsSecret = "REDACTED"
Secret:      REDACTED
RuleID:      aws-access-token
Entropy:     3.646439
File:       foofile
Line:        68
Fingerprint:foofile:aws-access-token:68
Expected behavior
It sholud run ignoring node_modules and dist paths, but it does not. Removing these paths the docker image runs the application in an expected time window.
Basic Info (please complete the following information):

OS: MacOS
Gitleaks Version: Latest docker image 8.18.0

I do really appreciate your attention my friends!
cc @zricethezav

For a while, I've just mounted both node_modules and dist directory as anonymous ones and it runs perfectly. But I guess this is just an workaround..

@JanPalach82 thanks for opening this issue. I'll try to investigate. I think there are some other issues with regard to running in docker mode that might provide some helpful context

Same issue here.
.gitleaks.toml
[allowlist]
  paths = ['''tests''']

Command:
$ docker run -v $PWD:/path zricethezav/gitleaks:latest detect --source="/path" -v

I'm trying to add gitleaks but can't figure out how to skip node_modules. I'm running gitleaks directly:
version
gitleaks --version
gitleaks version 8.21.2

gitleaks.toml
[extend]
useDefault = true

[allowlist]
description = "allowlist"

paths = [
  '''^node_modules/''',
]

Output
gitleaks dir --no-banner --config=gitleaks.toml --log-level=debug .

Output
5:03PM DBG using gitleaks config dev/lint/gitleaks/gitleaks.toml from `--config`
5:03PM DBG extending config with default config
5:03PM DBG Skipping symlink path=node_modules/.pnpm/@ag-grid-community+client-side-row-model@32.2.0/node_modules/@ag-grid-community/core
5:03PM DBG Skipping symlink path=node_modules/.pnpm/<EMAIL_ADDRESS>5:03PM DBG Skipping symlink path=node_modules/.pnpm/<EMAIL_ADDRESS>
Hypothesis
It looks like gitleaks descends into directories that match the allowlist instead of bailing early. If this is the problem, it's analogous to the find -path and -prune options. A common mistake with find is to filter out paths instead of pruning to avoid scanning directories.

Interestingly, passing a single file works. However, passing two or more files causes gitleaks to scan everything.

Hypothesis
It looks like gitleaks descends into directories that match the allowlist instead of bailing early. If this is the problem, it's analogous to the find -path and -prune options. A common mistake with find is to filter out paths instead of pruning to avoid scanning directories.

You're right — and this makes sense considering the logic was likely written to receive arbitrary paths from git log.
The dir command walks the entire tree and sends all files over a channel.
The paths allowlist currently isn't tested until after the file is read and passed to the Detect function.
https://github.com/gitleaks/gitleaks/blob/7f77987d91c590e021d9fa2b3c0e57c4a4376147/detect/detect.go#L176-L182

I've opened #1653 to fix this.

@zricethezav


Support Holley DTZ541 wrongly implemented CRC Algorithm

I have a Holley DTZ541 where the CRC16 Algorithm is wrongly implemented by the manufacturer.
As already implemented in libsml https://github.com/volkszaehler/libsml/pull/76 i did the workaround for opensml, too.
The meter often returns some invalid values which lets some calculations drift far away.
I'm using iobroker.smartmeter and hope this pr will be accepted and pulled upstream through https://github.com/Apollon77/smartmeter-obis and finally in https://github.com/Apollon77/ioBroker.smartmeter so i can enable the crc verification.
@Apollon77  ;)
added some test cases with holley sample data
feel free to review, iam happy to improve

Thank you, is there any way like via manufactorer string in the SML message to limit thjs special crc check to "just" the relevant sml messages?

I see different issues

There are HLY DTZ541 with different firmware versions in the field. Since a specific version they fixed their issues. I do not know which version it is

I do not have direct access to manufacturer, product and version number in file or message parsing without major changes

there will only be an impact on malformed telegrams which crc is not valid. The users receive valid telegrams most of the time, if they receive a invalid message a additional crc is calculated. That won't affect performance and a crc hash collision for the invalid message becoming falsely valid is not very likely

If you have some suggestion I did not see feel free to give me a hint

Is there anything else I can do?

I'm thinking about it atm :-)


document field config in changelog, readme

documenting #122 in changelog, readme, as discussed in #124

Nice, thanks :)


Update mill-main, mill-scalalib to 0.11.0

About this PR
📦 Updates

com.lihaoyi:mill-main
com.lihaoyi:mill-scalalib

from 0.11.0-M11 to 0.11.0
📜 GitHub Release Notes - Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (0.11.0-M11).
You might want to review and update them manually.
.github/workflows/build.yml
build.sc

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.lihaoyi" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.lihaoyi" }
}]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, old-version-remains, commit-count:1

Superseded by #50.


Error code is stripped when running execa

🐛 Bug Report
Running execa 4.0.0 with the following code results as follow:
const execa = require('execa');
(async () => {
	// Catching an error
	try {
		let res = (await execa('unknown', ['command']));
	} catch (error) {
		console.log(error);
/*
errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'spawn unknown',
  path: 'unknown',
  spawnargs: [ 'command' ],
  originalMessage: 'spawn unknown ENOENT',
  shortMessage: 'Command failed with ENOENT: unknown command\nspawn unknown ENOENT',
  command: 'unknown command',
  exitCode: undefined,
  signal: undefined,
  signalDescription: undefined,
  stdout: '',
  stderr: '',
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
  		*/
	}
})();

When running in jest the following code (execa@4 or execa@3):
it ('should have error', async () => {
    try {
        await execa.command('unknown command');
    } catch (e) {
        console.log(`e`);
        expect(e.code).toBeTruthy();
    }
  })
/* {
      "shortMessage": "Command failed with ENOENT: unknown command",
      "command": "unknown command",
      "stdout": "",
      "stderr": "",
      "failed": true,
      "timedOut": false,
      "isCanceled": false,
      "killed": false
    }*/

code and exitCode are missing.
Running the above test with<EMAIL_ADDRESS>results the following:
{
      "command": "unknown command",
      "exitCode": 2,
      "exitCodeName": "ENOENT",
      "stdout": "",
      "stderr": "",
      "all": "",
      "failed": true,
      "timedOut": false,
      "isCanceled": false,
      "killed": false
    }

I am aware that there are breaking changes between 2 and 3 related to the code, but I am wondering if the exitCode (and code and errno) should remain or not.
It is hard to tell if this is a jest or  execa issue.
It is also reported here: https://github.com/sindresorhus/execa/issues/422

Without checking execa's source code, I assume they use instanceof Error somewhere in their code, and this is caused by #2549

@ehmicky is fixing it on execa: https://github.com/sindresorhus/execa/pull/423


The -t / --theme flags were removed from hugo new

The -t / --theme flags were removed from hugo new (also absent in hugo new content): https://github.com/gohugoio/hugoDocs/commit/fb3027dafa391d48922240fc4359cbc4ad1cfdd5#diff-9b75f7a964edc681f1e213d44f1ec7a3d4f5f1678c25f45c78cb238cb2ca052cL62 Was that intentional? If yes, how to create new content using an archetype (--kind) in a specific theme? Thanks!
Originally posted by @yihui in https://github.com/gohugoio/hugo/issues/11015#issuecomment-1561952794
$ hugo version
hugo v0.112.3-ba6f74e40420d76f15fc8c2358be90f7aca98e0e+extended darwin/amd64 BuildDate=2023-05-24T14:42:50Z VendorInfo=gohugoio

$ hugo new post/foo.md --theme hugo-xmin
Error: command error: unknown flag: --theme

This is a bug, and I apologise. This was a massive Hugo upgrade on the technical side that we needed to do sooner rather than later, and I guess we (or at least I) was a little tired of it at the end and just wanted to get it out.

@yihui

how to create new content using an archetype

hugo new content --theme mytheme posts/post-1.md
hugo new content -t mytheme posts/post-1.md

The --theme / -t flag has no effect if you have an archetype in your project folder (as expected, same behavior as < v0.112.0).


Add static methods to Eloquent\Model to qualify columns

Overview:
This PR introduces new static methods, getQualifiedColumn and getQualifiedColumns, to Eloquent\Model. The purpose of these methods is to provide a convenient way to qualify column names when dealing with database relations, without having to create Model or Builder instances.
Benefits:

Provides a more intuitive and concise way to qualify column names.
Improves developer experience by offering static access to column qualification functionality. No more wondering how to get a model or builder instance to call qualifyColumns on.
Enhances code readability and maintainability.
Minimal changes to the framework, low burden to maintain

Method naming considerations:
🤔 Help wanted: I am not fully happy with the naming of the static methods. I also considered EloquentModelStub::qualifiedColumn() so it starts the same or EloquentModelStub::resolveQualifiedColumn().
Ideally the static and instance methods would be called the same so we can do EloquentModelStub::qualifyColumn(), but this is only possible with magic methods AFAIK
Example before:

Example after:

PHP supports static and instance methods with the same name, so you can just defer the static to the instance methods:
    /**
     * Qualify the given column name by the model's table.
     */
    public static function qualifyColumn(string $column): string
    {
        return (new static)->qualifyColumn($column);
    }

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


API: nodes object vs nodes array

I get that using object for nodes, ports etc. is more convenient (and effective) for lookup, but from user's perspective array seems more natural in this case (arrays are easier to build and there's no need to "duplicate" node id as property name). Object (or Map) could be an internal implementation in this case. What do you think on that?
(obviously I can make a wrapper for that - which I will do for now - but maybe it's worth changing API)

I'm open to change but not particularly enthused for said change. I too am converting the nodes, links and ports objects to an array before persisting them in a project using this lib. The simple solution would be to include a little util for this conversion.
Given the state can be managed externally, its not so easy to make Object or Map an internal implementation without adding extra complexity. I suppose it would require another internal type, something like IChartKeyed.
Alternatively, if the array form were used throughout, any state actions/reducers become more complex. Some, such as onLinkMove are called multiple times per second. The performance implications of links.find() on charts with a large number of links would need to looked into (although probably not an issue).


Add an example on how to use default environment variables

Our section on Default Environment Variables is missing an example of how environment variables are used.
Task
Add an example that shows some usage of one of these default environment variables.
Page to edit

Using environment variables

@sasoria, I know you've added some docs to this page a couple of days ago. Is this something you're interested in to pick up?
(Saying no is totally fine!)

Yes, I can pick this up. I'll try to get it done within this week.


SQLServer不支持socketTimeout

查询超过10s超时，这个配置从1.2.12开始设置为默认值，源码没有SQLServer的判断

I will process it later.

I'd like to fix this, please assign it to me @kimmking

it for you now. @Wincher

fixed now: https://github.com/alibaba/druid/commit/a9d9803dc86bdd32bc3634ceab948e2380e1acd9


[sdk] Test coverage

SDK
Unit testing

address
bcs
crypto
transaction
utils

E2E testing

all client methods

#SDK-Kit
E2E testing

all hook methods

I'll take this issue @wow-sven


Fix ContentCertificateProperties live validation error

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

The Content in ContentCertificateProperties is required in request and hided in response by design.
It has no customer impact because it is just an error on swagger and we do not need to update our backend code.
The behavior customers see is always require Content  property in request and no  Content  property in response.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[x] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@Descatles , can you get breaking change review approved?


Document how to increase file upload size on self hosted instances

increase limit by setting APPSMITH_CODEC_SIZE=100

Duplicate #14232. Closing this ticket.


Symbol-named properties get element-access completions

const c = Symbol();
let obj = { [Symbol.iterator]: 100 };
let a = obj['/**/']

Go to the /**/ marker and request a completion.
Expected: No completions.
Actual: Completions for __@iterator!
Currently with #15473, this is exacerbated.

PRs welcomed.

I created a PR to fix this, since this is more noticeable with the dynamic names PR.


Minimum software requirement for specific page section info is self-contradictory

[Either official documentation is misstated or the pre-requirements for Windows 11 for Microsoft Defender Application Guard for Office is thoroughly incorrect.]
This page refers to the part whereas "(Windows 10 only)" is stated under the minimum software requirement says above that all Windows 11 versions are supported. This makes absolutely no sense.
https://learn.microsoft.com/microsoft-365/security/office-365-security/install-app-guard#minimum-software-requirements
Self contradictory:
https://learn.microsoft.com/microsoft-365/security/office-365-security/install-app-guard#deploy-application-guard-for-office

I'm running Win11 with HCVI (UEFI lock), AMD-VT and VBS activated, yet am unable to run Microsoft Defender Application Guard for Office via virtual machine running on Dell switchless hyper-visor. I even installed the Microsoft Defender Application Guard Companion from the Microsoft Store and still not working. I have installed Microsoft Defender Application Guard for Office via Programs and Features > Turn Windows features on or off, confirmed installed. I have no logs to go after and seemingly no error messages appearing.

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

ID: f8cc5310-e03b-d538-e741-09be5f32ab13
Version Independent ID: 6f56df92-3eb1-56ff-efc9-a4d269efd7aa
Content: Application Guard for Office for admins - Office 365
Content Source: microsoft-365/security/office-365-security/install-app-guard.md
Service: microsoft-365-security
Sub-service: mdo
GitHub Login: @schmurky
Microsoft Alias: maccruz

@schmurky Please help us in resolving this issue. Thanks

@schmurky Please help us in resolving this issue. Thanks

The pre-requirements for Microsoft Defender Application Guard for Office are supposedly fulfilled yet the functionality is still not actively turned on.
Where are the log location for Microsoft Defender Application Guard for Office? Otherwise I cannot help you fix this issue.

Looking into this.

It looks like the comment about the contradiction is specifically referring to step 1 - the wording is supposed to indicate that step 1 needs to be followed for those running Windows 10 only. All subsequent steps are relevant to Windows 10 and 11.
@filippossemere you mentioned enabling the Windows Feature, did you also enable the policy as described in step 3?

This issue has been addressed: https://github.com/MicrosoftDocs/microsoft-365-docs-pr/pull/18624. The updated topic will be published later today.


new feature fortigate-autoscale 2.0 with fortianalyzer integration

consume the build artifacts of the FortiGate Autoscale feature branch: aws_quickstart_guide_2.0

@klc178 Hi Kimberly, would please start your review here in this PR?

can we remove those binaries from the repo?
BIN +264 KB functions/packages/fgt-asg-handler.zip
BIN +260 KB functions/packages/nic-attachment.zip

can we remove those binaries from the repo?
BIN +389 KB functions/packages/faz-handler.zip
BIN +264 KB functions/packages/fgt-asg-handler.zip
BIN +260 KB functions/packages/nic-attachment.zip

sorry, can't remove them because AWS QSG requires both source code and binary versions of the functions in the production repo.

@klc178 Hi Kimberly, your changes are pushed now. Please review and approve the latest changes. Thanks!

I approve this PR.


Fix curse only applying to non-respawns

RespawnObeliskBlock#getRespawnLocation currently applies the Immortality Curse if isTeleport || player.isAlive() instead of !(isTeleport || player.isAlive()).  This PR fixes that.
Essentially, this PR just makes the curse apply to respawning targets like the mod page says instead of only teleporting targets.

So, as of right now, the curse doesn't apply to respawning targets at all?

As of right now, it only applies to targets that were alive when the method was called.

Yeah no worries, just wanted to make the PR while I had the issue identified.


Fix_VsEditor_drag_in_from_scenetree

Moves the creation of the vs_instances after the decision and allows the creation of set and get propertynodes.

fix #26717
fix #49146
Moves the creation of the vs_instances after the decision and allows the creation of set and get propertynodes.

Tested on Master and 3.x
For cherry-pick 3.x I will make a extra PR
3.x requires 1 more argument on for lines.
Also:
Limit suggestions to useful methods, setters and getters. Other VsNodes are not required from this interaction.
Now includes the attached script of a Node for suggestions.

On hold I have been testing a other way. Info to follow

49749


HotswapHelper on HotswapAgent pages

Hi,
great plugin!
Would be nice to have it at this place instead of obsolete HotswapAgent plugin:
https://hotswapagent.org/mydoc_setup_intellij_idea.html

thanks, I'd be happy to help edit the websites, any way to edit https://hotswapagent.org/mydoc_setup_intellij_idea.html.

You have rights to project https://github.com/HotswapProjects/HotswapAgentPages now, there is file ./pages/mydoc/mydoc_setup_intellij_idea.md , please remove old plugin reference and add HotswapHelper. Pages will be refreshed after push - it could take some time to be refreshed fully. Thanks!


Discourse local communities

https://community.openstreetmap.org/c/communities/9/none lists local communities that (presumably) will replace forum.openstreetmap.org - there is already a link to the Discourse on the index, but not directly to any special communities.
LATAM and Thailand already are on the index, do you want to add the newly existing (with Austria being the newest one) in a batch by any of the two of us or would you want to have a request from any community by themselves?

I think the idea from https://community.openstreetmap.org/t/community-index-and-new-community-categories-here/2458 is that the local community leaders can make the request once they are ready to accommodate more users.

Ok.

The old forums are now closed for new posts, so maybe it's best to just do it centrally?
E.g., Norway is missing

The old forums are now closed for new posts, so maybe it's best to just do it centrally?

I agree, I think it's best to just remove all the old forums since they are readonly and officially deprecated now as of November 2022.

I'm opening a discussion on this at the community forums, because I have observed that a few active community forums that I pinged about this one year ago has not updated the index, maybe because they're JOSM users and not aware how prominent this is for iD users :)
If the most common communication channel is not listed there for new users, there's less chance they become active contributors
https://community.openstreetmap.org/t/add-all-community-forums-to-the-community-index/119315


node 18 update: missed nvmrc and travis

stuck on https://github.com/codecombat/codecombat-server/pull/510


:sparkles: Add time_scheduler

It seems like there is a timer_manager that is injected. How would I provide N timer_managers/timer_schedulers? If I have N hardware timers used for various purposes is there a way to create distinct user visible "timer schedulers"?

It seems like there is a timer_manager that is injected. How would I provide N timer_managers/timer_schedulers? If I have N hardware timers used for various purposes is there a way to create distinct user visible "timer schedulers"? These timers may have different time point conversions.

How would you like to handle it? Tag the various timer domains with tag types?

It seems like there is a timer_manager that is injected. How would I provide N timer_managers/timer_schedulers? If I have N hardware timers used for various purposes is there a way to create distinct user visible "timer schedulers"? These timers may have different time point conversions.

How would you like to handle it? Tag the various timer domains with tag types?

I was thinking tag types would work well. I am personally ok with the "singleton" limitation for this initial introduction of the time scheduler (PR is not blocked). I would love to see timer domain support. I have use cases!


WIP #8561 Increment to latest available value for deployments at time of writing

See https://learn.microsoft.com/en-us/azure/templates/microsoft.resources/allversions
Microsoft Reviewers: Open in CodeFlow

Fixes #8561

@edburns you'll most likely need to update baselines, and there may be some other tests linked to this API version.

See my note in the GH issue. I'm wondering if we should hold this PR until we are ready to make the change everywhere to the later API version.

@alex-frankel I defer to your judgement on when to address the old apiVersions issue. I just request that it not be allowed to cause Azure Marketplace problems in the future, but I believe @bmoore-msft 's changes mitigate that aspect.

Closing given Ed's response


Use unix-compat instead of unix for windows compat

Beginning of a better Windows compatibility story for Obelisk.
I have:

[X] Based work on latest develop branch
[X] Looked for lint in my changes with hlint . (lint found code you did not write can be left alone)
[X] Run the test suite: $(nix-build -A selftest --no-out-link)
[ ] (Optional) Run CI tests locally: nix-build release.nix -A build.x86_64-linux --no-out-link (or x86_64-darwin on macOS)

@mightybyte have you tested this on windows?

Not yet.  (It's building now.)  I anticipate more obstacles before I can actually use an Obelisk app on Windows.  Things like jsaddle-wkwebview, etc.  My goal here is pretty narrow--to build an Obelisk app as a Windows desktop app with GHC.  Note that this doesn't necessarily include making the ob command line app work on Windows.  All I need is for the obelisk-provided libraries to build.  I also don't intend to tackle the problem of getting ghcjs to build on Windows at all.  So while this in no way gets to what's needed for full-blown Obelisk Windows support, it is a necessary precondition.

Makes sense. As long as there's no expectation that I will start actively testing obelisk on Windows I don't mind accepting this provided nothing else suffers as a result.

Oh yes, I definitely don't expect any Windows testing.


All Brazilian NDCs must allow 9 digits

This PR implements the 9th digit on all Brazilian NDCs by removing the special NDC list.
See http://www.anatel.gov.br/setorregulado/index.php/nono-digito (pt only)

Changes Unknown when pulling 81439dac08a65fcd5d8bd9d006c9508ab7d09a1b on vindi:master into ** on floere:master**.

Hi @wagner ! Thanks a lot for this great PR 😊 – I am wondering about one thing: will Phony lose a lot of test cases since about 20-30 tests are replaced by two?

Hello @floere! The 'special states' doesn't make much sense now because all states are included in the 9 digit deployment. Anyway, I shouldn't have removed it, just renamed as I've just did.
Thanks! 😄

Changes Unknown when pulling 4174c80e8d989abf4bf610b057f949dfed4f0b94 on vindi:master into ** on floere:master**.

@wagner Great, thanks 😊 Thanks a lot for the PR, again!! Your work is released in version 2.15.34 🚀


Autoformat commad

Is it possible to use this to autoformat powershell code ?

In theory this should already work since PowerShell Editor Services (the language server for PowerShell) already supports formatting.
Just need to figure out how to invoke formatting with coc

Looking at my logs, it looks like the formatting isn’t turned on…
"documentFormattingProvider": false,
"documentRangeFormattingProvider": false,
"documentOnTypeFormattingProvider": null,

Is there any way to support you guys with some coins with these efforts?
IMO this project is going to be very popular as there is nothing else that would provide autoformat and autocomplete for powershell for vim it's a big deal for open-source community that wants to actually start using powershell, Microsoft should make this a priority project ;)

Right now we're just 2 Microsoft folks (and 1 non-Microsoft folk) moonlighting this project 😅
My team, the PowerShell team, would be the best place to officially own it... but the team (of 13 for all of PowerShell + Win32-OpenSSH) has a lot on its plate at the moment.
Best support would be time, if I'm brutally honest. Helping with docs, reproducing issues so we can fix them, and yes PRs always welcome 😊
We also need to setup a test suite so we don't break things.
If these are something you can help with, we'd be happy for the support 😊

Is code formatting handles by AnalysisService.cs?

Is code formatting handles by AnalysisService.cs?

Nice!
The good news is that PowerShell Editor Services already supports handling formatting so if we wanna enable this in coc-powershell, all we have to do is tell coc.nvim that it's supported.

@TylerLeonhardt I'm trying to implement format handlers for coc-fsharp these days, got some hands-on experience with coc.nvim;
Basically:

The formatexpr option is tied to gq, but not =. = uses built-in indent function, backed by the vimL associated with the file type (indent.vim) -- so that can also be rerouted.
Manually call CocAction('format') works great -- so is CocAction('formatSelection', 'v') -- mind the "mode string" again.
Haven't figure out how is the format-while-typing handler called by coc.nvim -- may be called during an automatic hard wrap (see 1.)

I discovered that PSES has poorly hooked up formatting... that relies on this code in the client side:
https://github.com/PowerShell/vscode-powershell/blob/master/src/features/DocumentFormatter.ts
I'm doing some major refactoring of PSES and this code wont be required in the future but for now it is

@TylerLeonhardt ringring ;)

Good news and bad news:
bad news - coc.nvim doesn't support:
vscode.languages.registerDocumentFormattingEditProvider
vscode.languages.registerDocumentRangeFormattingEditProvider
vscode.languages.registerOnTypeFormattingEditProvider
so I can't implement this at the moment. That said, PowerShell Editor Services is moving to handle the formatting registration automatically so in the 2.0 version of PowerShell Editor Services formatting should work out of the box.

good to know!

We will race with coc.nvim to see what happens first: https://github.com/neoclide/coc.nvim/issues/1179

race conditions! :D
yeah for F#, I just declared these capabilities in the language server so it works automatically.
Let's see how coc.nvim will respond.

I just declared these capabilities in the language server

Right. PowerShell Editor Services never did this for some reason... really not sure why.

Thanks to PSES 2.0, this works now :) :call CocAction('format')


Use PSR-4 now.

Refs https://github.com/propelorm/Propel2/issues/575
We should get all to psr-4 including tests (which currently are not yet in autoloader at all)
This would probably be for the 2.0 stable release.

Please rebase

Done, looks as green as before.


Update to .NET 8

Modifies the target framework to .NET 8.
⚠ Note: This won't be merged until .NET 8 releases later this month.

.NET 8 is now GA. Switched core packages to their stable versions.


translation of rules buggy?

I have a simple object:
class RecurringTask(CreatedUpdatedMixin):
    title = models.CharField(max_length=255)
    recurrence = RecurrenceField()

    def __str__(self):
        return (
            f"{self.title} ({', '.join([r.to_text() for r in self.recurrence.rrules])})"
        )

When I see it in the Django admin, it translates the rule correctly into German (alle 3 Monate):

But when I click on the item, the field is untranslated ("every 3 months"):

Could it be that the RecurrenceField uses an untranslated string output when creating the edit widget?
Or are these strings translated separatedly, and one is just not translated?

Did you follow the instructions how to set up i18n?
https://django-recurrence.readthedocs.io/en/latest/installation.html#set-up-internationalization

Yes, this is my main urls.py:
import django
from django.urls import path
from main.views import MainView
from django.views.i18n import JavaScriptCatalog

urlpatterns = [...]

js_info_dict = {
    'packages': ('recurrence', ),
}

urlpatterns += [
    path('jsi18n', JavaScriptCatalog.as_view(), js_info_dict),
]


Is "migrations" a reserved word or something?

I bumped into this one accidentally but seems to be very easy to reproduce.
run cargo new --bin migrations and open this new folder in vscode, when you add any dependency you will get this error (adding tokio for example):
[{
	"resource": "/home/me/dev/rust-tests/migrations/Cargo.toml",
	"owner": "_generated_diagnostic_collection_name_#0",
	"severity": 8,
	"message": "Additional properties are not allowed ('tokio' was unexpected)",
	"source": "Even Better TOML",
	"startLineNumber": 8,
	"startColumn": 2,
	"endLineNumber": 8,
	"endColumn": 14
}]

Here's an image of it:

If I rename the folder to migration instead of migrations the issue goes away for example, so seems to be specific to migrations, the project builds and runs fine even with the error if I keep it named migrations

Thanks for the bug report! I'm able to reproduce. I suspect this is related to https://github.com/SchemaStore/schemastore/issues/3021.
I think the next step is to figure out which schema is used. I suspect that the wrong one is used because of the file path matching another rule. However I don't know how to print the used schema, I'll have to investigate (this weekend at the earliest).

Actually using RUST_LOG=debug works:
  2023-06-20T22:10:12.417075Z DEBUG taplo_common::schema: failed to cache schema, error: cache path not set
    at crates/taplo-common/src/schema/mod.rs:211
    in taplo_common::schema::load_schema with schema_url=https://json.schemastore.org/drupal-migration.json
    in taplo_common::schema::validate with schema_url=https://json.schemastore.org/drupal-migration.json
    in taplo_common::schema::validate_root with schema_url=https://json.schemastore.org/drupal-migration.json
    in taplo_cli::commands::lint::lint_files
    in taplo::taplo

So for some reason it's using the drupal-migration schema...

Ok so the bug is in taplo, in particular the SchemaCatalog::transform_paths() function that replaces the extensions with toml, which means that the **/migrations/*.yml rule from Drupal Migration becomes **/migrations/*.toml. I don't know why this code exists. I would suggest removing it.

Thanks a lot for looking into this. I didn't notice the notifications, sorry for not replying earlier.


hset expire is not working

I'm trying to set expire in hset but it's not working for me.
hset('clubList', ${memberType}-${userId}, JSON.stringify(clubsData), 'EX', 1)

I don't think EX is supported by hset. Please check the official documentation for details: https://redis.io/commands/hset


point bounty

I'm considering giving points for people helping me out with the bot

well-described bug report in an issue: 1000 points
a good idea: 500-1500 points (depending on how good the idea is)
sending a PR with working code: 1000+ points (depends on the size of the PR)

you can chose whether to get the points in forsens or my chat
thoughts?

I think it's fine; they'll gamba all their pleb points away anyway 4Head
Only thing is I would suggest giving them more options than just your or Forsen's chat; someone might want points in one of your other bots.

Convert donation to points (1 dollar = 100 points) ?
!duel  all (like you did yesterday with !roulette all) ?
Possibility for subs to give points to someone with a tax (30% tax) ?
Duel with losing getting timeout ?

I dunno Kev

@T-Brawl !givepoints is implemented. i don't think i want tax on point transfers though
donation to points is a no-no
!duel all is trickier since there's a limit for how many points you can duel

Customizable ranking system(Let the admin add rankings and point/hour requirements) based on how many points the user has or how many hours it has spent in the channel.

Traslation/bot output customization interface to modify commands (ex: Name your points "keks" so instead of points it's !keks) and bot messages. Maybe in the config file (????).

BabyRage Windows Install Guide BabyRage (Maybe a how to emulate ubuntu in windows in case native windows install is impossible).

Any link to the current bot features to think of more?

I think the only place where the name "points" is fully hard-coded is on the website, where it links to the /points/ page etc.
When you add your own command to check how many points the user has, you could just do this:
!add command keks $(usersource;1:username_raw) has $(usersource;1:points) keks xD


[Airbrake] [Production] NoMethodError: undefined method `with_indifferent_access' for false:FalseClass

Airbrake error: #8430
Airbrake project: ETE
Error type: NoMethodError
Error message: NoMethodError: undefined method `with_indifferent_access' for false:FalseClass
Where: data/scenarios#update
Occurred at: Nov 08, 2017 08:46:52 UTC
First seen at: Nov 08, 2017 08:46:52 UTC
Occurrences: 0 (0 since last deploy on <no information>)
Severity: error
URL: https://engine.energytransitionmodel.com/data/latest/scenarios/340450
File: [PROJECT_ROOT]/app/models/scenario/user_updates.rb
Backtrace:
[PROJECT_ROOT]/app/models/scenario/user_updates.rb:82:in user_values_as_yaml=
[GEM_ROOT]/gems/activerecord-4.1.5/lib/active_record/attribute_assignment.rb:45:in public_send
[GEM_ROOT]/gems/activerecord-4.1.5/lib/active_record/attribute_assignment.rb:45:in _assign_attribute
[GEM_ROOT]/gems/activerecord-4.1.5/lib/active_record/attribute_assignment.rb:32:in block in assign_attributes

Was closed by 671fa7a9. I've cherry-picked it to production and it'll be deployed momentarily.


Also - Job type discrepancies on peviitor.ro

ENVIRONMENT: production
URL: https://firme.peviitor.ro/
Browser: Safari
Device: Laptop
OS: macOS 14 Sonoma
STEPS TO REPRODUCE:

Open URL in browser
Type "Also" in the search bar
Click on "Cauta"
Right-click and select "Inspect"
Copy the Request cURL: https://api.peviitor.ro/v3/search/?company=also&country=România&page=1
Open Postman and create a new entry with GET request
Click on "Send"

EXPECTED RESULT:
The GET request should return a response with a status of 200 OK and information related to job openings retrieved from the API response should match the information related to job openings listed on the official website of Also and on the peviitor.ro website.
ACTUAL RESULT:
Discrepancies are found in the job type information provided on our website peviitor.ro displayed as "remote", which does not accurately reflect the actual job type specified on the Also official website.

Job type is not displayed.

This is related to front end

rules:

if job_type is remote then don't show the city
if the location is not a county show only the city
if the location is county then show only the county and city all


HttpBinding improvements

Cleaning up + improving HttpBinding. Previously you couldn't return a simple scalar value from a function, e.g.:
module.exports = function (context, req) {
    context.res = 123;
    context.done();
}

This now works. We now use HttpRequestMessage.CreateResponse and let WebApi do its default thing in these scenarios.

👍


fix: remove setup labels for refresh month

I found a problem in the latest version 1.6.1.
When you refreshed current month it adding duplicates for day view labels, it will add as many labels as you many times you refresh month.
I found that this bug appears after the commit: https://github.com/CVCalendar/CVCalendar/commit/f38f9d461754c9a5a47c76778efb1f5c593a4f39
Hierarchy view

Thanks again for your contribution, really valuable to the project! I merged all of them and created a new release 1.6.2 which makes them available to all users on cocoapods. Please continue to add/suggest improvements! 🥇


New glitch demos

R: @jeffposnick @philipwalton
Moving the previously discussed new Workbox v5 demos that have already been deployed on Glitch and linked to in the Workbox Modules page.
Next steps would involve github -> glitch pipeline (to remove manual effort) and a minor build process to reduce steps needed to update demos when a new workbox version comes out.

Thanks, @philkrie!
There are currently a number of gulp tasks related to updating and publishing the demos, but I don't think there's going to carry over to the new demo setup.
If you're cool with it, I'm going to push a commit to this PR that will remove those gulp tasks and the related dependencies from package.json prior to merging.

Sure thing, makes sense. I'll do pipeline work within this directory and we can then migrate it to the top level gulp pipeline later.

Updated glitch and the repo to 5.0.0. Still no automated process, haven't had the time, but as mentioned, should be enough for a while

Coverage remained the same at 79.403% when pulling 23003257e459c28ec5e5c1b13bdc6cae0183615a on philkrie:master into c884ee2d9e0aa2b25fc7b754e923469bbae13b61 on GoogleChrome:master.

Thanks! I've gone ahead and merged.


Example code

Hi Ray,
Thanks for your work on this.
However in the example code should there not be a setTemplate command just before returning $pdf ?
$pdf->setTemplate();
I have just added this and it works
regds

Hi @sgarstin,
As you've noticed DOMPDFModule hasn't received the time and attention it deserves. I understand how frustrating this is and I'm sorry you've had to deal with this frustration 😢
I'm currently taking steps to stabilize DOMPDFModule which includes code updates as well as creating a backlog that will ensure its continued success.
You can follow project Phoneix  to see what immediate work is being prioritized.
Thank you for your understanding and patience.


Refactor SubversionRepository implementation in repo library

I've seen that Subversion 1.6.17 (current version) has nice Ruby bindings tests. I think we should learn from them and use the "right" thing in our implementation.
In particular, we are rolling our own SVN authz manipulation thing. We should replace it with bindings library calls.

I think the refactoring of this class is way better with using the svn command with system.
To me there are not a lot of svn command to be need more performances than using system command. Some big project like Redmine/Chilliproject use svn command line with success.
So it's really better to me to use this commandline instead of swig binding.
swig binding are some big issue :

No gem generated so you can't use it in your Gemfile
Dependent of ruby version you can't switch to new ruby version like 1.9

The command line works all the time and more readable if you know the svn in commandline.
The swig ruby binding documentation is hard to read too. more readable the commandline.

Hmm, so you are proposing to call out to svn instead of using the bindings?

Yes exactly with the system command
cyril mougel

I don't think from a pedagogical point of view it is a good thing to support only a DCVS. Even after having a course on git, students working on markus have trouble using this tool. Imagine having to deal with 300 students messing up their git repository, without mentionning that having teachers that uses svn on a regular basis is already quite rare (at least in France).
Even if we have git a the default backend for support, I think it is unrealistic not to provide svn support for CLI access courses (ie the problem of svn remains...).

Nelle: Perhaps. In my opinion it would be up to the users to decide what they'd like to use. I didn't mean to imply to drop SVN entirely. Since we don't have any other support than SVN this discussion is moot :)
In any case, I'm not a fan of "shelling" out to svn if we can avoid it. I'd prefer a solid implementation using the bindings. Yet, that's just one opinion.

Thats what I meant !
I don't have an opinion on using the svn bindings or not. I don't have
any experience with them.
On 2 December 2011 18:01, Severin Gehwolf
<EMAIL_ADDRESS>wrote:

Nelle: Perhaps. In my opinion it would be up to the users to decide what they'd like to use. I didn't mean to imply to drop SVN entirely. Since we don't have any other support than SVN this discussion is moot :)
In any case, I'm not a fan of "shelling" out to svn if we can avoid it. I'd prefer a solid implementation using the bindings. Yet, that's just one opinion.

Reply to this email directly or view it on GitHub:
https://github.com/MarkUsProject/Markus/issues/490#issuecomment-2992688

To my mind, bindings (in a general way) are better : they are platform independant.
MarkUs is supposed to work on GNU/Linux, Mac OS X and Windows (even if, on Windows…)
There is not yet a libsvn-ruby for ruby 1.9. I am looking to provide a Debian package as soon as possible.
Moreover, I think the best way is to abstract the CVS/DCVS system from MarkUs. But it is not the priority. In France, for example, it doesn't matter for teachers or students to use SVN as backend as they don't know what's happening in the backend.


update github attic-labs org logo

Recommend updating the attic-labs Github org logo to be noms for now since the org logo is what shows up in many places that show "preview image" of http://github.com/attic-labs/noms
e.g. https://twitter.com/mikergray/status/760870766397132800

I was using the galaxy on purpose for attic labs, as a sort of visual pun on "attic", but it's probably a little bit of a stretc.


DS-4557: Trim username otherwise a login with a legit value …

…containing leading or trailing spaces will fail
Description
https://jira.lyrasis.org/browse/DS-4557

I'm using XMLUI (Mirage 2) on DSpace 6.3, but can't seem to reproduce this. If I enter an email like "<EMAIL_ADDRESS>with a leading space, the JavaScript validation fails and displays a popup saying "Please enter an email address". See:

How were you testing this on XMLUI @marsaoua? Thanks!

Closing, as I cannot reproduce this issue on the 6.x demo site either: http://demo.dspace.org/xmlui/


Contructor issue with non-None timezone

Constructor of Arrow object (arrow.py) fails if tzinfo is non-None and if it does not contain field "zone".
The problematic part:
isinstance(tzinfo, dt_tzinfo)
and hasattr(tzinfo, "localize")
and tzinfo.zone
):
should be like
isinstance(tzinfo, dt_tzinfo)
and hasattr(tzinfo, "localize")
and hasattr(tzinfo, "zone")
):
The change came since version 0.14.5

Hello @mafycek, I don't understand what you mean, please can you provide a reproducible example.

Hey thanks for reporting this. Like Chris said, it would be great to have an example input that causes Arrow to fail so we can write a regression test :).

Hi guys,
hope that you are well.
Say, I have a (simple) program like:
`
import arrow
import dateparser
date_that_succeds = "1990-01-01T00:00:00"
date_that_fails = "1990-01-01T00:00:00+00:00"
for date in [date_that_succeds, date_that_fails]:
try:
parsed_date = dateparser.parse(date, date_formats=None or ['%d %B %Y', '%d/%m/%y', '%d/%m/%Y', '%d.%m.%Y'])
arrow_date = arrow.get(parsed_date)
print(date_that_succeded, arrow_date)
except:
print("It failed on date " + date)
`
Results:
with arrow 0.15.0
The first date passes however the the second fails.
with arrow 0.14.4 (I tested on 0.13.1)
Both pass
Explanation of the failure:
parsed_date is of type datetime with component variable tzinfo of type StaticTzInfo. The StaticTzInfo type has two component variables _StaticTzInfo__name of type str and _StaticTzInfo__offset of type timedelta. When such variable is inserted into arrow through get it fails in the constructor of arrow class because tzinfo in the constructor is of type StaticTzInfo that does not have component variable zone and that is why the interpreter says
AttributeError: 'StaticTzInfo' object has no attribute 'zone'
My comment:
I do not know if the test of zone component is correct. If yes that it should test presence of the variable and then the value if that is needed.
Bye,
Hynek

Colleague of mine fixed unnecessary stuff and typo. However the message is the same:
`
import arrow
import dateparser
date_that_succeeds = "1990-01-01T00:00:00"
date_that_fails = "1990-01-01T00:00:00+00:00"
for date in [date_that_succeeds, date_that_fails]:
try:
parsed_date = dateparser.parse(date, date_formats=['%d %B %Y', '%d/%m/%y', '%d/%m/%Y', '%d.%m.%Y'])
arrow_date = arrow.get(parsed_date)
print(date, arrow_date)
except:
print("It failed on date " + date)
`

Thanks @mafycek, we will do some digging on this bug and look at fixes.


VM: Add support for live shrinking of limits.memory

Adds support for shrinking the memory limit of VM (when hugepages are not being used) using lxc config set limits.memory.

Testsuite passed

Testsuite passed


🐛🐛  Bug Report: 获取撤回的群消息时，取不到真实的valueID

如题

This is the implementation detail of wechat protocol, and it's the normal behaviour for fetching the recall message.

This is the implementation detail of wechat protocol, and it's the normal behaviour for fetching the recall message.