Can't render Mapbox tiles

Hi, I've been playing around with this plugin for the last few days (and am really excited about it!), but I had a question around Mapbox support. With the given example, I'm able to successfully render a map with the Stadia Maps URL. However, when I try to use the Mapbox URL, it doesn't seem to render the tiles. I don't see any errors to the console. I was wondering if this is a known issue and/or if anyone has have any ideas to fix this.
Repro steps:

Download the example.
Add your Stadia Maps access token to the Stadia Maps URL in main.dart.
Change the zoom level to 15 (so that we should see streets and names on the initial render).
Run the application. I've encountered this issue on both Mac and Android (the only platforms I've tried).
See that it renders the map correctly.

Close the application and clear the cache. On Android, I'm doing this by long pressing on the app icon and navigating to "clear storage." On Mac, I'm doing this by deleting the "example" folder at ~/Library/Containers/.
Comment out the Stadia Maps URL, uncomment the Mapbox URL, and add your access token.
Run the application again.
See that streets/names don't show up.

Hi, thanks for the issue. I've seen this problem too, here's what I've found:
Though vector tiles have the same data structure and format, they don't necessarily have the same conventions when it comes to naming of source layers, and values for attributes. The theme that you use selects the data to render -- but if the data doesn't match the expected values as specified in the theme, then those features won't render. You can see the same result in https://maputnik.github.io/ by selecting the OSM Liberty style then setting the data source to Mapbox.
To use Mapbox you'll need to supply a style that works with Mapbox tilesets. A good place to start looking at Mapbox styles is their Gallery.
Once you've selected a style you'll find that some of the features used in the style aren't implemented in this library. For example, I had troubles with the background color function in one theme, and the text-placement function. For incompatibilities like this usually you'll see a stack trace. To solve this problem you can either change the style to use a form that's supported by this library, or you can open an issue for it and consider contributing a pull request.

closing but feel free to reopen if you think there's a bug here

Hi, thank you for your great work with this plugin and the very useful pointers in your response.
I'm trying to display a vector Mapbox in my app as well.
I followed your recommendations. I picked a basic Mapbox theme and tweaked it a bit in https://maputnik.github.io/ to make  ThemeReader errors related to text-anchor disappear. The theme works in Maputnik.
 How would one go about fixing those ?
It would be great if the ThemeReader had some kind of fallback for unsupported values, for example by substituting constants to unsupported expressions. :thinking:

Various options:

Removing those parts of the theme if not needed (this will also heavily increase performance; in our usecase we could remove a couple dozen unused theme layers like for US highway signs) and FPS jumped from 2-3 to 30.
Opening a PR to support those expressions in the vector-tile-renderer repo
Try out my fork of said repo by adding this to your pubspec.yaml

dependency_overrides:
  vector_tile_renderer:
    git:
      url: http://github.com/mvarendorff/dart-vector-tile-renderer
      ref: atmina

@oulianov could you attach your theme? I'll have a look.
@mvarendorff thanks for helping out. Feel free to submit PRs with your own improvements!

Thank you @mvarendorff for sharing your ideas. Some layers can be removed, but others less so (e.g. country names). I've looked at your repo but didn't find implementation of said functions.
@greensopinion Sure thing, here's the theme : https://pastebin.com/S3Ve3gPa
Reading through the mapbox expression documentation, here are some details about the unsupported expressions:

geometry-type : filter by type of geometry
coalesce: takes the first non-null value in a list
step: apply a step-wise function to a value
cubic-bezier: non-linear intepolation

Do you know what alternative, already implemented expressions could be used? Or how can I go about implementing those?
I've looked around in the code, but there are many layers of abstraction. For example, even though I know how to do a coalesce in Dart, it's hard for me to know where to start adding this logic in the code. But if you had some pointers about package architecture, or even would be available for an informal chat, I'd love to help you improve this package.

Do you know what alternative, already implemented expressions could be used? Or how can I go about implementing those?

A great place to get started is expression_parser_test.dart which should have tests for most (all?) supported syntax in expressions.

@oulianov here's an example PR adding support for geometry-type dart-vector-tile-renderer/pull/14
Feel free to comment on it or create some PRs of your own!

@greensopinion Hello,
I am facing almost similar problems with street map. I just want to use basic Street map theme of mapbox. But mostly areas are not loading for me.
I have tried to use Stadia but where ever i go it is always ignoring 1 tile.
Is there any chance that i need to clear cache or delete the app to make stadia functional?

Muhammad, if you want to use Mapbox you should be able to. I've tried several of their themes and they work well. You can see the results in the gallery and you'll find an example showing Mapbox themes working on the mapbox-example branc.
If you have one tile that's not showing correctly with Stadia, there's a good chance that there is some bad data in the cache. Clearing the cache may fix the issue. At the moment there is no good way to do that other than figuring out where the cache is located and deleting the files. Alternatively you could change "openmaptiles" to something else here but if you do that you'll also need to change the source to match in the theme.
If you have a stack trace on the application console, please open an issue because it will help me to understand what happened. Perhaps there's something that we could do to prevent blank tiles.

Hello @greensopinion , thank you for reply. I have tried that example from here but unfortunately my map is entirely not loading. I have downloaded whole theme from the mentioned URL and saved as a const String then encoded
mapboxTheme = vt.ThemeReader().read(mapBoxThemeEncoded);

as soon as i switch back to
theme: vt.ProvidedThemes.lightTheme(),
I see

Do i need to first load the map and then load the theme?

Looks like this is a case of "works for me" with the mapbox example
Here's what I did:

cloned this repository to get a clean local copy git clone git@github.com:greensopinion/flutter-vector-map-tiles.git && cd  flutter-vector-map-tiles
git checkout mapbox-example
git reset --hard 9068ae5 (just to be sure)
created a file example/lib/api_key.dart with contents const mapboxApiKey = '<my-mapbox-key>';
cd example
flutter pub get
flutter run --debug

If that's not working for you, it would be great if you could post any console messages (e.g. stack traces, errors) here.

I've added some examples that you may find helpful here: https://github.com/greensopinion/flutter-vector-map-tiles-examples


Repeats too often

So it repeats the same three digits (in different orders) along the vertical blocks. So like if there is three blocks that are 4 | 5 | 6, every where there is a 4, 5, or 6, the other two digits will be there on the same vertical line. Like 5 | 6 | 4  or  6 | 4 | 5.
Not a big issue just makes the game to easy.

fixed. will be much better in v1.1


DHT22 humidity and temperature values are incorrect

I'm using R-pi 3 with Python 2.7.13 and the DHT22 sensor for reading humidity and temperature values. I tried changing surrounding temperature but it does not read accurate values. In fact, it does not show significant change. I tried changing sensor but still facing the same issue. While when I use the same sensor with ESP8266 it shows a significant change in values.
Please suggest solutions.

@preranagawale So why did you close this issue? It might help others who are seeing the same thing that you did if you described what it was that fixed your problem.

The problem was with code. I was reading sensor values at the start and printing it in the loop. So basically It used to read sensor only once in some defined time interval and that's why it was unable to show significant changes.

@preranagawale,
I couldn’t find a better way to contact you so I’m writing here. This comment will be deleted in one week to keep the issue discussion clean.
My name is Marat, I am a PhD student at Carnegie Mellon University. As a part of my research, I’m trying to better understand the sources of issue reports in open source.
Can you please help me by answering few questions about this issue? It shouldn’t take more than a couple of minutes. Here’s the google form: link
I will share everything I learn from answers to this survey with the community afterwards.
Thank you very much!


review overlap of dv_user_email in Shapefile and DataverseInfo Forms

(11/1/2016) - review may be able to close; signatures removed)
potential bug if emails differ and dict contains info from both forms.
(signature_key is calculated using email)

Now using Dataverse service account. "Signature key" use deprecated


Feature request - Servo control via PPM instead of I2C

There have been some comments about swapping in/out the stock RC controller and since there are only 2 servo controls used( steering / throttle ) an Arduino could do this.  But since the rPi has only 1 hardware PWM, it would be more efficient to stream the servo control via a single PPM stream. This way an Arduino could decode the PPM and drive the servo's.  And with a single digial I/O flag/pin the Arduino could read and use the stock RC receiver signals for training.

That's what we do with OpenMV, and the Arduino allows both multichannel PWM
output and a wide range of inputs (analog, digital, serial, etc).  We
implement Firmata https://www.arduino.cc/en/Reference/Firmata on the
Arduino side, and recommend that be used as the the middleware standard for
I/O.
A standard Arduino Pi ha
http://www.robotshop.com/en/arduino-adapter-raspberry-pi.html?gclid=Cj0KCQjwn6DMBRC0ARIsAHZtCeOvuKO5HPcGp-gxiCQi4-hXyDFFxUjqCWcjBu6Y631-Ygxw_Lki9d0aAnN7EALw_wcBt
can work, although a custom shield like we designed for the OpenMV
https://circuits.io/circuits/4446963-openmv-arduino-shield simplifies the
wiring.
On Mon, Aug 7, 2017 at 3:11 PM, Doug LaRue<EMAIL_ADDRESS>wrote:

There have been some comments about swapping in/out the stock RC
controller and since there are only 2 servo controls used( steering /
throttle ) an Arduino could do this. But since the rPi has only 1 hardware
PWM, it would be more efficient to stream the servo control via a single
PPM stream. This way an Arduino could decode the PPM and drive the servo's.
And with a single digial I/O flag/pin the Arduino could read and use the
stock RC receiver signals for training.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wroscoe/donkey/issues/107, or mute the thread
https://github.com/notifications/unsubscribe-auth/AABGl6iIHpIFR0jDnXtPNSra3dWrIS7Eks5sV4uKgaJpZM4OwAss
.

--
◤CHRIS ANDERSON https://twitter.com/chr1sa
CEO
3DR
website http://www.3dr.com/ | twitter https://twitter.com/3drobotics
| facebook http://www.facebook.com/3drobotics | instagram
http://www.instagram.com/3drobotics

The more I thought about it, I think keeping I2C from the rPi makes sense since all I'm looking to do is add simple RC control back and if I can do it with a $3 ProMini and replace the Servo Driver($12) too then it's a feature improvement and cost cutter.  The RC control could also enable a remote kill switch via a 3rd channel.
As for adding sensors, an Arduino with Firmata sounds interesting. I'm only familiar with Firmata by using it with Snap4Arduino(Scratch for Arduino).  And idea to keep in the back pocket. Thanks.


fix: burst props with href when href is set by user

TODO: add error message when running in localhost


Managed HSM SKU defaults to B family

Describe the bug
I am a part of the Azure Managed HSM team. When creating a new Managed HSM resource using az keyvault create, the SKU defaults to the B family, irrespective of the SKU name specified. This is not correct since we have certain SKUs in the C family.
Source Code
Related command
az keyvault create --hsm-name "test" --resource-group "test" --sku Custom_C42
Errors
(BadRequest) The Managed HSM SKU is invalid.
Code: BadRequest
Message: The Managed HSM SKU is invalid.
Issue script & Debug output
cli.azure.cli.core.sdk.policies: Response content:
cli.azure.cli.core.sdk.policies: {"error":{"code":"BadRequest","message":"The Managed HSM SKU is invalid."}}
cli.azure.cli.core.azclierror: Traceback (most recent call last):
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 666, in execute
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 733, in _run_jobs_serially
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 703, in _run_job
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/init.py", line 336, in call
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/keyvault/custom.py", line 509, in create_vault_or_hsm
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/keyvault/custom.py", line 584, in create_hsm
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/util.py", line 710, in sdk_no_wait
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/core/tracing/decorator.py", line 76, in wrapper_use_tracer
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/mgmt/keyvault/v2023_07_01/operations/_managed_hsms_operations.py", line 537, in begin_create_or_update
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/mgmt/keyvault/v2023_07_01/operations/_managed_hsms_operations.py", line 408, in _create_or_update_initial
azure.core.exceptions.HttpResponseError: (BadRequest) The Managed HSM SKU is invalid.
Code: BadRequest
Message: The Managed HSM SKU is invalid.
cli.azure.cli.core.azclierror: (BadRequest) The Managed HSM SKU is invalid.
Code: BadRequest
Message: The Managed HSM SKU is invalid.
az_command_data_logger: (BadRequest) The Managed HSM SKU is invalid.
Code: BadRequest
Message: The Managed HSM SKU is invalid.
Expected behavior
These are all of the valid Managed HSM SKUs:
B SKU family: Standard_B1, Custom_B32, Custom_B6
C SKU family: Custom_C42, Custom_C10
For Custom_C42 and Custom_C10, the SKU family passed to ARM should be C instead of B.
This can be determined by checking the letter following the underscore in the SKU name.
Environment Summary
azure-cli                         2.65.0
core                              2.65.0
telemetry                          1.1.0
Dependencies:
msal                              1.31.0
azure-mgmt-resource               23.1.1
Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\dcherrett.azure\cliextensions'
Python (Windows) 3.11.8 (tags/v3.11.8:db85d51, Feb  6 2024, 21:52:07) [MSC v.1937 32 bit (Intel)]
Additional context
No response

Thank you for opening this issue, we will look into it.

Azure CLI is using 2023-07-01 API version for MHSM operations and from the swagger there're only skus for B family: Standard_B1,Custom_B32,Custom_B6. We are not aware of any C family. If there's feature added, can you pls update swagger to generate SDK new version and then file a feature request for CLI team?

Will re-open once new API version is released


Bugfix/#2863 No placeholders in gallery - offline mode

Related issues
#2863
#2925
Short description and why it's useful
As wrote @pkarw I changed gallery behavior in offline mode. Now in offline mode we show only offline image without zoom.
I implemented ProductImage to Wishlist, Checkout and Microcart.
Screenshots of visual changes before/after (if there are any)

Which environment this relates to
Check your case. In case of any doubts please read about Release Cycle

[x] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop
[ ] RC version (https://next.storefrontcloud.io) - this is a stabilisation fix for Release Candidate of Vue Storefront. I've created branch from release branch and want to merge it back to release
[ ] Stable version (https://demo.storefrontcloud.io) - this is an important fix for current stable version. I've created branch from hotfix or master branch and want to merge it back to hotfix

Upgrade Notes and Changelog

[ ] No upgrade steps required (100% backward compatibility and no breaking changes)
[x] I've updated the Upgrade notes and Changelog on how to port existing VS sites with this new feature

IMPORTANT NOTICE - Remember to update CHANGELOG.md with description of your change
Contribution and currently important rules acceptance

[x] I read and followed contribution rules
[x] I read the TypeScript Action Plan and adjusted my PR according to it
[x] I read about Vue Storefront Modules and I am aware that every new feature should be a module

@przspa I have placeholders everywhere in offline mode.

@alinadivante for me everything is working greate. I only fixed image source for single picture on product page in offline mode.

For me this bugfix resolve #2863 and #2925 bug. I tested it and I always have placeholder if image cannot loaded. But I have many cases when I see only placeolder. It's possible that it's a cache problem?

@przspa can You please resolve a conflict with the changelog?

@pkarw done

Thanks!


Re-instate v2.9.0 Diffs For v3.0.0

/cc https://github.com/terraform-providers/terraform-provider-github/issues/502#issuecomment-652399602

There is some follow up work to do here around testing and finalizing the provider schema ahead of a v3.0.0 release.  Aiming to merge this as-is though in order to contain follow ups in their own PR.


Backport runtime concurrent compactors count adjustment (CASSANDRA-12248)

@intjonathan

You couldn't do this before?!


Bump targetSdkVersion to 31 and organize static values

Bumps the targetSdkVersion to 31, and also moves the versions for
minSdkVersion,  compileSdkVersion, and targetSdkVersion to flutter.grade.

Ok, keeping up to date rather than latest sgtm then.

This seems to have broken flutter create; flutter run: https://github.com/flutter/flutter/issues/91936


lineHeight: "42px" not valid

Describe the issue
Types of property 'lineHeight' are incompatible.
Type 'StyleXClassNameFor<"lineHeight", "42px">' is not assignable to type 'StyleXClassNameFor<"lineHeight", Readonly<number | "initial" | "inherit" | "unset" | null | undefined>>'.
Expected behavior
It should work, or is there any reason why it should not?
Steps to reproduce
Define a style with lineHeight: "42px",
Test case
No response
Additional comments
No response

Hi @steida! I created this PR to solve the issue. Same issue as #356.


Fix a critical bug of SccTycker

Fixed not clearing reporter countings when one definition failed to tyck (which causes all coming definitions to be treated as failed)
Search both core and concrete term when highlighting
Skip DefVars from skipped modules and libraries

Suggest: replace all @UnknownNullability with @Nullable to force the IDE to tell you to remember null checks!!

Suggest: replace all @UnknownNullability with @Nullable to force the IDE to tell you to remember null checks!!

Yes we can. Are you gonna do it?

I did part of it in this PR and there're only 2 @UnknownNullability left in DefVar. I guess it's fine now.


Intersection of Two Sorted Linked Lists

Contributed to Intersection of Two Sorted Linked Lists

Thank you for the contribution


Add more hotkey outputs including DPad direction keys and LS/RS directions

Currently the hotkeys section only allows output of none directional keys.
It would be great if directional keys can be set as output too.

As of version 0.7.10 we now have hotkeys for DPad directions


Provide API to obtain a digest from a session desc to uniquely identify it.

This allows users to create session-specific cache folders without worrying about race conditions with other sessions.

Fixed in #3669.


Add copper workshop

Add copper workshop factory with recipes to weather and wax copper blocks

This factory is a good addition, totally slipped by me. @walkersgaming can you update this for the current FM config? There's some conflicts from FM updates.
As for balance/ cost, what do you think of 8 honeycomb for each stack? And increasing it to 4 water buckets for weathering

Instead of 4 water, which might be annoying in bulk. We can change the fuel like we do for the bio factory to add a cost there.

Probably didn't do it the exact right way, but caught up the PR with latest.
@RedDevel2 if this is about saving time (helping builders) doesn't it make sense to be fairly cheap? What do you suggest the fuel cost be instead?

Does copper oxidisation actually need to be something that's added to a factory ? It's possible to make farms for oxidising copper in vanilla that use the catalysing ability of "older" copper along with the proximity to other copper blocks factor to speed up oxidisation quite a bit. I imagine with civ this could be taken even further with bots potentially drastically simplifying the designs for such farms that utilise these two factors effecting oxidisation speed.
I've seen many other people successfully sell different building blocks, and I don't necessarily think making something that is potentially another niche industry for people to enter into just another easy factory recipe is the right approach to take. Builders are also a part of the world and should have to interact with it/with other players in some way. I think removing this potential niche just because currently no one has tried to make either a vanilla style catalysing oxidation farm, or a new more simple oxidation farm utilising bots that would be unique to CivMC is adding an easy fix for no reason that removes a potential unexplored niche.
Even just spreading the copper blocks out into the optimal distance, without any catalysing blocks present, underneath an active area has allowed a lot of people to obtain vast amounts of oxidised copper for very large copper builds quite easily. This could be taken even further if someone wished to by actually designing a farm around both the distance factor and the catalyst factor that greatly decreases the time in which they can oxidise vast amounts of copper blocks.
In relation to the waxxing recipe, and being able to wax large amounts of copper through a factory I do think this is a good addition as it just replaces a very simple script, whereas oxidation farms would be more complex with either approach. However, I think the honeycomb discount is far too much as red said. Honeycomb is one of the easiest items to farm in very large quantities with even a very small farm from what I have seen. The current proposal here would give a discount of 0.9375 honeycomb per copper block. I think that realistically farms that make honeycomb produce so much that there's not really a reason to devalue it any further (it is already valued pretty low when you buy it) and that a waxxing factory should realistically just make it easy for people to wax large amounts quickly at the same cost as vanilla of 1 honeycomb per waxxed block.
Similarly to the waxxing recipes though you could add a stripping recipe, using iron axes maybe, that allows you to strip large number of copper in a similar fashion to the waxxing factory. As this again would replace a very simple script similarly to the waxxing recipe and in contrast to the different complex farm options you have for the initial oxidising stage.
An iron axe has a durability of 250, so maybe 1 iron axe + 4 stacks of some sort of oxidised copper would revert those 4 stacks back to the stage directly before the one they are at and consume the axe.

Does copper oxidisation actually need to be something that's added to a factory ? It's possible to make farms for oxidising copper in vanilla that use the catalysing ability of "older" copper along with the proximity to other copper blocks factor to speed up oxidisation quite a bit. I imagine with civ this could be taken even further with bots potentially drastically simplifying the designs for such farms that utilise these two factors effecting oxidisation speed.
I've seen many other people successfully sell different building blocks, and I don't necessarily think making something that is potentially another niche industry for people to enter into just another easy factory recipe is the right approach to take. Builders are also a part of the world and should have to interact with it/with other players in some way. I think removing this potential niche just because currently no one has tried to make either a vanilla style catalysing oxidation farm, or a new more simple oxidation farm utilising bots that would be unique to CivMC is adding an easy fix for no reason that removes a potential unexplored niche.
Even just spreading the copper blocks out into the optimal distance, without any catalysing blocks present, underneath an active area has allowed a lot of people to obtain vast amounts of oxidised copper for very large copper builds quite easily. This could be taken even further if someone wished to by actually designing a farm around both the distance factor and the catalyst factor that greatly decreases the time in which they can oxidise vast amounts of copper blocks.
In relation to the waxxing recipe, and being able to wax large amounts of copper through a factory I do think this is a good addition as it just replaces a very simple script, whereas oxidation farms would be more complex with either approach. However, I think the honeycomb discount is far too much as red said. Honeycomb is one of the easiest items to farm in very large quantities with even a very small farm from what I have seen. The current proposal here would give a discount of 0.9375 honeycomb per copper block. I think that realistically farms that make honeycomb produce so much that there's not really a reason to devalue it any further (it is already valued pretty low when you buy it) and that a waxxing factory should realistically just make it easy for people to wax large amounts quickly at the same cost as vanilla of 1 honeycomb per waxxed block.
Similarly to the waxxing recipes though you could add a stripping recipe, using iron axes maybe, that allows you to strip large number of copper in a similar fashion to the waxxing factory. As this again would replace a very simple script similarly to the waxxing recipe and in contrast to the different complex farm options you have for the initial oxidising stage. An iron axe has a durability of 250, so maybe 1 iron axe + 4 stacks of some sort of oxidised copper would revert those 4 stacks back to the stage directly before the one they are at and consume the axe.

I doubt people bother with farms for oxidising given you can just place it and wait for it to oxidise. The point of factories is to add recipes to improve QOL, which this does. Enabling builders to expand the repertoire of blocks they can/want to build with

Does copper oxidisation actually need to be something that's added to a factory ? It's possible to make farms for oxidising copper in vanilla that use the catalysing ability of "older" copper along with the proximity to other copper blocks factor to speed up oxidisation quite a bit. I imagine with civ this could be taken even further with bots potentially drastically simplifying the designs for such farms that utilise these two factors effecting oxidisation speed.
I've seen many other people successfully sell different building blocks, and I don't necessarily think making something that is potentially another niche industry for people to enter into just another easy factory recipe is the right approach to take. Builders are also a part of the world and should have to interact with it/with other players in some way. I think removing this potential niche just because currently no one has tried to make either a vanilla style catalysing oxidation farm, or a new more simple oxidation farm utilising bots that would be unique to CivMC is adding an easy fix for no reason that removes a potential unexplored niche.
Even just spreading the copper blocks out into the optimal distance, without any catalysing blocks present, underneath an active area has allowed a lot of people to obtain vast amounts of oxidised copper for very large copper builds quite easily. This could be taken even further if someone wished to by actually designing a farm around both the distance factor and the catalyst factor that greatly decreases the time in which they can oxidise vast amounts of copper blocks.
In relation to the waxxing recipe, and being able to wax large amounts of copper through a factory I do think this is a good addition as it just replaces a very simple script, whereas oxidation farms would be more complex with either approach. However, I think the honeycomb discount is far too much as red said. Honeycomb is one of the easiest items to farm in very large quantities with even a very small farm from what I have seen. The current proposal here would give a discount of 0.9375 honeycomb per copper block. I think that realistically farms that make honeycomb produce so much that there's not really a reason to devalue it any further (it is already valued pretty low when you buy it) and that a waxxing factory should realistically just make it easy for people to wax large amounts quickly at the same cost as vanilla of 1 honeycomb per waxxed block.
Similarly to the waxxing recipes though you could add a stripping recipe, using iron axes maybe, that allows you to strip large number of copper in a similar fashion to the waxxing factory. As this again would replace a very simple script similarly to the waxxing recipe and in contrast to the different complex farm options you have for the initial oxidising stage. An iron axe has a durability of 250, so maybe 1 iron axe + 4 stacks of some sort of oxidised copper would revert those 4 stacks back to the stage directly before the one they are at and consume the axe.

I doubt people bother with farms for oxidising given you can just place it and wait for it to oxidise. The point of factories is to add recipes to improve QOL, which this does. Enabling builders to expand the repertoire of blocks they can/want to build with

Factories shouldn't just replace existing farms, or manual collection, though which can very much exist to produce blocks where their main purpose is to build with them. I've seen people selling blocks such as terracotta which only exist to be built with, and there's no way to even improve the efficiency of collection and it relies on manual collection. Just because something is primarily built with doesn't mean that every aspect of it's production should be moved into factories.
And copper blocks (of all weathering stages) very much currently exist within the repertoire of builders, people already gather large amounts of copper at different stages of weathering to build with it. The oxidising of the copper isn't even the most tedious aspect of collecting a large amount of partially oxidised copper, neither is it the second. By placing copper at the optimal distance underneath an active area it is very easy to oxidise a large amount of copper within  few days, considering builders use other blocks they can easily use these few days to gather other blocks or work on another building, this is how I oxidised 4-5 cs of copper blocks for a build.
And this is only putting in the minimal amount of effort to speeding the process up, using catalysts, a bot, or redstone mechanics of some sort can all also speed up the process further. Many other "building" blocks are currently not made in factories but though farms, or just by manual collection, at least in their "primary" stage. Wool has to be made from string, or by killing or shearing sheep, dyes are collected from flower farms, or other resources, plain terracotta is mined, honeycomb is mass produced via honeycomb farms etc... All of these give new niches for players to work in and produce goods to sell, the oxidisation process of aging copper would very much belong to a similar style of farming and of producing the "primary" stage of oxidation.
The much more tedious parts of producing the 2nd and 3rd stages of oxidation specifically in very large quantities, from my person experience, are the waxxing stage and also the stripping stage (which isn't even mentioned here). If the true aim is to help builders and to make the production process easier then these are the two stages which should actually be moved to factories.
The stripping stage is likely the most tedious stage as for every single fully oxidised copper block you have to right click it once or twice with an axe (consuming durability) and then mine it. The waxxing is also somewhat tedious but less so, as you can wax up to 64 blocks at once. These are the two processes which should be moved to a factory. The actual initial oxidation of the copper is fine as it is, even just leaving it under an active area in the optimal spacing allows you to oxidise large amounts of copper within 3 hours (you don't have to be there, the area is active so anyone else in the area is also loading it while you are off doing something else) and it can be sped up further using catalysing blocks, which you could then use redstone mechanics or bots alongside but it's not even necessary tbh as you just leave it in the active area and then come back later and mine it.

While I tend to agree with the kind of argument @Solitaire7 is making here, copper is so ridiculously abundant that it really doesn't matter. You could mistakenly let an entire "farm" oxidise too much and little of value would be lost. For that reason, I think reducing the overall tedium of it all seems like a good idea.

@wingzero54 @RedDevel2 let me know if you have further thoughts on costs/fuel

I think:
64 copper blocks, 32 wax for waxing recipe
64 copper blocks 1 water bucket for ageing recipe.
With the fuel being amethyst crystals, since it's the closest thing to a mineral that could oxidize, and is decently abundant.
And then make each step of aging take longer, and thus use more fuel the higher in age you want your copper to be.

That's pretty interesting, I like that it does introduce a use for amethyst crystals. What would your thoughts be on adding a scraping recipe similar to waxxing ? It's a more tedious process than waxxing as you have to go block by block whereas waxxing you can do a stack at a time in a crafting grid.
A potential recipe (since scraping takes axe durability) could be 4 stacks copper blocks + 1 iron axe returns 4 stacks copper blocks at the oxidation stage directly before (so you'd need 4 recipes similar to waxxing). And 1 diamond axe would scrape 24 stacks.
You could also potentially have 2 separate versions of the recipe 1 using iron axes and 1 using diamond axes, and then have the fuel be emeralds and allow the consumption of the singular iron/diamond axe to scrape a number of stacks similar to their durability with unbreaking 3. So for the iron axe recipe that'd be 16 stacks and for a diamond axe it'd be 96 stacks if you go by the vanilla durability. But maybe since these are bulk recipes they could be in an upgraded version of the factory (or just have greater efficiency anyway) and the iron axe + emeralds recipe could scrape 20 stacks and the diamond axe + emeralds recipe could scrape 2 ci. This would give a way to reduce the iron/diamond cost in return for supply emeralds, similar to how you can scrape more copper blocks with an unbreaking 3 axe.

#183


Events without timestamps?

Until now I assumed that events should always have a timestamp. I agree that this timestamp is part of the domain and it has a certain meaning, but can you think of an example where we don't need one?
If there are only events with timestamps, I suggest that we include it into the interface and provide a convenience base class which creates one in the constructor.

Until now I assumed that events should always have a timestamp

Right. Our point was rather that there are multiple types of timestamps:

When the event was stored
When the event occurred
(possibly) some domain-related events

For 3 I guess we agree that it should be part of the event payload and by default I'd like the system to just set the event timestamps to the current date & time but sometimes 1 & 2 need to be handled separately:
I recently imported ~500k events based from existing (non-event-sourced data) and for this I needed to be able to set the occurred timestamp explicitly (to the creation-timestamp of the corresponding record).
In my case I implemented a simple mechanism that allows to hook into events before they are published in order to add metadata (like IP address, timestamp, ...) if it's not already in the event. That worked out quite nicely.
To get back to your point: Whether that event metadata has a "fixed" concept of timestamp I don't really care but I agree that it probably makes sense!

So, I think it would be valid to provide a base class with "automatic timestamp generation" which has the meaning of "when the event occurred". As a developer you'd be able to override that timestamp of course.
The "when the event was stored" timestamp shouldn't be stored in the Event object but in an envelope managed by the Event Store.

Just saw in @dfeyer's Push Button example that he used regular DateTime objects for timestamps. I think that this is something which could go wrong when less experienced users are dealing with it.
How about using DateTimeImmutable instead?

Yes, the time when the Event occured should be part of the concept of an Event.
What I currently prefer to do is, wrap the concrete domain event classes (the pure POJOs) in an Envelope Event class (sth. like "DomainEvent"), that has payload and metadata and set the "occuredAt" timestamp inside the Aggregate recordThat method (along with some other aggregate-related info).
For importing events, I would go the same route as Bastian and just use an EventEnricher that sits between the Aggregate and the EventStore (currently using a Repository middleware aproach that plays really nice).

@albe I just wonder: what's left to justify the Event class then? It's a plain DTO, so it could actually be an array.
Because of that, what I did previously was to extend a DomainEvent base class which provided functions for setting / getting the payload, metadata and so and and took care of timestamps and identifiers.
So I did it the other way around. The advantage of extending a base class instead of wrapping the event is that you can instantiate an event and already have all the information:
$event = PullRequestSent::occur($pullRequestIdentifier, $subject, $author);
$payload = $event->getPayload(); // array('pullRequestIdentifier' => ..., 'subject' => ...);
$timestamp = $event->getOccurredTimestamp(); // \DateTimeImmutable
$uuid = $event->getIdentifier(); // Event identifier, not the aggregate identifier

...

$event = PullRequestSent::recreate($identifier, $timestamp, $payload, $metadata);

Of course, there are many ways to implement that part.

That's some good point there.
My reasoning behind the wrapping is mainly that it keeps the public facing API of the domain (which I see as Events+Commands) free from infrastructural dependencies, so that it is more safe from external/infrastructure changes.
And yes, basically the Events can in fact very well be simple arrays - they are, after all, supposed to be exchangeable remotely (so should at least be serializeable) and only hold facts about what happened. Making them a class is something to gain a better Developer experience with autocompletion for property accessors solely IMO.
Of course with that the question quickly comes up, which of the meta information of the wrapper is supposed to be used by any handlers (or if any at all), since from that PoV they shouldn't even know about that metadata. I think that leads to more thought being put into the essential event data (is occuredAt domain relevant?), but also quickly creates neccessity for more "boilerplate".

there are many ways to implement that part.

Very true and not only for that part :) After all, I don't have any issues with the implementation above.

My reasoning behind the wrapping is mainly that it keeps the public facing API of the domain (which I see as Events+Commands) free from infrastructural dependencies, so that it is more safe from external/infrastructure changes.

👍 the infrastructure need to be "invisible" for the implementer POV. That's the reason of the EventTransport in the current implementation. It offer the timestamp (when event occured, but by default use the metadata to store the value), if the timestamp is part of the domain, the implementer should add it explicitly in the event class (no magic here), it's pure domain, pure responsability of the implementer (by ex. we should named the property timestamp, but domain wise some can prefer createDate, orderDate, ...)

It's a plain DTO, so it could actually be an array.

Yes it can ;) is a pure POPO (Plain Old PHP Object), and it's good like this. Easy to test, no framework dependency, ...

The "when the event was stored" timestamp shouldn't be stored in the Event object but in an envelope managed by the Event Store.

That's mostly the reason behind the EventTransport object, see also my previous comment https://github.com/neos/Neos.Cqrs/issues/5#issuecomment-246022594


soft-fallback on not loading sundown

A hard fall back will not load dok for pure Lua setups.

Also, will not load a few more packages down the line....


ver 10.0.72000.706 not supported

just got newest update for windows 11..

RDPConf screenshot, please!

https://github.com/UMU618/rdpwrap.ini
Updated to support 10.0.72000.706

just got newest update for windows 11..

Attach your termsrv.dll, so i can help you

Closed because of missing answer


solve InfluxDB plugin with multiple instances.

Signed-off-by<EMAIL_ADDRESS>

Why does DCO check not successful，Which step is wrong？

Why does DCO check not successful，Which step is wrong？

Check the error message "Committer<EMAIL_ADDRESS>Smart33690 is not a valid email address. ". Use git config --global user.email<EMAIL_ADDRESS>to configure the email address.


benchmark batch Metric Vector

If we want to inc some VecMetric many times, we may first cache in a map then inc in batch.
let m = HashMap::new();
m["a"] += 1
m["b"] += 1
// many times

for (key, value) in &m {
    metric.with_label_values(&[key]).add(value);
}

to compare with
 metric.with_label_values(&["a"]).inc(1);
 metric.with_label_values(&["b"]).inc(1);
// many times

I prefer the second one.
Benchmark results are not accurate, if we cache things in a hashmap, because hashmap is relatively slow in Rust.

Sometimes we can't call the metric too frequently, so we should cache it and call the metric in batch.
Is HashMap really slow for the above case?
Or we can use BTreeMap or even define a structure for the multi metrics.
What I want here is to supply a optimization guide for user when they find metrics reduce the performance.
Btw, Benchmark may be not accurate, but it can still show something for us.


Use workbox-cli as a build step

Here's one way you could use Workbox as part of your build process to mix precaching along with runtime caching.
Instead of checking in your docs/sw.js file, it will be generated by npm run workbox.

Thank you! Much appreciated.


Redundant service call parameter "node_name" for system_modes services

Currently, system_modes/srv/GetAvailableModes, system_modes/srv/ChangeMode and system_modes/srv/GetMode require as parameter the node_name. However, the similar services from lifecycle_msgs/srv/* do not require to pass that parameter, since the service name/scope already includes it.
For example:
ros2 service call /actuation/get_available_modes system_modes/srv/GetAvailableModes "{node_name: actuation}"}"

Maybe that service parameter could be optional, also for system_modes to have a more similar interface to lifecycle?

Thanks, @chcorbato, this is a very valuable observation. This redundancy was indeed also present in the according lifecycle_msgs/srv/ when we first started this project (before pushing it to github), but was since removed: https://github.com/ros2/rcl_interfaces/pull/39 (October 2018).
So you are right, this should be removed from the system mode services as well.

@chcorbato please have a look at https://github.com/micro-ROS/system_modes/issues/24

Hi @norro
This issue is still present in the /feature/rules branch, I'm not sure if a new issue is needed, but It'll be good to apply the solution to that branch as well.

Very good point, I will port it there as well.

@marioney should be ported now. If it causes any issues, please don't hesitate to open further bug reports.


Altered datetime serialisation tests to cope with offsets better

With the Easter 2016 clocks going forward the serialisation tests for DateTime failed.
The serialiser converts Unspecified dates to Local and then formats using the ToString("o") formatter.
This will append the timezone differences if a date is Local.
This PR uses the recommended TimeZoneInfo.Local.GetUtcOffset(myDate); to find the timezone offset.  We then use this in the tests to assert the value the serialiser's ToString("o") formatter returns with the datetime passed into the SUT.

When I run these tests (en-US & -4 eastern daylight)  I'm getting two failing at NancySerializationStrategyFixture.cs#L80-112
Should_serialize_unspecified_datetime_object
Expected: 2014-03-09T17:03:25.2340000+-04:00
Actual:   2014-03-09T17:03:25.2340000-04:00

Should_serialize_local_datetime_object
Expected: 2014-03-09T17:03:25.2340000+-04:00
Actual:   2014-03-09T17:03:25.2340000-04:00

Those expected values look,um, interesting :)
On Saturday, 30 April 2016, Brian Surowiec<EMAIL_ADDRESS>wrote:

When I run these tests (en-US & -4 eastern daylight) I'm getting two
failing at NancySerializationStrategyFixture.cs#L80-112
https://github.com/NancyFx/Nancy/blob/2c07700b2d999d20c60f524480c48b2dc19b678c/test/Nancy.Tests/Unit/Json/Simple/NancySerializationStrategyFixture.cs#L80-112
Should_serialize_unspecified_datetime_object
Expected: 2014-03-09T17:03:25.2340000+-04:00
Actual:   2014-03-09T17:03:25.2340000-04:00
Should_serialize_local_datetime_object
Expected: 2014-03-09T17:03:25.2340000+-04:00
Actual:   2014-03-09T17:03:25.2340000-04:00
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/NancyFx/Nancy/pull/2385#issuecomment-215966501

Need to test those when #2427 is complete

The issue above has been fixed in #2525


crash w/depth shading when y=1

Crashes with divide by zero error when y=1 and depth shading is on. Obviously because I changed
int num=prevy+50-(128-y)/5;
int denom=y+50-(128-y)/5;
to
int num=prevy+50-(256-y)/5;
int denom=y+50-(256-y)/5;
without really understanding why those constants were chosen.
changing the 256 back to 128 works fine. changing the 50 to 76 has the same effect.
making num=prevy+1 and denom=y+1 also works, so do whatever makes sense to you.

Probably should redo that anyway.
Basically, we calculate a darkness based on the current depth, as well as the depth of the block to the left.  Dividing by 10 instead of 5 would keep the previous scale.


Categories mapping ignores duplicate names from different paths

Don't mean to bombard you with corner cases, but I did some analysis on an issue I was having with the parts category schema that matches Digikey. There are cases where sub categories are assigned different paths. A good example of this is for Transistors, which exists under both Discrete Semiconductor Products/Transistors and Electronics/Transistors which contains some sub categories as well. When building the category map, it seems like the 2nd instance of Transistors is ignored, which causes some import errors down the road.
The issue happens here.
    for category in categories.values():
        if category.structural or category.ignore:
            continue
        for alias in category.aliases:
            category_map[alias] = category
        if category.name not in ignore:
            if category.name not in category_map:
                category_map[category.name] = category
            else:
                ignore.add(category.name)
                category_map.pop(category.name)

Given that the map is keyed by name rather than by path, this is not a simple fix. So in the meantime, I will rename my duplicate categories in InvenTree and add aliases if I ever import parts that match one of the renamed categories.
thank you!

Importing the complete DigiKey category structure into InvenTree is just an awful idea.

lol. the idea of a newbe for using the InvenTree system. I am starting to realize this now but I have a good amount of data entered and a goal in mind so cleanup will wait. In the meantime I renamed the duplicates to get around the issue and will select them as aliases when importing parts in that given category. At least this will document the issue if someone was to stumble on the same problem

(Will keep this open, as it's still a bug, but I don't really have time to tackle this, thus the wontfix tag).


Build instructions for macOS

Can you update the build instructions to include macOS? Thanks

Never mind - I should have read the main page better...


Stop using an FFI representation for unit/empty shared structs

Right now if you define a shared struct
#[swift_bridge::bridge]
mod ffi {
    struct SomeStruct;
}

We generate an FFI representation that looks something like this:
#[repr(C)]
struct __swift_bridge__SomeStruct {
    _private_: u8,
}

impl swift_bridge::SharedStruct for SomeStruct {
    type FfiRepr = __swift_bridge__SomeStruct;
}

When passing SomeStruct across the FFI boundary, we create and pass a __swift_bridge__SomeStruct.
This is unnecessary since we control both sides of the FFI boundary.
For example ... say you have
#[swift_bridge::bridge]
mod ffi {
    struct SomeStruct;

    extern "Rust" {
        fn reflect(arg: SomeStruct, num: u8) -> SomeStruct;
    }
}

We should generate things like:
// Notice how the FFI function doesn't take a `SomeStruct` argument.
pub extern "C" fn __swift_bridge__reflect(num: u8) {
    super::reflect(SomeStruct, num)
}

The same idea would go for function return types.
Benefits

We no longer need a weird FFI representation for empty structs

We can add a BridgeableType.is_zero_sized_type() -> bool method so that other ZST's (like ()) can benefit from this solution.

Closed via #178

Still to stop generating the FFI #[repr(C)] representation when struct is empty. Then we can close this.


Hints on tooling to implement 'partial responses via filtering'

Hi, I would like to implement  'partial responses via filtering' (using the fields query parameter) in my Spring Boot REST services but I could not find any Spring / Jackson build in functionality or add-on libraries to do it. As you refer to Spring/Java in your API guidelines in some places, I was wondering how you have implemented it.
Best regards,
Julian

We actually have a Java/JavaScript library for this, that was retracted already 5 to 6 years ago. It was using simple filtering on top of the response. However, we do not think that this is a proper approach to provide this feature, since it resolves much more information from the database than it needs to.
Internally we advise our users - if possible - to filter the data at the source instead of applying a post filter because of the way higher efficiency. I also advise in talks and reviews to focus the usage of filter and embed to distinct high value use cases, where the effect compared to the effort and costs creates the maximum benefit.

Thanks  a lot for you answer!
So an example of "filter the data at the source" would be to transform the fields query into an sql projection and then use e.g. Java Optional fields to filter out uninitialized fields in the response payload?
You mentioned  filter-sets. What do you mean with "sets"? Something predefined?

@sareykaj Yes, I used the term filter-sets and embed-combinations to describe that I suggest to provide a list of valid filter and embed keyword combinations that are supported instead of allowing the full might of the expression language defined. This is especially simple, if the properties that are disabled or enabled by the embed or filter are already structured into objects in the response.


When is the mitsuku-api implementaion getting back into the repo?

HI,
Why is the mitsuku-api removed from the repo?
How are the default chat commands handled in the current implementation?
Thanks & Regards

Hi there, you can find the legacy v2.0 (Jarvis)'s code from the tags. Just updated the README regarding this.


FlatButton produces inconsistent padding and margin on iOS vs web.

import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Material App',
      home: Scaffold(
        appBar: AppBar(
          title: Text('Material App Bar'),
        ),
        body: Container(
          width: double.infinity,
          padding: EdgeInsets.symmetric(horizontal: 15.0),
          child: FlatButton(
            child: Text('Title'),
            onPressed: () {},
            color: Colors.red,
          ),
        ),
      ),
    );
  }
}

Produces two very different results on iOS vs web.

Here is my flutter doctor output:
✓] Flutter (Channel beta, 1.23.0-18.1.pre, on Mac OS X 10.15.7 19H2
    x86_64, locale en-US)
    • Flutter version 1.23.0-18.1.pre at
      /Users/jameswasher/development/flutter
    • Framework revision 198df796aa (4 weeks ago), 2020-10-15
      12:04:33 -0700
    • Engine revision 1d12d82d9c
    • Dart version 2.11.0 (build 2.11.0-213.1.beta)

[✓] Android toolchain - develop for Android devices (Android SDK
    version 29.0.3)
    • Android SDK at /Users/jameswasher/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.1, Build version 12A7403
    • CocoaPods version 1.9.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google
      Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.7761
    • Java version OpenJDK Runtime Environment (build
      1.8.0_212-release-1586-b4-5784211)

[✓] VS Code (version 1.51.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (3 available)
    • iPad Pro (12.9-inch) (4th generation) (mobile) •
    • Web Server (web)                               • web-server
      • web-javascript • Flutter Tools
    • Chrome (web)                                   • chrome
      • web-javascript • Google Chrome 86.0.4240.183

• No issues found!

@jameswasher
Flatbutton widget has been deprecated. Please see this official documentation and new equivalent widget recommended instead is TextButton.
You may try with TextButton widget and see if it still produces same behavior.
Thanks.

I was able to fix this by setting the visualDensity on the ThemeData to VisualDensity.standard.  I'm not sure why I didn't have to do that before Flutter 1.23.

Hey, I still got this inconsistent visual issue on Android and Web even after migrating my FlatButton to TextButton. I've tried @jameswasher 's solution too but got no luck. Any idea?
[✓] Flutter (Channel beta, 1.22.0-12.1.pre, on Mac OS X 10.15.7 19H2, locale en-ID)


[CircleCi] Update bootstrap compiler to 2.072.2

Bump CircleCi bootstrap compiler to 2.072.2 - it should be in sync with the dmd repo. I also did a minor cleanup of the CircleCi files.

Where do we still test bootstrapping with 2.068 (last C++ compiler)?

This is just a follow-up to https://github.com/dlang/dmd/pull/6411
However, it seems that even for Travis we don't test bootstrapping with 2.068 anymore: https://github.com/dlang/dmd/blob/master/.travis.yml

I also added a soft retry loop for the CodeCov script as there were some errors in the last days.
For DMD & Druntime the respective CircleCi.sh changes are here:
https://github.com/dlang/dmd/pull/6053
https://github.com/dlang/druntime/pull/1725

I hope that we can soon integrate the style checks with new Dlang CI, s.t. we don't need need this upgrade
See also: https://github.com/Dicebot/dlangci/issues/18


'if eq' in go template

While trying to add conditional lines to the frontend http-in section of haproxy_template.cfg based on an Env variable from marathon, the following code:
{{ if eq $app.Env.SOME_VAR "bar" }}
        acl {{ $app.EscapedId }}-aclrule {{ $service.Acl}}
        use_backend {{ $app.EscapedId }}-cluster if {{ $app.EscapedId }}-aclrule
        {{ else }}
        # ignoring, SOME_VAR={{app.Env.SOME_VAR}}
        {{ end }}

gives "error calling eq: invalid type for comparison"
Searching the net has not been fruitful, any suggestions please?

+1 for this; Right now it seems like I can only tell if an ENV exists or not.  I have not been able to figure out any way to do comparisons.

FYI, for anybody that might have a similar issue
  {{ if $app.Env.BAMBOO_STICK_SESSION }}
    {{ if eq $app.Env.BAMBOO_STICK_SESSION "foobar" }}
       # foobar
    {{ end }}
  {{ end }}

This works.  You have to check for the existence of the var prior to comparing it.

Ah, good point! thx.

You can also do:
    {{ if eq (default $app.Env.BAMBOO_STICK_SESSION "foobar") "foobar" }}
       # foobar
    {{ end }}

FYI, for anybody that might have a similar issue THIS ALSO WORKS
    {{ if eq (or $app.Env.BAMBOO_STICK_SESSION "some useless value or nothing at all") "foobar" }}
       # foobar
    {{ end }}

This works. You have to check for the existence of the var prior to comparing it.
what seems to be happening... is that  {{ if eq $app.Env.BAMBOO_STICK_SESSION "foobar" }}  if $app.Env.BAMBOO_STICK_SESSION resolves to undefined then an exception is thrown, however, in my example if the variable is empty or nil then it is assigned the or value.


502 on /germany EP

The /germany Endpoint throws a 502 Server error.

EDIT: The whole API is affected :(


New version: MeshCatMechanisms v0.7.1

Registering package: MeshCatMechanisms
Repository: https://github.com/JuliaRobotics/MeshCatMechanisms.jl
Created by: @rdeits
Version: v0.7.1
Commit:<PHONE_NUMBER>d84d92b4807828643ae62f9d89e5a9
Reviewed by: @rdeits
Reference: https://github.com/JuliaRobotics/MeshCatMechanisms.jl/commit/8391842119d84d92b4807828643ae62f9d89e5a9#commitcomment-37839787

Ah, sorry. I forgot I'd already bumped the version. Please close this, and I'll open a PR to tag the correct version.


Feature : Enhancing UI of What our customers think section

Issue Template
Description
Your What our customers think section is not looking good UI.
I wanted to create its UI using Card Component and swiper.js  Like from this -

to this -

I will mainain your website background them and content with font-styles.
assign issue under gssoc and hactoberfest.

thanks for your interest @VinayLodhi1712 , but the current one is enhanced one with one of the contributors. so there's no plan of re-enhancing it. sorry about that.


How can i mock broker ?

in my project system, pulsar is core part. so we need test unit to promise code is correct. but i don't know how to mock pulsar. can offer shou some example about it. we need mock pulsar broker .

@codelipenghui @jiazhai Can you provide some guidance on mocking Pulsar broker?

https://github.com/streamnative/aop/blob/master/tests/src/test/java/io/streamnative/pulsar/handlers/amqp/AmqpProtocolHandlerTestBase.java

@zhijianfree Can you check the example that Jia shared?

Closed the issue since Jia has provided the example. If it is not sufficient, please reopen the issue.


Collaborative gameplay

Is it possible for two people to play in the same room? If so, I would like to request, and possibly help implement this feature. I imagine that the inputs from both clients would be sent such that a single game is controlled by both.
Thank you!

Hi @smasher164,
Yes, that feature is definitely the one I'm looking for!! It is a possible thing that can enhance the gaming experience. It is awesome that we can bring online gaming to retro game.
That logic of collaborative gameplay was in the code before but after some interaction, it is not maintained and not worked anymore.
The flow I'm looking for is:

The first user runs a new game.
That user share the game (Click share button. Sharable link is copied to clipboard)
The second user joins the same game by accessing that sharable link
4.1) The second user will use W,A,S,D, H,J,K,L.
4.2) The second user's input still use Arrow Key and ZXCV. These key are later mapped to second controller in the code.

Currently, The code supports 1,2,3. I think you can pick either 4.1 or 4.2 approaches. 4.1 is easier when you don't need to know if the player is the first or second because arrow keys and WASD are separated, you can just send the input as it is. 4.2 is harder because we need to determine the index of the player and do a correct input mapping.
You can take a look at those files
https://github.com/giongto35/cloud-game/blob/master/worker/room/room.go#L188 <- Input mapping can be done here
https://github.com/giongto35/cloud-game/blob/master/emulator/gameview.go#L195  <- NES Emulator second controller input
https://github.com/giongto35/cloud-game/blob/master/libretro/nanoarch/nanoarch.go#L79 <- Libretro Emulator input (you may not need to consider implement for this one, LibRetro is a generic emulator based on RetroArch)
https://github.com/giongto35/cloud-game/blob/master/static/js/ws.js#L274 (Legacy playerIndex)
I have some attempts to introduce playerIndex in the code. However, currently, playerIndex is from frontend payload and always set with 1. Feel free to make anychange on that
Thank you very much for your help :D

I think you can pick either 4.1 or 4.2 approaches.

Many games have both a single-player and local multi-player. 4.2 implies that we restrict controller input to the first or second controller input, unless we provided UI to distinguish the player index. 4.1 is the simplest option that doesn't introduce new UI. Both clients can use ZXCV🡑🡓🡐🡒 to control player 1, and HJKLWASD to control player 2.

It's correct. 4.2 requires extra logic to determine player index based on number of rtcSessions in that room. e.g: If there is already a player, the next user index will be player 2 and if there are already 2 players, the next one will be player 3. It can serve the multiplayer game with more than 2 users. In that way we don't need to introduce new UI.
I consider 4.2 is the ideal approach but 4.1 is much simpler and the result is still awesome. So if you can work on 4.1, I still really appreciate it.

Just to be clear, this feature request is for collaborative gameplay, not necessarily multiplayer. If I understand you correctly, 4.2 says "based on the number of rtcSessions, we can assign the next player to an index as player n".
However that implies that although this is legal:

Client
Player

1
1

2
2

3
3

This is not:

Client
Player

1
1

2
1

3
2

This feature request asks to make the second example legal. In order for two clients to have the same player number, I don't see how the number of rtcSessions can help. The client would have to explicitly specify the player number it wants to send its input as.

Got your point!
Yes, I know about TwitchPlaysPokemon. It's very interesting gameplay and can drag a lot of interaction. I hope to support both collaborative + multiplayer but seems like it's hard with current UI.
I think you can to move forward with collaborative, I really like to see it in action. Let me know if there is anything I can help to explain during the implementation.


[Card - pictogram] Design updates to improve mobile accessibility

Problem
Card - pictogram component  has a few issues:

When pictogram is bottom, a hover interaction reveals additional body copy. On mobile (no hover state), these additional body copy is never readable. We should have a new mobile design so the body copy is always revealed
When the body copy and card headline are long, hover interaction makes the card grow taller. This is probably because the card size is not calculated with those elements present at first. Might need a refactor?

Task

Look into additional of the designs for mobile design
Create logic for how the content edge cases should be handled

Additional information

Design spec: https://ibm.ent.box.com/folder/114042319288
Functional spec: https://ibm.box.com/s/hgvu48r1fv2ga2h0yn3qshrtxjc71vch

React version is behind a feature flag.  React component will not be updated.  No issues needed.
https://ibmdotcom-react-experimental.mybluemix.net/iframe.html?id=components-card--default&knob-Show pictogram (hides CTA)_Card=true&knob-Card Eyebrow_Card=Eyebrow text&knob-Card Heading_Card=Lorem ipsum dolor sit amet&knob-Card body copy_Card=&knob-CTA copy_Card=Card CTA text

Jeff will include agenda item in the engineering Huddle to talk about deprecating the Pure React version of Card - pictogram component.

Re: deprecating Pure react card pictogram @jeffchew @RobertaJHahn

I believe IBM Docs is using currently, so should we clear it with them first?
if we can get the Web component card pictogram fixed first, that would make it easier for deprecation first I hope

Design spec: https://ibm.ent.box.com/folder/114042319288
Functional spec: https://ibm.box.com/s/hgvu48r1fv2ga2h0yn3qshrtxjc71vch

This epic is complete


Misleading error message is displayed when updating Closed Elevate Recurring Donation

As a user I want to be able to edit non-Elevate fields on a Closed Elevate Recurring Donation from RD Edit Form.
Details and Steps to Reproduce
Test Steps:

NPSP Org connected to Elevate Int1 environment
Navigate to NPSP org and create a new contact
Navigate to recurring donations page and try to create a new recurring donation for an amount with value "50" and for the contact created in step#2
Wait for the RD details to display
From the top action buttons on the page, click close RD. Close the RD by providing a reason "Financial Difficulty"
Wait for the page to populate the status closed
click 'Edit' from the Quick Action and update any non-elevate related field

Expected:
The update goes through
Actual:
The error message: "Cannot read property of 'null'" is displayed

W-9580620


ux: update training profile prompts for clarity

updates text clarifying reset procedure
rewords misleading text about non-nvidia gpu support
enhances profile choices to be more human-readable
Issue resolved by this Pull Request:
Resolves #2028
Checklist:

[x] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[x] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

Amazing, great additions. This is so much clearer 🤘


Add MultipleMockRequestDispatcher

Please help keep the CHANGELOG up to date by providing a one sentence summary of your change:
Add MultipleMockRequestDispatcher to permit mocking multiple requests to the same client.

Looks like there were some async related changes that I will need to take into account. I'll try again after reworking.


Opentms incidents

Adding OpenTMS-Incident messages to the WZDx translator

Tested in RTDH Test
Added is_incident method to determine whether a msg is an incident and whether it has the correct metadata to be a work zone. Integrated into message translation to only process work zone incidents
Added create_description method to create new description when the 511 CARS error is present. Not rigorously defined, just thrown together, this was a low priority
Added and updated unit tests

@payneBrandon This is a fairly minor update to the planned events translator. I have tested the change in RTDH Test, and Tony wants me to get my latest changes into Main so that we can publish some of the code/documentation


ModuleNotFoundError: No module named 'tree'

I've tried installing this on several different OS environments. With and without Conda. And I encounter the same python error. It seems I am not able to import a module named tree. I thought this was a typo in importing through sklearn but this is not the same decision tree type module. Please help.

Hi, I believe the environment is missing the package dm-tree, e.g. https://github.com/aqlaboratory/openfold/blob/main/environment.yml#L35

That resolved the issue for Linux thank you.


(PUP-4242) change deprecation for namespace mismatch to an error.

@Magisus we need to do SERVER-2218 before we take this change into our dev environment.

CLA signed by all contributors.

This PR does not do what the title says "change to an error" since it uses the strict setting making it possible for users to turn it off, get a warning or error.
If the intention is to actually make it an error, then there is no need to configure it at all since the default for a reported issue is to error. If there is a desire to be explicit, rather than removing the entire line where it used to set :deprecation, it can be set to :error to always error.
The tests do test that it is controlled by strict flag - so... is it just the title of the PR that is wrong and we want Puppet 6 to have this configurable?

@hlindberg, @joshcooper what is the appropriate level of error for this issue?  My changes are based on other issues found in lib/puppet/pops/validation/validator_factory_4_0.rb, which were the same as an earlier PR which was reviewed and merged, so I did not ask for further feedback.

Since the issue is set to :deprecated in 5.y I assumed it would be a hard error in 6.0.0 and not under user's control. In fact, making it be under the control of the strict flag makes it more relaxed than 5.y since there it is a hard deprecation. I made a comment on the ticket as well - a decision is needed (on the ticket).

👍 Could you squash the two commits, since the second commit is needed to make the first commit pass?

@joshcooper squashed.

AppVeyor timed out - restarted


fseeko and ftello for 64bit file support.

Remaining issues on 32bit OS #4075:
Use the 64bit capable fseeko and ftello to allow file sizes larger than 2G

@freerdp-bot come on, test

@freerdp-bot test please


Remove pure from all non-ghost interface methods

and introduce spec (ghost + pure) functions instead

Same as #226

Introduce LenSpec and TypeSpec for Len and Type in Path


Windows build fails: cannot open include file 'netinet/in.h'

Godot version:
master b07a3f503b75831414f92d2cc6886d045eeb96fb
OS/device including version:
Windows 10
Issue description:
Windows build fails, even with clean build. Worked before #44433 was merged. cc @akien-mga
C:\Users\mbr\Documents\Projects\godot\thirdparty\wslay\wslay_net.h(38): fatal error C1083: Cannot open include file: 'netinet/in.h': No such file or directory
C:\Users\mbr\Documents\Projects\godot\thirdparty\wslay\wslay_net.h(38): fatal error C1083: Cannot open include file: 'netinet/in.h': No such file or directory
scons: *** [thirdparty\wslay\wslay_net.windows.opt.tools.64.obj] Error 2
scons: *** [thirdparty\wslay\wslay_event.windows.opt.tools.64.obj] Error 2
scons: building terminated because of errors.

I can reproduce the issue with MSVC too, I think my changes made it so that the modules build now use an incomplete environment, without the relevant config to target Windows 7+ APIs, which means that these headers are not available.
I'll fix it.


Implementation URL in CapabilityStatement does not respect X-Forwarded-Host

We have a problem with caching in AnalyticsServerCapabilities.
If you take a look at one of the /fhir/metadata endpoints in production, you will see that http://localhost:8080 is reported as the implementation URL. This happens even if the X-Forwarded-Host and X-Forwarded-Proto headers are correctly set.
I think the reason for this is caching within the HAPI RestfulServer implementation with respect to CapabilityStatements. The first request to the CapabilityStatement (which is probably from Docker, not containing the proxy headers) is cached for all subsequent requests.
There does not seem to be an obvious way to disable the caching within the public API of HAPI, i.e. IServerConformanceProvider.

Yep, HAPI caches the capability stmt by default.  We have code in Ontoserver that avoids this.
Michael

From: John Grimes<EMAIL_ADDRESS>Sent: Friday, April 10, 2020 9:25:15 AM
To: aehrc/pathling<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [aehrc/pathling] Implementation URL in CapabilityStatement does not respect X-Forwarded-Host (#19)
We have a problem with caching in AnalyticsServerCapabilities.
If you take a look at one of the /fhir/metadata endpoints in production, you will see that http://localhost:8080 is reported as the implementation URL. This happens even if the X-Forwarded-Host and X-Forwarded-Proto headers are correctly set.
I think the reason for this is caching within the HAPI RestfulServer implementation with respect to CapabilityStatements. The first request to the CapabilityStatement (which is probably from Docker, not containing the proxy headers) is cached for all subsequent requests.
There does not seem to be an obvious way to disable the caching within the public API of HAPI, i.e. IServerConformanceProvider.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/aehrc/pathling/issues/19, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAGDWXWAWJQ6B4XBAB6ZMADRLZKNXANCNFSM4MFDAE6A.

In the newest version of HAPI, the @Metadata annotation has a cacheMillis parameter, which can be set to 0 to disable caching.


Update links in Wiki for Python and JS

This is part of the "Move docs out of MicrosoftDocs team" epic.

We're not going to get to this anytime soon.  This isn't blocking anything currently.


Unable to manage several releases parameters

Hi,
Suppose I have 2 (or more) components named comp1 and comp2. Each of these components has a log-level parameter in their values.yaml
I want to use environment concept. For that, I create a file associated with each environment.
In the prod environment file, I want to set log-level parameter to info for comp1 and log-level parameter to debug for comp2.
It seems, it is not possible because the value are not organized by component.
Am I clear ? Am I wrong ?

Just above an example to be clearest :
I use the following directory structure
helmfile.yaml
|--elastic
|-- elastic.yaml
helmfile.yaml content
helmfiles:

path: "elastic/elastic.yaml"
values:

name: mdh69

elastic.yaml content
repositories:
Official helm charts

name: "hardis"
url: "https://chart.hg-as.io/"

releases:

name: "elastic-{{ requiredEnv "NAME" }}"
chart: "hardis/esoperator"
version: 0.1.0
wait: true
hooks:

events: ["presync"]
command: "/bin/sh"
args: ["-c", "kubectl get crd elasticsearches.elasticsearch.k8s.elastic.co >/dev/null 2>&1 ||
kubectl apply -f https://download.elastic.co/downloads/eck/0.9.0/all-in-one.yaml"]

==> The value of the variable name is not take into account
If I modify the elastic.yaml file by the following content :
repositories:
Official helm charts

name: "hardis"
url: "https://chart.hg-as.io/"

releases:

name: "elastic-{{ requiredEnv "NAME" }}"
chart: "hardis/esoperator"
version: 0.1.0
wait: true
hooks:

events: ["presync"]
command: "/bin/sh"
args: ["-c", "kubectl get crd elasticsearches.elasticsearch.k8s.elastic.co >/dev/null 2>&1 ||
kubectl apply -f https://download.elastic.co/downloads/eck/0.9.0/all-in-one.yaml"]
values:
name: mdh69

The value of name is taking account.
My objective is to propose to the OPS only ONE file to adapt even if the stack is composed of several components.

@mdh69-github Hey!
helmfile[].values and releases[].values has nothing to do with each other.
You'd need to update your elastic.yaml to something like the below. Look at the last two lines:
repositories:
  # Official helm charts
  - name: "hardis"
    url: "https://chart.hg-as.io/"

releases:
- name: "elastic-{{ requiredEnv "NAME" }}"
  chart: "hardis/esoperator"
  version: 0.1.0
  wait: true
  hooks:
  - events: ["presync"]
    command: "/bin/sh"
    args: ["-c", "kubectl get crd elasticsearches.elasticsearch.k8s.elastic.co >/dev/null 2>&1 || \
           kubectl apply -f https://download.elastic.co/downloads/eck/0.9.0/all-in-o
  values:
  - name: {{ .Values.name }}


⚠ ClamAV has degraded performance

In e8bb1a2, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 77 ms

Resolved: ClamAV performance has improved in 4cde4b7.


Font face never declared

What font face do you use for the demo screenshots?

It's likely Fira Code with ligatures enabled. :)


Changing HSV not working

Prior to running any command this is what I get running tplight details [ip]
"light_state": {
    "on_off": 1,
    "mode": "normal",
    "hue": 261,
    "saturation": 43,
    "color_temp": 0,
    "brightness": 45
We can see the HSV is 261, 43, 45 here.
After running the following code:
smartBulb.HSV.Hue = 222;
smartBulb.HSV.Saturation = 78;
smartBulb.HSV.Value = 91;
(Which is #3369e8 hex code converted into HSV), if I check the details of the bulb again it's still the same colour
 "light_state": {
    "on_off": 1,
    "mode": "normal",
    "hue": 261,
    "saturation": 43,
    "color_temp": 0,
    "brightness": 45
Am I using the command wrong to change values? here's the method
            var smartBulb = new TPLinkSmartDevices.Devices.TPLinkSmartBulb(bulbIP);
            smartBulb.HSV.Hue = hue;
            smartBulb.HSV.Saturation = sat;
            smartBulb.HSV.Value = val;
(hue, sat, val are rounded integers passed in after converting hex to hsv)

https://github.com/anthturner/TPLinkSmartDevices/blob/b4423be77b1273f83b1f61f2d1fd9a6d5dcba44c/TPLinkSmartDevices/Devices/TPLinkSmartBulb.cs#L33-L54
When changing the HSV on the bulb, all 3 properties are updated simultaneously. Because of that, the setter on the HSV property is what controls execution of the change. So here, you'd want to create a new BulbHSV object with your preferred values, then use the setter:
var preferredHsv = new BulbHSV()
{
    Hue = hue,
    Saturation = sat,
    Value = val
};
smartBulb.HSV = preferredHsv;

Now it's my turn to facepalm. I was looking at it for so long and didn't even think to create a BulbHSV obj. Thanks

Might have closed this prematurely.. I can see it's changing the HSV to 222/78/91 (as you see below)

But the HSV shown by the nodejs package (tplink-lightbulb) still shows the purple HSV?

(it's a bulb at a friends house but he has confirmed it's still purple)

@TheBauwssss any ideas on the above?

I don't own one of these lights, so I can't test or try it for myself. I can see that in the Refresh() method of the TPLinkSmartBulb class the value returned for Brightness (in the BulbHSV class called Value) is not the raw JSON value returned by the Smart Light Bulb. The returned value is the JSON value modified like this:
https://github.com/anthturner/TPLinkSmartDevices/blob/b4423be77b1273f83b1f61f2d1fd9a6d5dcba44c/TPLinkSmartDevices/Devices/TPLinkSmartBulb.cs#L120
When serializing the BulbHSV object back to JSON the modification is undone by the opposite of the operation:
https://github.com/anthturner/TPLinkSmartDevices/blob/b4423be77b1273f83b1f61f2d1fd9a6d5dcba44c/TPLinkSmartDevices/Devices/TPLinkSmartBulb.cs#L50
I think you need to modify your brightness value input in a similar way. If that does not work, off the top of my head I can think of two more possible things to try:

Checkout https://github.com/anthturner/TPLinkSmartDevices/commit/4bac4ceed59e7c09fcfb91ba43c3cabfe6e6def0 (before I made my changes adding support for the HS110) and see if that fixes the issue
Add a breakpoint to the JSON network handler (or just use Telerik Fiddler) and inspect the JSON values the API is sending to the Smart Light Bulb. Do those values confirm to the specification?

It is late and I am tired so my English might be severely compromised, or at least it feels like it is :D Anyhow, please accept my apologies for the grammatically questionable and weird English I might have used here and there. I can't think of a better way to put it into words without convoluting my sentences.
If this does not fix your issue, could you install Fiddler and send me a copy of the JSON payload your Smart Light Bulb returns to the API (through the Refresh() method) and a copy of the JSON object the API send the Smart Light Bulb?

I did try using Fiddler but it wasn't finding anything from my server.
This is the contents of the message sent to the bulb

(this is equivalent to #ff5c40)
Following the code I can see the HSV is 240, 75, 100 in subResult after executing the code

I spent almost an hour researching and typing my previous reply, please read it carefully and follow the steps/possible solutions:

Did you try setting the brightness value mapped from 0 to 1 instead of 0 to 255?

Did you try possible solutions 1 and 2 from my previous reply?

If you're not seeing that JSON come along in Fiddler then something else is wrong. Please follow my possible solution 2 and send me a complete dump of the JSON message the APi is sending and the JSON response the bulb sends back.

@TheBauwssss , what is this math supposed to do?
(int)(value.Value * 100 / 255)
Value = lightState.brightness * 255 / 100
Is that supposed to map a 0-1 value to 0-255 and vice versa?  If so, the math seems wrong, no?

@TheBauwssss , @pekempy
FYI, the below linked library works, but it's in Java.  Perhaps something can be learned from it, regarding this issue.
https://github.com/openhab/openhab2-addons/tree/master/bundles/org.openhab.binding.tplinksmarthome/src/main/java/org/openhab/binding/tplinksmarthome/internal

The issue is the "light_state" string being passed into the argument param here
https://github.com/anthturner/TPLinkSmartDevices/blob/b4423be77b1273f83b1f61f2d1fd9a6d5dcba44c/TPLinkSmartDevices/Devices/TPLinkSmartBulb.cs#L46
It is totally unnecessary and infact stops the state change ever beinge executed. You need to pass just the JObject as the value with no argument.

is this project dead ? this bug has been opened for 5 years but hasn't been fixed. I'm also having problems changing the HSV of my KL125 bulb

Hey there! Unfortunately, I have stopped using these devices and therefore don't have a test unit to use when changing code on this project. I appreciate your (and others') use of this library over the years and am more than happy to accept pull requests to integrate upstream. I'd love to continue helping keep this library relevant by accepting others' contributions. I appreciate all the stars, forks, follows, and other means of support throughout the life of this library and want to continue to facilitate the use of this project as long as I can.

ah that's too bad, I really wanted to do this in C#.  For now I'll be using https://github.com/python-kasa/python-kasa as the HSV setter works with my bulb. I'll try to see how they did it in the python project to see if it's easily fixable in the C# project, but I don't really know python :(


Feature: Support HashMap<_, _, ahash::RandomState>

I am wondering if we can support HashMap<_, _, hash::Random State> from https://docs.rs/ahash/latest/ahash/. pyo3 supports this type as well. BTW, thanks for your effort, and the library's really helpful!
error[E0277]: the trait bound `HashMap<i64, char, ahash::RandomState>: PyStubType` is
not satisfied
   --> crates/deepbiop-fq/src/python.rs:457:15
    |
457 |     id_table: HashMap<i64, char>,
    |               ^^^^^^^^^^^^^^^^^^ the trait `PyStubType` is not implemented for `
HashMap<i64, char, ahash::RandomState>`
    |
    = help: the trait `PyStubType` is implemented for `HashMap<Key, Value>`

error[E0277]: the trait bound `HashMap<std::string::String, Predict, ahash::RandomStat
e>: PyStubType` is not satisfied
    |
459 | ) -> Result<HashMap<String, Predict>> {
    |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `PyStubType` is not implemented
for `HashMap<std::string::String, Predict, ahash::RandomState>`, which is required by
`Result<HashMap<std::string::String, Predict, ahash::RandomState>, anyhow::Error>: PyS
tubType`
    |
    = help: the trait `PyStubType` is implemented for `HashMap<Key, Value>`
    = note: required for `Result<HashMap<std::string::String, Predict, ahash::RandomSt
ate>, anyhow::Error>` to implement `PyStubType`

For more information about this error, try `rustc --explain E0277`.

Added in #55 , and released as 0.5.2. Thanks feedback!

Thanks very much!


Missing Train_DDP

When i try to  run 'python train_prior.py' i get this:
No such file or directory: 'AccoMontage3/prior_model_VQ-Q&A-T/train_DDP.py'

Is the file train_DDP.py just not there or do i have to download that dependency that i missed?

Thanks for the feedback. Some files were renamed but the training script is not yet updated.

Line 222 should be readme_fn = './train_prior.py'. The purpose is to save this training script itself so that some settings (hyperparameters, etc.) can be reviewed later on if needed.

Line 34 should be PRETRAIN_PATH = "data_file_dir/params_qa.pt". The purpose is to load the pre-trained Q&A model.

Line 49 (lmd_dir) also needs to be reconfigured. The data here is currently missing. I will check the code and upload the data by late April.


parser: fix alter_stmt order by syntax

What problem does this PR solve?
Fix ORDER BY syntax. Issue: https://github.com/pingcap/parser/issues/499
MySQL Syntax:
alter_specification:
...
  | ORDER BY col_name [, col_name] ...

Bad SQL Case:
ALTER TABLE t_n ORDER BY ident

Check List
Tests

Unit test

Code changes

Has exported variable/fields change
Has interface methods change

Related changes

Need to update the documentation

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Rambo seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@tangenta PTAL


Support the Navigation API

What problem does this feature solve?
Chromium 102 has been released stable, which means that Chrome, Edge, Opera, Brave, Vivaldi, etc and Electron supports the Navigation API
https://chromestatus.com/feature/6232287446302720
The Navigation API is the successor of the History API and is better suited for SPAs.
Therefore, routers should allow to target and leverage it.
Why should this feature be included?

The existing window.history API is hard to deal with in practice, especially for single-page applications. In the best case, developers can work around this with various hacks. In the worst case, it causes user-facing pain in the form of lost state and broken back buttons, or the inability to achieve the desired navigation flow for a web app.

What does the proposed API look like?
see the spec https://chromestatus.com/feature/6232287446302720

I'm aware and active in the open discussion of the API and it's still too early to adopt. It will be adopted possible.


VC's termOfUse type clarification

According to the https://www.w3.org/TR/vc-data-model/#terms-of-use termsOfUse property MUST specify one or more terms, but in the code https://github.com/spruceid/ssi/blob/main/ssi-vc/src/lib.rs#L76 it is represented exactly as Vec. Maybe OneOrMany type is more appropriate in this case?

Sounds cool. I will do.

Thank you, released as part of ssi-vc v0.2.1


[Feature] Track committee size.

This PR:

tracks the committee size in a metadata mapping.
enforces that the committee size does not exceed 200.
enforces that the number of delegators does not exceed 100_000.

The benches/rewards branch measures the performance of atomic_post_ratify for various numbers of delegators distributed uniformly over 200 validators.
On a 2021 M1 MAX:
DB: `atomic_post_ratify` with 0 delegators and 200 validators
                        time:   [81.338 ms 84.660 ms 94.507 ms]

DB: `atomic_post_ratify` with 1000 delegators and 200 validators
                        time:   [363.47 ms 385.06 ms 425.20 ms]

DB: `atomic_post_ratify` with 10000 delegators and 200 validators
                        time:   [2.8112 s 2.8222 s 2.8336 s]

DB: `atomic_post_ratify` with 100000 delegators and 200 validators
                        time:   [27.545 s 27.862 s 28.284 s]

Hi @randomsleep thank you for the extra heads up. Just FYI we've seen the issue, great finding, we will circle back on HackerOne.


Node stops working in execution stage when block has no ommers

Describe the bug
The node stops working an errors with the following message when no ommers are found for a block
2022-12-29T15:53:36.179031Z ERROR execute{stage=Execution}: Stage encountered a fatal error: A database integrity error occurred: Block ommers not found for block #1. stage=Execution
2022-12-29T15:53:36.179087Z ERROR Error: A stage encountered an irrecoverable error.

Caused by:
   0: A database integrity error occurred: Block ommers not found for block #1
   1: Block ommers not found for block #1

Steps to reproduce
The bug was found when playing around to sync up to block 5
https://etherscan.io/block/5
To reproduce, run
RUST_LOG=info,sync::stages=trace,downloaders=trace cargo r --release -- node --debug.tip 0xf37c632d361e0a93f08ba29b1a2c708d9caa3ee19d1ee8d2a02612bffe49f0a9

Node logs
2022-12-29T15:53:36.179031Z ERROR execute{stage=Execution}: Stage encountered a fatal error: A database integrity error occurred: Block ommers not found for block #1. stage=Execution
2022-12-29T15:53:36.179087Z ERROR Error: A stage encountered an irrecoverable error.

Caused by:
   0: A database integrity error occurred: Block ommers not found for block #1
   1: Block ommers not found for block #1

### Platform(s)

_No response_

### Code of Conduct

- [X] I agree to follow the Code of Conduct

closing this :)


Fix failing accessibility tests

The tests failed because the accessor was shown in the display string.
Removing the accessor was not as easy as I hoped. The problem was that
the private[x] keyword is not represented as a flag. The only way to
know that a symbol is private for a package is by checking if it has no
other visibility.  This meant that the already existing flag mask
couldn't be used, since the private keyword just couldn't be masked out.

I fixed it by adding another parameter showAccessor, which needs to be
set to false when the accessor shouldn't be shown. For public, protected
and normal private visibility it is also possible to mask the flags with
the flagMask parameter. Just not for private[x].

Superseded by #1035


Vulnerability roundup 51: samba-4.7.10

samba-4.7.10: 2 advisories
search, files

[ ] CVE-2018-1050 (unstable)
[ ] CVE-2018-1057 (unstable)

According to samba all version >4.7.6 include the patch for CVE-2018-1050: https://www.samba.org/samba/security/CVE-2018-1050.html

And the same applies for CVE-2018-1057: https://www.samba.org/samba/security/CVE-2018-1050.html

We are safe for 18.03, 18.09 and current master


Can the week start on Monday instead of Sunday?

Example:

Can it start on monday?

you can, the start of the week is determined by the localizer. when using the included ones the week will start at the appropriate day for the chosen culture.
if you want to change it yourself to something non standard for a culture {such as always setting it to monday) you can look at how localizer work, and edit/create your own since they are pluggable

I'm not sure but this seems that it's not working anymore and there is a bit of inconsistency from docs and github repo.
In the docs http://intljusticemission.github.io/react-big-calendar/examples/index.html#intro
import BigCalendar from 'react-big-calendar';
import moment from 'moment';

// Setup the localizer by providing the moment (or globalize) Object
// to the correct localizer.
BigCalendar.momentLocalizer(moment); // or globalizeLocalizer

I tried this also with moment.locale('en-GB') before passing the object.
Then I checked the master repo and seems different:
BigCalendar.setLocalizer(
  BigCalendar.momentLocalizer(moment)
);

Both of them are not working for me anyway, the week is always starting on Sunday when it's supposed to start on Monday.


strung.match crashing

And I'm having difficulties figuring out why. In large scale project I call require("strung").install() early on during initialize and I always crash here:
https://github.com/CapsAdmin/goluwa/blob/master/.base/lua/modules/lj-opengl/init.lua#L165
where line is
"VOID wglBlitContextFramebufferAMD (HGLRC dstCtx, GLint srcX0, GLint srcY0, GLint srcX1, GLint srcY1, GLint dstX0, GLint dstY0, GLint dstX1, GLint dstY1, GLbitfield mask, GLenum filter)"
but isolating this does not crash so it may be a garbage collection thing. I'm using latest luajit 2.1 from the git repo.

This crash does no longer happen and I'm not sure what fixed it. My framework has gone through a lot of change and there's been a few updates to luajit as well since. :)


Create a simplified kepler API.

Based on the API described here.
Todo:

[x] Currently creates a new orbit each time. Once the orbit URI work is complete we can deterministically generate the orbit id and therefore will be able to connect to the same orbit from different dapps without needing to store anything client-side.
[x] ~Discuss and come up with appropriate types for the response from the orbit methods (or is the fetch Response type sufficient?)~ ~Sam agreed on slack that the fetch Response is appropriate, and I believe Kelsey and Charles previously agreed on this type too.~ See new design in the proposal above.
[x] Refactor the codebase so that this is the only way to use the sdk. This can be done once the orbit URI and capability changes are done.

it makes sense, no semantic or logical reason the peer permission can't be delegated alongside read and write

it makes sense, no semantic or logical reason the peer permission can't be delegated alongside read and write

FYI - when trying to do this I couldn't work out how to construct the invocation to contain the generated peer ID. In the SIWE authn, the peer id is stored in the URI field, but I couldn't work out what the analogue for that is in the zcap authn.

bit of misleading code there, that message is actually a delegation, so the URI is the delegate/peer. in the zcap delegation the equivalent is invoker (but might soon change to controller)

I would recommend we don't restrict the mime types when putting, as I think there's no reason we should prevent users from uploading any type they want and it doesn't make it easier to use.

Spoke about this in the Kepler meeting. To clarify, the put function doesn't restrict mime types, it just only knows how to construct blobs for certain types:

If you do orbit.put(key, value, { type: "text/<text-type>"}), then the sdk will store a new Blob([value], {type: 'text/<text-type>'}).
If you do orbit.put(key, value, { type: "application/json"}), then the sdk will store a new Blob([JSON.serialize(value)], {type: 'application/json'}.
If you do orbit.put(key, value), and value.constructor.name === 'Blob', then the sdk will just store that blob.
Otherwise the sdk will error as it does not understand how to store the value you have provided.

This gives us the flexibility to support other types directly in the future, but for now users would need to construct a Blob themselves if they want to store something that isn't text or json.
The alternative would be providing 3 put functions, one for each of text, object and Blob. IMO this would make the code simpler and more obvious at the expense of a slightly broader API, so if there is an appetite for that I would happily switch. Opinions? @wyc @skgbafa @chunningham

For @skgbafa and anyone else who wants to test this, this branch is currently dependent on the fat_packaged version of didkit, which can be built by running this script:
https://github.com/spruceid/didkit/blob/feat/fat_bundle/lib/web/fat_bundle.sh

After more testing and discussions with Simon, we decided the best option would be to vendor the didkit fat pkg here until we figure out and resolve the async import issue.

Linter and .nvmrc added. Will address the publishing of the docs in a future PR.


Parent sidebar should reselect item when child sidebar is closed

Steps to Reproduce:

Click on a node
Click on a tensor or connection
Close the tensor or connection sidebar
The node is not reselected on the graph in the same way you'd expect if you clicked on a node through a connection sidebar

@kylesayrs can you submit pull requests to address these issues.
#1298


Update list.dart

Line 745 .
Added the value of words.asMap() as a comment
it allows to have an idea of the result of the use of the asMap function.

Review in https://dart-review.googlesource.com/c/sdk/+/174940


Typo in the Readme  of the condor pytorch

Creating the conda environment and loading it
conda env create -f environment.yaml
The File extension is wrong it seems .  environment.yaml -->  environment.yml

Thank you @rohithagaram. It is fixed.