tap: suppress TAP header in subtests

There appears to be no official standard for subtests, but the tap4j
that the Jenkins TAP plugin uses seems to expect only one header and
barfs if the subtests include their own headers.
See http://instanttap.appspot.com/

Fixed the tests and commit message, includes regenerated fixtures. Shall I merge once Travis is green? Or do you want to mull it over a bit more?

Discussion in npm irc channel: https://gist.github.com/isaacs/1a31aecd161de6ab8da6

Travis failures are because the save-file test is taking enough ms to be rounded to 1s in the timing output.
Worth fixing, but unrelated to this PR.  LGTM!

@isaacs I can merge but publishing is still up to you. Would you mind cutting a release?

Re release:
22:54 <@isaacs> rmg: So, I am going to replace t.tearDown(fn)  (and also t.beforeEach, t.beforeAll, t.afterAll, t.afterEach)
22:55 <@isaacs> rmg: it's almost done but there's an issue I need to work out re the root test.  see the `teardown` branch on isaacs/node-tap
22:57 <@isaacs> rmg: since that's almost done, and these things are subtle behavior changes anyway, maybe we could push off until a 1.3
                release?
22:57 <@isaacs> I don't think these behavior changes are *breaking*, per se, since all the user-facing stuff stays consistent.
22:58 <@isaacs> but you could argue that "now with tap4j support!" is a new feature of sorts

I've got some config changes I'd like to roll out to StrongLoop's CI that are waiting on this patch so that it doesn't result in a flood of passing tests failing at the last minute when parsing the TAP results. (Yay Jenkins!)


ci: merge opae-libs

Automated changes by create-pull-request GitHub action

Coverage decreased (-0.03%) to 77.944% when pulling 53aead4af370f236b74dda636271edbd8886d46b on auto/update-libs into e7b36d07b6ea175c92eb8a725d9d3bc0d11fcd97 on master.

Coverage decreased (-0.03%) to 77.944% when pulling 53aead4af370f236b74dda636271edbd8886d46b on auto/update-libs into e7b36d07b6ea175c92eb8a725d9d3bc0d11fcd97 on master.


Old links to prepared scenarios broken

I have a spreadsheet with many links to microcovid.org models for quickly updating the sheet by opening each link and copying out the new numbers.
Unfortunately, the recent changes to the UI broke all these links. Is there any way we can maintain backwards compatibility for old links? or if there's a way to easily migrate the links, that would work too.
For example:
https://www.microcovid.org/?distance=normal&duration=600&interaction=oneTime&personCount=80&riskProfile=average&setting=indoor&subLocation=US_12086&theirMask=none&topLocation=US_12&voice=loud&yourMask=none&yourVaccineDoses=2&yourVaccineType=pfizer
https://www.microcovid.org/?distance=normal&duration=1040&interaction=oneTime&personCount=20&riskProfile=average&setting=indoor&subLocation=US_06085&theirMask=thin&topLocation=US_06&voice=normal&yourMask=thin&yourVaccineDoses=2
(Actually the links still seem to give numbers, they just don't show the selections in the UI anymore?)

Looks like adding &scenarioName=custom is what is needed.

Yeah, it's currently set to not show anything if scenarioName is "". I think I can fix this by replacing an absent query parameter with "custom" instead of "". Thanks for the report!

@Hixie can you try out #902 over at https://deploy-preview-902--microcov.netlify.app/ ?

Looks good!


iso installation docs unclear on supported RHEL versions

The docs don't mention anywhere which RHEL versions are supported. More than that, there is some confusion on that within the team itself: we build RHEL 9 RPMs, does that mean we support it, or just that it might work? The documentation currently hardcodes RHEL 8 in the yum config file.

[ ] find a concensus on which iso versions support which RHEL versions and how this will be going forward
[ ] make sure documentation matches this, preferably without having to introduce a new major release task, e.g. irt could read pyproject.toml and set a variable in docs/conf.py that can then be used by the docs files in core.

This is a duplicate of https://github.com/inmanta/inmanta-core/issues/6324

Right, we even talked about it, what was I thinking...

closing as duplicate


[Builtins] Polish handling of integral types

This

adds support for throwing operational unlifting errors in the builtins machinery, which allows us to attach a message to an unlifting failure. Unfortunately this is still not enough to propagate proper error messages to the user, because they get erased by the evaluation machinery down the line, this is our 2018's legacy of the stupid idea to have raw evaluation failures that don't carry any content
makes handling of integral types in PlutusCore.Default.Universe uniform (it was a mess before with a weird partial set of instances and morally the same instances being implemented differently)

Unfortunately this is still not enough to propagate proper error messages to the user, because they get erased by the evaluation machinery down the line, this is our 2018's legacy of the stupid idea to have raw evaluation failures that don't carry any content

I'll either create a separate PR for it or open an issue (likely the latter).


Generate 2021-10-15 SDK and update tests

All SDK Contribution checklist:
based on new swagger from https://github.com/Azure/azure-rest-api-specs/pull/16388
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[X] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[X] I have read the contribution guidelines.
[X] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[X] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[X] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[X] Include updated management metadata.
[X] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

How are the files under "SessionRecords" generated? Could someone please help resolve ci issues? I am unable to identify what I am missing.


gRPC with protobuf payloads is not supported

gRPC is a popular approach to  building API's these days practiced by big tech and fintech companies, but it's not supported in the current Akto implementation.  To reproduce:

Install Akto plugin in BurpSuite with automatic export enabled
Install Akto Dashboard
Run a REST API with JSON payload in Burp's Repeater and observe that the export from Burp to Akto Dashboard works
Run an gRPC API with protobuf payload in Burp's repeater and observe that export to Dashboard doesn't work
Try exporting gRPC payload to HAR file in Burp's Akto Plugin and observe that 'entries' field is empty:

{"log":{"version":"1.2","creator":{"name":"Akto","version":"3.19.2"},"pages":[],"entries":[]}}

Thanks @ogryb
We have added this to the roadmap now for this quarter. https://github.com/orgs/akto-api-security/projects/8/views/1

It's supported now in our latest release. Closing the issue


Setup alert manager against rule sets

Details
Configure alert manager with some sample/basic rule sets.

Done.


[IOS] Location updates not coming in the background

Hi Team,
First of all thanks a lot for this plugin it's extremely useful!
While it is working great for me on Android am facing some issue on IOS.
Here is what I have tried:

Copies the Example code given here
Gave all the needed permission in XCode
Tried running the app

Expectation:
I should be able to see location updates when

The screen in the foreground
The App is minimized
When the phone is locked

Monitored the logs coming from the app and found that am only getting location updates when the app is in the foreground.
Am I missing anything here? How can I make sure the location updates are coming even when the phone is locked or the app is minimized?
Please let me know if any other details are needed!
Regards,
Rajdeep Barad

What is your test device? Are you testing on real phone or simulator?

Mehdi,
I support Rajdeep with this. We are testing on a real device - iPhone 6S with the latest iOS version installed.
On the app settings on device: Background Refresh is ON, Location capture is set to "Always"
Xcode: background capabilities are enabled for location updates, background fetch and background processing
Info.plist screenshot attached too.
Thanks,
Mehul

Try to simulate location update with iSpoofer and see if you can receive any location update or not. If not, try the example app and see if situation is the same or not;

We have already tried the example app and it's the same behaviour there.
I will try the iSpoofer and would let you know the results but am not sure if that will help here.

Any update?

Closed the issue due inactivity, feel free to open it anytime;


Add issue template

we need to add issue template for manage issues and their messages

i think we should write a structure about issues category that you want @amiremohamadi

thanks for mentioning. I’m gonna close this issue as it’s not that beneficial for now.


org.jasig.cas.authentication.HandlerResult ignoring argument

org.jasig.cas.authentication.HandlerResult ctor ignoring the argument warnings: https://github.com/Jasig/cas/blob/4.0.x/cas-server-core/src/main/java/org/jasig/cas/authentication/HandlerResult.java#L68
git branch: 4.0.x

You're right: the same issue occurs on master as well: https://github.com/Jasig/cas/blob/master/cas-server-core/src/main/java/org/jasig/cas/authentication/HandlerResult.java#L90
Would you mind sending pull requests to fix that?

In the interest of moving forward with the release, I'll take care of this.


There should be consistent styling for Field Guide pages

This page in particular uses much smaller font than other pages seem to
http://www.freecodecamp.com/field-guide/how-do-free-code-camp's-nonprofit-projects-work

Hi,
The Headings seem to alternate between H2 and H3, should these be reversed mayhap?

This issue is related to a question I had about authoring field guides: why are parts of the text which semantically should probably be paragraphs marked up using <h3> tags? How is this markup generated?

I thought the h3 looked better than p, but we can use p and style it later if we need to. Google will like p better. I've made the changes and will push the release tomorrow.


why using cube maps for fonts?

I'm learning how font example works and curious why bgfx implements texts as cube maps instead of a regular texture2D? Thanks!

On some platforms maximum 2D texture size was 2048x2048, by using cube map you increase capacity of the atlas 6x. In bgfx example this is not used, but it was neat trick.


Updating Instance name to Name

Updating Instance name to Name as per the Jira issue https://issues.redhat.com/browse/MGDSTRM-4897 and doc https://docs.google.com/document/d/1gVd_dQrap0T78Tk-kZs2cJqL0zGAedpaME9CSTmI8zs/edit#

Sounds good!


Add Makefile_Mac_clang_shared analogous to Makefile_linux_shared

should i do this in the dev branch or the master branch?  develop seems to be the default branch for this repository

This was useful for me - thanks!

This looks a bit different in the upcoming v2.9.0, so I can't take the merge directly.  But thanks!


h3 heading to h4

from @metageeky Accessibility fix: the collections under Collections (H3) should all be H4

837e43a94b027d43d996b840971dac3b40cdcf90


Docker Cleanup

remove version from registry image so latest tag is always pulled

include init so processes aren't running as pid 1

add optional persistent volumes for agents and workspaces

Clamp layers from scratch on runner

move deps from frontend to own build step for faster builds when using cached in CI

Mounting the volumes for some reason is throwing errors despite the containers have full read-write and the Objective Work Log fails to print so I commented it out but maybe you want to just remove it completely.
2023-04-25 18:55:05 agent-llm-backend-1   | ERROR:    Exception in ASGI application
2023-04-25 18:55:05 agent-llm-backend-1   | Traceback (most recent call last):
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/uvicorn/protocols/http/httptools_impl.py", line 436, in run_asgi
2023-04-25 18:55:05 agent-llm-backend-1   |     result = await app(  # type: ignore[func-returns-value]
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py", line 78, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     return await self.app(scope, receive, send)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/fastapi/applications.py", line 276, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     await super().__call__(scope, receive, send)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/applications.py", line 122, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     await self.middleware_stack(scope, receive, send)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/errors.py", line 184, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     raise exc
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/errors.py", line 162, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     await self.app(scope, receive, _send)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/cors.py", line 92, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     await self.simple_response(scope, receive, send, request_headers=headers)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/cors.py", line 147, in simple_response
2023-04-25 18:55:05 agent-llm-backend-1   |     await self.app(scope, receive, send)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 79, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     raise exc
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 68, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     await self.app(scope, receive, sender)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     raise e
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     await self.app(scope, receive, send)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 718, in __call__
2023-04-25 18:55:05 agent-llm-backend-1   |     await route.handle(scope, receive, send)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 276, in handle
2023-04-25 18:55:05 agent-llm-backend-1   |     await self.app(scope, receive, send)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/starlette/routing.py", line 66, in app
2023-04-25 18:55:05 agent-llm-backend-1   |     response = await func(request)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/fastapi/routing.py", line 237, in app
2023-04-25 18:55:05 agent-llm-backend-1   |     raw_response = await run_endpoint_function(
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/usr/local/lib/python3.10/site-packages/fastapi/routing.py", line 163, in run_endpoint_function
2023-04-25 18:55:05 agent-llm-backend-1   |     return await dependant.call(**values)
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/app/app.py", line 190, in get_task_status
2023-04-25 18:55:05 agent-llm-backend-1   |     status = CFG.agent_instances[agent_name].get_status()
2023-04-25 18:55:05 agent-llm-backend-1   |   File "/app/AgentLLM.py", line 161, in get_status
2023-04-25 18:55:05 agent-llm-backend-1   |     return not self.stop_running_event.is_set()
2023-04-25 18:55:05 agent-llm-backend-1   | AttributeError: 'NoneType' object has no attribute 'is_set'
2023-04-25 18:55:27 agent-llm-backend-1   | Starting task with objective: some test.


Document BitBucket Pipelines

Add documentation on how to use localstack in BitBucket Pipelines.

@dominikschubert is that PR ready?

We now have some docs ready: https://docs.localstack.cloud/user-guide/ci/bitbucket/


Sidekiq 4 support?

Does this gem support Sidekiq 4?
Thanks!

I haven't tested it since I haven't switched to Sidekiq 4 yet.  I'll add a build for that to the matrix and we'll find out!

Any update?

It seems that Sidekiq 4.0.2 was added to the build matrix and have tests passing: https://travis-ci.org/hummingbird-me/sidekiq-debounce

Working with Sidekiq 4.2.9.
Seems like it would be plenty safe to close this issue out.

As stated, we seem to be all green on Sidekiq 4 👌


1.18.2 Lootr TPS drop

https://spark.lucko.me/252KImLJ8k
noobanidus.mods.lootr.block.entities.TileTicker.serverTick() 21.55%
Last 1.18.2 version from curseforge

Could you give me some more context about this? I realise that this is quite a higher number, but the overall TPS of the server seems to be stable at 20. Is this during a period of significant lag? How long was the sample? Is this happening constantly, or was the sample taken during world generation?
I do have some ideas for improving the performance of this piece of code, but unfortunately, due to its nature, it's always going to be slightly more expensive; the alternative is accidentally loading chunks on the main thread while they're still being generated, which would produce tremendously more lag.

This happens during the progression of chunks in which there is a chest,

@noobanidus This is due to https://github.com/noobanidus/Lootr/blob/e65147f1c8fab9bb96173a48c535a968982325ac/src/main/java/noobanidus/mods/lootr/event/HandleChunk.java#L21-L32
You are caching every loaded chunk and never unloading it. After a while, the map gets so huge, that every lookup kills the server's performance. Can confirm that on my 1.19.2 server at the moment, Lootr is taking up 80% of the tick time, dropping TPS to 15. You should be able to subscribe to something like onChunkUnload and clean up the chunks that you have loaded once they are no longer needed.
Same issue is present on Forge and Fabric btw.

I realize the chunk position map is problematic (for other reasons), but please note that this is the chunk position that's being cached, which is a combination of the X and Z coordinates of the chunk, not the actual chunk itself being stored.
Likewise, no chunks are actually being loaded at this point; the LOADED_CHUNKS map is being populated with the coordinates once the chunk has been fully loaded -- there's never any actual chunk loading. Without having this system, the conversion of chests would cause chunk-loading on the main thread which would block and causing significant lag. That said, the data structure could be due for some redesign, as well as the method of accessing it.
However, some further context is needed: is this happening all of the time, for every tick of the server without exploration, or is it only happening during exploration? A link to the full report would be good.
If the former, then it appears as though there's something stuck in the queue for conversion that's causing it to constantly refer back to the list, but failing to convert. Does this issue persist through server restart?

Apologies, I didn't have the time to look carefully and only glimpsed at the code. I was aware that you're not loading the chunks, but I thought you were keeping a reference to them indefinitely, which prevented them from getting GC'd. Given you're only storing the position, that should not be the case, unless the position holds a back-reference to the chunk. Not sure what the structure is there.
This issue happens for every tick, during no exploration at all. A restart helps, bringing the tick usage down from 70% to 30%, but even just after a fresh start, it is still way above everything else. Possible causes could be Compact Machines mod (they create chunk-loaded mini dimensions), and FTB Chunks mod (force loaded some overworld chunks). Maybe a chunk is getting repeatedly loaded/unloaded for some reason?
You can find the low TPS profile here: https://transfer.sh/InfkwA/ifPYySdjU3.sparkprofile
Here's profile right after server restart: https://transfer.sh/paQ6wx/zDrtBKsnh3.sparkprofile
Load at: https://spark.lucko.me/

It seems most likely to me that the TileTicker.tileEntries is continuously growing over time, as HashSet.<init> is appearing with a substantial percentage in the profile, and that should only be slow if the constructor is copying a large number of elements from a provided collection/set. This seems to match @noobanidus's theory about something being stuck in the queue.
Resetting the server probably helps because it empties the set.

I think there are multiple issues here: the large number of stored chunk positions (as far as I'm aware it's just a basic Pair class with the X and Z and some functions, so no actual reference) combined with repeated checks implying that there's a "stuck" tile entry.
Reasoning for the current system and further on what I said before: since 1.17, the standard method of just checking if the chunk that the block entity was in being properly loaded ceased to be sufficient: setBlock to convert the chest to a Lootr chest force-loads 25 chunks (5x5) around the relevant chunk.
Without the current code, it would see that the chest's chunk was loaded, attempt to replace it in the main thread and then proceed to block the main thread as it waited on 25 other chunks to complete generation and loading.
It's definitely an intermittent issue, though, as I've only had a few reports of issues with it, and generally those issues are concurrent with the actual world generation.
However, as you're experiencing it constantly, without world generation or exploration, that means an entry (or multiple entries) are failing to unload.
Steps I'd like to take:

A linked hash set would most likely reduce some of the overhead as repeated entries would be accessed quicker.
Re-doing "containsAll" chunk to check each required chunk and then store those not contained. This would reduce the number of look-ups and also allow the identification of specific, problematic chunks that are never being "loaded".
Re-adding decay to tile entries: if they fail to resolve after X period of time (configurable, perhaps), they should just be removed from the list. Downsides: this could potentially result in some chests not getting converted. Upsides: we can specifically log which entries are being unloaded.
Adding decay for the chunk storage. After a certain period of time being in the list, chunks would be removed, resulting in a smaller set of chunks to consider. In theory this should never cause any problems.

I'll need to make some more considerations over this.
At the very least, a debug build could be made that would at the very least identify which block entries are getting "stuck" so there's some way to investigate what's happening...
I'm afraid I've got quite a bit on my plate at the minute, but I will try to work on something later this evening my time. If you're able to join my Discord, I can use that to get you a server-side replacement version for testing, otherwise I can try uploading a version here.
Further to that, which exact version of Lootr is this for 1.19 so I can ensure that I don't cause a version conflict with the debug build?

Dumping some of our findings from Discord to track better here.
I used a debug build provided by @noobanidus that logs entries which are unable to be converted after 2 minutes, as well as remove them from the queue:

lootr-1.19-<IP_ADDRESS>.jar.zip

:warning: DO NOT use this build in your production servers

From this build, I got the following —

Spammed every tick:

[12:52:51] [Server thread/ERROR] [no.mo.lo.ap.LootrAPI/]: Removed old (2 minutes or older) entry for ResourceKey[minecraft:dimension / compactmachines:compact_world] at BlockPos{x=8, y=41, z=-1016}

Appeared once:

[12:52:42] [Server thread/ERROR] [no.mo.lo.ap.LootrAPI/]: Removed old (2 minutes or older) entry for ResourceKey[minecraft:dimension / minecraft:overworld] at BlockPos{x=-194, y=66, z=2096}
[12:52:42] [Server thread/ERROR] [no.mo.lo.ap.LootrAPI/]: Removed old (2 minutes or older) entry for ResourceKey[minecraft:dimension / minecraft:overworld] at BlockPos{x=-193, y=66, z=2096}
[12:52:42] [Server thread/ERROR] [no.mo.lo.ap.LootrAPI/]: Removed old (2 minutes or older) entry for ResourceKey[minecraft:dimension / minecraft:overworld] at BlockPos{x=-195, y=66, z=2096}
[12:52:42] [Server thread/ERROR] [no.mo.lo.ap.LootrAPI/]: Removed old (2 minutes or older) entry for ResourceKey[minecraft:dimension / minecraft:overworld] at BlockPos{x=66, y=67, z=-300}
[12:52:43] [Server thread/ERROR] [no.mo.lo.ap.LootrAPI/]: Removed old (2 minutes or older) entry for ResourceKey[minecraft:dimension / minecraft:overworld] at BlockPos{x=167, y=80, z=-285}
[12:52:43] [Server thread/ERROR] [no.mo.lo.ap.LootrAPI/]: Removed old (2 minutes or older) entry for ResourceKey[minecraft:dimension / minecraft:overworld] at BlockPos{x=167, y=80, z=-284}

The offending entry that keeps appearing again and again despite being removed looks like this:

It is unknown what causes the chest to keep appearing every tick. For now, you can work around this issue by blacklisting the "compactmachines:compact_world" dimension in Lootr's config. Check the referenced issue above my reply for an example.

@ViRb3 Were you able to use the custom build I provided via Discord and did that help at all? The issue appeared to be all chests being added at load time rather than being filtered to chests with loot tables -- although that might potentially cause an issue where some tables are assigned their loot table later in the process.

I'm afraid that I had to bring down my server and never had the time to investigate further. The blacklist was a functional workaround, though.

Hey! We're having a similar issue with lootr taking up a lot of perf. Here's a spark report: https://spark.lucko.me/tTerVBkGFy
I can help test things if needed

@booleancoercion  I think this is going to be basically identical to Virb3's issue; hopefully the same fixes can do something to help. If you're on Discord, I can try to get you a build. What version of Minecraft, Fabric and Lootr are you running?

Minecraft 1.18.2
Fabric 0.14.10
Lootr 1.18.2-<IP_ADDRESS>
We're running a slightly modified version of AOF5 basically, I believe you can find the mod list in the spark report. I'll join the discord server and we can go from there.

here to say it occurs on 1.19.2 forge too
https://spark.lucko.me/F3O3FBjMch

I believe this should be addressed with the most recently released versions of Lootr. If people are still having problems, please file a new issue.


errors compiling and with tests

trying to use tree-sitter-scheme from my program like so:

p.set_language(&tree_sitter_scheme::LANGUAGE.into()).expect("error loading scheme grammar");

i get the compiler error

the trait From<LanguageFn> is not implemented for tree_sitter::Language, which is required by LanguageFn: Into<_>

also, trying to run cargo test in the tree-sitter-scheme repo outputs an error:

error[E0433]: failed to resolve: use of undeclared crate or module tree_sitter
--> bindings/rust/lib.rs:48:26
|
48 |         let mut parser = tree_sitter::Parser::new();
|                          ^^^^^^^^^^^ use of undeclared crate or module tree_sitter

Thanks for your report.
These language bindings are generated by upstream tree-sitter cli.
There is a bug in 0.23 cli that it generated incorrect 0.22 tree-sitter dev dependencies instead of 0.23.

Ah, the test works now, thanks for the quick reply! Think the other problem was my code using a wrong version somehow.


Update job log "Submit Issue" with context (label + error itself)

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1219
Originally created by @derek-knox on 2019-10-25 17:10:27

View 2 previous comments from the original issue on GitLab


mark more obsolete behavior

Move to internals.

Public API changes: ❌CP0001 T:Microsoft.PowerFx.Interpreter.UDF.DefineFunctionsResult❌CP0002 M:Microsoft.PowerFx.RecalcEngine.DefineFunctions(System.String,System.Boolean)

What was the motivator for removing the ability to register user-defined functions? Was this functionality moved elsewhere? Defining reflection functions is generally the more powerful option, however there are benefits to users being able to define helper functions without the need to recompile and redeploy the C# solution.

@EvanPriceSencom - this was a proof-of-concept implementation. We're in the middle of a fully productized implementation that will be public soon, but the APIs for that will look different.

@EvanPriceSencom - this was a proof-of-concept implementation. We're in the middle of a fully productized implementation that will be public soon, but the APIs for that will look different.

Understood, thank you for the reply. Looking forward to what comes of it; things are fantastic thus far.


CodaLab Submission Error

Hi, I recently generate the test results and validation results on CodaLab as the following structure.
--Submit.zip
----hl_val_submission.jsonl
----hl_test_submission.jsonl

The CodaLab gave me the error IOError: [Errno 2] No such file or directory: '/tmp/codalab/tmphfqu8Q/run/input/res/hl_test_submission.jsonl'
How can I solve this problem?

Hi @vateye, Did you have an enclosing directory for these two files? The eval script expects no directory for the files.

Hi @vateye, Did you have an enclosing directory for these two files? The eval script expects no directory for the files.

Yes, I just place the two files under res folder, and use zip -r submission.zip ./res/* to pack the files.

There is no need to place them under res, this res is an internal dir used by CodaLab. Select the two files directly and zip them.


Investigate and implement JHU branded public pages

First attempt at pages is here: https://github.com/jhu-sheridan-libraries/pass-ui-public/pull/1
However, there is content on these pages that is relevant to Eclipse and should be removed (e.g. footer, references to Eclipse, etc).
Some investigation with the Scholarly Comms Group might need to be done to arrive at a final set of pages, but we might want to take a first stab at doing them on our own.

@jaredgalanis Will we know enough to get a customization guide out of this exercise?

related to #652

related to https://github.com/eclipse-pass/main/issues/667


The "Table" chart displays N/A instead of timestamps with IANA codes

The "Table" chart can't display timestamps from Trino with IANA labels added.
I'm not sure if it's Trino specific, though.
How to reproduce the bug

Create a dataset from Trino. It should contain a timestamp. The dates at the source are in UTC. Make sure everything is fetched normally.
Create a "Table" chart using that dataset. Make sure the timestamps are displayed properly.
Modify the query to convert timestamps to specified time zone using an IANA code: select t.timestamp at time zone 'America/New_York' from ....
Rebuilt the chart. You'll see N/A in the timestamp column.

What works

Everything is properly displayed in the SQL Lab. Example: 2022-12-19 04:30:08.442 America/New_York.
The "Time-series Line Chart" properly parses such timestamps nonetheless.
Using -05:00 instead of America/New_York in the query allows the "Table" chart to properly display timestamps. So, it seems that an IANA code shouldn't be a part of the timestamp to be properly rendered by the "Table" chart.

Environment
Started with docker-compose. Commit: 5e1b8170c

browser type and version: Brave Version 1.46.140 Chromium: 108.0.5359.99 (Official Build) (64-bit)
superset version: 0.0.0-dev (that was displayed in the "About" section of the GUI)
python version: python 3.8.13
any feature flags active:

ALERT_REPORTS
DASHBOARD_RBAC

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ ] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

This is an interesting one... is this still an issue in 3.x?

Still not sure if it's an issue in 3.x... or by now, in 4.x. Closing as stale, but happy to revisit/reopen if anyone is still experiencing this in currently supported versions.


Flowchem main refactor

(somehow messed up with the a conflict resolution in #82 branch ;)

TODO:

[ ] update flowchem-vapourtec
[ ] update flowchem-spinsolve + update test
[ ] investigate pump router missing routes for ML600 (valve is ok, similar inheritance except SyringePump has no init)


Done!!!


Include Intl polyfill as local file

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!


MudTable Repeating Content after Window Resized

Bug type
Component
Component name
MudExpansionPanel
What happened?
I wrote a table that contains a list of device info but after resizing the window size, inside RowTemplate seems it repeated the content provided to MudTable.Items (btw. the Type passed in is a tuple list List<(string, object)>)
p.s. the item is contained inside a for-loop, as the repro link example.
please pay attention: the repro link is not as what I wrote inside my project, the items inside the first loop was wrapped as a single component. In my project, this bug is not shown at first time but will appear after the action of resizing the window.
Expected behavior
What I provided is a List, should the table render only the list content once rather than randomly repeating it.
Reproduction link
https://try.mudblazor.com/snippet/ckcIkdwiFUqWzdzx
Reproduction steps

create a MudTable inside a MudExpansionPanel
use foreach to add elements inside the variable that will passed into MudTable before rendering the table
wrap those stuffs inside any for-loop
voilà!
...

Relevant log output
nothing logged, and nothing printed as if an error.

Version (bug)
6.19.1
Version (working)
none has tested.
What browsers are you seeing the problem on?
Firefox, Chrome, Microsoft Edge, Safari
On what operating system are you experiencing the issue?
Mac OSX
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

holy i think im dizzy right now

Okay seems inside the expansion panel will the second loop run again in each UI change.

Team is too busy to work on this right now but if you're able to do a PR we'll make sure to review it quickly.

okay I found that this is not the error of MudTable, I'm now editing the original issue

the problem seems from MudExpansionPanel

Team is too busy to work on this right now (or most issues in general) but if you're able to do a PR we'll make sure to review it quickly.

yea i saw you got thousands of issues...
I will try to figure out the problem if i got free time

Team is too busy to work on this right now (or most issues in general) but if you're able to do a PR we'll make sure to review it quickly.

I found the root of the problem. MudExpansionPanel.cs line 143? using "((Microsoft.AspNetCore.Components.ComponentBase) this).StateHasChanged)", the method "StateHasChanged" re-invoked the loop caused content of ExpansionPanel rendering more. But currently I have no idea about how to fix this, or people should never use a loop inside the panel.

Unfortunately, this issue is unsolvable under the current structure and ASP.NET. I found that seems each time of announcing StateHasChange will cause the segment which has loop run again and pass the entire result WITH the former result to the MudExpansionPanel, then it will render both former result of loop and the new result of loop into the panel area.
it just like:
// pseudo code
on state has change:
    newResult = runContentRender()
    render.apply(childContent += newResult)

Or, this is solvable, if someone has enough time to remake the mechanism of UpdateAllAsync to avoid the announcement of StateHasChanged to all other components, or, set up a valid method that is able to modify the default delegate of pass-in RenderFragment, and figure out the duplicated items during construction of RenderTreeBuilder then remove them and continue the rest of construction of fragment.
for sure, giving up and updating documentation to announce users do not use any loop inside MudExpansionPanel is the easiest way, but this actually solved nothing but protecting users away from this weird issue. In this case, I will keep trying my research on this issue, although my ability is way worse than every others who contributed to the project. Or we can wait for Microsoft to optimize these bases.

@fr1g why not populate the table once in OnInitialized instead of doing the logic within the component rendering?
Even if you needed to do it in the rendering for some reason, you'd either need logic to ensure that the table is only populated once (some boolean check) or clear the table before adding to it each time.
I modified your example to use OnInitialized.
You stated your actual code is somewhat different so if this solution doesn't work for you, you may need to show what you actual code looks like.

@fr1g why not populate the table once in OnInitialized instead of doing the logic within the component rendering? Even if you needed to do it in the rendering for some reason, you'd either need logic to ensure that the table is only populated once (some boolean check) or clear the table before adding to it each time.
I modified your example to use OnInitialized.
You stated your actual code is somewhat different so if this solution doesn't work for you, you may need to show what you actual code looks like.

I did try to use some boolean to control whether the render should run the loop or not,,,
but if put that judgement around the inner loop seems not work on my situation.
Indeed your solution did work but still I cannot understand why only "OnInitialized" can work?
Forgive me, I'm not good at seeking for those reasons 🥺

Indeed your solution did work but still I cannot understand why only "OnInitialized" can work? Forgive me, I'm not good at seeking for those reasons 🥺

Basically you run the logic when the component loads (OnInitialized) and any additional re-rending of the page does not affect that initially created list.


Update Add-AzureADDirectoryRoleMember.md

Clarified supported member types (user, service principal).

@VinceSmith,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


[Suggestion] The ability to display a creature catcher that has a mob inside it.

While the creature catchers has a mob instead when viewed in the hotbar they have a nice visual, akin to a snowglobe.  The ability to be able to set these down as is and display them in world would give some insteresting design options similar to Ars Nouveau and its containment jars, though doesn't need the farming ability.

I think they work in Item Frames - but a way to place them in world might be cool. I'll add it to the list of nice to haves :)


Remove unused functions and classes

Fix #2329.
Some functions may be used. Others can be considered useful to keep; we should mark those as unused.

Codecov Report
Patch coverage: 57.14% and project coverage change: +0.65% :tada:

Comparison is base (812cfc7) 54.20% compared to head (2e89d9c) 54.85%.

:exclamation: Current head 2e89d9c differs from pull request most recent head 236dc63. Consider uploading reports for the commit 236dc63 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #2427      +/-   ##
==========================================
+ Coverage   54.20%   54.85%   +0.65%
==========================================
  Files         115      114       -1
  Lines        9355     9158     -197
==========================================
- Hits         5071     5024      -47
+ Misses       4284     4134     -150

Flag
Coverage Δ

unittests
54.85% <57.14%> (+0.65%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed
Coverage Δ

anyway/globalmaptiles.py
15.06% <ø> (-0.76%)
:arrow_down:

anyway/graphqlSchema.py
0.00% <ø> (ø)

anyway/models.py
88.97% <0.00%> (+0.43%)
:arrow_up:

anyway/parsers/infographics_data_cache_updater.py
35.05% <ø> (+2.91%)
:arrow_up:

anyway/parsers/location_extraction.py
23.13% <ø> (+2.04%)
:arrow_up:

anyway/parsers/news_flash_db_adapter.py
73.68% <ø> (+3.19%)
:arrow_up:

anyway/parsers/registered.py
0.00% <0.00%> (ø)

anyway/parsers/twitter.py
50.00% <ø> (+6.52%)
:arrow_up:

anyway/utilities.py
54.70% <ø> (+0.60%)
:arrow_up:

anyway/widgets/widget.py
85.89% <ø> (+2.36%)
:arrow_up:

... and 4 more

... and 1 file with indirect coverage changes

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

@tkalir @ziv17 what do you think? Maybe some deletions are not good for us and we want to keep some of the functions?


[bug] 'compiled-objects-have-debug-symbols' false positive on mach-o files that have been passed through 'strip'

What did you expect to happen?
Expected compiled-objects-have-debug-symbols check to only find debug symbols if a mach-o binary contains them.
What actually happened?
Over in LightGBM, observed that when upgrading scikit-build-core for a shared library from v0.4.4 to 0.9.3, pydistcheck started raising this on the resulting library lib_lightgbm.dylib.
1. [compiled-objects-have-debug-symbols] Found compiled object containing debug symbols. For details, extract the distribution contents and run 'nm -a "lightgbm/lib/lib_lightgbm.dylib"'.
errors found while checking: 1

But ONLY that macOS library... not the equivalent files on linux (lib_lightgbm.so) or windows (lib_lightgbm.dll).
How can someone else reproduce this problem?
I mention that scikit-build-core version because in that range, scikit-build-core added the ability to strip the binaries it produced.
https://github.com/scikit-build/scikit-build-core/blob/2994db5d993f0cb252dbeebfac7d66677b670ed8/README.md#L278-279
I built that library (lib_lightgbm.dylib) on an M2 mac, in a build driven by scikit-build-core, like this:
git clone \
    --recursive \
    git@github.com:microsoft/LightGBM.git \
    /tmp/lightgbm

cd /tmp/lightgbm
sh build-python.sh bdist_wheel
unzip -d ./tmp ./dist/*.whl
nm ./lightgbm/lib/lib_lightgbm.dylib > o.txt
nm -a ./lightgbm/lib/lib_lightgbm.dylib > a.txt

Then diffed those files. Only saw 1 difference.

The results of nm -a includes this:
0000000005614542 - 00 0000   OPT radr://5614542

It seems that maybe this is added by strip?
I found this repo, https://github.com/nico/lssym, which says
(Compare with the output of `nm lssym` and `dsymutil -s lssym` in both cases.
Note that `strip` adds a symbol that looks like

    radr://5614542    N_STAB 3c    n_sect 000 n_desc 0x0000    n_value 0x5614542

I wonder what that bug is. `nm` doesn't list it because `nm` only lists symbols,
and this is a stabs debug info entry which `nm` only shows if you pass `-a`.)

I strongly suspect that's what's happening here! Not sure what the best fix is though for pydistcheck, will need to think through that.
What version of pydistcheck are you using?
0.6.0
Notes
Thanks @nico for putting up https://github.com/nico/lssym! It was a great clue to help me investigate this!!

Looks like this is a special case that might be possible to ignore safely, because Xcode's strip prefers to keep weak symbols, see: https://x.com/yaakov_h/status/478656504162029568/photo/1
The corresponding Apple Open Source pages have unfortunately been wiped into oblivion:

Looks like this is a special, corner case that might be possible to ignore safely, because Xcode's strip prefers to keep weak symbols like , see: https://x.com/yaakov_h/status/478656504162029568/photo/1
Unfortunately, the corresponding Apple Open Source pages have been wiped into oblivion. I tried

https://opensource.apple.com/source/cctools/cctools-822/misc/strip.c
https://opensource.apple.com/source/cctools/cctools-973.0.1/misc/strip.c.auto.html
https://opensource.apple.com/source/cctools/cctools-751/misc/strip.c.auto.html

and I naïvely thought I could look them up on archival services such as https://archive.is/opensource.apple.com or on the Internet Archive's Wayback Machine, but to no avail – it is apparent that Apple has probably worked aggressively to stop the spread of this knowledge.
It is a remnant of the linker, though, so maybe using alternative linkers such as Zld will avoid this problem.
Even on this page: https://docs.angr.io/projects/cle/en/v9.2.70/_modules/cle/backends/macho/symbol.html, the sentence seems incomplete:

# The addr isn't really an address, but a magic value that is used to indicate that the symbol is

I don't claim any conspiracies here, though. 😃
IDA 7.6 seems to ignore it as well: https://docs.hex-rays.com/release-notes/7_6#file-formats

I managed to find a link that still works: https://archive.is/7voAu

Wow AMAZING investigation!!! Thank you so much for looking into that.
Are you interested in submitting a PR that ignores this specific symbol when nm / llvm-nm are use on mach-o` files here? If not, no worries, I'd be happy to attempt it.
I think it'd involve filtering that out around here:
https://github.com/jameslamb/pydistcheck/blob/85b8af32b87eb8d9def9fe318381a1704be41aba/src/pydistcheck/shared_lib_utils.py#L65-L68
with a code comment pointing back to this issue to explain why

Thank you for the pointer! Yes, I'm interested in contributing and will put together a PR this week :D


Any chance of using hashes rather than random numbers for layer id's?

I'm confused why layers are refered to using random numbers rather than with cryptographic hashes. We already know that using random numbers as IDs lead to security problems at Docker, so why continue using this approach in a new standard?
The only thing that occures to me, is that one might think it possible that two layers of the same image would have the same hash, for example, if a file was repetedly whited out. But in truth this would NEVER happen, as the JSON file, which specifies the layers parent, would be different.

I believe we should just update the language to say the ID MUST be a crypto hash. Would you mind submitting a PR to the location that has this language?

The current text is this:
 Image ID
    Each layer is given an ID upon its creation. It is represented as a hexadecimal encoding of 256 bits, e.g., a9561eb1b190625c9adb5a9513e72c4dedafc1cb2d4c5236c9a6957ec7dfd5a9. Image IDs should be sufficiently random so as to be globally unique. 32 bytes read from /dev/urandom is sufficient for all practical purposes. Alternatively, an image ID may be derived as a cryptographic hash of image contents as the result is considered indistinguishable from random. The choice is left up to implementors.

If I change it to being:
An image ID must be derived as a cryptographic hash of image contents.

That doesn't work, because as I already stated, there can be multiple layer.tar files with the same contents.
I would propose:
The layer ID is derived as a cryptographic hash of the files which define the image passed to an SHA256 hash function in the following order:

 - The unicode encoded string "json".
 - The contents of the json file.
 - The unicode encoded string "layer.tar"
 - The contents of the layer.tar file
 - The unicode encoded string "VERSION".
 - The contents of the VERSION file.

In order to have a proper hash across a directory, it needs to be specified that closely (well, actually, I put it in alphabetic order, but I think it is easier to understand when it is written out in long form.)

Does anyone know the exact specification, including order of meta-data hashing, is for Docker image ids?

Will a traversal order for the filesystem contents be specified for the hash of the layer tar file?

Ah I see this is what you mean about there being mulltiple layer tar files with the same contents.

@vbatts the new serialization doc removes all of the non CAS ids, right? This can be closed, I think.

Correct.


Memory Patching

It would be nice if there were functions to help with patching bytes in memory.

not planned


QC Logic for post assembly quality controls

determine PASS/FAIL of post assembly quality controls using QUAST and BUSCO.

How should we determine what the PASS cutoff is for QUAST results?
My ideas:
Total length of the assembly vs Reference length
GC (%) of the assembly vs Reference GC (%)

I'd expect that the assembly length vs reference length would be the more useful metric, and probably easier to draw sensible thresholds around.


Move the trash can to where it can be seen always

Is your feature request related to a problem? Please describe.
I had a hard time finding the little trash can to delete environments and ended up with many unused ones causing clutter.
I eventually found it off to the right, but I had to scroll to see it. Since my environment variables were long.
Describe the solution you'd like
The trash can could be moved left so it is always visible.

Thanks for reporting. I don't think it is better to be placed at the left. The right feels more appropriate since it's not an action to be promoted unless required. However I understand it might be difficult to locate at the moment, so I've updated it to contain the Delete text and also set the destructive action class on it to be more obvious. Hope that helps.


Add support for If statements

if statements take a variety of forms in CoffeeScript. Here's how I think they should map:
# simple, multi-line
if a
  b

# single-line
b if a

# if-then-else single-line
if a then b else c

# if-then-else multi-line
if a then b
else c

# if-else multi-line
if a
  b
else
  c

# unless
unless a
  b

// simple, multi-line
if (a) {
  b;
}

// single-line
if (a) { b; }

// if-then-else single-line
if (a) { b; } else { c; }

// if-then-else multi-line
if (a) { b; }
else { c; }

// if-else multi-line
if (a) {
  b;
} else {
  c;
}

// unless
if (!a) {
  b;
}

Note that the fully transformed JavaScript is shown, but this transform should only concern itself with adding parentheses, braces, and transforming unless to if. I anticipate there may be issues with this one, especially changing post-if to regular if, due to the MagicString limitation of only allowing modifying a given location once.

With the release of v1.10.1 this is effectively complete. Any specific issues should be filed separately.


cargo build fail on stable compiler

Hi, very cool project! I wanted to try it.
$ cargo add pdf2pwg
$ cd ~/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pdf2pwg-0.2.1
$ cargo build

...
   Compiling pdf2pwg v0.2.1 (/var/home/user/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pdf2pwg-0.2.1)
error[E0554]: `#![feature]` may not be used on the stable release channel
 --> src/lib.rs:1:12
  |
1 | #![feature(slice_as_chunks)]
  |            ^^^^^^^^^^^^^^^

$ rustc --explain E0554
Feature attributes are only allowed on the nightly release channel. Stable or beta compilers will not comply.

Erroneous code example:

#![feature(lang_items)] // error: `#![feature]` may not be used on the
                        //        stable release channel

If you need the feature, make sure to use a nightly release of the compiler (but be warned that the feature may be removed or altered in
the future).

I have changed forming of chunks and removed nightly-dependent code.

I have changed forming of chunks and removed nightly-dependent code.

Awesome!


Visual Fix for DnD5e 3.X

On the new dnd update, the chat card gets the icon and user shown, but this can be reverted by adding a single line on the main.js file after the 174 line
html.querySelector('.message-header').style.display = 'none';

Result:

Sorry, I don't know how to do a pull request, but this is here for anyone who is using this module and wants a little fix. Thanks @jessev14 for the module.

any update soon? :P

Cool, can confirm it works!

Sorry, I don't know how to do a pull request, but this is here for anyone who is using this module and wants a little fix. Thanks @jessev14 for the module.

Sure, why not.  I already have another one in the queue...

Done:  https://github.com/jessev14/health-monitor/pull/19

I don't know when the original author will pull in these pull requests, so in the meantime, if you want to try out the fixes, you can load a preview build here:
Install Module - Manifest URL - https://github.com/kiloforce/health-monitor/releases/latest/download/module.json

I have a new version of Character Monitor coming out that includes Health Monitor. Gimme a week or so.

I have a new version of Character Monitor coming out that includes Health Monitor. Gimme a week or so.

👍


⚠ Bofrost.be has degraded performance

In ea10a13, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 930 ms

Resolved: Bofrost.be performance has improved in f10dd40.


Hid the recaptcha badge and added text the login and create page.

Overview
Solves issue #189
Demo

Approved the changes made ... Anand Jois<EMAIL_ADDRESS>


use openssl 1.0.2 to be able to build qca

see https://github.com/opengisch/OSGeo4A/pull/25

thanks @PeterPetrik do you know if there is an upstream issue in qca?

no idea where they have issue tracker, but last release is 20month old and we use it :(


How do I use the VS in RosOnWindow

I want to know the method of using VS in RosOnWindows. I want to know how to edit and compile the code by using VS and add the code compiled by VS to ROS. Thanks very much.

Cross-post of How do I use the VS in RosOnWindows on ROS Answers.

(Disclaimer: I am not related in any way to the ROSOnWindows project, so this is not an official answer).
I have successfully used the C++ libraries installed by ROSOnWindows's Chocolatey packages in a plain CMake project simply by running the "C:\opt\ros\melodic\x64\setup.bat" script in a terminal and then by launching CMake from that terminal. This was possible because the setup scripts sets the CMAKE_PREFIX_PATH environmental variable that is used by CMake's find_packagecommand to find its dependencies, including the ROS's libraries. For an example of using ROS's libraries from a plain CMake project, see https://github.com/gerkey/ros1_external_use.
Once you have a plain CMake project that use ROS's libraries, you can easily generate a Visual Studio solution for it. For more details on this, see the related CGold section.
Note that this is a bit different from the classical strategy of using catkin to build ROS-dependent code. I personally have no experience of using catkin to generate Visual Studio solutions.
Note: the ROSOnWindows Chocolatey repository is currently not providing Debug libraries binaries, so in general you cannot use the Debug Visual Studio configuration to build code, for more info see https://github.com/ms-iot/ROSOnWindows/issues/31.

We are working on releasing a ROS vscode extension which supports windows. in the mean time, you can build it yourself from here: https://github.com/ms-iot/vscode-ros


cip-19: Review status

Change status to review

Or is it In Review? Also, where is the list of all the possible statuses?

Review is correct, in CIP-1, https://github.com/celestiaorg/CIPs/blob/main/cips/cip-1.md#cip-process

Found it, CIP-1

While CIP-1 doesn't mention anything about how long a CIP remains in Draft before going to Review, should this remain in Draft longer than just a few hours?

Actually, @jcstein, let's keep it as a draft; I will add one more container and ID type for the eds.

While CIP-1 doesn't mention anything about how long a CIP remains in Draft before going to Review, should this remain in Draft longer than just a few hours? cc @YazzyYaz @rootulp @ebuchman

IMO there doesn't need to be a minimum time enforced on how long a CIP is in Draft before moving to Review.

Actually, @jcstein, let's keep it as a draft; I will add one more container and ID type for the eds.

Sounds good. Should this PR be closed?

We may, but the transition to review will happen anyway, and it's also the case that the change will be strictly additive and won't change the existing doc, so it still makes sense to keep what exist in the review stage


Let the IpExtractor work on an alternative header name

IpExtractor does this:
    public TokenCredentials extract(WebContext context) {
        String ip = context.getRemoteAddr();
        return ip == null?null:new TokenCredentials(ip, this.clientName);
    }

Add support so a header can be used instead, which might be useful for proxying scenarios.

I think we might need a 1.8.10 or something for this patch as well.

Yes, it makes sense and yes, we could have it for 1.8.x stream as well.

@mmoayyed see: https://github.com/pac4j/pac4j/pull/679 for master and: https://github.com/pac4j/pac4j/pull/680 for the 1.8.x branch


Add Message.edits

Message[] for consistency :eyes:

Yep, type should be Message[].

Didn't know about that convention. Fixed! :D


Add variables doc

This is missing specific details on which variables are sent to OC, whether or not custom PVA variables are sent to OC, and how to use those variables in OC.

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

ID: 3427b1fd-1a36-9e75-a3e6-d1850fdb4631
Version Independent ID: 5b4e98a4-5798-f597-55d4-9f694c981682
Content: Configure hand-off to Dynamics 365 Customer Service - Power Virtual Agents
Content Source: power-virtual-agents/configuration-hand-off-omnichannel.md
Service: power-virtual-agents
GitHub Login: @iaanw
Microsoft Alias: iawilt

@anbhar Thanks for your question! The first two pieces of information you're looking for are currently documented on the top of the omnichannel article:

When you hand off a conversation, you share the full history of the conversation (the context) as well as all user-defined variables. This allows your omnichannel service to route incoming escalations to the right live agent queue and enables engaging live agents to review context from the prior conversation and resume the conversation.

For more information about hand off, and how to use hand-off within a bot conversation, see the Using Transfer to agent node topic.

However the last piece is indeed missing, but it will be added in a coming doc update. In the meantime, please refer to https://docs.microsoft.com/dynamics365/customer-service/context-variables-for-bot


JavaScript Intellisense not working

We write JS files for NetSuite, and as such have an api file we include in our projects to provide some intellisense. This works in other IDEs:
Small snipet from api file:
/**
 * Return a new instance of nlobjRequest used for scripting web requests in Suitelets
 *
 * @classDescription Accessor to Http request data made available to Suitelets
 * @return {nlobjRequest}
 * @constructor
 */
function nlobjRequest( ) { return new nlobjRequest(); }

/**
 * return the value of a request parameter.
 *
 * @param {string} name parameter name
 * @return {string}
 * @method
 * @memberOf nlobjRequest
 *
 * @since 2008.2
 */
nlobjRequest.prototype.getParameter = function( name ) { return new String(); }

In our actual script, the parameter types remain as 'any'
/**
 * @param {nlobjRequest} request
 * @param {nlobjResponse} response
 */
function run(request, response)
{
    var form = new nlobjForm();

}

Does your workspace contain a jsconfig.json file? If not try creating one with the contents:
{
}

This should ensure that all js files in your workspace are treated as part of the same javascript project

Yes, it does in the root folder.
<EMAIL_ADDRESS>Adam Parker, MCSA
Member, Director of Technology
Kraft Enterprise Systems, LLC
10 Cadillac Drive, Suite 380
Brentwood, TN  37027
(615) 542-1558
aparker<EMAIL_ADDRESS>Sign up for timely news updates from KraftCPAs herehttp://www.kraftcpas.com/Newsletter_Email_List.php!
From: Matt Bierner<EMAIL_ADDRESS>Sent: Thursday, July 6, 2017 4:04 PM
To: Microsoft/vscode<EMAIL_ADDRESS>Cc: Adam Parker<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode] JavaScript Intellisense not working (#30205)
Does your workspace contain a jsconfig.jsonhttps://code.visualstudio.com/docs/languages/javascript#_location-of-jsconfigjson file? If not try creating one with the contents:
{
}
This should ensure that all js files in your workspace are treated as part of the same javascript project
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/30205#issuecomment-313518708, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AckfXMSvjOy7FIV32PKTaaWt6ntNzG-vks5sLUvMgaJpZM4OQAO9.

Can you please try uploading the image again. Looks like something went wrong with the email reply
Also:

What are the paths to two files in your example?
Does either file use require or import or export anywhere? This will make it into a module which will not share globals with other files

Thanks

sorry, not sure why screenshot didn’t’ send. Here is the text from my jsconfig.json
{
"compilerOptions": {
"target": "ES5"
}
}
Script file is in the root, api file is in a subfolder called ‘api’. No require, import, or export
Adam Parker, MCSA
Member, Director of Technology
Kraft Enterprise Systems, LLC
10 Cadillac Drive, Suite 380
Brentwood, TN  37027
(615) 542-1558
aparker<EMAIL_ADDRESS>Sign up for timely news updates from KraftCPAs herehttp://www.kraftcpas.com/Newsletter_Email_List.php!
From: Matt Bierner<EMAIL_ADDRESS>Sent: Thursday, July 6, 2017 4:33 PM
To: Microsoft/vscode<EMAIL_ADDRESS>Cc: Adam Parker<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode] JavaScript Intellisense not working (#30205)
Can you please try uploading the image again. Looks like something went wrong with the email reply
Also:

What are the paths to two files in your example?
Does either file use require or import or export anywhere? This will make it into a module which will not share globals with other files

Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/30205#issuecomment-313525500, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AckfXGPLWpuTkMs-BXJnhzNAB3lbRK3Hks5sLVKngaJpZM4OQAO9.

Can you please try the current insiders build (or vscode 1.14 once it comes out early next week): https://code.visualstudio.com/insiders
I see this working properly in the insiders builds but not in VSCode 1.13.

New version fixed this issue, thanks!
Adam Parker, MCSA
Member, Director of Technology
Kraft Enterprise Systems, LLC
10 Cadillac Drive, Suite 380
Brentwood, TN  37027
(615) 542-1558
aparker<EMAIL_ADDRESS>Sign up for timely news updates from KraftCPAs herehttp://www.kraftcpas.com/Newsletter_Email_List.php!
From: Matt Bierner<EMAIL_ADDRESS>Sent: Friday, July 7, 2017 1:40 PM
To: Microsoft/vscode<EMAIL_ADDRESS>Cc: Adam Parker<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode] JavaScript Intellisense not working (#30205)
Can you please try the current insiders build (or vscode 1.14 once it comes out early next week): https://code.visualstudio.com/insiders
I see this working properly in the insiders builds but not in VSCode 1.13.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vscode/issues/30205#issuecomment-313761273, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AckfXHBGcPbdwLOnnK0N4DSa2b2R9PUoks5sLnuUgaJpZM4OQAO9.


Being able to select notify subscribers when issue is posted

In some occasions it would be useful to be able to choose which subscribers we can send notifications of the updates of issues and maintenances.

You appear to have submitted a pull request rather than a normal issue. Please can you re-add as an issue.


update fake and suggest to use paket for dotnet-fake clitool versioning

Updates fake and fake packages to rc001
Add dotnet-fake to clitools to manage the version with paket
replace dotnet-fake.fsproj with build.proj (basically the same but extended in a way such that you can run dotnet build build.proj)

Thank you :)


esy build fail on building skia (macos)

Seems like someone was having a similar problem, but I don't know how much is applicable to me. They were using windows and I am using macOS Big Sur version 11.5.2.
Using esy version 0.6.12, when I run esy build I get this error log:
info esy build 0.6.12 (using package.json)
info building esy-skia@github:revery-ui/esy-skia#91c98f6@d41d8cd9
error: build failed with exit code: 1
  build log:
    # esy-build-package: building: esy-skia@github:revery-ui/esy-skia#91c98f6
    # esy-build-package: pwd: /Users/duncanbritt/.esy/3/b/esy_skia-c3eadd32
    # esy-build-package: running: 'bash' './esy/build.sh' 'darwin' '/Users/duncanbritt/.esy/3____________________________________________________________/i/esy_libjpeg_turbo-dc3b4679'
    fatal: repository 'https://skia.googlesource.com/external/github.com/Tencent/rapidjson.git/' not found
    buildtools                           @ 505de88083136eefd056e5ee4ca0f01fe9b33de8
    common                               @ 9737551d7a52c3db3262db5856e6bcd62c462b92
    third_party/externals/angle2         @ b001528ffa00e7c15a5002124f707570e59a5697
    third_party/externals/dng_sdk        @ 96443b262250c390b0caefbf3eed8463ba35ecae
    third_party/externals/expat          @ android-6.0.1_r55
    third_party/externals/freetype       @ fa6da7bf6dcbcfa22d2464259ad1cccee3233189
    third_party/externals/googletest     @ dd43b9998e9a44a579a7aba6c1309407d1a5ed95
    third_party/externals/harfbuzz       @ 1.4.2
    third_party/externals/icu            @ ec9c1133693148470ffe2e5e53576998e3650c1d
    third_party/externals/imgui          @ 6384eee34f08cb7eab8d835043e1738e4adcdf75
    third_party/externals/jsoncpp        @ 1.0.0
    third_party/externals/libjpeg-turbo  @ 1.5.3
    third_party/externals/libpng         @ v1.6.33
    third_party/externals/libwebp        @ v0.6.1
    third_party/externals/lua            @ v5-3-4
    third_party/externals/microhttpd     @ 748945ec6f1c67b7efc934ab0808e1d32f2fb98d
    third_party/externals/piex           @ bb217acdca1cc0c16b704669dd6f91a1b509c406
    Traceback (most recent call last):
      File "tools/git-sync-deps", line 254, in <module>
        exit(main(sys.argv[1:]))
      File "tools/git-sync-deps", line 246, in main
        git_sync_deps(deps_file_path, argv, verbose)
      File "tools/git-sync-deps", line 218, in git_sync_deps
        git_checkout_to_directory(*args)
      File "tools/git-sync-deps", line 132, in git_checkout_to_directory
        [git, 'clone', '--quiet', repo, directory])
      File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 190, in check_call
        raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['git', 'clone', '--quiet', 'https://skia.googlesource.com/external/github.com/Tencent/rapidjson.git', 'third_party/externals/rapidjson']' returned non-zero exit status 128
    llvm toolset-7.0 does not need to be manually activated
    ./esy/build.sh: line 44: bin/gn: No such file or directory
    error: command failed: 'bash' './esy/build.sh' 'darwin' '/Users/duncanbritt/.esy/3____________________________________________________________/i/esy_libjpeg_turbo-dc3b4679' (exited with 255)
    esy-build-package: exiting with errors above...

  building esy-skia@github:revery-ui/esy-skia#91c98f6
esy: exiting due to errors above

Any suggestions for me would be greatly appreciated.

This was fixed a while ago in esy-skia. But as I don't have the power to make releases you'll have to set up a manual resolution to esy-skia's master branch.

This was fixed a while ago in esy-skia. But as I don't have the power to make releases you'll have to set up a manual resolution to esy-skia's master branch.

Pardon my ignorance: I don't know what it means to set up a manual resolution or how to do it. So I was looking through the directory and found esy.lock/index.json and in it there seems to be a reference to esy-skia that looks like this:
    "esy-skia@github:revery-ui/esy-skia#91c98f6@d41d8cd9": {
      "id": "esy-skia@github:revery-ui/esy-skia#91c98f6@d41d8cd9",
      "name": "esy-skia",
      "version": "github:revery-ui/esy-skia#91c98f6",
      "source": {
        "type": "install",
        "source": [ "github:revery-ui/esy-skia#91c98f6" ]
      },
      "overrides": [],
      "dependencies": [
        "esy-libjpeg-turbo@github:revery-ui/libjpeg-turbo#dbb3dd5@d41d8cd9",
        "@esy-cross/ninja-build@1.8.2001@d41d8cd9"
      ],
      "devDependencies": []
    },

Would it be a simple matter of editing this file in some way, and running esy install and esy build, or is it something else entirely?

You might get away with that for a short while, but it would quickly get overwritten once you add or update a package. The right way is to add a resolution to your projects package.json. See https://esy.sh/docs/en/using-repo-sources-workflow.html#with-esy-packages

This problem is also in Linux:
$ esy build
info esy build 0.7.2 (using package.json)
info building esy-skia@github:revery-ui/esy-skia#91c98f6@d41d8cd9
error: build failed with exit code: 1
  build log:
    # esy-build-package: building: esy-skia@github:revery-ui/esy-skia#91c98f6
    # esy-build-package: pwd: /home/enter_user_home_name/.esy/3/b/esy_skia-1c806f78
    # esy-build-package: running: 'bash' './esy/build.sh' 'linux' '/home/enter_user_home_name/.esy/3_________________________________________________________________/i/esy_libjpeg_turbo-e4385a3b'
    fatal: repository 'https://skia.googlesource.com/external/github.com/Tencent/rapidjson.git/' not found
    buildtools                           @ 505de88083136eefd056e5ee4ca0f01fe9b33de8
    common                               @ 9737551d7a52c3db3262db5856e6bcd62c462b92
    third_party/externals/angle2         @ b001528ffa00e7c15a5002124f707570e59a5697
    third_party/externals/dng_sdk        @ 96443b262250c390b0caefbf3eed8463ba35ecae
    third_party/externals/expat          @ android-6.0.1_r55
    third_party/externals/freetype       @ fa6da7bf6dcbcfa22d2464259ad1cccee3233189
    third_party/externals/googletest     @ dd43b9998e9a44a579a7aba6c1309407d1a5ed95
    third_party/externals/harfbuzz       @ 1.4.2
    third_party/externals/icu            @ ec9c1133693148470ffe2e5e53576998e3650c1d
    third_party/externals/imgui          @ 6384eee34f08cb7eab8d835043e1738e4adcdf75
    third_party/externals/jsoncpp        @ 1.0.0
    third_party/externals/libjpeg-turbo  @ 1.5.3
    third_party/externals/libpng         @ v1.6.33
    third_party/externals/libwebp        @ v0.6.1
    third_party/externals/lua            @ v5-3-4
    third_party/externals/microhttpd     @ 748945ec6f1c67b7efc934ab0808e1d32f2fb98d
    third_party/externals/piex           @ bb217acdca1cc0c16b704669dd6f91a1b509c406
    Traceback (most recent call last):
      File "tools/git-sync-deps", line 254, in <module>
        exit(main(sys.argv[1:]))
      File "tools/git-sync-deps", line 246, in main
        git_sync_deps(deps_file_path, argv, verbose)
      File "tools/git-sync-deps", line 218, in git_sync_deps
        git_checkout_to_directory(*args)
      File "tools/git-sync-deps", line 132, in git_checkout_to_directory
        [git, 'clone', '--quiet', repo, directory])
      File "/usr/lib64/python2.7/subprocess.py", line 190, in check_call
        raise CalledProcessError(retcode, cmd)
    subprocess.CalledProcessError: Command '['git', 'clone', '--quiet', 'https://skia.googlesource.com/external/github.com/Tencent/rapidjson.git', 'third_party/externals/rapidjson']' returned non-zero exit status 128
    llvm toolset-7.0 does not need to be manually activated
    ./esy/build.sh: line 44: bin/gn: No such file or directory
    error: command failed: 'bash' './esy/build.sh' 'linux' '/home/enter_user_home_name/.esy/3_________________________________________________________________/i/esy_libjpeg_turbo-e4385a3b' (exited with 255)
    esy-build-package: exiting with errors above...

  building esy-skia@github:revery-ui/esy-skia#91c98f6
esy: exiting due to errors above

And, @glennsl, your link is broken


[TIR] Allow symbolic bounds in IndexMap analysis

This PR adds the bounds of shape variables to the arithmetic analyzer so that it is possible to simplify certain expressions.

@LeiWang1999 what you met seems is related to the index bound(i32 i64 related), which is a bit unfortunate but as we transition to enable i64 it is necessary.
index_map = IndexMap.from_func(ldmatrix_trans_permutation_16x16_32x8_16x16, index_dtype="int32")

if you add index_dtype="int32", given your loops are in i32, the inverse map seems to be OK. if we don't do that, there will be cast as a result we cannot make the inverse

Thanks tq, I found that under index_map = IndexMap.from_func(ldmatrix_trans_permutation_16x16_32x8_16x16, index_dtype="int32") though, the inverse map is not ok, the output is:
========================inject transform=============================
# from tvm.script import tir as T

@T.prim_func
def main(A: T.Buffer((16, 16), "float16"), B: T.Buffer((16, 16), "float16")):
    T.func_attr({"tir.noalias": T.bool(True)})
    # with T.block("root"):
    for i, j in T.grid(16, 16):
        with T.block("B"):
            vi, vj = T.axis.remap("SS", [i, j])
            T.reads(B[(vi * 2 + vj // 8) // 16 * 8 + (vi * 2 + vj // 8) % 8, (vi * 2 + vj // 8) % 16 // 8 * 8 + vj % 8])
            T.writes(A[vi, vj])
            A[vi, vj] = B[(vi * 2 + vj // 8) // 16 * 8 + (vi * 2 + vj // 8) % 8, (vi * 2 + vj // 8) % 16 // 8 * 8 + vj % 8]
========================inverse inject transform=============================
# from tvm.script import tir as T

@T.prim_func
def main(A: T.Buffer((16, 16), "float16"), B: T.Buffer((16, 16), "float16")):
    T.func_attr({"tir.noalias": T.bool(True)})
    # with T.block("root"):
    for i, j in T.grid(16, 16):yu
        with T.block("B"):
            vi, vj = T.axis.remap("SS", [i, j])
            T.reads(B[(vi * 2 + vj // 8) // 2, vj % 16])
            T.writes(A[vi, vj])
            A[vi, vj] = B[(vi * 2 + vj // 8) // 2, vj % 16]

After applying the inverse_map to the map, the layout should remain consistent with its state prior to the transformation.
Before this pull request, the code was functioning as expected.
========================inject transform=============================
# from tvm.script import tir as T
@T.prim_func
def func(A: T.Buffer[(16, 16), "float16"], B: T.Buffer[(16, 16), "float16"]):
    # function attr dict
    T.func_attr({"tir.noalias": True, "global_symbol": "main"})
    # body
    # with T.block("root")
    for i, j in T.grid(16, 16):
        with T.block("B"):
            vi, vj = T.axis.remap("SS", [i, j])
            T.reads(B[vi // 8 * 8 + vi % 4 * 2 + vj // 8, vi % 8 // 4 * 8 + vj % 8])
            T.writes(A[vi, vj])
            A[vi, vj] = B[vi // 8 * 8 + vi % 4 * 2 + vj // 8, vi % 8 // 4 * 8 + vj % 8]

========================inverse inject transform=============================
# from tvm.script import tir as T
@T.prim_func
def func(A: T.Buffer[(16, 16), "float16"], B: T.Buffer[(16, 16), "float16"]):
    # function attr dict
    T.func_attr({"tir.noalias": True, "global_symbol": "main"})
    # body
    # with T.block("root")
    for i, j in T.grid(16, 16):
        with T.block("B"):
            vi, vj = T.axis.remap("SS", [i, j])
            T.reads(B[vi, vj])
            T.writes(A[vi, vj])
            A[vi, vj] = B[vi, vj]

I'll take a look tomorrow.

insert (*indices).MutateByApply(         [&](const PrimExpr& e) { return SimplifyNonTrivialExpr(e, analyzer_); });
before  https://github.com/apache/tvm/blob/f36a093c20963a3827be0cf4fd5e15a0cac69f31/src/tir/schedule/primitive/layout_transformation.cc#L806-L807
to simplify the indice works for me. looks like it's removed by this commit, wonder if there’s a specific rationale behind it.

Previously, we would like to have option that preserves trivial simplify (simplifies iterator of range 1 to zero).
See implementation here https://github.com/apache/tvm/blob/main/src/arith/ir_mutator_with_analyzer.cc#L52
Running SimplifyNonTrivialExpr  before means we cannot have the non-trivial option. I think it might be fine to update  IterMapSimplifyWithContext  to includeSimplifyNonTrivialExpr but still preserve the non-trivial option.
I thin the best approach would be to enhance IterMapSimplify to handle this case, since this involves affine map transformation and the best case we don;t rely on other simplifier.
We can can see (vi * 2 + vj // 8) // 16 should be readily transformed to (vi // 8 + vj // 128), my suspect is that if you apply IterMap simplify again on the result it should also work (maybe some intermediate values did not further simplifes). Good to dig a bit what happens in this case without relying on other simplfier(so it have potential to work for future symbolic case)


Update README to list ds-deadlines.github.io

Hi,
I've updated the README file to include another fork of the project: https://github.com/ds-deadlines/ds-deadlines.github.io
ds-deadlines lists deadlines of conferences on distributed systems, event-based systems, performance, and software engineering.

Thanks for the contribution.


Legend for rasters

Add the possibility to add a legend to each raster.
Probably using the existing placeholder for legends that is not being used currently for rasters.
Another idea would it be to create some kind of json definition for legends that could be used by the user to define the legend similarly as it can use cartocss for defining style.

Latest carto synch introduced the ability to create custom legends. This issue should focus on enabling that feature for raster layers.
Meanwhile as workaround legends can be introduced for maps with rasters just by adding a new layer with a transparent point and creating the legend into that layer. For example:


Auto load all chords on transpose

Load all chords to db on transpose clicked (if not exist already)

Done


Fix collect time metric in CoalesceBatches

fixes https://github.com/NVIDIA/spark-rapids/issues/658
GpuCoalesceBatches has a collectTime metric that measures the time a task spent waiting to collect all the input batches. This metric can be incorrect when a task becomes blocked by the GPU semaphore trying to access the GPU. GpuCoalesceBatches only starts the collectTime metric in the next() call, but the GPU semphore may try to be acquired by an upstream node when GpuCoalesceBatches's input iterator's hasNext() call is invoked. Any time spent in the first invocation of the input iterator hasNext() method is not tracked, leading to large discrepancies in time as reported in #622.
Moved the start of this into hasNext which was most straight forward.
Note also needed to move the totalTime metric.
attached is screenshot of the fix where GpuCoalesceBatches properly shows collect batch time and total time very close to the GpuShuffledHashJoin build time.  Without the fix the times are very different.
After Fix:

Before Fix:

build


Can't start node on Win 10 Home

Look at the error - looks like an issue with spaces in 'program files' path...


python apds-9930 library problem on raspberry pi 3

I have problem when i use python apds-9930 library i use your test program on github but i see this error on python shell
Traceback (most recent call last):
  File "/home/pi/apds-9930v1.py", line 10, in <module>
    a = APDS9930(busno)
  File "build/bdist.linux-armv7l/egg/apds9930/__init__.py", line 107, in __init__
    raise SensorError("Device ID not recognized: {0}".format(hex(self.id)))
SensorError: Device ID not recognized: 0x29

i use raspberry pi 3
i think you can help me
and i have a question can use this library in python 3
thank you

This is the wrong repo 🤦♂🤦♂🤦♂🤦♂
https://github.com/Depaulicious/python-apds9930

Anyway, you're either using the wrong device or have connection issues. If the value (0x29) is always the same, you're definitely using a different model.
The datasheet clearly states that the device should identify itself as 0x39:

If you're 10000000% sure you're using a 9930, you can try installing the Python module in development mode:
git clone https://github.com/Depaulicious/python-apds9930
cd python-apds9930
sudo pip install -e .

edit values.py and add 0x29 to APDS9930_IDs at line 252.
You should then test ALL the features and, if they work, report it to me so that I can add this unknown ID to both Arduino and Python libraries.

thank you it's worked for me but only print Proximity and Ambient light value is 0

You need to enable the proximity sensor:
https://apds-9930-python-bindings.readthedocs.io/en/latest/#apds9930.APDS9930.enable_proximity_sensor
If it doesn't work even after enabling it you DON'T HAVE an APDS-9930. You have another sensor. That happens way too often on Chinese websites that put the wrong description to products. When I got my APDS-9930 I was actually expecting an APDS-9960 but they sent the wrong one.
Make sure that it works and that you get meaningful values and I'll consider adding the ID you provided to the libraries.

I think you're right because when i use this sensor on arduino Ambient sensor value is 0
i have problem with python 3 when i use python 3 i see this error
Traceback (most recent call last):
File "/home/pi/apds-9930v2.py", line 4, in
from apds9930 import APDS9930
File "/usr/local/lib/python3.4/dist-packages/apds9930/init.py", line 584
print "   REGISTER       DECIMAL  HEXADECIMAL     BINARY"
^
SyntaxError: Missing parentheses in call to 'print'

@amir11111111 The library was written years ago without Python 3 compatibility in mind. PRs are accepted if you're willing to port it to py3.

How can I do that?

https://docs.python.org/3/howto/pyporting.html


Cannot update to the latest version 1.0.0-m6

I tried to update to the latest version of mvnd but with no success
asdf install mvnd latest
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     9  100     9    0     0     30      0 --:--:-- --:--:-- --:--:--    30
[/tmp/mvnd_D0GHtsr/mvnd-1.0-m6.zip]
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of /tmp/mvnd_D0GHtsr/mvnd-1.0-m6.zip or
        /tmp/mvnd_D0GHtsr/mvnd-1.0-m6.zip.zip, and cannot find /tmp/mvnd_D0GHtsr/mvnd-1.0-m6.zip.ZIP, period.
asdf-mvnd error:  failed to extract mvnd archive

It looks like they cannot make up their minds about the naming schema of their artifacts. 🙄
maven-mvnd-0.9.0-darwin-aarch64.zip
maven-mvnd-1.0.0-m4-darwin-aarch64.zip
maven-mvnd-1.0-m6-m39-darwin-aarch64.zip
maven-mvnd-1.0-m6-m40-darwin-aarch64.zip

Will there be a fix to this issue? It has been open for half a year. Plenty of other asdf plugins have inconsistent naming conventions; just look at java or python. I would rather simply have the full list, warts and all, than worry about getting a nice semver output.


[DOC] Revise step 2 input code example

Description
Corrects step input code example
Issues Resolved
NA
Checklist

[X] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@heemin32 Will you approve this PR? I can merge it once it's approved. Thank you :)


python3Package.celery-singleton: enable redis tests

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 259045 run on x86_64-linux 1

4 packages built:

python310Packages.celery-singleton
python310Packages.celery-singleton.dist
python311Packages.celery-singleton
python311Packages.celery-singleton.dist

Result of nixpkgs-review pr 259045 run on x86_64-linux 1

4 packages built:

python310Packages.celery-singleton
python310Packages.celery-singleton.dist
python311Packages.celery-singleton
python311Packages.celery-singleton.dist

@natsukium fixed

@ofborg build python311Package.celery-singleton

@ofborg build python311Packages.celery-singleton


wrong text in distribution section in releases tab

Releases alpha.7, alpha.8 and alpha.9 mention asciidoctor-pdf instead of asciidoctor-epub in the distribuion name.
see: https://github.com/asciidoctor/asciidoctor-epub3/releases/tag/v1.5.0.alpha.9

Thanks! All fixed.
(The link to the full diff was also wrong).


Feature: add additional fields for PEM output

Currently, exporting the generated Key object in PEM format supports the least fields by default.

func (k *Key) PEM() (string, error)

For the future usage (such as ECDH support, #37), PEM key may require additional fields. Context or protocol versions for example.
- func (k *Key) PEM() (string, error)
+ func (k *Key) PEM[T string|int](optField ...[string]T) (string, error)

We need to be careful implementing this.
Including custom fields (headers) to PEM is easy, but reading the PEM file and generate a new Key object will not include those customized fields.


qc_metrics update

Following on discussion from #316, I've renamed a number of arguments and metrics. Additionally I've optimized a bit for memory usage.
Changes to naming can be summarized as follows:

current
proposed

total_features_by_{expr_values}
n_{var_type}_by_{expr_type}

total_{expr_values}
total_{expr_type}

pct_{expr_values}_in_top_{n}_features
pct_{expr_type}_in_top_{n}_{var_type}

total_{expr_values}_{feature_control}
total_{expr_type}_{qc_var}

pct_{expr_values}_{feature_control}
pct_{expr_type}_{qc_var}

total_{expr_values}
total_{expr_type}

mean_{expr_values}
mean_{expr_type}

n_cells_by_{expr_values}
n_cells_by_{expr_type}

pct_dropout_by_{expr_values}
pct_dropout_by_{expr_type}

I went with qc_vars over control_vars on the recommendation of a lab mate, since they are presumably variables which are important for quality control, but were not necessarily controlled.

This is very great! :smile:

PS: Don't worry about the tutorial, I'll move that into the Scanpy docs without images soon and update it there. Thank you!


Using multiple Placeholder on one form with the same name leads to error

Package
filament/forms
Package Version
v2.12.7
Laravel Version
v9.12.2
Livewire Version
v2.10.5
PHP Version
PHP 8.1.4
Bug description
When the Placeholder element is used several times in the same form it is not possible to not assign it a name, therefore leaving it with Placeholder::make('').
Doing this throws an error:
SQLSTATE[HY000]: General error: 1364 Field 'title' doesn't have a default value

As Placeholders are listed under "Layout" it would be good to have the option simply not naming them but including a content to be displayed. By that you have a lot more possibilities to add specific content that helps to explain forms.
Steps to reproduce

Create a form
Place mutliple Placeholder::make('') in it
Submit form

Example for an unnamed Placeholder:
Placeholder::make('')
                    ->content(new HTMLString('
General Data

BlablablablaBlablabla
')),

Relevant log output
SQLSTATE[HY000]: General error: 1364 Field 'title' doesn't have a default value

Yeah this is deliberate, fields must have a unique name. If you'd like to disable the label, use ->disableLabel()

Thank you, I did not know about this option - now, it'S one of my favourites!


podman: 3.1.1 -> 3.1.2

https://github.com/containers/podman/releases/tag/v3.1.2

Motivation for this change
Things done

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

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

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

Result of nixpkgs-review pr 120110 at bde37653 run on aarch64-linux 1

2 packages built successfully:

podman
podman-unwrapped

1 suggestion:

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/applications/virtualization/podman/default.nix:30:5:
   |
30 |     ./remove-unconfigured-runtime-warn.patch
   |     ^


Change eo:cloud_cover type from integer to number

Change eo:cloud_cover type from integer to number as proposed by @philvarner originally in PR #261.
Fixes #265

@m-mohr thanks for putting the change in!


new feature: sending POI to the vehicle

The app and web interface offer the option to send a POI (Point Of Interest) to the vehicle. This pull request will add this feature to the library.
For testing there is a new CLI command available:
$ bimmerconnected sendpoi -h
usage: bimmerconnected sendpoi [-h]
                               username password
                               {north_america,china,rest_of_world} vin
                               latitude longitude [name]

send a point of interest to the vehicle

positional arguments:
  username              Connected Drive user name
  password              Connected Drive password
  {north_america,china,rest_of_world}
                        Region of the Connected Drive account
  vin                   vehicle identification number
  latitude              latitude of the POI
  longitude             longitude of the POI
  name                  (optional) name of the POI

optional arguments:
  -h, --help            show this help message and exit

Sending to the server seems to be working, need to check what really arrives in the vehicle.

Is possible with this library? A example, please.

Is possible with this library? A example, please.

Until this is merged you'll need the sendpoi branch with the above cli arguments. Just give latitude and longitude as decimals.

I have tested this change PR with my '17 i3 with Rex. POI can be sent to the car and are received properly as messages. The "name" parameter does not work -- the POI in the messages list on the dash display is nameless, so the user must look thru the messages one by one if there are more. But coordinates do come through.


feat: Added GamepadState that can be updated

Usage:
final gamepads = await Gamepads.listGamepads();
final gamepad = gamepads.first;

// Now, at any point, you can check gamepad
print(gamepad.state.buttonInputs);
print(gamepad.state.analogInputs);

// When you're done with the gamepad, call dispose:
await gamepad.dispose();

Was not able to test on Windows due to some long compiler errors (see my message here) but will hopefully be able to test on Linux later this week

The class looks good, but I bit strange that the user has to update it themselves?

Updated the API, see the new example. I had to pass an instance of the plugin to the GamepadController constructor to automatically subscribe, but now you check state and call dispose

Done, thanks for the quick review


Address validation?

Hi. I need to verify that an address that comes from user input is valid. I'm looking at the method AddressFactory::isValidAddress, and it looks like it only checks for the first character of an address, but I understand that addresses include a checksum to verify their own validity, Is there anything that will do that validation? thanks.

https://github.com/Bit-Wasp/bitcoin-php/blob/master/src/Address/AddressFactory.php#L85
That function is fine to use for validation - it calls Base58::fromString, which calls Base58::decodeCheck which does checksum part.

Ah, I missed that, thanks!


Zabbix 5.x

Hi
Any chance that you might consider updating it for 5.x?
Regards
Per

Hi,
Probably not.
Regards,
Stevenes Donato
Em sex., 26 de mar. de 2021 às 07:40, pqvindesland @.***>
escreveu:

Hi
Any chance that you might consider updating it for 5.x?
Regards
Per
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/stdonato/zabdash/issues/13, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2RUTNKVA42REASVYPLATTTFRXB5ANCNFSM4Z3HSB5A
.


[bug] Syncing without fast-sync checkpoints returns an error

I receive the following error when attempting to sync from scratch, using the --without-checkpoints flag.   When were minimum fees applied? 1.0 seems awfully high.  If fees lower were allowed prior to a certain height, that needs added to tx verification it looks like.
 DEBUG   transaction 0e7ea5c090b4f85ef54c6f3e17afb9b618dbb7a00cfaf8a93a39219ff045733e came in processObjects
 ERROR   [Core] Transaction fee is not enough: 0.01000000, minimum fee: 1.00000000

As a result of this, when that flag is turned on, I am unable to sync past block 6875.

See here: https://github.com/monero-project/monero/pull/5547 Looks like they're not willing to patch this one, either. So whether something is done about it.... really up to you a decision.

this will not be the easiest fix, as some analytics will be needed to determine at what point https://github.com/qwertycoin-org/qwertycoin/commit/0795bd0220301fc89b5520ad7f715d09ab8013fe this change in minimum fees took effect.  It was a effectively a hardforking change, but was not treated as such. So, restrospectively, we need to figure out when the most recent transaction with a fee below this amount took place.

Easiest move is to change the fee back to the previous lower fee within the next PR?

@who-biz this should fix the --without-checkpoints problem. I've added the update height for the minimum fee.

awesome. @nnian closing as resolved, then.


perf update -> css streaming

Enabling the streaming of css files handled by browsersync.
Will look through the list of changed file and if only css or scss file was changed, then all css files will be internally reloaded per stream by browsersync. If some other file type is found amongst the changed one - a standard  reload will occur.
It works nicely with scss, when a separate task compiles a concat file containing all of the styles and a normal watch will only find the scss files, as they are the ones lying in the project scope.
Note that component scoped css files will not be covered by this as they are loaded by angular directly.
Addresses #804.

Looks great! I left a small comment for consistency.

Thanks for the comment!
Noted.


[SECURESIGN-574] Independently Deployable CT-log

After testing and signing and veryfying it should be up to scrath and working now.
To test you it is advised ctlog and trillian not be in the same namespace as the main change is to check that ctlog can successfully reach trillian elsewhere.

please squash commits into single one

/ok-to-test

/test images

/test tas-operator-e2e

/lgtm

/override ci/prow/images
/override ci/prow/tas-operator-e2e