text:
mongo plugin crashing after updating intellij

here is the stacktrace:
null
java.lang.NullPointerException
at org.codinjutsu.tools.mongo.view.MongoExplorerPanel$2.run(MongoExplorerPanel.java:124)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:319)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
at com.intellij.ide.IdeEventQueue.e(IdeEventQueue.java:697)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:524)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:335)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)
java.lang.NullPointerException
at org.codinjutsu.tools.mongo.view.MongoExplorerPanel$2.run(MongoExplorerPanel.java:124)
at com.intellij.openapi.application.impl.LaterInvocator$FlushQueue.run(LaterInvocator.java:319)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
at java.awt.EventQueue.access$200(EventQueue.java:103)
at java.awt.EventQueue$3.run(EventQueue.java:694)
at java.awt.EventQueue$3.run(EventQueue.java:692)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
at com.intellij.ide.IdeEventQueue.e(IdeEventQueue.java:697)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:524)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:335)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

Same issue here:
https://gist.github.com/jorgeartware/396a8cad56d8dd8f8861
It crashed during webstorm restart.
Not sure if it is relevant but I had just installed pyCharm community edition while I had webstorm open at the same time and then closed pycharm and restarted webstorm, it was about to finish loading just before this error showed up.
Could it be an encapsulation error/conflict of the intellyJ api maybe?

Hi,
Thanks for this stacktrace. The root cause seems to be the same than the stacktrace mentioned at the top of this thread.
Could you please remove the plugin, reinstall it from Webstorm and tell me if the bug still occurs?
Thanks.

Hi,
I uploaded a snapshot version tested on Webstorm 9. It should work on Idea 14 too.
Please tell me if it works on your IDE.
David

Release 0.7.0 available on Jetbrains plugin repository

authors: dboissier jorgeartware villesau


text:
How to get coordinates(x, y) from object?

Hi.
How to get contour location(x, y) from instance segmentation object ?
I hope to develop auto-drawing-labeler. so, want to know coordinates (X, Y) of instance segmentation.

If the yolact does not have any output option for contour coordinates, you can try to integrate the instance segmentation with canny edge detection(opencv).

source: gharchive/issue

repo: dbolya/yolact

license: MIT

license_type: permissive

license_source: github-api


text:
wvunpack should ignore qmode from WavpackGetMode() for WAV family output

As the title says.
When a big endian caf file is encoded with -r option set, wvunpack decodes it into a big endian wav file by default.

Thanks, good catch!
There are actually several things along those lines that I need to look into. Without even trying, I'm afraid that using the --skip and --until options might produce some wrong results with other formats/endians too.
And I really need to figure out how I want the -r (raw) option in wvunpack to work. I think it should always output the native (original) endian, but then I should have alternate versions like --raw-be and --raw-le to force a specific format.
But yeah, WAVs should always be LE...  :-)

I decided that to really fix this (and related) issues correctly I need to store the source file format in the file, along with the original extension, and create an array of available output formats that wvunpack can use.
So now, if you pack a big-endian caf file with -r and unpack it, you'll get a big-endian caf file (with a freshly generated generic caf header). If you want a wav file instead, the -w option will do it, and it will not be big-endian (obviously). I think I covered all the bases here, but feel free to point out if I missed anything.
Thanks again!

repo: dbry/WavPack

license_source: bigquery


text:
Fixed compilation errors when using a C++ compiler.

What have I done?
In order to compile the C code in a C++ project, I've had to C-style cast anything that was of type void* to the destination type.
The issue we were running into is the blasted error C2440.
Why have I done this? What was I trying to do?
A bit of background: I'm a C++ developer using JUCE. In-house at AudioWorks we have our own Unity Build modules, following similar conventions to JUCE's modules.
We are trying to use this repository as a submodule in order to avoid the whole Not Invented Here problem, and having a facilitated way of keeping up to date. To do this, we have wrapped WavPack's source in a derived implementation of juce::AudioFormatReader using a similar approach to JUCE's OGG and FLAC  support: including the .c files directly.

If my pull request is completely missing the mark, or if I've gone about this the wrong way (eg: not quite 'getting' C, coding style, wrong repo), let me know what I need to change - assuming you're interested.
...and if the motivation is too left-field, feel free to close the pull request.
Cheers!

I'm not totally against this patch, because it obviously doesn't break anything, but I am a little hesitant. I am very familiar with the C++ requirement for these casts, but all the build systems I've worked on have always automatically compiled .c files as C language, and it's certainly a little weird to require that C code adhere to C++ rules.
On Visual Studio, for example, you can go into Configure Properties → C/C++ → Advanced → Compile as to specify C compilation even for files named .cpp.
I also just tried -fpermissive on gcc and it converted this error into a warning, which might work for you. This also works inline as a pragma: #pragma GCC diagnostic warning "-fpermissive"
Does this requirement have something to do with the Unity build? Are the C and C++ files all smushed together?
Another issue is that even if I incorporated this change, I would probably break the code when I make changes in the future because none of my build configurations check for this error, and I'm sure I'd forget to include this cast at some point (especially because I believe that the whole point of using a void pointer is to avoid silly casts like these).
However, like I said, I'm not totally against this and obviously I'd like to accommodate anyone who is adding WavPack support to an application! If you can't figure out another way around this, I'll go ahead and incorporate the patch.
Thanks!
David

Does this requirement have something to do with the Unity build? Are the C and C++ files all smushed together?

Yep, that's generally it.

Another issue is that even if I incorporated this change, I would probably break the code when I make changes in the future because none of my build configurations check for this error, and I'm sure I'd forget to include this cast at some point (especially because I believe that the whole point of using a void pointer is to avoid silly casts like these).

I've no issues with helping out in this department! Seeing that we're including the files directly from a submodule of this repository, an update to the submodule would mean fixing any errors/warnings that come up.

Okay, cool!

source: gharchive/pull-request

authors: dbry jrlanglois


text:
Optimize wavpack.h

The goal is to remove duplicated code from wavpack.h & wavpack_local.h. WavPackContext is still opaque pointer for library users, but for private use it is typedef to internal struct.

Include wavpack.h to wavpack_local.h
WavPackContext is now typedef of struct WavPackContext in
wavpack_local.h
Remove duplicates from wavpack_local.h

It's better to test, maybe I'm wrong here. If so, ABI version could be untouched.

I have decided to go ahead with this. The definition of WavpackContext does not change for the library code. What gets exported from wavpack.h changes from a void typedef to an opaque struct typedef, which adds type checking to the API and should be equivalent from an ABI standpoint.
If this becomes a problem we can always change the definition in wavpack.h to:
#ifdef WAVPACK_LOCAL_H
typedef struct WavpackContext WavpackContext;
#else
typedef void WavpackContext;
#endif

so that everything's identical and we still eliminate the duplicated stuff.
Thanks for doing this!

authors: dbry evpobr


text:
[Feature] Raise an error for unit tests that don't contain all filtering columns

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Fixtures that are missing required columns in models lead to a hard-to-debug silent failure in the unit test.
Expected Behavior
When a dbt model requires a filtering column, unit tests should raise an error when fixtures don't contain the required columns.
Steps To Reproduce

Model:

with
foo as (
    select col1,col2 from {{ ref('foo') }} where filtercol is not null
)

bar as (
Transformations here
)

select * from bar

Unit test:

unit_tests:
  - name: foobar
    model: mymodel
    given:
      - input: ref ('foo')
        format: csv
        fixture: foo
    expect:
      format: csv
      fixture: bar

Fixture (foo.csv) missing the filtercol used in the model:

col1,col2
1,2
3,4

Relevant log output
Note: only expected output is expected, because due to the missing filtering column in the input fixture, no rows were selected.
15:38:29  Finished running 1 unit test in 0 hours 0 minutes and 1.46 seconds (1.46s).
15:38:29  Completed with 1 error and 0 warnings:
15:38:29  Failure in unit_test foobar (models/unit_tests.yaml)
15:38:29
actual differs from expected:
@@ ,col1,col2
---,1,   2
---,3,   4

Environment
- OS: Ubuntu 22.04
- Python: 3.11
- dbt: 1.8.6

Which database adapter are you using with dbt?
other (mention it in "Additional Context")
Additional Context
Adapter used: Clickhouse

Thanks for raising this @leonardobocci !
I switched this from a bug report to a feature request since dbt is behaving the way we expect. Namely, for any columns that are not specified in a unit testing fixture, dbt takes that to mean the value doesn't matter and it will supply an arbitrary value to the transformation model. The default arbitrary value is null, but some adapters may choose to override this default. If any value is relevant to your expected output (like filtercol in your example!), then you'll need to supply it. dbt doesn't know which columns are important or not (and my initial guess is that it can't know).
Either way, we aren't planning to do anything fancier in this regard than we're doing currently, so I'm going to close this as "not planned".

repo: dbt-labs/dbt-core


text:
[implementation] define project-wide vars in vars.yml, outside of dbt_project.yml

Short description
From https://github.com/dbt-labs/dbt-core/issues/2955
"I want to define project-wide variables outside of my dbt_project.yml."
"I want to be able to reference variables in my dbt_project.yml at parse-time."
Acceptance criteria

I can define project-wide ("global variables") variables in a vars.yml file, separate from my dbt_project.yml

# vars.yml

vars:
  start_date: '2016-06-01'

dbt parses vars.yml before parsing dbt_project.yml, meaning default values of vars called in dbt_project.yml would work the way folks expect, rather than how it is today (equivalent to how this works when defining vars through the CLI a la --vars)

Option 1 - behavior change

You cannot define variables in both places, you must chose the "new" or "legacy" way
As such, this would need to be behind a behavior change flag
Open question: Given that behavior change flags are set in dbt_project.yml, would this even be possible?

Option 2 - backwards compatible

You can define variables in either places
Open question: Would we still get the parsing benefit if we went this route?

Current workaround: Have a really massive dbt_project.yml file with no ability to reference variables in your project configurations

Is there a reason to make it specific for vars instead of making it possible for any configuration like in this other issue?

authors: b-per graciegoheen


text:
Minimize pre-commit install

Description
Minimize the installs to run pre-commit
Checklist

[ ] I have read the contributing guide and understand what's expected of me
[ ] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[ ] I have run changie new to create a changelog entry

@JCZuurmond probably we want to change mypy to a pre-commit dependency, instead relying on the system by changing the pre-commit configuration:
  - repo: https://github.com/pre-commit/mirrors-mypy
    rev: v0.991
    hooks:
      - id: mypy
        args: [--show-error-codes, --ignore-missing-imports]
        files: ^dbt/adapters/.*

Hi @Fokko, nice seeing you here again! I made this PR a draft PR, am struggling to get mypy working correctly. It is stuck on the double spark submodule:
dbt/adapters/spark/connections.py: error: Source file found twice under different module names: "spark.connections" and "dbt.adapters.spark.connections"
dbt/adapters/spark/connections.py: note: See https://mypy.readthedocs.io/en/stable/running_mypy.html#mapping-file-paths-to-modules for more info
dbt/adapters/spark/connections.py: note: Common resolutions include: a) adding `__init__.py` somewhere, b) using `--explicit-package-bases` or adjusting MYPYPATH

Need to find some time to continue with this.

authors: Fokko JCZuurmond

repo: dbt-labs/dbt-spark


text:
Enable deprecation: dispatch-packages

dispatch-packages
Introduced in: v0.19.2
In the last week, raised by: 276 projects (~9% of eligible projects)
Instead of raising a deprecation warning when the user has defined the packages arg, or has passed a list instead of a string, we should instead raise a clear error. That error message should point to the same documentation that the deprecation warning message currently does
https://github.com/dbt-labs/dbt/blob/96083dcaf51ab7725f1b554891581e1522e32d7d/core/dbt/context/providers.py#L137-L140
Then, we can:

Remove DispatchPackagesDeprecation from the list of active deprecations
Significantly simplify the logic (removing jank backwards compatibility) from jinja_static.py — to discuss with @gshank

Originally posted by @jtcohen6 in https://github.com/dbt-labs/dbt/issues/2798#issuecomment-919998174

https://docs.getdbt.com/reference/dbt-jinja-functions/dispatch will also need an update.

@jtcohen6 Should I rip out the packages arg all together or leave it in for now and just raise an exception when it's used?

@emmyoop I think I prefer leaving it in and raising an explicit exception when it's used explicitly. That feels like the same approach as raising an explicit exception when a list is passed to the second positional argument.
At the same time, we should feel very comfortable removing all the code from jinja_static.py that exists to handle values being passed to packages. This was all for backwards compatibility, since we had to rework dispatch in a patch release (v0.19.2) to fix some regressions from v0.19.1.

repo: dbt-labs/dbt


text:
[Core] Add content to v1.9 upgrade guide for beta

Link to the page(s) on docs.getdbt.com requiring updates
Add any relevant content to v1.9 upgrade guide for upcoming beta
Tell us more about this update
Please use the following template as guidance (@matthewshaver will have more info): https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-v1.8
Reviewers/Stakeholders/SMEs
@graciegoheen
@jtcohen6
Related GitHub issues
No response
Additional information
No response

Now that adapters are decoupled from core.. should the 1.9 guide only focus on new "core" features (microbatch, snapshot improvements, etc.) or should it include "adapter" features still also (iceberg table format, etc.)?
cc: @jtcohen6

My very rough thoughts on what should go in this! (cc: @dbeatty10 @jtcohen6)
Big features to highlight:

new microbatch incremental_strategy

new supporting configs (event_time, begin, lookback, batch_size

improvements to snapshots

new snapshot spec (define in yml)
new snapshot_meta_column_names config for customizing name of meta fields
target_schema is now optional for snapshots - omit for environment-aware snapshots
add standard schema/database configs for snapshots
warning when updated_at is not proper data type / timestamp
[maybe] new way to track deletes (config etc.)

Small wins:

can now add descriptions to singular data tests
can use ref and source in foreign key constraints
can use --exclude-resource-type + associated environment variable (and "include" opposites --resource-type) in dbt test command (for excluding unit tests in production)
new --inline-direct parameter for 'dbt show'
[adapters] data_test accepts arbitrary config options (allows you to set snowflake_warehouse for tests, as an example)
[adapters] behavior flags
[maybe] state:modified improvements

Other callouts:

a reminder for Cloud folks to use versionless to get access to these new features
a reminder that adapters have been decoupled with core (implications for installation)
behavior change flag callouts!
check with semantic layer team if there's anything to add! (time spines?) @Jstein77
check with adapters team if there's anything to add! @amychen1776


text:
Add devspace

Wraps all the README.md set up instructions into a GitHub codespace so that rather than:

installing VSCode & Python
doing the virtual env setup stuff from the README.md
All a user needs to do is click the "Open in Codespaces" button on this repo, and everything is set up for them, including a chunk of the configuration provided in my Using dbt in VSCode guide

Caveat: pricing & availability
I have free access still via my now-defunct MSFT MVP award status, but the feature is only available via a user's GitHub organization. At the very least folks here at dbt Labs could make us of it? Pretty great to be able to run jaffle shop on dbt-core from the browser from any computer with zero setup!

@dataders Can you make a loom video and post here? It can serve both as UX AND PR testing AND can be used for future getting started newcomers!
I tested this personally and got these errors that would likely confuse a newcomer.
Can you update the configs to prevent these?

@sungchun12 Can you try again now? I was also getting those errors, I think it has to do with a version mismatch b/w the Python extension and the Pylance extension. I was using the insiders version of Code and Python. The fix was as easy as dropping the Pylance setting.

@dataders now it's not starting the container at all

@dataders now it's not starting the container at all
wtf! at the risk of mansplaining, are you picking the PR's branch (add_devspace) to build from?

@dataders I did, I left it alone for a couple minutes and opened it up again, but I'm still getting python isn't installed errors.

@sungchun12 woof! https://github.com/dbt-labs/jaffle_shop_duckdb/pull/28/commits/caf864e3018c3cd244cb96e9f631091c06c3675e should fix it! I sloppily uncommented a comment in requirements.txt
validating the build again meow

Almost there. Can you remove this error?

Almost there. Can you remove this error?

yeah i see that in the browser view -- do you get this error if you open it in Code Desktop?

Not in VScode locally.
But as a newcomer, I'll likely use the browser only experience to get started.

@dataders Cool thanks for verifying the Chrome piece working well without that funky error.

Can you also add to the Mach Speed Readme portion for how to setup the codespaces(with a toggle) underneath the current toggles?

Can you add to the Troubleshoot Readme portion for people encountering the funky errors if they use browsers like firefox and brave?


text:
Deployment_type argument appears to be redundant

Provider version: dbt-labs/dbtcloud v0.2.2
Terraform:
resource "dbtcloud_environment" "data_platform_test_production" {
  dbt_version     = "1.6.1-latest" # TODO: parameterise as a variable, ideally get from dbt/requirements.txt
  name            = "Production"
  type            = "deployment"
  deployment_type = "production"
  project_id      = dbtcloud_project.data_platform_test.id
}

Output:
dbt-cloud % terraform plan
╷
│ Error: Unsupported argument
│
│   on main.tf line 45, in resource "dbtcloud_environment" "data_platform_test_production":
│   45:   deployment_type = "production"
│
│ An argument named "deployment_type" is not expected here.

Workaround:
Omit deployment_type argument from terraform configuration
Proposed fix (assuming this is from new feature development):
Refactor docs and guidance to reflect appropriate handling: https://registry.terraform.io/providers/dbt-labs/dbtcloud/latest/docs/resources/environment

Hi @LeoTheGriff !
The deployment_type is a field that was not available in 0.2.2 but was added later.
If you use an older version of the provider, just check that the correct one is selected when you navigate the docs.

Thank you for spotting that!

authors: LeoTheGriff b-per

repo: dbt-labs/terraform-provider-dbtcloud


text:
Expand notification resource to support Slack type

Is your feature request related to a problem? Please describe.
I'm working to import dbt Cloud resources into our Terraform state, and would like to be able to include our Slack notifications.
Describe the solution you'd like
I'd like to be able to configure Slack notifications for a job as a resource.
I see an existing notification resource, but it appears to be specific to email notifications. Please correct me if I'm wrong here!
Describe alternatives you've considered
The documentation includes guidance for using the HTTP provider to retrieve data, but I figured I'd start by raising an issue.
Additional context
Based on the existing resource and the Create Notification endpoint, I think an example could look like:
resource "dbtcloud_notification" "slack" {
    user_id            = 12345
    slack_channel_id   = "A1234BC45DE"
    slack_channel_name = "#dbt-cloud-notifications"
    on_cancel          = [123456]
    on_failure         = [123456]
    on_success         = [123456]
    // the Type 2 is used for Slack notifications
    notification_type  = 2
}

Hi Katie!  I think this is a great suggestion for sure.  Slack is tricky, because in our current backend code, a single admin-level user per account makes the connection to slack, and from there, all notifications are sent over that bridge.
I'm not saying it's impossible, it's just an additional layer of complexity involved, because for email we are self contained.  For slack, we have to OAuth against slack initially to link dbt Cloud to your Slack account, before we can actually configure the notifications.
Likely this might require the configuration of two different terraform resources:
Resource 1 for the connection itself (which is stored in one database table)
Resource 2 for the notification configuration record (which is in a different table, but the same one as the email configs).
I'll let @b-per drop his thoughts in too, as this would be great to be able to do!

I can have a look yes, but I am not sure how easy it is. It definitely won't be easy or possible to set the Slack connection itself from Terraform, but we might be able to set the notifications, once the connection is configured correctly from the UI.
As a workaround, would you be able to use the ability to send emails to a specific address to get notifications sent to Slack?

Sending notifications to external email addresses is already available in the Terraform provider.

Yes! I'll give it a look this week and report back.

I'm blocked on our Slack admins at the moment, but agree in principle that email notifications represent a workaround.
At the same time, I do still think the ability to configure Slack notifications in Terraform (assuming a manually pre-configured connection) is worth exploring.

That's so exciting! Thank you, Benoit.


text:
fix AAD integrated authentication

using authentication: ActiveDirectoryIntegrated doesn't work. most likely due to this chunk not helping anything just causing problems. @NandanHegde15 is in the process of testing will open a PR to resolve this ASAP.
https://github.com/dbt-msft/dbt-sqlserver/blob/f98edd015b252fbd7eb5acd2bd4c28d49e746d6f/dbt/adapters/sqlserver/connections.py#L153-L155

@swanderz  Should we include this in next release?

Yeah that'd be ideal! We hope to add less-technical users to our projects soon. Giving access via AAD is way more secure and simple than SQL account.
While the fix itself is simple, @NandanHegde15 has been working on how we can test in CircleCI that ActiveDirectoryIntegrated is working with our test Azure tenant and an Azure VM. Though maybe if we can't get that finished in the next few days, we can merge this PR (after manually testing of course), cut a new release, and address the CI testing in a future PR and release.

@swanderz can this be closed?

@swanderz can this be closed?

@swanderz can this be closed?

I'll close it now. For posterity, here's our recommendation:

no one should use ActiveDirectoryIntegrated, unless they have an:

on-prem Active Directory, or
Azure Active Directory with Active Directory Federation Services (ADFS) enabled.

@swanderz can this be closed?

I'll close it now. For posterity, here's our recommendation:

no one should use ActiveDirectoryIntegrated, unless they have an:

on-prem Active Directory, or
Azure Active Directory with Active Directory Federation Services (ADFS) enabled.

authors: mikaelene swanderz

repo: dbt-msft/dbt-sqlserver


text:
My first revup foo

Topic: foo

Reviews in this chain:
└https://github.com/dcai-emancro/revup-tutorial/pull/1 My first revup foo

#
head
base
diff
date
summary

0
41892cfc
c78b1781
diff
Nov 4 23:58 PM
1 file changed, 1 insertion(+)

repo: dcai-emancro/revup-tutorial


text:
Can I use this library to create a typed javascript class without protobuf?

As proto3 supports json, I want to use json over http 1.1, for web clients.
I'll also use https://github.com/google/googleapis/blob/master/google/api/http.proto to declare rest api on .proto file.
Is this supported?

You could use ProtoBuf.js to create the JSON representations of messages, not using Message#encode but Message#encodeJSON, and sending the result over HTTP, decoding it with Message.decodeJSON.

Sorry for delay.
I meaned I want to create plain javascript class with this, and now I find it available, but I want to know if this library supports additional thngs in rpc {} from google/api/http.proto

ProtoBuf.js is be able to parse the http.proto you linked so that you can work with its structures, but it does not implement the API it describes.

Thanks for yout help.
But now I found that this drops comment.


text:
Fix segfault in tests and potential badness in general.

DC/OS compiles Mesos with Libevent and SSL enabled, which means that -DUSE_SSL_SOCKET is defined during compilation time across all files.  This definition was missing in this modules repo, which leads to a subtle abort/segfault during tests:
[ RUN      ] DockerRemoveTest.VerifyRemoveDockerCfgHook
ABORT: (../../3rdparty/stout/include/stout/flags/flags.hpp:433): Attempted to add flag 'hostname' with incompatible type
*** Aborted at 1499293280 (unix time) try "date -d @1499293280" if you are using GNU date ***
PC: @     0x2b806a3607ef (unknown)
*** SIGABRT (@0x3e80000636d) received by PID 25453 (TID 0x2b8061116280) from PID 25453; stack trace: ***
    @     0x556f73d34f0c _Abort()
    @     0x2b8066c7fe05 _ZN5flags9FlagsBase3addIN5mesos8internal5slave5FlagsENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEZNS0_3addIS5_SB_EEvMT_6OptionIT0_ERKNS_4NameERKSB_EUlRKSE_ISB_EE_EEvSH_SK_RKSE_ISI_ESM_T1_
    @     0x2b8066c7c953 flags::FlagsBase::add<>()
    @     0x2b8066c72336 mesos::internal::slave::Flags::Flags()
    @     0x2b8069880e92 mesos::internal::tests::MesosTest::CreateSlaveFlags()
    @     0x556f73d2fb88 mesos::dockerRemove::tests::DockerRemoveTest_VerifyRemoveDockerCfgHook_Test::TestBody()

This error occurs when calling the rather innocent looking constructor for the Mesos Agent flags: mesos::internal::slave::Flags::Flags().  Under the hood, Flags is a super-class of the stout FlagsBase template class.  Each time we go to add a new field to the Flags, the FlagsBase attempts to up-cast (via dynamic_cast) from FlagsBase to the templatized Flags type.  dynamic_cast will return nullptr if the cast fails, hence the segfaults.
The reason why the up-cast was failing is because the agent flags include an #ifdef USE_SSL_SOCKET, which means that the Flags with and without USE_SSL_SOCKET are actually different classes.  This meant the module tests were attempting to construct non-SSL agent flags, while linking to SSL agent flags.

Oops, only the Makefile.am change is relevant here.

That other stuff is mostly for making sure we respect the configure setup for things like debug-builds.

authors: kaysoky tillt

repo: dcos/dcos-mesos-modules


text:
Separate tests and packages

Lists out all dcos_test_utils as submodules and moves tests into their own directory

🤔 ERROR: unknown environment 'py35-integration-tests' Do those CI configs need to be updated?

@margaret Those shouldn't have been run against this PR at all because that integration test is not implemented until PR 36

authors: margaret mellenburg

repo: dcos/dcos-test-utils


text:
chore(deps): update dependency html-webpack-plugin to v4

This PR contains the following updates:

Package
Type
Update
Change

html-webpack-plugin
devDependencies
major
3.2.0 -> 4.0.2

Release Notes

jantimon/html-webpack-plugin
v4.0.2
Compare Source
Bug Fixes

don't remove trailing slashes from self closing tags by default (2281e4b)

v4.0.1
Compare Source
Bug Fixes

don't remove trailing slashes from self closing tags by default (2281e4b)

v4.0.0
Compare Source
The summary can be found in the release blog post.
Bug Fixes

Add dependencies from the child compilation to the main compilation (27c3e72)
Add typing for assets(Close jantimon#1243) (9fef060)
allow contenthash along with templatehash (049d4d3), closes #1033
Catch and ignore pretty-error errors (2056139), closes #921
Drop @types/webpack dependency (d4eb1c7)
Ignore foreign child compilers (1422664)
Improve perfomance for appcache files (b94e043)
load script files before style files files in defer script loading mode (97f9fb9)
Prevent chunks from beeing added multiple times (d65b37d)
Prevent lodash from being inlined to work around a babel-loader incompatibility (7f21910), closes #1223
Remove compilation.getStats() call for performance reasons (7005a55)
remove useless links for options (#1153) (267e0e0)
Update references to html-minifier (24bf1b5), closes #1311
typings.d.ts: added apply method type to HtmlWwbpackPlugin class definitoin (8b7255f), closes jantimon#1244
rename contenthash to templatehash (4c11c5d)
Repair typings (#1166) (f4cb241)
small type. minifcation instead of minification (#1154) (56037a6)
Use src/index.ejs by default if present (#1167) (c27e5e4)
chunksorter: Don't sort chunks by default (22fb03f)
loader: switch to loaderUtils.getOptions (a0a0f0d)
README: adds a link to template option documentation (f40aeae)
tests: Upgrade webpack-recompilation-simulator (dfe1d10)
Update lodash to 4.17.10 (cc3bf49)

Code Refactoring

Change the structure of the internal assets object (37db086)
Changed hook names and arguments - the hook order is 'beforeAssetTagGeneration', 'alterAssetTags', 'alterAssetTagGroups', 'afterTemplateExecution', 'beforeEmit', 'afterEmit' (14b4456)
Use Webpack 4 APIs (47efdea)

Features

add .toString implementation to htmlTags to allow easier rendering (34d8aa5)
Add default viewport meta tag for default template (302e39e), closes #897 #978
Add defer script loading (de315eb)
Add support for relative publicPath   (dbbdd81)
Add support for  tag (#1160) (c5d4b86)
Add support for minifying inline ES6 inside html templates (c66766c), closes #1262
Add support for the [contenthash] placeholder inside htm file names (ae8233a)
Add typings to package.json (a524e8f), closes #1132
Allow to return async template parameters (99f9362)
drop workaround for "Uncaught TypeError: webpack_require(...) is not a function" to be compatible with webpack 5 (15ad0d2)
Export major version of this plugin (6ae6f48)
merge templateParameters with default template parameters (1d66e53)
Provide a verbose error message if html minification failed (7df269f)
compiler: Add file dependencies (bbc07a3)
compiler: Use a single compiler for multiple plugin instances (f29ae88)
compiler: Use timestamps to verify cache validity (0ebcd17)
Remove selfClosingTag (5d3d8e4)
Remove type="text/javascript" from injected script tags (b46bf67)
Replace jade with pug in examples (d7ec407)
Switch from jasmine to jest (ae1f435)
hooks: Add a helper for easier hook access (b6dec4b)
hooks: Provide static getHook method for access to all html-webpack-plugin hooks (#995) (82b34a1)
Simplify  element and charset attribute (55313be)
support ES6 template string in default loader (d6b65dd), closes #950
Use jsdoc for static typing (a6b8d2d)
Use webpack 4 entries api to extract asset information (342867e)
html-tags: Add a helper to create html-tags (ee6a165)

BREAKING CHANGES

defaults: Use src/index.ejs if no template option is set.
defaults: The default template has now a predefined viewport meta tag
defaults: The default meta utf-8 declaration was changed to
hooks: Renamed beforeHtmlGeneration hook to beforeAssetTagGeneration
hooks: Renamed beforeHtmlProcessing hook to alterAssetTags
hooks: Renamed afterHtmlProcessing hook to beforeEmit
hooks: The html-webpack-plugin doesn't add its hooks to the compilation object anymore
The assets object which is used for the template parameters and inside hooks was changed. The chunks property was removed and the js and css property was converted from a string into an object { entryName: string, path: string}
The mimetype information "text/javascript" is removed from all generated script
tags
Remove selfClosingTag attribute
Template strings inside templates are now disabled by default
Dropped support for Webpack 1 - 3
Template variable webpack was removed
chunksorter: Chunks aren't sorted anymore by default

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

:tada: This PR is included in version 3.2.5 :tada:
The release is available on:

v3.2.5
GitHub release

Your semantic-release bot :package::rocket:

authors: mesosphere-ci mesosphere-renovate

repo: dcos/dcos-ui


text:
Add icons to repo

This PR adds all of the icons to our repository.

Reviewer: @daiyiwhale

authors: jfurrow mesosphere-web


text:
Feature/demos page

Description
https://jira.mesosphere.com/browse/DCOS_SITE-159
Urgency

[ ] Blocker
[ ] High
[ ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, and 1.9).
See the contribution guidelines.

Also, I just added a description to the tweeter demo, and all the other cards disappeared. Not sure what's up with that. Screencap attached:

@daveyheuser We're getting there! Last couple nitpicks:

[ ] Add a gray border around images/videos
[ ] Add the demos page to the list of pages for the build to watch
[ ] Change button text to "Try Demo"
[ ] Change the "Packages" field to "Services"

Hi @daveyheuser I added a video for the tweeter demo, and its not showing up correctly (see screencap):

Also, please don't forget about the comments above! thanks!

Hi Judith,
I fixed the video issue and the 4 others issues. PR: https://github.com/dcos/dcos-website/pull/1270 (this will merge my changes to the feature/demos-page branch).
Regards,
Rene

Sure is. I think we can just show them as a link next to the main call out button or as a secondary button. What would you want the label to be called?

"Watch Video" please :)

@daveyheuser I think this is almost ready. Still to do:

[ ] display pics instead of videos for non-featured demos
[ ] add "Watch Video" links for non-featured demos
[ ] change "Version" to "DC/OS Version"

Hi Judith,
I've completed the todo's, my changes can be found here: https://github.com/dcos/dcos-website/pull/1285
Regards,
Rene

[ ] All metadata fields should display well as arrays (currently the spacing is off)
[ ] Align featured demo video with title rather than use case
[ ] Make "Language" field plural ("Languages")
[ ] Build still seems like it's not auto-refreshing (this may be my problem)

@renesijnke It looks like we're still missing

[ ] All metadata fields should display well as arrays (use case and languages are still not right)
[ ] Use case should be a different font as it is in the mockup
[ ] My browser page now refreshes when I save changes to demos.json on a local build, but those changes still aren't reflected when the page refreshes. I still have to stop and start the build to make it work

Thanks for all your work on this!

Hi @judithpatudith
By 'Use case' you mean text like 'Fast Data, Logging' right? Because this is already a bold font. http://jmp.sh/20OCO1X
What exactly do you mean by 'use case and language are still not right'? You mean the vertical alignment between the demos? http://jmp.sh/1V9OmgW So the buttons 'Try demo' should be vertical aligned with each other?

@renesijnke
Yes, the use case is "Fast Data, Logging" etc. For some reason, it's called demo_name in the demos.json file. I see that it is bolded, but in the mockup that we agreed upon, it was also a different font from the demo title, and I would like it to be a different font here as well.
That same field should be able to take an array and display each element in the array correctly. All the elements are currently squished together, and there are no spaces between the elements.
This is also a problem for the listed languages. They should be displayed correctly when demos.json contains an array there, and currently, it is missing spaces between the elements.
The vertical alignment is also still inconsistent, but I'd rather just get the above changes in and ship this page than make other changes. We can file the vertical alignment problems as a bug later.

Hi @judithpatudith ,
I've fixed the issues & the font change. I've updated the feature/demos-page branch :)
Rene

@renesijnke sorry to nitpick, but are you able to change the use case font? I think it was arial or something on the mockup, and I know its a silly little thing but I thought it made a big difference. For reference the mockup is here.

Hi @judithpatudith,
I've changed the font so it matches with the mockup.
Rene

authors: daveyheuser judithpatudith renesijnke

repo: dcos/dcos-website


text:
Dummy change. DO NOT MERGE

Description

Urgency

[ ] Blocker
[ ] High
[ ] Medium

Requirements

See the contribution guidelines.
Build content locally and test for formatting/links.

retest this please

retest this please

retest this please

@joerg84 can I close this?


text:
[1.11] dcos-net not starting if IPv6 is disabled

High-level description
dcos-net is not starting when IPv6 is disabled.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-21471 dcos-net not starting if IPv6 is disabled

Related tickets (optional)
Other tickets related to this change:
Checklist for all PRs

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[x] Test Results: [link to CI job test results for component]
[x] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label [Ready For Review]

@mesosphere-mergebot override-status teamcity/dcos/test/azure/arm DCOS-21492

@mesosphere-mergebot override-status teamcity/dcos/test/azure/arm DCOS-21492

@mesosphere-mergebot bump-ee

@mesosphere-mergebot override-status teamcity/dcos/test/azure/arm QUALITY-1881

@mesosphere-mergebot bump-ee

authors: orsenthil urbanserj

repo: dcos/dcos


text:
Finalize assignments

Make assignment 1 ready for publishing in week 3
Clarify usage of ChatGPT and other AI tools (suggestion: allow students to use them but they need to explain how they used them, incl prompts and a description why it is correct, which should be about as long as the solution or longer)
Create grading rules (code executes, code is creating correct result, code is well written) and include it in assignment so that it is transparent to students.
add number of max points to each question
Finished code and solutions for assignments 3 and 4

Clarify usage of ChatGPT and other AI tools, create grading rules, add number of max points to each question for assignments 2 and 3

repo: ddahlmeier/sutd-mlops-course-code


text:
🛑 Danbs is down

In 99fa373, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 4112 ms

Resolved: Danbs is back up in 1d23f00.

repo: ddanbs/upptime


text:
🛑 Danbs is down

In ad0b9ad, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 3126 ms

Resolved: Danbs is back up in e6a4921 after 6 minutes.


text:
🛑 Danbs is down

In 2a281bc, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 3476 ms

Resolved: Danbs is back up in 5c6033f after 27 minutes.


text:
🛑 Danbs is down

In 7f080f6, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 3794 ms

Resolved: Danbs is back up in e5eee35 after 6 minutes.


text:
🛑 Danbs is down

In e94ba9f, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 96 ms

Resolved: Danbs is back up in 5ade151 after 20 minutes.


text:
🛑 Danbs is down

In 867f7c8, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 97 ms

Resolved: Danbs is back up in e64f19c after 12 minutes.


text:
🛑 Danbs is down

In 18062b0, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 128 ms

Resolved: Danbs is back up in ce0c17b after 13 minutes.


text:
🛑 Danbs is down

In 0f895c5, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 170 ms

Resolved: Danbs is back up in 6580704 after 24 minutes.


text:
🛑 Danbs is down

In d8a591d, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 254 ms

Resolved: Danbs is back up in 4f5a8f3.


text:
🛑 Danbs is down

In 5f670d4, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 96 ms

Resolved: Danbs is back up in b3a9718.


text:
🛑 Danbs is down

In bf83423, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 170 ms

Resolved: Danbs is back up in 49fabe2.


text:
🛑 Danbs is down

In 8c6f16f, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 196 ms

Resolved: Danbs is back up in 268aaab.


text:
🛑 Danbs is down

In cd3c00e, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 193 ms

Resolved: Danbs is back up in 7ba8003.


text:
Addd mkcert and make chrome trust https URLs, fixes #15

#15 points out that https URLs aren't trusted by chrome here.
This installs mkcert in the chrome container and makes it trust the shared mkcert CA.
curl also works inside the chrome container.
You can test this PR with
ddev get https://github.com/rfay/ddev-selenium-standalone-chrome/tarball/20230121_trust_certs
This seems to demonstrate that the demonstration repo provided by @ptmkenny in #15 will work OK, trusting https URLs.

So I tried running ddev get https://github.com/rfay/ddev-selenium-standalone-chrome/tarball/20230121_trust_certs in the test repo and then doing ddev restart but I couldn't get it working-- when I run ddev composer behat, I'm seeing an SSL failure after removing the --ignore-certificates flag in behat-ddev-selenium.yml.
I then tried to delete the data and start over with ddev delete and then ddev drush site:install --account-name=admin --account-pass=admin -y but I got the same error.
I committed my changes to a new branch so maybe you can see what I'm doing wrong?
https://github.com/ptmkenny/d10-behat/compare/main...pr17

I'm frustrated that you had the --ignore-certificate-errors in your repo that was supposed to demonstrate the error. Maybe I missed something along the way.
And I guess I don't know why you now care to remove that, and what trouble it causes.

I didn't have any trouble with your repo and ddev composer behat as you had put it out there to demo. Seems like you're changing the rules of the game :)
I imagine headless chrome needs something to install the CA at a different point, not sure.
Can you please get your repo to a place where it demonstrates the problem we're trying to solve? Or is that what the pr17 branch now is?

Please also help me to understand how to know that the failure which I now see is a result of untrusted cert. Behat has always been a bit inscrutable in its explanation of what's going on. How can I see the cert failure?

Ah, I see I can see the interaction at
https://d10-behat.ddev.site:7900/

I'm sorry to cause you frustration.  I'm going to restate the problem to avoid further miscommunication and to make sure that we have the same understanding.
The issue at hand is that when testing with behat using the selenium-standalone-chrome container, you get a certificate error if you test with an https URL. This error can be worked around by setting the  --ignore-certificate-errors flag for Chrome in the behat config file (in my repo's case, tests/behat/behat-ddev-selenium.yml.  Since this allows behat tests to be run, I submitted a PR that added a note to the README about setting this flag.  Then you suggested it would be better to fix this in the container itself if possible by getting it to trust the certificate (which I agree- that would definitely be better because it's zero config on the part of the user).
The repo I added was a "working" demonstration of an https URL with the --ignore-certificates flag.  That's probably the source of the confusion-- I submitted a repo in a working state instead of in a broken state because (to my mind) I was demonstrating the "fix" (my workaround) rather than a bug that needed to be fixed, but thinking about it now it makes more sense to submit a broken repo showing the problem and then an additional branch showing the fix, so I'm sorry about that.
So, to sum up, to see the problem, --ignore-certificate-errors should not be set (as is the case in pr-17, so pr-17 is demonstrating the problem, whereas the original main branch is "fixing" the https issue by setting --ignore-certificate-errors).

Looks like the installation of CA is covered in https://github.com/seleniumhq-community/docker-seleniarm#install-certificates-for-chromium-based-browsers, and apparently it doesn't trust the system CA by default.

But @ptmkenny does --ignore-certificate-errors solve all your problems? Is that the easy path?

But @ptmkenny does --ignore-certificate-errors solve all your problems? Is that the easy path?

Yes, it solves all my problems, specifically:

All the tests run as expected.  All https URLs, including images and CSS, load properly in the tests.
http to https redirects on the test site work.

I think this is also a pretty easy way to do it because if you are running behat tests like this you probably already have a behat.yml, and this is just adding one line to that file.

The chrome launched in the container should be able to accept --ignore-certificate-errors by default, but I haven't figured out how to get it to do that, despite a number of resources.

https://stackoverflow.com/a/25063706/215713
https://stackoverflow.com/a/49835651/215713
https://sahajamit.medium.com/selenium-chrome-dev-tools-makes-a-perfect-browser-automation-recipe-c35c7f6a2360
https://stackoverflow.com/a/74733865/215713
http://blogs.stevelongchen.com/2020/05/14/selenium-how-to-disable-or-bypass-connection-is-not-private-for-chrome-and-firefox/

I would have thought that just this would do the job,
  - MINK_DRIVER_ARGS_WEBDRIVER=[\"chrome\", {\"browserName\":\"chrome\",\"chromeOptions\":{\"w3c\":false,\"args\":[\"--disable-gpu\",\"--headless\", \"--no-sandbox\", \"--disable-dev-shm-usage\", \"--ignore-certificate-errors\",\"--allow-insecure-localhost\"]}}, \"http://selenium-chrome:4444/wd/hub\"]

I'm pretty sure we can make the selenium-chrome container trust the mkcert CA with docs, but it would be so very much easier to just figure out where the magic goes for defaulting --ignore-certificate-errors

I would have thought that just this would do the job,  - MINK_DRIVER_ARGS_WEBDRIVER=[\"chrome\", {\"browserName\":\"chrome\",\"chromeOptions\":{\"w3c\":false,\"args\":[\"--disable-gpu\",\"--headless\", \"--no-sandbox\", \"--disable-dev-shm-usage\", \"--ignore-certificate-errors\",\"--allow-insecure-localhost\"]}}, \"http://selenium-chrome:4444/wd/hub\"]

I am not an expert on this, but fixing it here should work for anyone using the default args, so the only people who wouldn't be covered by this case would (I think) be people like me who are specifying additional chrome options/setting up a browser profile in a behat config.yaml, which will require setting the flag manually.

@ptmkenny that's what I was aiming for. All the changes discussed here were aiming at that. The quote I gave was something in the docker-compose.

Closing this for now. Happy to return to it later or work on solving this problem another way. For now it's distracting for it to be in here.

authors: ptmkenny rfay

repo: ddev/ddev-selenium-standalone-chrome


text:
DDEV v1.24.0 Release notes draft

We have so many things to communicate about for the release. This set of release notes should also become a blog, so we should note things that people need to learn about for this.
(Related blog post in preparation at https://ddev.com.ddev.site:4321/blog/release-v1240 )
Highlights:
This is a major version of DDEV, with some changes in defaults.

PHP 8.4.1 is included, with all of the normal extensions, including Xdebug.
The drupal11 project type is added, and the drupal project type simply becomes an alias for it.
ddevcd command can be used to switch between projects. See ddev debug cd.
The ddev-webserver image is at least 25% smaller. Only a few locales are included by default, and only currently-supported versions of PHP are built in by default (but all the other versions still work). It was 480MB compressed, is now 361MB compressed.
ddev auth ssh can now be used with individual key files and can follow symlinks.

Change in defaults:

PHP 8.3 becomes the default for new projects for most project types.
NodeJS 22 becomes the default nodejs_version unless configured otherwise in the project's .ddev/config.yaml.

Installation
See the installation instructions for details, but it's easy:

macOS: brew install ddev/ddev/ddev or just brew upgrade ddev.
Linux or WSL2: Use apt install ddev or apt upgrade ddev see apt/yum installation
Traditional Windows: Use choco upgrade -y ddev, or download the ddev_windows_installer below.
Consider ddev delete images or ddev delete images --all after upgrading to free up disk space used by previous docker image versions. This does no harm.
Consider ddev config --auto to update your projects to current configuration.

Reversions and removals:

drupal project type is no longer a generic project type, but instead is an alias to latest stable Drupal (drupal11 right now)
In v1.23.5 we started preferring vendor/bin/composer to the specified composer_version but users thought that was a mistake, so this was reverted
The nginx-proxy router has been removed.
The ddev service enable and ddev service disable commands were removed, as they have long been superceded by the use of ddev add-on get and ddev add-on remove
Removed support for Python and Django4 projects.

Behavior Changes and Smaller Items:

Added dynamic timeout handling for scripts on start based on setting of default_container_timeout.
ddev describe changes how exposed ports are displayed for better clarity (thanks @ hanoii)
Only a limited set of locales is now installed in ddev-webserver by default. If you need more, use webimage_extra_packages: [locales-all]
Complex ddev composer command usage with json or args with spaces is fixed. (Bug was introduced in v1.23.5)

What's Changed

For the locale change described in the highlights: when I read about this change, I didn't see how to add back the locales because I didn't read the whole document. The answer is in the "Behavior changes and smaller items" section. So it would be nice to have a "read more" link in the highlights connecting the two sections on the locale change, or combine them into a single section in the highlights.

Also I'm happy to take a look at the blog post but I don't know how to access it because it's a local ddev link at the moment.

Sorry @ptmkenny - I had the wrong link in there. The PR is

https://github.com/ddev/ddev.com/pull/279

The rendered link is https://20241127-release-v1-24-0.ddev-com-front-end.pages.dev/blog/release-v1240/
Thanks for reviewing!

Released.

repo: ddev/ddev


text:
fix: add Docker filter by label without value, fixes #6088

The Issue

#6088

How This PR Solves The Issue
The Docker filter used the old syntax from fsouza/go-dockerclient, and as a result, it was looking for label=label=com.ddev.site-name instead of label=com.ddev.site-name.
I also finally figured out the syntax for filtering by label only.
Manual Testing Instructions
See #6088.
Automated Testing Overview

Related Issue Link(s)

#5787

Release/Deployment Notes

Testing with:

docker run --name=emptylabel -l com.ddev.site-name=""  ddev/ddev-webserver:v1.23.0 ls
 docker run --name=withlabel -l com.ddev.site-name="withlabel"  ddev/ddev-webserve r:v1.23.0 ls
 docker run -it --name=withlabel-running -l com.ddev.site-name="withlabel-running"  ddev/ddev-webserver:v1.23.0 bash

👍 All of these got stopped on ddev poweroff

authors: rfay stasadev


text:
Installing Jminer on ubuntu, launch fails with CL_OUT_OF_RESOURCES

I am running ubuntu 16.04 and attempting to get jminer up and going, I have already configed my props file and pathed the plot files but when attempting to run jminer from command line with ./run.sh I get the following TB:
Exception in thread "readerPool-1" org.jocl.CLException: CL_OUT_OF_RESOURCES
at org.jocl.CL.checkResult(CL.java:808)
at org.jocl.CL.clEnqueueNDRangeKernel(CL.java:20823)
at burstcoin.jminer.core.checker.util.OCLChecker.findLowest(OCLChecker.java:223)
at burstcoin.jminer.core.checker.task.OCLCheckerTask.run(OCLCheckerTask.java:71)
at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:50)
at burstcoin.jminer.core.checker.Checker.handleMessage(Checker.java:72)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.springframework.context.event.ApplicationListenerMethodAdapter.doInvoke(ApplicationListenerMethodAdapter.java:253)
at org.springframework.context.event.ApplicationListenerMethodAdapter.processEvent(ApplicationListenerMethodAdapter.java:174)
at org.springframework.context.event.ApplicationListenerMethodAdapter.onApplicationEvent(ApplicationListenerMethodAdapter.java:137)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:167)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:139)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:350)
at burstcoin.jminer.core.reader.task.ReaderLoadDriveTask.load(ReaderLoadDriveTask.java:140)
at burstcoin.jminer.core.reader.task.ReaderLoadDriveTask.run(ReaderLoadDriveTask.java:96)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Any assistance with this issue would be greatly appreciated.

I am a dippy doo, if you run into this issue please verify you defined your platform and device in props like so :

- OpenCL -----------------------------------------------------------------------------
-----------------------------------------------------------------------------------
The miner uses openCL for most of the mining calculations, ensure it is setup correctly.
Instructions can be found e.g. here (thanks cryo):
https://github.com/bhamon/gpuPlotGenerator/blob/master/README.md
You could also use that instruction to find your platformId and deviceId if needed.

platformId     - id of openCL platform on your system. one platform may have multiple
(default:0)      devices, the miner currently uses just one (in general not the bottleneck)

deviceId       - specifies the device used by OCLCecker, can be your first GPU,
(default:0)      in most cases it will not be 100% used. (depends on capacity)
-----------------------------------------------------------------------------------
platformId=1
deviceId=0

repo: de-luxe/burstcoin-jminer

license: mit


text:
Regarding the loading error of action.yaml

Hello,
I hope this message finds you well. I have been using de-vri-es/setup-git-credentials@v2 action, but I have encountered the following error:
Error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ''using: node20' is not supported, use 'docker', 'node12' or 'node16' instead.')
   at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs)
   at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Error: Fail to load de-vri-es/setup-git-credentials/v2/action.yml

Even when I specify @v2.1.0, I still encounter the same error.
Could you please take a look into this issue and provide assistance?
Thank you for your attention.

Thanks for reporting the issue. This was recently introduces in v2.1.1.
I've fixed the node version to node16 and released as 2.1.1. The v2 and v2.1 tags are also updated.
Thanks for reporting it!

Strange - it works just fine when I run actions with this module directly from my fork.

@takuya-takahash1 Which type of github-runner are you running this on? It's working fine on ubuntu-latest

@smlgbl
I cannot provide details, but I am running on a self-hosted runner using Image : myoung34/github-runner:latest on EKS.

@de-vri-es Issue has been resolved. Thank you for your prompt assistance!

No problem. However, I would prefer to update to node20 again. Is that self hosted runner image outdated?
If it is, one option is to stick with v2.0 if you can't support node20. Then v2.1 can upgrade to node20.

@de-vri-es
We are aware that the runner image is out of date and will be addressed in the near future.
Until then, we will use v2, so you can upgrade v2.1.0 to node20.

Be sure to pin it to v2.0, because the v2 tag will update to point to the latest v.2.x.y.

Cool! Upgraded to node20 again and released as v2.1.2.

authors: de-vri-es smlgbl takuya-takahash1

repo: de-vri-es/setup-git-credentials


text:
Open folder from termux terminal

Pls add opening folder from termux terminal using command line command
acode -o /path/

Hey @deadlyjack , I'm sorry I see this feature closed but I don't see know to do it.
Is there any way to open Acode via Termux?
I did something like this but it doesn't open any file/folder like this.
alias acode="am start --user 0 -n com.foxdebug.acode/com.foxdebug.acode.MainActivity"

Any help?

authors: ghost kud

repo: deadlyjack/Acode


text:
List Checkbox Spacer

Hey!
I really love your funky theme :) You did an amazing job on it!
However, there should definitely be a space between the checkbox and the text.
Currently, it's looking like this:

I edited the obsidian.css this way (very very ugly I imagine and as soon as somebody changes the font size the space is broken)
.markdown-preview-view .task-list-item-checkbox {
-webkit-appearance: none;
box-sizing: border-box;
border: 1px solid  var(--accent-2);
position: relative;
width: 1.25em;
height: 1.25em;
margin: 0;
margin-right: 10px;
box-shadow: 0 0 0.5em var(--accent-2);
}
It now looks like this:

Hope you can insert a space between the box and text in the next iteration!
Keep up the good work :)

Thanks, @chi-wi, This isn't my default theme, so I hadn't noticed. It's fixed now, so you should be able to update (or reapply the community theme).

authors: chi-wi deathau

license: Unlicense


text:
Getting the base domain

I would like to tag my clips with the source domain.
Therefore it would be nice to have the possibility to extract the base domain of an article.
For example https://www.theverge.com/2021/5/3/22417725/apple-vs-epic-full-trial-slideshows-opening-arguments would become
theverge.com

I just noticed that it isn't possible to use a tag with a dot (theverge.com) in Obsidian so maybe it is possible to only get the domain without the top level domain?
However since Obsidian just ignores the top level domain the full domain would still work.

repo: deathau/markdownload


text:
Update weaver-cats, weaver-discipline, ... to 0.7.13

Updates

com.disneystreaming:weaver-cats
com.disneystreaming:weaver-discipline
com.disneystreaming:weaver-scalacheck

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

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

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

labels: library-update, early-semver-minor, semver-spec-patch, commit-count:1

Superseded by #166.

repo: debasishg/tradeio


text:
Dbz 4146

https://issues.redhat.com/browse/DBZ-4146
Using backend response to fetch the SMT list and their properties.

Backend End point fixed, it's good to go.

@indraraj  - I'm seeing a couple issues while testing this.  Are you seeing the same?

Add a transformation.  The first time I select a transformation type, I get the following console warning:

react-dom.development.js?a814:67 Warning: Received the string true for the boolean attribute checked. Although this works, it will not work as expected if you pass the string "false". Did you mean checked={true}?
at input
at div
at Checkbox (webpack-internal:///../../node_modules/@patternfly/react-core/dist/esm/components/Checkbox/Checkbox.js:19:9)
at div
at SplitItem (webpack-internal:///../../node_modules/@patternfly/react-core/dist/esm/layouts/Split/SplitItem.js:16:11)
at div
at Split (webpack-internal:///../../node_modules/@patternfly/react-core/dist/esm/layouts/Split/Split.js:16:11)
at FormCheckboxComponent (webpack-internal:///./src/app/components/formHelpers/FormCheckboxComponent.tsx:22:108)
...

After adding a transformation, click apply.  Then click next to next page.  Then click 'back' to go back to SMT page.  Get the following error:

TransformsStep.tsx?f72a:55 Uncaught TypeError: response.forEach is not a function
at getOptions (TransformsStep.tsx?f72a:55)
at eval (TransformsStep.tsx?f72a:319)
at Array.map ()
at Object.eval [as children] (TransformsStep.tsx?f72a:304)
at WithLoader.render (WithLoader.tsx?e511:98)
at finishClassComponent (react-dom.development.js?a814:17485)
at updateClassComponent (react-dom.development.js?a814:17435)
at beginWork (react-dom.development.js?a814:19073)
at HTMLUnknownElement.callCallback (react-dom.development.js?a814:3945)
at Object.invokeGuardedCallbackDev (react-dom.development.js?a814:3994)
getOptions @ TransformsStep.tsx?f72a:55
eval @ TransformsStep.tsx?f72a:319
eval @ TransformsStep.tsx?f72a:304
WithLoader.render @ WithLoader.tsx?e511:98
...

Hey @mdrillin for the first points looks like its backend response issue for the type boolean default value is coming as "true"
defaultValue: "true"
title: "Add source topic name into key"
type: "BOOLEAN"
x-name: "key.enforce.uniqueness"

authors: indraraj mdrillin

repo: debezium/debezium-ui


text:
Audit log blog post (don't merge yet)

The basic flow is there, but still needs polishing and a summary/outlook.

Thanks a lot for the thorough proof-reading, @hpgrahsl! I've pushed one more commit addressing most your remarks and resolved the corresponding discussions.

Still reading but one comment is that all your Farmers in the transactions table are men as a lady farmer it would be nice to see a Farmer Margaret 🙂

Still reading but one comment is that all your Farmers in the transactions table are men as a lady farmer it would be nice to see a Farmer Margaret

@jbfletch, uff, absolutely, will update. Sorry Barry, Margaret it is :)

Pushed one more commit to address Jiri's remarks and add Margaret :)

Thanks a lot for all the feedback, everyone! I think I've incorporated all the suggestion and am quite happy about this piece. I'll push it to the website later today. Thanks again!

And it's live: https://twitter.com/gunnarmorling/status/1179062410134638594 :)

authors: gunnarmorling jbfletch


text:
Remove Unreachable if statement

if statement never will be true

@erdinctaskin Applied, thanks

authors: erdinctaskin jpechane

repo: debezium/debezium


text:
Add missing addresses for Zodiac and Usul on local network

Description
Add missing addresses for Zodiac and Usul on local network, assuming that it would be identical to Goerli
Notes
Bug appeared again after latest merge of #532
Issue (if applicable)
Closes #538
Testing

Run playwright tests and ensure issue described in #532 is solved

Screenshots (if applicable)

I am seeing the following console error related to network 4 not being set on https://deploy-preview-548--fractal-framework-interface-dev.netlify.app/#/daos/new
Array(0)```

I am seeing the following console error related to network 4 not being set on https://deploy-preview-548--fractal-framework-interface-dev.netlify.app/#/daos/new
At least one address for network 4 is not set! Array(0)

All the tests pass consistently for me, I'm not seeing that error

I am seeing the following console error related to network 4 not being set on https://deploy-preview-548--fractal-framework-interface-dev.netlify.app/#/daos/new
At least one address for network 4 is not set! Array(0)

This is fine IMO, we're going to remove Rinkeby support soon anyway.

I am seeing the following console error related to network 4 not being set on https://deploy-preview-548--fractal-framework-interface-dev.netlify.app/#/daos/new
At least one address for network 4 is not set! Array(0)

This is fine IMO, we're going to remove Rinkeby support soon anyway.

Ahhhhh that's Rinkeby, then yeah this is fine.

authors: SudoPumpkin adamgall herbig mudrila

repo: decent-dao/fractal-interface


text:
Content Change Detection and Tracking vs. Content Change Notification

The current EDV CS V1 spec supports the former but not the latter.
However, the latter can be built on top of the former at the client or CS Services level.

Discussed on the 24th of June WG call, since the opening of this issue the spec has added an API to expose a list of changes to documents in an EDV in a PULL style model. However this does not cover the case of notification or PUSH models.

The issue here is unclea.  It seems you might reword title and/or initial post to say "we need a push mechanism" because ... we do.

Discussed on Sep 2, 2021 call.
@mwherman2000 - Can you add further clarification to this? It's unclear on what the ask is.
Adding a 'Pending Close - 14 days' tag.

Closing, please feel free to open further issues with questions or clarification.

authors: TallTed dmitrizagidulin mwherman2000 tplooker

repo: decentralized-identity/edv-spec


text:
Minecraft 1.8 and lower not run

[ERROR] Error: Could not create the Java Virtual Machine.
Process exited with error code 1(There could be problems). Session since 18:21:05(0 min. total)

Исключение: Возникло исключение "System.NullReferenceException" в dotMCLauncher.Core.dll ("Ссылка на объект не указывает на экземпляр объекта."). Возникло исключение "System.NullReferenceException" в dotMCLauncher.Core.dll ("Ссылка на объект не указывает на экземпляр объекта.")

Исправил, спасибо!

authors: LowSkillGamer dedepete

repo: dedepete/FreeLauncher


text:
Fixes Frontend API requests

Some comments for the new API request:

Some CONST ENDPOINTS have been merged
Not sure: The token should still be in the header authorization w/ Bearer and we also need the userID for every API call from the frontend to the web backend
Status of the election ( we need that in the API doc, or ENUM/CONST somewhere to know which status corresponds to what )
Make a distinction between the hooks of getInfo and getAllInfo ( now they are the same , otherwise it breaks everything)
postData() hook function should change name

Pull Request Test Coverage Report for Build 2160975519

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 54.729%

Files with Coverage Reduction
New Missed Lines
%

contracts/evoting/evoting.go
3
73.7%

Totals

Change from base Build 2150150491:
-0.02%

Covered Lines:
3003

Relevant Lines:
5487

💛  - Coveralls

authors: badrlarhdir coveralls

repo: dedis/d-voting


text:
[CONTROLLER/PROMETHEUS] supports multi orgs in cache

This PR is for:

Server

supports multi orgs in cache
Checklist

[ ] Added unit test.

Backport to branches

main

 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.zhengya 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.

repo: deepflowio/deepflow


text:
bug - pressing space while typing a message causes the microphone to toggle

pressing space while typing a message causes the microphone to toggle

fixed


text:
feat: add fonts-agave

agave is a fixed-width outline typeface, designed and produced by type agaric.
Log: add fonts-agave
Issue: https://github.com/deepin-community/sig-deepin-sysdev-team/issues/386

/lgtm

authors: chenchongbiao chuan-boss

repo: deepin-community/fonts-agave


text:
SentencePiece is not supported by Android

Description
I'm trying to use SentencePiece lib in Android platform, but I get the following exception, saying SentencePiece is not supported in this platform:
    java.lang.UnsupportedOperationException: SentencePiece is not supported by this platform
        at ai.djl.sentencepiece.jni.LibUtils.copyJniLibraryFromClasspath(LibUtils.java:77)
        at ai.djl.sentencepiece.jni.LibUtils.loadLibrary(LibUtils.java:51)
        at ai.djl.sentencepiece.SpProcessor.<clinit>(SpProcessor.java:26)
        at ai.djl.sentencepiece.SpProcessor.newInstance(SpProcessor.java:37)
        at ai.djl.sentencepiece.SpTokenizer.<init>(SpTokenizer.java:49)
        at ai.djl.sentencepiece.SpTokenizer.<init>(SpTokenizer.java:38)
        at com.example.myapplication.nmt.NmtMarian.predict(NmtMarian.java:97)
        at com.example.myapplication.nmt.NmtClient.predict(NmtClient.java:126)
        at com.example.myapplication.MainActivity.Translate(MainActivity.java:70)
        at com.example.myapplication.TopSectionFragment.buttonClicked(TopSectionFragment.java:57)
        at com.example.myapplication.TopSectionFragment$1.onClick(TopSectionFragment.java:47)
        at android.view.View.performClick(View.java:7448)
        at android.view.View.performClickInternal(View.java:7425)
        at android.view.View.access$3600(View.java:810)
        at android.view.View$PerformClick.run(View.java:28305)
        at android.os.Handler.handleCallback(Handler.java:938)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at android.os.Looper.loop(Looper.java:223)
        at android.app.ActivityThread.main(ActivityThread.java:7656)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

Any solutions? I was wondering what causes SentencePiece not to be callable in Android.

@Arman-IMRSV DJL currently doesn't support android for SentencePiece.
Currently DJL doesn't have CI to build arm based binary. We only release Android binaries for PyTorch for the time being. We hope community contributors can help support arm base releases.
You can manually build SentencePiece using Android NDK, and make some changes to LibUtils.java to load the library.

For reference, someone was able to build SentencePiece for Android (not with DJL) at https://github.com/google/sentencepiece/issues/346

authors: Arman-IMRSV frankfliu zachgk

repo: deepjavalibrary/djl


text:
whether could you provide me a example for tensorflow that predict by gpu ，and tell me the computer setting info？

          I'm not sure if this is caused by CUDA 12.1 you are using. Can you try CUDA 11.3? or use PyTorch engine?

Originally posted by @frankfliu in https://github.com/deepjavalibrary/djl/issues/2554#issuecomment-1514796760
unfortunately，i had used CUDA 11.3 still get unknow device.
whether could you provide me a example for tensorflow that predict by gpu ，and tell me the computer setting info？

thanks very much ，is real cause by my local enviroment。


text:
Attempt to invoke virtual method 'void com.otaliastudios.transcoder.transcode.internal.AudioEngine.drainDecoder(int, java.nio.ByteBuffer, long, boolean)' on a null object reference

E/Transcoder: Fatal error while transcoding, this might be invalid format or bug in engine or Android.
java.lang.NullPointerException: Attempt to invoke virtual method 'void com.otaliastudios.transcoder.transcode.internal.AudioEngine.drainDecoder(int, java.nio.ByteBuffer, long, boolean)' on a null object reference
at com.otaliastudios.transcoder.transcode.AudioTrackTranscoder.onDrainDecoder(AudioTrackTranscoder.java:70)
at com.otaliastudios.transcoder.transcode.BaseTrackTranscoder.drainDecoder(BaseTrackTranscoder.java:250)
at com.otaliastudios.transcoder.transcode.BaseTrackTranscoder.transcode(BaseTrackTranscoder.java:165)
at com.otaliastudios.transcoder.engine.Engine.transcode(Engine.java:373)
at com.otaliastudios.transcoder.Transcoder$1.call(Transcoder.java:150)
at com.otaliastudios.transcoder.Transcoder$1.call(Transcoder.java:140)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)

(Pasted to all my answers today: it's been a long time since my last issues review. I am sorry about the delay and I know you likely have moved on by now. Still, I'm going to answer where I can)
I can't follow the stacktrace above, because the codebase was changed. Possibly the issue was fixed. Please let me know if you have any comments.

repo: deepmedia/Transcoder


text:
Error aria2c downloading files

I found that on an NFS filesystem, downloading the reference files with aria2c leads to an error. I googled and found a solution here:
find ~/alphafold/scripts/ -name "download*sh" | while read i; do perl -p -i -e 's/aria2c\ \"/aria2c\ \-\-file\-allocation\=trunc \"/' $i; done

Then following the instructions from then onwards works.

Neat. The other option might be to use wget or curl, the only potential disadvantage being slower download speed.

authors: Augustin-Zidek avilella

repo: deepmind/alphafold


text:
The tutorial uses deprecated methods

Hi, I ran the tutorial on both colab and the local machine, but it seems that some methods used in the tutorial are not supported in the current version of Reverb. Can you update the tutorial?

Hi, how did you solve this issue?

Actually, the tutorial is ahead of the release (v0.2.0). So, you can try the previous tutorials which match your reverb version: v0.2.0 demo

Hi, how did you solve this issue?

Hi, @MorganeAyle. Actually, the tutorial is ahead of the release (v0.2.0). So, you can try the previous tutorials which match your reverb version: v0.2.0 demo

Hi, how did you solve this issue?

Hi, @MorganeAyle. Actually, the tutorial is ahead of the release (v0.2.0). So, you can try the previous tutorials which match your reverb version: v0.2.0 demo

Thank you!

authors: MorganeAyle zhangxiaochuan

repo: deepmind/reverb


text:
v2: dynamic_unroll using lstm_with_recurrent_dropout doesn't work

The following code doesn't work:
import tensorflow as tf
import numpy as np
import sonnet as snt

class A():

    def __init__(self):
        self.train_core, test_core = snt.lstm_with_recurrent_dropout(1, dropout=0.5)

    @tf.function
    def forward(self, inp):
        return snt.dynamic_unroll(self.train_core, inp, self.train_core.initial_state(5))

a = A()
inp = tf.tile(tf.linspace(-1., 1., 20)[:,None,None], [1,5,1])
print(a.forward(inp))

promopting
ValueError: in converted code:

    test.py:13 forward  *
        return snt.dynamic_unroll(self.train_core, inp,
    /home/ziyu/sonnet/sonnet/src/utils.py:310 smart_autograph_wrapper  *
        return f_autograph(*args, **kwargs)
    /tmp/tmp8pmfpnpt.py:79 tf__dynamic_unroll
        state, output_tas, outputs = ag__.for_stmt(ag__.converted_call(tf.range, (1, num_steps), None, fscope), None, loop_body, get_state, set_state, (state, output_tas, outputs), ('state', 'output_tas', 'outputs'), ())
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/autograph/operators/control_flow.py:315 for_stmt
        composite_symbol_names)
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/autograph/operators/control_flow.py:478 _tf_range_for_stmt
        opts=opts,
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/autograph/operators/control_flow.py:794 _tf_while_stmt
        aug_init_vars, **opts)
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/ops/control_flow_ops.py:2675 while_loop
        back_prop=back_prop)
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/ops/while_v2.py:77 while_loop
        expand_composites=True)
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/util/nest.py:568 map_structure
        structure[0], [func(*x) for x in entries],
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/util/nest.py:568 <listcomp>
        structure[0], [func(*x) for x in entries],
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/indexed_slices.py:318 internal_convert_to_tensor_or_indexed_slices
        return ops.convert_to_tensor(value, dtype=dtype, name=name, as_ref=as_ref)
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/ops.py:1314 convert_to_tensor
        ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/constant_op.py:317 _constant_tensor_conversion_function
        return constant(v, dtype=dtype, name=name)
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/constant_op.py:258 constant
        allow_broadcast=True)
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/constant_op.py:296 _constant_impl
        allow_broadcast=allow_broadcast))
    /home/ziyu/anaconda3/envs/tf2/lib/python3.6/site-packages/tensorflow_core/python/framework/tensor_util.py:439 make_tensor_proto
        raise ValueError("None values not supported.")

    ValueError: None values not supported.

Seems it is because you are trying to store a None value to the initial state of a while loop. Changing the None value on this line to 0. appears to fix this.
I'm using tensorflow-gpu 2.1.0 and python 3.6. For sonnet I've tried both 2.0.0b0 and the HEAD version (1f5c0c241).

CC @superbobry

Seems it is because you are trying to store a None value to the initial state of a while loop. Changing the None value on this line to 0. appears to fix this.

The line mentioned:
  rate = LSTMState(hidden=dropout, cell=None)
@meta-inf do you think that extracting cell / initial state to the parameters of lstm_with_recurrent_dropout gonna fix issue?
So your usage can look like:
self.train_core, test_core = snt.lstm_with_recurrent_dropout(1, dropout=0.5, initial_state=0)

@SergeyVolodko I'm not sure what you meant by initial_state, since the LSTMState created in lstm_with_recurrent_dropout is used to store the dropout rate, and is not an initial state. The initial state of _RecurrentDropoutWrapper consists of both the initial state of the base RNN core, as well as a dropout mask (see here), and it doesn't seem like we should change the entire state to 0.
I guess the easiest fix is to set that cell parameter to 0: it's a placeholder and is never used. But any change that makes my original code example work would be fine to me.

Thanks, @meta-inf !
Indeed the parameter name I proposed is wrong. I will dive a bit deeper into the topic to get a better understanding of RNNs, LSTMs, and the code (any useful links are welcome).
But the approach I'm proposing is kind of intuitive: make currently hardcoded variable a parameter to increase method flexibility.
If somebody can confirm that extracting this parameter will make sense for other use cases - I'm happy to create a pull request with the improvement!
Of course, you are more than welcome to suggest a more suitable name for this parameter :)

authors: SergeyVolodko meta-inf tomhennigan

repo: deepmind/sonnet


text:
Fix for Paraphraser reader not to give degenerate labels

as they are only 1 or 0

as they are only 1 or 0

they are -1, 0, 1

repo: deepmipt/DeepPavlov


text:
Getting empty answer

Found 10 FAQs with empty answers indexed in elasticsearch. Deleted them now.
@bogdankostic Can you please filter out scraper results that have an empty answer string to avoid something like this in the future?

@tholor
The meta-scraper is already filtering out empty answers (see here).
I checked the resulting dataframe for empty strings, but none of the answer cells is empty. Also, I checked whether there are answer cells which only contain whitespace (thus not being technically empty), but this is not the case either.

authors: bogdankostic theapache64 tholor

repo: deepset-ai/COVID-QA


text:
feat: ability to override titles of specific pages

also

removing --unstable since it's no longer necessary
removing most of the safelist, due to PR 2266 in fresh
switching from as to satisfies in the fixture configs

there's some coverage debt missing here and in https://github.com/deer/fresh_blog/pull/31 that i'll fix later


text:
message inline

How or when can you use the functionality of telegram online messages

Hi, I'm not sure to have understood your question, could you elaborate please?

https://core.telegram.org/bots/inline.
To enable inline mode, please send me the placeholder message for queries to your bot. People will see this placeholder whenever they type @bot in the message field – in any chat. Tell them what they can get from your bot (e.g., Search GIFs...).

https://core.telegram.org/bots/inline.
To enable inline mode, please send me the placeholder message for queries
to your bot. People will see this placeholder whenever they type @bot
https://github.com/bot in the message field – in any chat. Tell them what
they can get from your bot (e.g., Search GIFs...).
El sáb, 28 may 2022 a las 18:23, Fabio Ivona @.***>)
escribió:

Hi, I'm not sure to have understood your question, could you elaborate
please?
—
Reply to this email directly, view it on GitHub
https://github.com/def-studio/telegraph/issues/90#issuecomment-1140337476,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMJB6HMQAR7GFCNOA4NUFUTVMKMGVANCNFSM5XHEMC7A
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ok I got it, will work on it over the next week and will ship and update with these features

repo: def-studio/telegraph


text:
Update url.py

Fix url.py to collect old tweet
original issue =>https://github.com/twintproject/twint/issues/1260

Nice 👍

repo: defaultcf/twint


text:
개요 - defjin

https://defjin.github.io/_posts/TextTheme/Usage
설정 변경  폴더 안에 있는 _config.yml 파일의 값들을 수정한다.구독피드  xml라이센스  license국제화  다양한 언어로 표시되도록 할 수 있음.마크다운강조_config.yml 에서 각 값들을 true로 변경한 후에 사용가능. 기본값은 false MathJax, Me...

ㅎㅇ

테스트


text:
win32-open3 not working with ruby 1.9.2

Although comes along with it, doesn't work.
Any alternatives...?

try https://github.com/matschaffer/win32-open3-19 which is available as a gem

authors: domainadmin ssboisen

repo: defunkt/github-gem


text:
doc(objectstorage): refactor configuring object storage documentation

Couple of things I wanted to accomplish here.

Make the top of the doc goal oriented to actually walk folks through wiring this up.
Remove as much repeated content as possible like the redundant helm charts sections.
Expand on the paths and env vars used to help point folks in the right direction if debugging.

Pretty major rewrite, so I wanted to throw this up for feedback. Haven't given it a close read for spelling and grammar.

@slack other than the typo this LGTM

Closes #169

authors: arschles slack

repo: deis/workflow


text:
Error  when running krustlet with Kind

Hi, I am experiencing the following error when I tried the steps in the link. I used version 0.4.0 for krustlet. Output is:
$ krustlet-wascc --node-ip 172.17.0.1 --bootstrap-file=~/.krustlet/config/bootstrap.conf
BOOTSTRAP: TLS certificate requires manual approval. Run kubectl certificate approve inst1-tls
BOOTSTRAP: received TLS certificate approval: continuing
[2020-08-12 ERROR kubelet::kubelet] Unable to patch status during pod failure for kube-proxy-4m6f4: ApiError: pods "kube-proxy-4m6f4" not found: NotFound (ErrorResponse { status: "Failure", message: "pods "kube-proxy-4m6f4" not found", reason: "NotFound", code: 404 })
[2020-08-12 ERROR wascc_provider] Unable to find pod kube-proxy-l5x4t in namespace kube-system when trying to stop all containers
Any sugestion on how to resolve this?

On the release page, it's mentioned as an issue, however it does not impact the running of krustlet.

repo: deislabs/krustlet


text:
Unable to find a specification for SlideMenuControllerSwift

I just upgrade Xcode to 8.0 and my project to Swift3.0
After that i remove all pod and reinstall all of them again.
But i have a problem to run 'pod install', i get the following error:
Analyzing dependencies
[!] Unable to find a specification for SlideMenuControllerSwift
I have no idea to fix it. Please help me.

Is there any other framework okay?

repo: dekatotoro/SlideMenuControllerSwift


text:
Subclass or wrapper for form models.

Currently 2 approaches are used.
For the profile form a subclass of the activerecord model is used, for the registration form a wrapper class is used.
Why use 2 different approaches?

Activerecord subclasses represent a row from a table, however other models are used to collect user input and do some logic, we cannot use activerecord for this.

authors: SamMousa dmeroff


text:
Refactoring DeltaTable for cleanliness

Previously DeltaTable was only taking Dataset[Row] as the parameter. And was trying to figure out the DeltaLog via the analyzed plan. Moved to a cleaner approach where we pass the DeltaLog as well as a parameter.

I agree this is a cleaner approach. However, I am making the release 0.3.0 today, so lets hold off this PR until that is done. thank you for contributing.

authors: rahulsmahadev tdas

repo: delta-io/delta


text:
Updated Hyperdrive metadata

Description
This PR adds a kind function to each contract that provides a human-readable way to identify a given contract. In addition to this change, the registry was updated to support kind, and the name and version fields were added to any straggler contracts.
Review Checklists
Please check each item before approving the pull request. While going
through the checklist, it is recommended to leave comments on items that are
referenced in the checklist to make sure that they are reviewed. If there are
multiple reviewers, copy the checklists into sections titled ## [Reviewer Name].
If the PR doesn't touch Solidity, the corresponding checklist can
be removed.
[[Reviewer Name]]

[ ] Tokens

[ ] Do all approve calls use forceApprove?
[ ] Do all transfer calls use safeTransfer?
[ ] Do all transferFrom calls use msg.sender as the from address?

[ ] If not, is the function access restricted to prevent unauthorized
token spend?

[ ] Low-level calls (call, delegatecall, staticcall, transfer, send)

[ ] Is the returned success boolean checked to handle failed calls?
[ ] If using delegatecall, are there strict access controls on the
addresses that can be called? It shouldn't be possible to delegatecall
arbitrary addresses, so the list of possible targets should either be
immutable or tightly controlled by an admin.

[ ] Reentrancy

[ ] Are functions that make external calls or transfer ether marked as nonReentrant?

[ ] If not, is there documentation that explains why reentrancy is
not a concern or how it's mitigated?

[ ] Gas Optimizations

[ ] Is the logic as simple as possible?
[ ] Are the storage values that are used repeatedly cached in stack or
memory variables?
[ ] If loops are used, are there guards in place to avoid out-of-gas
issues?

[ ] Visibility

[ ] Are all payable functions restricted to avoid stuck ether?

[ ] Math

[ ] Is all of the arithmetic checked or guarded by if-statements that will
catch underflows?
[ ] If Safe functions are altered, are potential underflows and
overflows caught so that a failure flag can be thrown?
[ ] Are all of the rounding directions clearly documented?

[ ] Testing

[ ] Are there new or updated unit or integration tests?
[ ] Do the tests cover the happy paths?
[ ] Do the tests cover the unhappy paths?
[ ] Are there an adequate number of fuzz tests to ensure that we are
covering the full input space?

Pull Request Test Coverage Report for Build 9559219588
Details

8 of 9 (88.89%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 92.092%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/src/deployers/HyperdriveDeployerCoordinator.sol
0
1
0.0%

Totals

Change from base Build 9556880128:
-0.03%

Covered Lines:
1968

Relevant Lines:
2137

💛  - Coveralls

Pull Request Test Coverage Report for Build 9570416796
Details

8 of 9 (88.89%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 92.092%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/src/deployers/HyperdriveDeployerCoordinator.sol
0
1
0.0%

Totals

Change from base Build 9556880128:
-0.03%

Covered Lines:
1968

Relevant Lines:
2137

💛  - Coveralls

Pull Request Test Coverage Report for Build 9570416286
Details

8 of 9 (88.89%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 92.092%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/src/deployers/HyperdriveDeployerCoordinator.sol
0
1
0.0%

Totals

Change from base Build 9556880128:
-0.03%

Covered Lines:
1968

Relevant Lines:
2137

💛  - Coveralls

Pull Request Test Coverage Report for Build 9570724127
Details

8 of 9 (88.89%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 92.092%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/src/deployers/HyperdriveDeployerCoordinator.sol
0
1
0.0%

Totals

Change from base Build 9556880128:
-0.03%

Covered Lines:
1968

Relevant Lines:
2137

💛  - Coveralls

Pull Request Test Coverage Report for Build 9571274219
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

8 of 9 (88.89%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 92.092%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/src/deployers/HyperdriveDeployerCoordinator.sol
0
1
0.0%

Totals

Change from base Build 9556880128:
-0.03%

Covered Lines:
1968

Relevant Lines:
2137

💛  - Coveralls

Pull Request Test Coverage Report for Build 9571577157
Details

8 of 9 (88.89%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 92.106%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/src/deployers/HyperdriveDeployerCoordinator.sol
0
1
0.0%

Totals

Change from base Build 9571325900:
-0.03%

Covered Lines:
1972

Relevant Lines:
2141

💛  - Coveralls

authors: coveralls jalextowle

repo: delvtech/hyperdrive


text:
🛑 SearxNG is down

In 9e6d904, SearxNG (https://sx.eka.monster) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SearxNG is back up in 2bcfe98 after 7 minutes.

repo: demonsteru/up


text:
🛑 SearxNG is down

In 509eb8f, SearxNG (https://sx.eka.monster) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SearxNG is back up in 3843cbc.