[making wav2letter compatible with cuda 11.1]

Hello,
cuda11.1 is the latest version of cuda, can you please make wav2letter compatible with it?

Duplicate of https://github.com/facebookresearch/flashlight/issues/357. Will track in that.


feature ideas from 7/20 test

stopdragging out
** auto-scroll clue
enter backwards clues easier
shift words left/right?
click on third one and type in answer
add sync
** making it type like nyt

label row number and letters
scrolling to see clue

lost underscores in pasting _____

when you mark a word on grid, it removes the clue
confused about whether I was on a band or a row
tab goes to next clue
confetti
delete
fix highlight

verify solution


file titles being showed wrong color as if they are not committed in git, in windows 10

Type: Bug
Some file titles of a opened folder(which is a windows 10 folder) are showed in yellow(the dirty color that mark file changed but not commited in git), which is wrong since they are already commited.
 Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

/gifPlease

blob:https://gifcap.dev/144e8232-4fea-47df-9103-2ad6315d9712

@zzzh, could you just attach a screenshot? Thanks!

@zzzh, could you just attach a screenshot? Thanks!

Sure, here it is:

@zzzh, are you able to reproduce this issue with extensions disabled? I am asking as any extension can contribute file decorations so I just want to make sure that those are not contributed by other extensions.

@lszomoru , sure, I did that by calling "code --disable-extensions", seems the problem still exists, look the picture:

@zzzh, could you hover over one of the tabs that has the "M" file decoration? Also, I am not recognising the product icon for the "Source Control" view (last icon in the activity bar). Are you sure that all extensions are being disabled? Thanks!

@zzzh, could you hover over one of the tabs that has the "M" file decoration? Also, I am not recognising the product icon for the "Source Control" view (last icon in the activity bar). Are you sure that all extensions are being disabled? Thanks!

Of course, here it is:

@zzzh, could you share a screenshot of the "Source Control" view? File decorations are being created based on the resources in the "Source Control" view. Do you have multiple git repositories in the folder/workspace?
Also, are you able to reproduce the issue with the latest VS Code Insiders release? Thanks!

@zzzh, could you share a screenshot of the "Source Control" view? File decorations are being created based on the resources in the "Source Control" view. Do you have multiple git repositories in the folder/workspace?
Also, are you able to reproduce the issue with the latest VS Code Insiders release? Thanks!

As I remember, there's only 1 git reposit in the folder, I used to switch between 3 terminals: PowerShell, command prompt and git bash, does that matter?
My vscode was set to update itself automatically, so I guess it's already the latest.
Here's the about info of vscode:

@lszomoru
I got it, there's another git repository in lib folder, I created it before then forgot..
It looks good now after I remove it.
Sorry for the disturbance, my apologies.

@lszomoru
It's all because .git can't be seen, not in vscode, nor in file explorer.
So I think make .git viewable or mark a git repository folder with a special logo should be a good idea.

Thanks for the update. Glad you were able to track down the issue.


Create Home Page and Navbar

Value definition
As a Roleplayer
I want to open the App and see the possibilities to navigate through the App and can click a button to switch the Page, so that I can switch to the Page I prefer to see/ use.
Description

(the Button "Dice" is not relevant for now!)
Acceptance criteria

[ ] The buttons must be clicked and navigate to the right page
[ ] The buttons must have a hover effect to show it is clickable
[ ] The buttons must change their color when the right page is showing
[ ] The buttons need to be big enough to click it on a mobile screen with the finger
[ ] The buttons font must be readable

Tasks

[ ] Create a branch
[ ] Create and push first commit for upstream
[ ] Create grid for layout (Headline, Content, Navbar)
[ ] Create Navbar-Component
[ ] Create Button-Components on the Content section for the pages
[ ] Create Page files in project for navigating
[ ] Link the Buttons to the corresponding page
[ ] Copy and paste the Layout/ Navbar to all pages

Complexity
medium

Hey there! Impressive that you already created your first user story! I have a little bit of feedback, though. Also - this wouldn't actually be your first user story in terms of what you start with.
A general note:
You wouldn't actually start with a home page and navigation. At present, you can't meet your own acceptance criteria, because there isn't anything to navigate TO yet. I understand the want to start with the page you see first when you open the app, but instead you'd start with your core feature: the character form. Your first concern is getting data to display. If you're ever wondering where to start: it's all in the abbreviation CRUD. ;)
The idea is that every user story is supposed to provide the user with a fully functioning app. Obviously, the first version of your app (after the first user story is done) will be very limited in what it can actually do, but that's how you'd want to go about it. Hence the note about starting with the form first, because that's something the user can actually use once it's done. If that's not super clear yet, we can talk about it a little more.
Here are a couple more specific notes:

"As a Roleplayer
I want to open the App and see the possibilities to navigate through the App and can click a button to switch the Page, so that I can switch to the Page I prefer to see/ use."

I think replacing User with Roleplayer is a cute idea, but strictly speaking, that's something you wouldn't necessarily change. It's not wrong, just unusual. I would perhaps shorten the sentence following, like so: "As a Roleplayer, I want to see a home page when I start the app, as well as a navigation I can easily access." Something like that, as short and concise as you can make it.

(the Button "Dice" is not relevant for now!)

No need to include it then. ;) As far as user stories, code reviews, QA, etc are concerned - don't include things that aren't part of the feature, don't commit commented out code, and so on.
Do you perhaps have any acceptance criteria for the home page as well? Maybe something to do with accessibility, being able to see everything, ...
Regarding the tasks, there's differing opinions regarding whether or not to include steps such as "create a branch"/etc as part of your tasks. I suppose it's up to you whether you want to be as specific, but personally I don't think it's absolutely necessary. It can be assumed that that would be your starting point, and so on. If you want to include it, feel free to do so, though! :)
Don't get discouraged by how nit-picky I'm being, it's still all part of the learning process! <3

I have switch my first two UserStorys, to have in Story 1 a MVP and update it in the Wireframes and a little bit in the information details!

closed #4


separate scalars for input types in typescript

Is your feature request related to a problem? Please describe.
Currently scalar field on input types use the same types as scalars on normal types.  It would be really useful to be able to use a separate map of scalars for input types.
My specific use case is that several of our scalars have normalization built in, so that the types that can be handled by internals of our graphql implementation are looser than those that are received from graphql. More concretely, resolvers can return looser types than those that the resolver will receive in its input arguments.
Some examples of this in our server implementation are:

for ID fields, internally everything is coerced to a string, so an input ID field will always be string, but a resolver for an ID field can return a string, number, or BigInt.
our custom DateTime scalar will always be a Date scalar in an input, but could be either a iso-date string, or a Date object when returned from a resolver.

Describe the solution you'd like
This could probably be implemented with a new inputScalar map in the plugin options that mirrors the scalar map.  When present, it would generate a InputScalar map that has the same behavior as the current scalars, and would be used for all scalars in input types.  When not specified, only the current Scalars type would be generated and both normal types and input types would use the same scalars type.
Describe alternatives you've considered

always generating an InputScalars map
just providing the looser types for scalras, and using type asserts or coercions on inputs in resolvers.
Writing a custom plugin

Additional context
I am happy to provide a PR to implement this, I just wanted to make sure this would be a reasonable change that would be likely to be accepted before spending too much time on it.

related: https://github.com/dotansimha/graphql-code-generator/issues/2588

@hayes, given the amount of time that has passed, I'm curious if/how you've solved this? We're asking ourselves the same questions right now.

For server side stuff we decided writing our schema using a code first approach was better, so I wrote https://giraphql.com/. For client side, I don't remember if this was solved.

@hayes  Thanks for letting me know!
@dotansimha  Would you be interested in a PR that solves this?

Without adding a new key it can be expanded as string | { input, output }.
I'd like to make a PR for this. Is there any other discussion I should be aware of? @n1ru4l @dotansimha


DM-33534: Fix errors in production-tools.

Sorry, I reviewed this prematurely; happy to take another look when you've finished debugging.

No worries @rra, it did take a handful of additional commits to debug but it's up and running now, so this PR is ready if you want to give it a check.


Train when dataset doesn't fit available GPU memory?

Given an imposed set of GPU devices (8x V100 16Go) and using DaskXGBClassifier, is there a way to train XGBoost on a dataset that exceeds available GPU memory?
Assuming I can't resort to distributed training and I'm being limited to this specific set of GPUs.
I've already tried the subsample option down to 0.1 and it's effective to a degree, but going any lower really hurts validation metrics. Is the only available option to get bigger global GPU memory?

Assuming I can't resort to distributed training and I'm being limited to this specific set of GPUs.

But DaskXGBCLassifier is using distributed training?

ve already tried the subsample option down to 0.1 and it's effective to a degree

Are you using the external memory version of XGBoost?

Sorry for the confusion. I'm using Dask XGBoost classifier but in a way that is "distributed" only across the multiple GPUs the machine I'm using is equipped with, not distributed over several machines.
Also, what are you referring to when mentioning the external memory version of XGBoost?

Also, what are you referring to when mentioning the external memory version of XGBoost?

Sampling directly doesn't reduce memory usage. But for GPU, one can use external memory version along with sampling to reduce memory usage.  See data iterator and GPU support. However, it doesn't work with distributed training and might not be able to train your data with only 1 GPU.


unable to change keyword for sending command to bard in v1.2.0

I tried to change the keyword from default !bard to say bard, or even empty/null in file bot.py. However it is not working. I still need to use !bard to wake up bard.
This is what I used, which removes the keyword completely.
self.bard_prog = re.compile(r"^(.+)$")
This is what I used, which changes the keyword to bard.
self.bard_prog = re.compile(r"^\sbard\s(.+)$")
I've not tested other new features, like session isolation yet.
Cheers.

How did you run the bot?

I run via docker compose up -d.
My compose.yaml file is like below. I've changed bot.py as above.
services:
app:
image: hibobmaster/matrixchatgptbot:v1.2.0
container_name: bardbot
restart: unless-stopped
env_file:
- .env
volumes:
- ./db:/app/db
- ./bot.py:/app/bot.py
networks:
- matrix

./bot.py:/app/src/bot.py

It works. Thanks.


Improper pluralization of octopus/stadium

Pluralization of octopus should be either "Octopodes" for the greek style, or "Octopuses" for the american style. Octopi is incorrect, though comonly misused.
https://english.stackexchange.com/questions/270/what-is-the-correct-plural-of-octopus/271
Similarly, plural for "stadium" should be "stadia".

Seems like it should be stadiums and not stadia though? https://english.stackexchange.com/questions/29060/what-is-the-correct-plural-of-stadium
Feel free to submit a PR to change "octopuses".


Normalise function does not work when deployed

index.js:159 Uncaught ReferenceError: setValue is not defined
    at normaliseProgram (index.js:159)
    at HTMLSelectElement.onchange ((index):40)

For some reason the setValue function isn't present in the deployed malbolge.js, but was there during testing.  This is probably due to the GitHub Action always taking the HEAD of the repo.
Actions:

Investigate why the setValue function has disappeared
Checkout an emSDK tag version and document it in the README for others

Reproduced locally, is indeed due to an emSDK version mismatch.  Fixing emSDK at the 2.0.6 tag.


Changed output from '/dev/stdout' to '-'

Hi guys,
Running the plugin thought Git for Windows bash interpreter fails with a '/dev/stdout' redirect so I have changed this to a more conventional '-' which tests fine in Windows.
Regards,
Mark.

@mgrlabs thanks for the PR! I've pinged @lox for feedback, but looks pretty good to me!

Sounds good to me!


Load baseline Data

By running: experimental_data = colab_utils.load_baselines('/content')
I get this error:

TypeError                                 Traceback (most recent call last)
 in <cell line: 3>()
1 # @title Load baseline data
2 get_ipython().system('gsutil -q -m cp -R gs://download-dopamine-rl/preprocessed-benchmarks/* /content/')
----> 3 experimental_data = colab_utils.load_baselines('/content')
4
5 print('experimental_data')
1 frames
/usr/lib/python3.10/copyreg.py in _reconstructor(cls, base, state)
47 def _reconstructor(cls, base, state):
48     if base is object:
---> 49         obj = object.new(cls)
50     else:
51         obj = base.new(cls, state)
TypeError: object.new(BlockManager) is not safe, use BlockManager.new()
Help please

Also https://colab.research.google.com/github/google/dopamine/blob/master/dopamine/colab/agents.ipynb is not running well. Please help, need that for a Study


Update all dependencies + revamp errors

TODO:

try to get all kinds of errors to make sure they are good
fix mysql  -> getting caused by: Could not connect to address /var/run/mysqld/mysqld.sock': No such file or directory (os error 2) but no time to investigate atm

Looks like the mysql issue is some docker issue


Readme enhancements

Could you provide a short README with installation instructions? After that we could start to mention the script in Tasmota wiki.

:smiley: :+1:


Add meetup provider

Not sure if it's possible but doing live streaming for a group that is based with Meetup.com so being able to pull avatars fro there would be useful.

User profile at meetup are under login, so this is not possible 😭


KeyError: 'bpy_prop_collection[key]: key "Principled BSDF" not found

I encountered this error while trying to import the trophy from the arcades

Try changing the interface language to English.


Add support for Google Analytics

Description
We need a means to start gathering metrics so we can understand how users interact with the site and gather data to help us experiment with new layouts and extra data to improve the users overall experience. Googles platform provides us with a fast path to the tools that we need, with Tag Manager, Optimise and Analytics. As such, we should get this enabled on the platform and configure it so that stakeholders can be empowered to start running experiments on the site and gather data to inform decisions moving forward.
Tasks

[ ] Is the cookie-less option for GA4 GPDR compliant?
[ ]

Definition of Done

[ ] Stakeholders able to view analytics data about visits to the specific pages on the site.
[ ] Stakeholders able to create triggers to gather more specific data about user interaction with on page elements.
[ ] Stakeholders able to create and conduct A/B testing to experiment with different layouts and gather appropriate data for analysis.
[ ] Solution deployed into a staging environment and accessible publicly.
[ ] Solution shared with stakeholders.

@scottaubrey @will-byrne I raised this based on the discussion in the review meeting this morning. Can you please add any questions/tasks/etc to the task list and we can break those out into new tickets to add to the board.
Hopefully the goals are clear enough, will refine them more with @chris-huggins and @Maelplaine in the next review meeting.

Do you need a GA snippet of code? I can create a new GA property and generate one

Adding GA to the application is easy, configuring it is not, on Sciety after many attempts to do it ourselves I believe a consultant was hired to do the configuration.

Thanks for the other @Maelplaine, but I don't think so. I should be able to get everything setup with the guys and I'd quite like to do it myself to build my understanding of analytics.

@NuclearRedeye We can pair on this if you want. If you create it yourself, I recommend you to add it as a new property of the "elife-subdomain-...". Please make sure you are an admin. We will need to link this to GTM and create a new property there too. The snippet of code to embed will actually be generated by GTM

Is the cookie-less option for GA4 GPDR compliant?

It's likely GA is not compliant with GDPR in general:

Austria: https://iapp.org/news/a/far-reaching-implications-anticipated-with-austrian-dpas-google-analytics-decision/
CNIL: https://iapp.org/news/a/cnil-is-latest-authority-to-rule-google-analytics-violates-gdpr/

The trailing comments in the CNIL article are interesting but ultimately it's up to GA to adopt EU-only data processing.

This was merged

Thanks @scottaubrey
Do you mind if we keep this ticket open until I've confirmed we are receiving data from GA?
I've just linked GTM to GA, and we should be able to see some data soon

It looks like it is working

https://analytics.google.com/analytics/web/#/p326649811/realtime/overview?params=_u..nav%3Dmaui%26_u.comparisonOption%3Ddisabled%26_u.date00%3D20220714%26_u.date01%3D20220810&collectionId=life-cycle
I am going to close this ticket


Bump sbt-comms-packaging

Also add policy to let credstash run at startup

This PR was successfully deployed to production by CircleCI build 52 at 2017-04-28 11:54 BST.


CI: Cover all defines

Currently, we do not systematically ensure all our code is buildable for each define documented in README.md. For example, LWM2M_RAW_BLOCK1_REQUESTS is not set in any builds, allowing issues like #583 to slip in.
Acceptance Criteria

For all flags documented in README.md, the Wakaama source gets compiled and unit-tests executed with the flag enable and disabled at lest once.

Non-Goal

Building all possible combinations of compile time defines (too many combinations, waste of energy)

See https://github.com/eclipse/wakaama/pull/596#discussion_r620447382 for another reason why we need this.

PR #646 implements this partially (unit testes are not getting built multiple times).


"Error processing" on swift package page

Hi 👋
I see an "Error processing" message on the swift package page and I'm not exactly sure how I can fix the error: https://swiftpackageregistry.com/GigaBitcoin/secp256k1.swift
I think it has to with the fact I'm using submodules behind the scenes to build a c library before mapping it into swift.

Any guidance would be super helpful!

@twodayslate thoughts? :)

@csjones strange I didn’t get a notification for the original ticket. Thanks for @ing me.
Could it be the sub modules?

@csjones strange I didn’t get a notification for the original ticket. Thanks for @ing me.
It looks to be the sub modules. I’ll have to switch from pulling the GitHub archive to actually using git
Thanks for catching this edge case!

Thanks for the response! Is the change complicated?

Should be changing the wget to a git clone https://github.com/twodayslate/swift-package-registry/blob/master/lib/process.js#L178

@csjones Should be fixed in 93a309eab25a7f8f7851afdd331b7387dc2afd80
https://swiftpackageregistry.com/GigaBitcoin/secp256k1.swift

@csjones Should be fixed in 93a309e
https://swiftpackageregistry.com/GigaBitcoin/secp256k1.swift

Awesome, thank you for the fix! 😁


Add Build number (Buildversion)

Hi Skype-Team
Would it be possible to add the build version to each Package Name/Patch?
I would like to see if I am on the current version or a legacy build (not all build numbers are listed in the sub links).
Article (build missing):
https://docs.microsoft.com/en-us/skypeforbusiness/sfb-server-updates
Reference (shape like this):
https://docs.microsoft.com/en-us/exchange/new-features/build-numbers-and-release-dates?view=exchserver-2019

@SerdarSoysal do you know who can help with this Exchange article as David has left?

Hi @TinaMcN
The Exchange article is not a problem just a reference how it could be shaped in the skype article...

@TinaMcN
Any updates on this?

@Ariantor I believe you own this Skype article, can you please comment on whether it's possible to add build versions https://docs.microsoft.com/en-us/skypeforbusiness/sfb-server-updates

@Ariantor Would it be possible to add this?

@TinaMcN / @Ariantor
Any updates on this?

@TinaMcN / @Ariantor Any updates on this available?


OCPBUGS-6658: Disable managed identity authentication

Managed identity authentication has precedence over username+password from azure-disk-credentials Secret. Force disable it when merging cloud.conf json.
See https://github.com/openshift/cluster-cloud-controller-manager-operator/pull/223 for what the new cmdline option does (it forces useManagedIdentityExtension: false in cloud.conf).
@openshift/storage

From e2e-azure-csi: the driver logs:

I0208 16:54:57.198153       1 azure_disk_utils.go:192] read cloud config from file: /etc/kubernetes/cloud.conf successfully
I0208 16:54:57.198945       1 azure_auth.go:138] azure: using client_id+client_secret to retrieve access token

Without this PR, it has logged:

I0206 16:39:59.594334       1 azure_disk_utils.go:189] read cloud config from file: /etc/kubernetes/cloud.conf successfully
I0206 16:39:59.595386       1 azure_auth.go:96] azure: using managed identity extension to retrieve access token

/retest required

/retest-required


Re-implement "meta" attribute on scripts

Feature:
Implement a meta attribute on the script decorator. Anything inside of this will be passed to the script as "meta" at runtime
Use Case:
Generating scripts dynamically in a loop
for script in scripts:
    external_script = lambda meta, *args: subprocess.run(
         [meata, *args[2:]], check=True
     )

     cli.script(Path(script).name, script_type=st.POSITIONAL, meta=script)(external_script)

In the example above, bindings script to an argument like you normally would for a function created in a loop wouldn't work because of the way that the POSITIONAL script operates. Instead of receiving the script object, it would receive the first argument. And because POSITIONAL enforces that *args be the last argument, it cannot be placed after either.
Workaround:
for script in scripts:
    external_script = lambda *args, script=script: subprocess.run(
        [script, *args[2:]], check=True
    )

    self.cli.script(Path(script).name, script_type=st.RAW)(external_script)

Raw scripts don't enforce *args as the last argument (should they?) so they can be used to get around this issue for now

Added !


Usage of pytest plugins can lead to PytestAssertRewriteWarning

Hi,
I found a quite intresting behaviour when using pytest plugins:
my_module/fixtures.py
import pytest
@pytest.fixture
def my_fixture():
    pass

tests/conftest.py
pytest_plugins= ("my_module.fixtures",)

If I now run pylint on my_module with pylint-pytest enabled, I see a PytestAssertRewriteWarning: Module already imported so cannot be rewritten. Basically this is not a big issues and the warning can be ignored by using pytest settings.
However, it would be nice, if it would be possible to avoid this issue or if pylint-pytest could ignore this warning by default.
Versions:

pytest==6.2.2
pylint==2.7.1
pylint-pytest==1.0.0

Best regrads,
Kai

Fixed & released with 1.0.2


Screenshot

There is no preview from the theme

There is no preview from the theme

thanks a lot for mentioning


Using maxEventCount hides some events that should be shown

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

Expected behaviour

Steps To Reproduce
Using the attached config, with the last line should show the six first events, from the list that is shown without the last line.
As can be seen in the Current Behavior-picture, the events the 22nd and 23rd are left out, even if they are among the first six events.
Mode
Calendar
Card Version
9.3.0 Beta 3
Home Assistant Version
2024.1.2
Configuration
type: custom:atomic-calendar-revive
entities:
   - entity: calendar.xxxx
maxEventCount: 6

Relevant log output
No response
Code of Conduct

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

Think this will be related to #1338 currently looking at this issue I'll double check with this too

Unfortunately, the error still persists for me despite version 9.4.0. 😢

Yes this issue hasn't been resolved.
The release notes will let you know what's been fixed on each version and should be checked before installing.
Once an issue is resolved and released it will automatically close by the release workflow. Generally I don't close an issue without having confirmation from a beta test that it's working.
This will likely be the next issue that I look into.

Oh, sorry. I thought it was the same as #1338. My bad English. 😬

Ah no, it's related to the same thing, but a different scenario.  I need to do some tests and will release a fix soon.
Hopefully in next few days if it's not too complex.

Thank you!

It works! All issues resolved. Thanks' alot!
Den tis 23 jan. 2024 kl 10:35 skrev Steven Marks @.***>:

Hopefully this latest release resolves issues with sorting, there is still
an issue with milestone sorting but that will be more complex to resolve
—
Reply to this email directly, view it on GitHub
https://github.com/totaldebug/atomic-calendar-revive/issues/1378#issuecomment-1905655129,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APD2WAC2MQTRPVYOZLRHV5DYP577DAVCNFSM6AAAAABCAYG7ZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBVGY2TKMJSHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Really? Not for me. What am I doing wrong? 😫

@Pscharumbel please send the following for me to troubleshoot:
1: a copy of your card config
2: press f12 click the console tab and send a screenshot of the "atomic calendar revive" entry
3: screenshot of what you see
4: screenshot of what you expect to see
Hopefully this will give me enough to figure out what's wrong

Alright!
1:
type: custom:atomic-calendar-revive
name: null
enableModeChange: true
entities:

entity: calendar.geburtstage
name: Geburtstage
entity: calendar.tine_jens
entity: calendar.abfallkalender
name: Abfallkalender
entity: calendar.feiertage_brandenburg
showDate: false
showLoader: false
showRelativeTime: false
showLocation: false
showMultiDay: true
maxEventCount: 5
maxDaysToShow: 4
hideDuplicates: false
showMultiDayEventParts: true
compactMode: false
offsetHeaderDate: false
showAllDayEvents: true
hoursOnSameLine: false
showAllDayHours: false
showTimeRemaining: false
showEventDate: true
showWeekNumber: false
showDatePerEvent: false
showProgressBar: false
showWeekDay: true
showDescription: false
disableEventLink: false
disableLocationLink: false
showNoEventsForToday: false
showFullDayProgress: false
showMonth: false
showCalendarName: false
showHiddenText: false
disableCalLink: false
allDayBottom: false
card_mod:
style: |
ha-card {
margin-top: -9px;
font-size: 15px;
color: #808080;
line-height: 170%;
}

2:

3:
Without: maxDaysToShow: 4

4:
With: maxDaysToShow: 4

I hope it helps!

@Pscharumbel I have just done a new release, please try with v9.4.0-beta.5

Hello!
Thank you very much for your effort! At first, it seemed to work perfectly. I only had one appointment per day. When I added a second one for Thursday, unfortunately, the appointment on Friday disappeared, and the one on Saturday was displayed.
Best regards!

are the events you added in different or the same calendar?
I'm struggling to replicate your issue.

Hi!
I use multiple calendars with a mix of all-day and timed events. As a test, I've added and deleted some appointments, and tried different values for maxEventCount, and I couldn't reproduce the error anymore. 🤷🏻♂
So, tank you very much again for your work!! 😃👌🏼


Outdated terminology and information on linked articles

Linked article has 6 years old note At this time, the Azure Cosmos DB trigger, input bindings, and output bindings work with SQL API and Graph API accounts only.

Terms SQL API and Graph API are not used anymore!
Does any function binding version support CosmosDB Graph API(SIC) accounts?

Updates needed for linked article and for following articles:

https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-cosmosdb?tabs=csharp
Also note that this lists only SQL API being supported. No notes about Graph API

Following articles are using proper terms:

https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-cosmosdb-v2?tabs=isolated-process%2Cextensionv4&pivots=programming-language-csharp

This is using term NoSQL
Graph API not listed as supported

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

ID: 939101cd-9c92-ed8f-b241-664794db8a0d
Version Independent ID: 21392fd3-c4e7-f785-a660-ebbbf88646e4
Content: Store unstructured data using Azure Cosmos DB and Functions
Content Source: articles/azure-functions/functions-integrate-store-unstructured-data-cosmosdb.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@jikuja
Thanks for your feedback! We will investigate and update as appropriate.


Figure out how to run Docker container on a Synology DS920 NAS

I have a Synology NAS always running, so I would love to run some custom container on it.

First, I need to install the Docker package.
On DSM 7, visit the Package Center and install the Docker App:

I would love to access the Docker server from my Mac, but it looks like the easiest path is to ssh into the NAS.
Let's give this solution a try.
Open Control Panel > Terminal & SNMP > Terminal and enable SSH service:

Now I am ready to access the NAS and run some docker commands:


Insufficient warning when an estimation method with low accuracy is used

Currently the library provides no warning when an estimation method is used to calculate a chemical property. This was exemplified in #3 , where glycerol has no accurate viscosity data at the time and the estimation methods Letsou_Stiel and Przedziecki_Sridhar worked terribly but without any warning.
It might be a good idea to provide a warning when an inaccurate estimation method is used, or to provide an overall description of the quality of the data for a chemical, or to attempt to quantify the error of a property.
It would be straightforward to generate a warning, using the warnings module, whenever a low-accuracy estimation method is called. However, how often should they be generated? If a plotting command is used and the estimation method is used repeatedly, generating a warning for each calculation would not be desirable. Furthermore, some caching is used to store chemical properties for future use. The caching layer does not know what method was used, and if it is accurate or not.
One more pain point - Many of the VDI PPDS coefficients are regressed from estimated data using the same methods used in the library. The same applies for what DIPPR data are available. Even the TRC ideal gas heat capacity database contains plenty of estimated data using the Benson method. None of these sources state which chemicals have estimated data and which do not. Some coefficient sources, such as the VDI PPDS coefficients, do not even have a temperature range specified, and definitely stop working at very low and very temperatures - some crude measurements based on properties derivatives are currently used to limit these coefficients.
The long-term solution is to do what NIST's Thermodynamics Research Center does - collect experimental data, regress coefficients, and estimate uncertainties based on that.
Considering the above, there is no obvious path for when to generate warnings. Please share any thoughts - use cases, issues when you were surprised by a low-accuracy datum, or other suggestions about providing warnings to the user here.

Since you know in advance which compounds have experimental data available or not, you can generate a field for each temperature/pressure-dependent property, i.e. ExperimentalDataAvailable = true/false.
DWSIM would greatly benefit from this feature, as I would have a mechanism to tell the user whether the compound property is estimated or not. If estimated, I assume that the library chose the best method to do so.


Improve deploy.yml workflow

The deploy.yml workflows fails too often.
That is because when building the app, the server sometimes runs out of memory.
Retrying the workflow often solves the issue. We need a way to run the workflow again if it fails.
A maximum retry cap should be set to 3.
We could try it like this:
name: "Retry action using retry step"
on:
	# This action is called when this is pushed to GitHub
	push:
	# This action can be manually triggered
	workflow_call:
jobs:
    # This name is up to you
	retry-job:
		runs-on: "ubuntu-latest"
		name: My Job
		steps:
			- name: Checkout repository
			  uses: actions/checkout@v3

			- name: Some action that can fail
			  # You need to specify an id to be able to tell what the status of this action was
			  id: myStepId1
			  # This needs to be true to proceed to the next step of failure
			  continue-on-error: true
			  uses: actions/someaction

			# Duplicate of the step that might fail ~ manual retry
			- name: Some action that can fail
			  id: myStepId2
			  # Only run this step if step 1 fails. It knows that step one failed because we specified an `id` for the first step
			  if: steps.myStepId1.outcome == 'failure'
			  # This needs to be true to proceed to the next step of failure
			  continue-on-error: true
			  uses: actions/someaction

(Sourced from https://www.thisdot.co/blog/how-to-retry-failed-steps-in-github-action-workflows)

We may want to add the supervisorctl restart vegancheck to the script to ensure everything works right


Expose UNSTABLE container for RSP overlays

Reverts adobe/react-spectrum#5806
I've also made another commit to show how much threading through this requires. I still haven't done all the components. I think the color components, date/time pickers, every component with contextual help, and breadcrumbs, would all need to expose this prop too if we do it as it is currently setup.
I think this is a good time to consider doing a context based approach instead.

closing in favor of https://github.com/adobe/react-spectrum/pull/6141


Error number 14 opening dll library pbvm90u.dll in pfc_n_cst_platformunicode object function of_printdlg line 29

Hi,
we just migrated our PB 12.5.2 classic apps to PB2017 R3 and deployed them as 64 bit applications, we are getting error opening dll library pbvm90u.dll when trying to call PFC_PrintDlg function.
Please suggest if there is an alternate solution,
pbvm90u.docx
Thanks a lot.
Venu Kokkula

Did you update the version of PFC you were using?  The dependency on a particular version of the PowerBuilder VM was removed in PFC version 10.

Yes, we did try with the Appeon powerbuilder 2017 pfc libraries.

I'm not familiar with any Appeon PFC version for 2017.  Last I heard Appeon stopped distributing their own version of PFC and simply provided instructions for eliminating those portions of PFC that aren't supported by PowerServer.
There is no reference to a PowerBuilder runtime DLL in any version of PFC version 10 or later.


Suggestion: Supporting events as interfaces?

This is mainly meant as a probing discussion item to see what you would think of adding a feature like this.
Currently if you have an event like this
public interface IPickedUpWeapon {
    string WeaponType { get; }
}
public class PickedUpWeapon : IPickedUpWeapon {
   public string WeaponType { get; set; }
}

then the aggregate still needs to refer to the concrete type in order for AggregateAsync to apply it properly
public class AdventurerAggregate {
    // .....
    public Apply(IPickedUpWeapon e) {
        // This will not be called
    }
}

Im currently using Jil as a serializer, and from what I can see Jil has no problems with serializing and deserializing interfaces (and doesnt need to store any additional type information in the events to do so), but of course then Marten wont actually apply the events even if they serialize/deserialize properly.
One problem with allowing for interfaces instead of only concrete classes would be if an event implements several interfaces.
public interface IPickedUpWeapon { string WeaponType { get; } }
public interface IPickedUpArmor { string ArmorType { get; } }
public interface IPickedUpWeaponAndArmor : IPickedUpWeapon, IPickedUpArmor { }

then applying this event to an aggregate with handlers for some combination of the events would be a bit weird. I think that it would be ok to call all matching appliers with the event and just document that the order that they are called in is undefined and should not be relied on. (If ordering for this case is really necessary for an aggregate it could probably be done by decorating the apply methods with interfaces or adding some sort of marker interface, but I dont really think that it should be necessary).

To add some context to this, we're currently using MassTransit for our messaging fabric which encourages the use of interfaces as message contracts, naturally including events.  So, we currently expose a common "message contracts" library per (sub)domain containing all of the [read only] interfaces for commands & events, and only implement concrete classes where we plan to publish/send new messages.  It would feel natural for us to be able to read out the events as [read only] interfaces from the event store (primarily thinking of async projections here) the same way we would receive them on the bus, instead of needing to share concrete implementations with setters, which breaks the convention that we're currently using (impl where creating new events).

same issue here regarding MassTransit

A year later I am less convinced about this being a good idea (and more convinced that maybe MassTransit is the weird one for using interfaces as they do).

@wastaz could you elaborate and share some lessons learned?

I would questions whether events in the Marten event stream should be directly put on a messaging wire. These are different models that I believe are better served by encapsulation. This would require lots of mapping logic to maintain the separation, but ultimately I think that's a price that's worth paying for keeping things encapsulated. Just my $0.02.

@oskardudycz Sure thing. Ill try to do a braindump and we'll see what comes out ;)

The exact reason that @jeffdoolittle states. It sounds very nice in the beginning to just publish all eventsourced messages on the eventbus (both words starts with "event" after all!). But it turns out (who would have thunk) that this sometimes leads to exposing "private" state to other domains. While this might not always be a problem (apart from sending around a lot of information that didnt need to be sent around in the first place), in some cases it does lead to some unwanted or (as when GDPR is involved) extremely problematic situations. As such, just publishing all eventsourced events to the bus has turned out for us to be a pretty bad default, and we have now introduced a non-optional mapping layer in our internal framework for integrating these things (which can of course still choose to not do any mapping at all for some event types, the amount of mapping code we needed was much less than we first thought). This also makes it easier to change your events later (its gonna happen) and not break downstream consumers.

Serialization woes. While Jil turned out to be able to handle serialization of interfaces pretty fine without adding unnecessary type information and other stuff, that is not the case for all serializers out there. Json.net occasionally adds a lot of typenames and other cruft and other fun stuff you might not want. We no longer use Jil for serialization and went back to json.net. Mainly because no matter what you do you still end up with json.net in your project and maintaining one serializer is easier than maintaining two (and also we had some other issues with Jil serialization of some stuff). No one likes fighting with serialization issues.

The one thing that would be nice would have been event immutability. While it should be possible to do immutable events in marten as it is today...C# is just such an annoying language to work with when it comes to immutability. So in the end the most pragmatic way of handling things is "gentleman immutability" anyway. Maybe if we finally get records in C# somewhere around C#9 those could be used instead, but yea.

Reading through this issue thread, I am deriving a conclusion that there is nothing required to be done at Marten end.  Closing the same.