ArcDps crash on empty message

Freesnöw at 9/20/2020 7:53:34 PM +00:00

🤔 interesting.  <@!243389466100760576>
14:51:36.6600 | FATAL | Blish_HUD.DebugService | Blish HUD encountered a fatal crash!
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at Blish_HUD.ArcDpsService.MessageHandler(MessageData data) in D:\a\Blish-HUD\Blish-HUD\Blish HUD\GameServices\ArcDpsService.cs:line 140
   at Blish_HUD.ArcDps.SocketListener.ProcessReceivedData(Int32 dataStartOffset, Int32 totalReceivedDataSize, Int32 alreadyProcessedDataSize, AsyncUserToken token, SocketAsyncEventArgs e) in D:\a\Blish-HUD\Blish-HUD\Blish HUD\GameServices\ArcDps\SocketListener\SocketListener.cs:line 139
   at Blish_HUD.ArcDps.SocketListener.ProcessReceive(SocketAsyncEventArgs e) in D:\a\Blish-HUD\Blish-HUD\Blish HUD\GameServices\ArcDps\SocketListener\SocketListener.cs:line 109
   at System.Net.Sockets.SocketAsyncEventArgs.OnCompleted(SocketAsyncEventArgs e)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.Sockets.SocketAsyncEventArgs.FinishOperationSuccess(SocketError socketError, Int32 bytesTransferred, SocketFlags flags)
   at System.Net.Sockets.SocketAsyncEventArgs.CompletionPortCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* nativeOverlapped)
   at System.Threading._IOCompletionCallback.PerformIOCompletionCallback(UInt32 errorCode, UInt32 numBytes, NativeOverlapped* pOVERLAP)

(From QuitarHero: "i was just superspeed+quickness choya'ing in a frac")

REF: https://discordapp.com/channels/531175899588984842/534492173362528287/757328626156044338

another discussion about it: https://discord.com/channels/531175899588984842/536970543736291346/805811006605099038

Hasn't been an issue in a long time.


Add bounds for packages

Added back the original bounds, but bumped versions for http-client, http-client-tls, and bifunctors. Also bumped stack resolver to LTS 8.20.

so, what's the point of having the stack resolver and the cabal file package bounds? Even though there's tons of documentation on stack, I can't find anything about this stuff.

As I understand it, although stack does make explicitly stating bounds in the cabal file unnecessary, it is still best practice to include bounds in the cabal files of packages that will be uploaded to hackage, as not everyone attempting to build the package will be using stack to do so. See the discussion here.

ok thanks.
I thought that stack would generate a .cabal file with these bounds before uploading to hackage, but I'm not sure if I actually read that anywhere or imagined it


Error: ER_NO_DEFAULT_FOR_FIELD: Field 'streaming_read_key' doesn't have a default value

Hi,
I have this error on the last versions of jsbin v3.27.X.
I created the mysql database from  full-db-v3.mysql.sql
But when I want to save a bin I have this error :
Error: ER_NO_DEFAULT_FOR_FIELD: Field 'streaming_read_key' doesn't have a default value

I found this old issue : #1102
What should I do ? remove the columns ?

+1

Hi there,
Any idea on this one ?


Use a custom unmarshaller for vars, fix IncludeWorkflow autovars

Autovars can now be used in Vars

Codecov Report

Merging #92 into master will increase coverage by 0.26%.
The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master      #92      +/-   ##
==========================================
+ Coverage   79.29%   79.55%   +0.26%
==========================================
  Files          20       20
  Lines        1560     1541      -19
==========================================
- Hits         1237     1226      -11
+ Misses        247      242       -5
+ Partials       76       73       -3

Impacted Files
Coverage Δ

daisy/workflow/step_includeworkflow.go
61.11% <100%> (+4.35%)
:arrow_up:

daisy/workflow/step_sub_workflow.go
46.15% <100%> (-2%)
:arrow_down:

daisy/workflow/workflow.go
82.79% <83.33%> (+0.63%)
:arrow_up:

daisy/workflow/step.go
92.59% <0%> (+1.23%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 40f806c...a16a55b. Read the comment docs.


Edl/closest point on curve chain with distance index

It is observed (by NW) that "closestPoint" query to a CurveChainWithDistanceIndex fails when the nearest primitive is an IntegratedSpiral.
This is because in construction of the distance index the spiral presented its strokes instead of a reference to itself with a stroke count.        This problem may affect multiple primitive types that sometimes present themselves directly and sometimes as strokes.
To solve, there is a new optional method in the stroking interface.  The handler requesting strokes can directly indicate that it wants  the primary geometry with stroke count, instead of being represented by a proxy linestring.
Specifically, in the IntegratedSpiral, it diverts to the "else" branch of the announcement in emitStrokableParts.  This may
need to be added to other emitStrokableParts implementations . . .)

@Mergifyio update

@Mergifyio update


How to know if a Method is async?

I've looked at the docs and printed a method using {{ method }} but I don't see how to know if a method is async.
I can see a boolean for the throwing effect (throws = true) but not for the async one.
Is there a way to know if a method is async or is just not supported yet?

Not supported yet, we'd need to add it

I'm also interested in that, I have a template for generating initializers but thats not working with async closures.
{% for type in types.structs %}
{% if type|annotated:"AutoInit" %}
{% set spacing %}{% if type.parentName %}    {% endif %}{% endset %}
{% map type.storedVariables into parameters using var %}{{ var.name }}: {% if var.typeName|hasPrefix:"(" %}@escaping {% endif %}{{ var.typeName }}{% endmap %}
// sourcery:inline:auto:{{ type.name }}.AutoInit
{{spacing}}{{ type.accessLevel }} init({{ parameters|join:", " }}) {
{{spacing}}    {% for variable in type.storedVariables %}
{{spacing}}    self.{{ variable.name }} = {{ variable.name }}
{{spacing}}    {% endfor %}
{{spacing}}}
// sourcery:end
{% endif %}
{% endfor %}

Is someone already adding support for this? If not I can try to add it, just point me to the right direction @krzysztofzablocki

When I run the command sourcery in root path of project, i get this error.
Using configuration file at '.sourcery.yml'
Scanning sources...
Found 57 types in 41 files, 7 changed from last run.
Loading templates...
error: Error Domain=NSCocoaErrorDomain Code=260 "The file “ejs.js” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/opt/homebrew/bin/ejs.js, NSUnderlyingError=0x13d686420 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
Error Domain=NSCocoaErrorDomain Code=260 "The file “ejs.js” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/opt/homebrew/bin/ejs.js, NSUnderlyingError=0x13d686420 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}%

I submitted the PR, but the tests are failing in CircleCI.
I didn't know why.

@krzysztofzablocki I think this issue could be closed, doesn't it?
The implementation was merged and available for using in master branch.

FYI I used the master branch to update our templates and this works as expected 👌🏻
Thanks!


feat: add admonitions

Example result:

Closes #22

cc @janetwu11

Since we have relatively high certainty that Devnet data will have to be migrated to Testnet by developers, we can add "It is expected that Devnet data will be incompatible with Testnet and developers will need to be responsible for migrating Devnet applications and data to Testnet. Detailed migration guides will be provided when Testnet becomes available."

"It is expected that Devnet data will be incompatible with Testnet and developers will need to be responsible for migrating Devnet applications and data to Testnet. Detailed migration guides will be provided when Testnet becomes available.

Thanks a lot, @janetwu11. I've added a slightly adapted version of your suggestion to the disclaimers in 7f4697f64be6987a8b86b4f8d268e03c998071ec.


Blank screen after logout

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Log into an account with some chats
Perform some, actions, switch between some chats
Sign out

Expected Result:
User can see log in page.
Actual Result:
Blank page with this console error.

Workaround:
Refresh the page.
Platform:

Where is this issue occurring?
Probably all of them.

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
Reproducible in staging?: Yes
Reproducible in production?: No
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @roryabraham
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1636082766011900
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Introduced by solving this issue in this PR: https://github.com/Expensify/App/pull/6084.


How to sanitize $_FILES super global?

Is there a way to sanitize the $_FILES array or is whitelisting my only option?
if ( ! empty( $_FILES['avatar']['name'] ) ) {
    $avatar = wp_handle_upload(
		wp_unslash( $_FILES['avatar'] ),
		array(
			'mimes'                    => $this->mime_types,
			'test_form'                => false,
			'unique_filename_callback' => array( $this, 'unique_filename_callback' ),
		)
    );
}

Gives:
Detected usage of a non-sanitized input variable: $_FILES

I think that wp_handle_upload() and wp_handle_sideload() should be added to the list of sanitizing functions. They both use _wp_handle_upload(), which sanitizes the file name, type, and extension.

I should note that some filters and error functions could be called before the sanitization occurs, however.


fix: Remove module_variable_optional_attrs experiment

The experiment module_variable_optional_attrs has ended and version 1.3 of Terraform will not permit a configuration to contain reference to the experiment, thus, this module is not working in 1.3.

Because the experiment is concluded, the experimental implementation of this feature is no longer available and Terraform v1.3.0 and later will not accept any module that contains the explicit experiment opt-in.

https://www.terraform.io/language/upgrade-guides#concluding-the-optional-attributes-experiment
I have removed module_variable_optional_attrs from providers.tf and changed the minimum version to 1.3. I think this bump in version (from 0.14 -> 1.3) qualifies as a breaking change, so this should be released as v3 of the module.
As a short term workaround for anyone encountering this issue, limit your version of Terraform to 1.2:
terraform {
  required_version = "~> 1.2.0"

  experiments = [module_variable_optional_attrs]
}

Ah, great. Thanks for this!


 There's a link to it in the README.md.

@steshaw thanks for reminding me! I made the repository private as I work out some issues with the formalism. I'll update the README tomorrow...


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_b4pf8swhkb/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_b4pf8swhkb/clone/recipe/meta.yaml:24: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b4pf8swhkb/clone/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_b4pf8swhkb/clone/recipe/meta.yaml:48: missing_pip_check: For pypi packages, pip check should be present in the test commands
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_e0nsh7hf6j/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_e0nsh7hf6j/clone/recipe/meta.yaml:24: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_e0nsh7hf6j/clone/recipe/meta.yaml:24: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_e0nsh7hf6j/clone/recipe/meta.yaml:48: missing_pip_check: For pypi packages, pip check should be present in the test commands
Errors were found


2 tooltips appear

when the element I hover on to show the tooltip is near the edge of the window, 2 tooltips appear.

Closed in favor of https://github.com/wwayne/react-tooltip/issues/371


"failed to parse app options file" on admin.initializeApp()

Environment

Operating System: Ubuntu 14.04 LTS
Firebase SDK: 5.11.0
Library: 1.0.0
Firebase Product: SDK / Cloud Functions

Problem
After upgrading to Firebase Functions 1.0.0 as described in the migration guide, and migrating the way admin.initializeApp() is called, the project no longer deploys correctly.
Seems that the following error is thrown from loadOptionsFromEnvVar() method, which tries to read from process.env[exports.FIREBASE_CONFIG_VAR] and, AFAIK, is not defined.
Steps to Reproduce:
Running npm run deploy from a clean project setup:
alix@Spin7:~/firebase-test/functions$ npm run deploy

> functions@ deploy /home/alix/firebase-test/functions
> firebase deploy --only functions

=== Deploying to 'firebase-test'...

i  deploying functions
Running command: npm --prefix "$RESOURCE_DIR" run lint

> functions@ lint /home/alix/firebase-test/functions
> tslint --project tsconfig.json

Running command: npm --prefix "$RESOURCE_DIR" run build

> functions@ build /home/alix/firebase-test/functions
> tsc

✔  functions: Finished running predeploy script.
i  functions: ensuring necessary APIs are enabled...
✔  functions: all necessary APIs are enabled
i  functions: preparing functions directory for uploading...

Error: Error occurred while parsing your function triggers.

Error: Failed to parse app options file: Error: ENOENT: no such file or directory, open '[object Object]'
    at FirebaseAppError.FirebaseError [as constructor] (/home/alix/firebase-test/functions/node_modules/firebase-admin/lib/utils/error.js:39:28)
    at FirebaseAppError.PrefixedFirebaseError [as constructor] (/home/alix/firebase-test/functions/node_modules/firebase-admin/lib/utils/error.js:85:28)
    at new FirebaseAppError (/home/alix/firebase-test/functions/node_modules/firebase-admin/lib/utils/error.js:119:28)
    at FirebaseNamespaceInternals.loadOptionsFromEnvVar (/home/alix/firebase-test/functions/node_modules/firebase-admin/lib/firebase-namespace.js:214:19)
    at FirebaseNamespaceInternals.initializeApp (/home/alix/firebase-test/functions/node_modules/firebase-admin/lib/firebase-namespace.js:64:28)
    at FirebaseNamespace.initializeApp (/home/alix/firebase-test/functions/node_modules/firebase-admin/lib/firebase-namespace.js:362:30)
    at Object.<anonymous> (/home/alix/firebase-test/functions/lib/index.js:5:7)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)

Having trouble? Try firebase deploy --help
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! functions@ deploy: `firebase deploy --only functions`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the functions@ deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alix/.npm/_logs/2018-04-06T09_46_33_752Z-debug.log

Relevant Code:
import * as admin from 'firebase-admin';
import * as functions from 'firebase-functions';

admin.initializeApp();

export const helloWorld = functions.https.onRequest((request, response) => {
  response.send("Hello from Firebase!");
});

Solved by downgrading firebase-tools: https://github.com/firebase/firebase-tools/issues/725#issuecomment-379171518.


Hruschka et al. 2014: Turkic

https://doi.org/10.1016/j.cub.2014.10.064

supplement doesn't contain mcc or posterior. Need to contact the authors.


Dark mode toggle - Visual design

Dark mode toggle
As it stands I only include the mode toggles on mobile in the "main menu display" (to avoid them getting lost in longer scrolls on submenu pages...I suppose they could go above nav items, but don't think they need that prioritization).

@all-contributors please add @shea-fitz for design

Closed by #199


Is there a way to use this extension without building a mix project?

I am using exercism and my elixir folder contains pre-written pieces of tests and code in folders that do not have any mix files attached to them. I am not able to use the features of your extension in these situations.
Is this a bug on my end? Or is this not supported?

Hi,
currently we can only support Mix projects.

Ok, Thanks


[GHSA-5rqg-jm4f-cqx7] Infinite loop causing Denial of Service in colors

Updates

Affected products

Comments
wrong npm package name!

Hi @seng1e, unfortunately we are not accepting this contribution because upon further review the affected package is accurate. If you have any reference(s) to support your contribution feel free to post them here. Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!

Hi @CallmeMari , I made sure the name of the affected package was colors,with lowercase initials. And found the analysis article on the poisoning attack at the time, and all three versions affected by the vulnerability have been removed, but the package name is indeed colors.


ignoring forks

How can I modify the query to ignore/exclude the forks from the results?

Hi @badar-chachar! To accomplish that, you will need to make two simple modifications in the index.js file:

Remove the 'forks' property from the 'formattedResults' data structure to ensure it's excluded from the final output.

Eliminate the 'forkCount' field from the query to ensure it's not included when fetching the data.

Let me know if this helps!

Hello @oscarpobletes, thanks for the prompt reply.  Removing 'forkCount' and 'forks' doesn't impact the query results, it returns the same number of repositories.
Can we explicitly specify 'fork=false' in the query? Or something similar?

Hi @badar-chachar
It looks like that possibility is a recent addition (March 2023) to Github search results. see here:
https://github.com/orgs/community/discussions/39870#discussioncomment-5294549
Normally you only need to add "NOT is:fork" to the search query in the command line
Let us know how it goes. Later today, I will test it myself.

@ksegla I added NOT is:fork to the query string as given below,
query ($searchQuery: String!, $first: Int, $after: String) {   search(query: $searchQuery, NOT is:fork, type: REPOSITORY, first: $first, after: $after)
and it gives error Error: Parse error on "is" (IDENTIFIER) at [2, 35]
let me know if NOT is:fork is to be added somewhere else in the query.

@ksegla you were right, passing not is:fork via command line does the trick.
node index.js --query "smart contract not is:fork"

Great!
Closing the issue then.


Ruby272 warnings

Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call

👍

👍


[4pt] Display rockets - Lists render

Use useSelector() Redux Hook to select the state slices and render lists of rockets in corresponding routes. i.e.:

// get rockets data from the store
const rockets = useSelector(state => state.rockets);

You can style the whole application "by hand" or you could use React Bootstrap, a UI library that could speed up the process. This is a popular library and working with its components would be good practice.
Render a list of rockets (as per design). For the image of a rocket use the first image in the array of flickr_images.

Hello @DJ-MrJay
Kindly look at this PR for code review.
https://github.com/Zuhaib042/Space-Travelers-Hub/pull/29


500 error response in data object disassociation from DUP

/api/data-uses/{dupId}/objects/{sdOid}
Need to check in the BE.

let's check functionality with new BE


Empty seats skip sorting problems

Hello, may I ask how to skip the red checkered (empty seats), thank you

did you fix this one?


net-linux-smp crash in autobuild

Original author: Nikhil Jain
Original issue: https://charm.cs.illinois.edu/redmine/issues/835

Investigate the cause for the crash. Attempt a run with +isomalloc_sync as a possible solution.

Original date: 2015-09-18 19:03:30

+isomalloc_sync does not solve the problem.. The crash happens once in a while and the same problem exists in netlrts as well.
I'm investigating it more..

Original date: 2015-09-18 19:17:30

The fix is implemented here: ~~https://charm.cs.illinois.edu/gerrit/#/c/832/~~ https://github.com/UIUC-PPL/charm/commit/7ecb906c111ebd6968f142cbf6ddfdb5f89d0849

Original date: 2015-11-11 03:05:25

Set status back to Merged so that we can distinguish whether the code was changed in some way, or the fix was elsewhere. Both are non-open states from Redmine's perspective.


⚠ Guya.moe Proxied has degraded performance

In 9ff53df, Guya.moe Proxied (https://ice.guya.moe/) experienced degraded performance:

HTTP code: 200
Response time: 12959 ms

Resolved: Guya.moe Proxied performance has improved in 6e4d89e after 12 hours, 53 minutes.


Fix typo

[ ] I have added an entry to docs/changelog.md

Summary of changes
Test plan

Tested by running
# command(s) to exercise these changes

thanks!


owasp-crs-v030301-id932130-rce triggers with () on a form's input field

Hi,
I'm using GLPI (https://glpi-project.org/) and when I'm about to create a new ticket case we've seen that whenever we input an empty pair of parenthesis [()], (image below)

it triggers the following rule:
"priority": 3,
"outcome": "DENY",
"preconfiguredExprIds": [
"owasp-crs-v030301-id932130-rce"
],
"name": "glpi-owasp-rules",
"configuredAction": "DENY"
}
It doesn't matter if there is something inside the parenthesis, it triggers the deny rule, which seems a bit odd given that there is no further pattern besides the parenthesis.

When I test with your input () as an argument against our sandbox, the request doesn't trigger any rule:
Nightly build:
curl --header "x-crs-paranoia-level: 1" --header "x-format-output: txt-matched-rules" --header "x-crs-version: nightly"  'http://sandbox.coreruleset.org/?arg=%28%29'
3.3.2:
curl --header "x-crs-paranoia-level: 1" --header "x-format-output: txt-matched-rules" --header "x-crs-version: 3.3.2"  'http://sandbox.coreruleset.org/?arg=%28%29'
Which version are you using? Do you have more information? I can not reproduce your issue.

Thanks for the info, here is what I think is happening:
on the input field, there are a coulpe  tags inserted by the framework, and when we inserted () we ended up with >() which according to the rule would match something like:

(foo)    Process substitution

and it does indeed find a match in the regex pattern for:

()
https://regex101.com/r/YeifBP/1

I don't know if that's the intended purpose for the rule, because it's a bit vague to block traffic based on that patter on P1, right now for example we can't use parentheses in the input field to add supplemental information.

There are actually frameworks that add tags to the request, which are then blocked by the CRS.
In your case, I would add a tuning rule that removes the target ARGS:<name-of-description-field> from the rule 932130 with:
SecRuleUpdateTargetById 932130 !ARGS:<name-of-description-field> and add this tuning rule AFTER the CRS rules.
I searched for false positives reports of rule 932130 in old issues and didn't find similar cases.
So, I don't think we're going to change the CRS rule here unless there are other opinions from the team.

I second your assessment @franbuehler and sorry for the inconvenience @cccnc. And thank you for reporting even if we are not likely to take action. It helps us having FPs in our records for future reference or rules evolving into serial offenders.


[FLINK-10493][core] Migrating the TupleSerializerBase serializers family

What is the purpose of the change
This PR migrates the serializers that inherit from the TupleSerializerBase to the new type serializer snapshot abstraction.
The following serializers are migrated as part of this PR:

TupleSerializer
Tuple0Serializer
Tuple2CaseClassSerializer
CaseClassSerializer (scala macro generated)

Brief change log

97f41a0fa3 Add SelfResolvingTypeSerializer
0198e59caf Add support for sub types
f204fd9ac2 Make case class definition top level
a057f5869b Migrate the Tuple0Serializer
61272d836f Add Tuple2 snapshot class
1ff7f34add Add new TupleSerializerSnapshot
236e61297d Add SpecificCaseClassSerializer
c652f017ef Migrate the CaseClassSerializer

Verifying this change
This PR adds serializer migration tests.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@flinkbot approve description

@flinkbot approve description

cc @tzulitai (so I get him his the reviewers/assignee section ... 😅)

@flinkbot approve description
@flinkbot approve consensus

@flinkbot approve architecture
@flinkbot approve quality

To recap the changes here:

Added a SelfResolvingTypeSerializer interface to facilitate redirecting compatibility checks to new snapshot classes.
Tuple0Serializer, TupleSerializer, Tuple2CaseClassSerializer, and CaseClassSerializer all implement the SelfResolvingTypeSerializer.
Because of that, ensureCompatibility on the TupleSerializerBase can be removed (and is removed in this PR), because the serializers themselves all redirect the compatibility checks themselves, and would therefore not rely on TupleSerializerBase anymore for the compatibility check.
A new concrete class SpecificCaseClassSerializer is added to replace CaseClassSerializer.
New snapshot classes Tuple0SerializerSnapshot, TupleSerializerSnapshot, and Tuple2CaseClassSerializerSnapshot and SpecificCaseClassSerializerSnapshot are added to replace the original TupleSerializerConfigSnapshot.
Scala Macro for generating case class serializers is touched to always return the new SpecificCaseClassSerializer, while still generating anonymous classes with same classnames (assured by tests) for backwards compatibility.


Bug: PDFView not showed when loaded in background in android 5.0, 6.0

I have found this bug in android 5.0, 6.0: when i load the PDFView in an Asynctask, the view is not showed. The loading works perfectly in android 8.0.
I have attached to this issue a detailed report:
bug_report.zip
This library is wonderful! Thank you!
Have a nice day,
Develtar

The version 3.0.0-beta.5 of the library fixed the bug


chore(scripts): use shorter arg aliases; remove debugging args from jest

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4

Relevant Lines:
4

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4

Relevant Lines:
4

💛  - Coveralls


Promotion - discount on global cart

Hi,
i'm not sure if is possible to discount cart globally.
So I suggest it as new feature.
regards.

hi @ghena
can you please elaborate the feature that you want ?

Apply a discount to the whole cart in percentual on products only or whole cart.

@ghena
Thanks for reporting.
We will implement this in the upcoming release

You can achieve this by creating a cart rule with "Percentage of Product Price" by adding conditions that accept all the products on the cart.
If you want to include shipping then set "Apply to Shipping" to "Yes".

I suppose should be better use just one option to do this.

As this can't be implemented and we have suggested an alternative as well.
Closing this issue.


[GCP] Document no UI Deployment story for KF 1.1

There are currently no plans to support Click To Deploy for Kubeflow 1.1 on GCP.
So as part of the Kubeflow 1.1. release we should update the website documentation to point people to deploy using the CLI.

/swikar

/assign @Swikar

You mean delete "Deploy using UI" section completely from doc? https://www.kubeflow.org/docs/gke/deploy/deploy-ui/

Docs have been updatedd.
https://master.kubeflow.org/docs/gke/deploy/deploy-ui/

What was the main reason for removing this functionality? Was it still working at the point of deletion?


Update: Tencent.TIM version <IP_ADDRESS>70

Removing old versions to reduce clutter
Microsoft Reviewers: Open in CodeFlow

/azp run


android - vision not recognize qr code of around more than 300 character in lower mega pixel camera like 3.2 mega pixel even in 5 mega pixel.

I have using this library but my qr image contains 300 to 500 character information so i have tested on 8 mega pixel it is easy to recognize the qr image but in 3.2 or even in 5 mega pixel camera is not recognizing.please provide me any solution i am awaiting for the answer.

More information would be helpful.
Do you have example images of the codes you're having trouble recognizing? When you capture 8MP vs. 3.2/5MP images, are you using the same camera (configured differently), or different models? Do you have autofocus enabled?

Thanks for your reply but I got the solution for this problem actually the was why the camera of 3.2 and 5 mgp was unable to recognise if qr image contains  around 300 or more character because that image dimension was low around 300 px but as soon as I increase the image dimension I was able to the recognise that qr code. So be careful while generating a long character qr your qr should be big.

Thanks for your reply but I got the solution for this problem actually the issue  was why the camera of 3.2 and 5 mgp was unable to recognise if qr image contains  around 300 or more character because that image dimension was low around 300 px but as soon as I increase the image dimension device was able to the recognise that qr code. So be careful while generating a long character qr your qr image should be big. But 3.2  mgp camera was unable recognise qr image that contains more than 300 character even though the imadimensiontion is big.


Cluster image set

@dgoodwin this should be ready for another look

@dgoodwin rebased and added additional deprovision tests to the clusterdeployment controller. I'll handle the move to using ClusterImageSets by default in a follow-up PR. I'm not sure if there is a "latest" release image, but will definitely look into it.

/lgtm

sorry @dgoodwin I missed fixing a comment's case. fixed now

/lgtm


Only post a comment if at least one reaction with an ID changed

Fixes #411

@connorcoley PTAL

Oops, broke some tests (good!); I'll comment again when ready.

@connorcoley PTAL; added a "changed" statistic to capture +0/-0.


Re-enable Notifications

Is is possible to re-enable desktop notifications on song/episode changes?

Hello, sure! Will look into it, hopefully will get it done bug-free this time


add FSharpEntity.ArrayRank

Simply exposing rankOfArrayTyconRef. Fails if entity is not an array.

Hi @Jand42 , Could you add a test too please?  Thanks

Currently I am using td.DisplayName.Length - 1 as a workaround, a bit hackish, but works as proposed td.ArrayRank.

Great, thanks for the contribution!


chore(main): release 0.2.0

:robot: I have created a release beep boop
0.2.0 (2024-08-05)
Features

config: load config  (#10) (5592c12)

Performance Improvements

update prompt (#11) (4e64ac4)

Documentation

README: Update caution note for development status (44d9e86)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.2.0
:sunflower:


Tearsheet alignment to design guidelines

Detailed description
Updates to tearsheet component are required to ensure consistency between the design guidelines and the implementation with code. There are a number of instances where things differ (probably due to my lack of specific guidance here and there). This issue will list as many as can be found.
Issues

[ ] 1. Clicking on background overlay for large and narrow transactional/danger tearsheets should not close dialog.
[ ] 2. Navigation buttons should be always right aligned even when a right-hand-side-panel is present.
[ ] 3. Navigation buttons should use a max width of 232px for wide tearsheets, 50% for narrow tearsheets.
[ ] 4. Wide tearsheet with no side panels should give the Cancel button an extra 16px of padding to the left.
[ ] 5. Tearsheet grid should be adjusted to fit new DSAG guidance.

Issue 1
Clicking on background overlay for large and narrow transactional/danger tearsheets should not close dialog.
Description
This will help prevent user errs from occurring if users are editing sensitive information and accidentally click off. We should use this to encourage users to click an action instead of an ambiguous area - they wouldn't know if the data is saved, erased, or applied if they click the background. It is noted as preventCloseOnClickOutside but should only apply as mandatory as false to transactional tearsheets and mandatory as true for passive tearsheets.
Reproduce

Open a tearsheet component.
Click on the background overlay
Tearsheet closes

Expected behavior
Expected to not allow for interactions if transactional tearsheet is open (i.e has action buttons).
Image
No image required

Issue 2
Navigation buttons should be always right aligned even when a right-hand-side-panel is present.
Description
Side panels on the left influence how the navigation buttons align. The cancel button get's inside by the width of the side panel. However, on the right side, this behavior should not occur. The Primary and secondary buttons are required to sit "outside" of the content body area to acknowledge they operate the entire tearsheet not just a portion of it.
Expected behavior
Influencer panels on the left influence navigation button placement. Influencer panels on the right should sit above the navigation buttons.
Image
Current:

Expected:

Issue 3
Navigation buttons should use a max width of 232px for wide tearsheets, 50% for narrow tearsheets.
Description
Buttons can extend based on percentages due to the width of the tearsheet according to the viewport. However, buttons should only stretch until 232px as their max width.
Expected behavior
Navigation buttons stop stretching when they hit a max-width of 232px for wide tearsheets. Narrow tearsheets may continue to use percentage of width.
Image
Current:

Expected:

Issue 4
Wide tearsheet with no side panels should give the Cancel button an extra 16px of padding to the left
Description
Cancel button text should align to the text of the area it is within/below. This applies only to wide tearsheets.

If the tearsheet has no influencer side panel on the left and the cancel button is left aligned to the edge, it should have an additional 16px padding.
If the tearsheet has an influencer side panel on the left it, again should sit with an additional 16px padding.

Expected behavior
Cancel button should include 16px extra padding on the left to allow it to align to content text / grid.
Image
Current:

Expected:

Issue 5
Tearsheet grid should be adjusted to fit new DSAG guidance.
Description
Follow new tearsheet guidance for wide tearsheet and narrow tearsheet grid and behaviors for responsive sizes/media queries. Link: https://pages.github.ibm.com/cdai-design/pal/components/grid-behaviors
Expected behavior
Follow guidelines by Kacie Eberhart.
Image
No image required.

Thanks @mitchellbernstein! A few questions:
Issue 1
To confirm, you'd like the preventCloseOnClickOutside prop removing and instead the behavior will be automatic, preventing close on click outside when the tearsheet is transactional (has action buttons) and allowing it when the tearsheet is passive (no buttons).
Question: should we do the same thing for hasCloseIcon? i.e. remove this prop as well, and make it automatic, with no close icon for transactional tearsheets and showing a close icon for passive tearsheets? Or is this an option individual cases may wish to make individual decisions on?
Issue 2
If the buttons are to remain at the right edge of the tearsheet, they will need to extend UNDER the right-aligned influencer -- is that what you intend?
Question: should they similarly extend UNDER a left-aligned influencer? or will the two alignments of influencer be different in this regard?
Question: when the buttons extend under an influencer, should each button continue to be sized to 25% of the content area width, which is what the design currently calls for? Or should they now be 25% of the whole tearsheet width?

@dcwarwick

To confirm, you'd like the preventCloseOnClickOutside prop removing and instead the behavior will be automatic, preventing close on click outside when the tearsheet is transactional (has action buttons) and allowing it when the tearsheet is passive (no buttons).

Yep!

Question: should we do the same thing for hasCloseIcon? i.e. remove this prop as well, and make it automatic, with no close icon for transactional tearsheets and showing a close icon for passive tearsheets? Or is this an option individual cases may wish to make individual decisions on?

I don't know the answer per say to this one. My expectation based on the logic set forth by carbon (who doesn't follow this but is now aware of it) that if the modal is passive (i.e uses a close icon and no buttons in the bottom of the tearsheet) then it it can use background overlay click to close it. If the component includes no close icon and does include buttons, it should not allow for clicking off the tearsheet to close.

To confirm, the buttons will extend UNDER a right-aligned influencer, but will NOT extend under a left-aligned influencer.

Yep!

when the buttons extend under a right-aligned influencer, should each button continue to be sized to 25% of the content area width (i.e. the width of the tearsheet minus the width of the influencer), which I think is what the design currently calls for? Or should they in this case be 25% of the whole tearsheet width?

Great question. The buttons should only react to the width of their available space (i.e a full width tearsheet with no left panel influencer or with a left panel influencer tearsheet) which is the content area. Weird I know.. but to answer your question, the buttons have a max-width of 232px but use 50% until they reach that width.

Thank you @mitchellbernstein. I have this item assigned and am working on it now, and hope to have the code changes checked in this week (or the first day or two of next week at the latest) -- I'll let you know when they are live to check.

@mitchellbernstein issues 1-4 are complete now I believe.
For issue 5 (grid), I have worked through the page you linked to, but it is not clear how much of it can or should be applied to a tearsheet.

The page talks about a "large tearsheet" grid, and I don't know what this means -- perhaps it means a wide tearsheet? It suggests that the width of the tearsheet should become full-screen at sm and md breakpoints, so I have implemented that by making wide tearsheets snap to full-screen width for sm/md viewports.
Beyond that, if there are principles which should apply to the tearsheet, I think if would help to update the tearsheet pattern documentation so that it's clear to designers and implementers how to put these into practice. For example, the page suggests that at small viewports (when the tearsheet is a full screen width) the influencer should become a slide-out, but it doesn't provide any details of how that should happen, what behaviour it should have, what affordances the user would use to cause the panel to slide out or back, etc. If there are specific mismatches between design and implementation you can see, or if the design is updated to reflect grid behaviour and these need to be implemented, please open issues to highlight those and we'll action them as promptly as we can.

@andrea-gm fyi


corrupted fonts in game

put Korean in the game, the font will corrupted
can you add a font editing function?

The font should be generated using UDK (UE3), but you will have to convert it to big endian


build: Add missing flags for x86 asm support

Hi all,
This MR fixes an issue we observed in GStreamer when linking for Android x86:
Build log
FAILED: libopenh264.so
/builds/tpm/cerbero/cb/android-ndk-25/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ -target i686-linux-android21 --sysroot /builds/tpm/cerbero/cb/android-ndk-25/toolchains/llvm/prebuilt/linux-x86_64/sysroot  -o libopenh264.so  -L/builds/tpm/cerbero/cb/dist/android_universal/x86/lib -L/builds/tpm/cerbero/cb/android-ndk-25/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/i686-linux-android/21 -Wl,--as-needed -Wl,--no-undefined -shared -fPIC -Wl,-soname,libopenh264.so -Wl,--whole-archive -Wl,--start-group codec/common/libcommon.a codec/processing/libprocessing.a codec/encoder/libencoder.a codec/decoder/libdecoder.a -Wl,--no-whole-archive -fPIC -no-canonical-prefixes -Wl,-no-undefined -Wl,-z,noexecstack -Wl,-z,relro -Wl,-z,now -Wl,--gc-sections -Wl,--warn-shared-textrel -Wl,-z,nocopyreloc -Wl,--sysroot=/builds/tpm/cerbero/cb/android-ndk-25/toolchains/llvm/prebuilt/linux-x86_64/sysroot -fuse-ld=lld -pthread -lm -Wl,--end-group
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x337) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x34D) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x355) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x366) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x37C) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x384) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x395) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x3AB) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x3B3) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x3C4) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x3DA) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x3E2) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x4AC) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x4C2) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x4CA) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x4DB) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x4F1) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x4F9) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x50A) in archive codec/common/libcommon.a
ld.lld: error: relocation R_386_32 cannot be used against local symbol; recompile with -fPIC
>>> defined in codec/common/libcommon.a(libcommon.a.p/dct.o)
>>> referenced by ../codec/common/x86/dct.asm
>>>               libcommon.a.p/dct.o:(.text+0x520) in archive codec/common/libcommon.a
ld.lld: error: too many errors emitted, stopping now (use -error-limit=0 to see all errors)
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.

The fix is to extend https://github.com/cisco/openh264/pull/2611 to the Meson build system, and I added (as a failsafe) the two linker flags that x264 already uses to work around the same issue.
All feedback is appreciated.

From an OpenBSD perspective this looks pretty important.


Request: Presence Sensors

We're an iPhone family but I don't want to put the SmartThings app on all my kids' devices just to get presence detection because they get everything else that comes with it (namely the ability to modify devices). I want to use HomeKit with HomeBridge so I can create routines in SmartThings. To do so, I've added them to my house in HomeKit with minimal permissions. Then I'm using TAustin's vEdge Creator to create virtual switches and presence sensors, using HomeKit to turn a virtual switch on or off based on their presence, and a SmartThings routine to update the virtual presence sensor based on the switch.
Having extra virtual devices and automations works, albeit kludge. It would be great if your plugin added support for virtual presence sensors so I can cut out a few devices and automations on the SmartThings side.

My plugin is designed to bring Smartthings devices into Home Kit.  I'm not sure if these virtual presence sensors are in smartthings based on your description, or in home kit.  I don't push anything into smartthings.

I'm suggesting that you expose a SmartThings virtual presence sensor to HomeKit. The virtual presence sensor has an on/off switch; on causes the sensor to report as present and off as not present. I want to use HomeKit automations to turn on or off the virtual sensor when someone with their iPhone arrives or leaves.

Ok.  I'll take a look at it.  I'll need you to test it out for me.

Hey guys. I’m at a trade show so I’m out of pocket until Thursday, but I see that there was a plugin update and I applied it and my contacts are still not showing. I’ll troubleshoot later this week and catch up on the thread, and keep copying me, but I just wanted to say thanks to Klein for this outstanding effort. No other plugin is doing this since Samsung changed their platform. I did change one of the contacts to be a switch and then it came over into HomeKit so I know that I have everything generally setup correctly. Catch you guys in a few days. Darrell SpencerSent from my iPhoneOn Oct 3, 2022, at 2:40 PM, iklein99 @.***> wrote:
Ok.  I'll take a look at it.  I'll need you to test it out for me.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

I use a plugin called “Dummy” to create dummy switches to do the automation you’re talking about. Darrell SpencerSent from my iPhoneOn Oct 3, 2022, at 1:59 PM, Kendal Van Dyke @.***> wrote:
I'm suggesting that you expose a SmartThings virtual presence sensor to HomeKit. The virtual presence sensor has an on/off switch; on causes the sensor to report as present and off as not present. I want to use HomeKit automations to turn on or off the virtual sensor when someone with their iPhone arrives or leaves.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Added support in 1.4.0.  Let me know how it works.  I will leave this open for a couple of days.  If I don't hear anything, I'll be closing it.

Thanks for doing this! I see all SmartThings presence sensors in HomeBridge, but nothing shows up in HomeKit. Guessing that HomeKit doesn't understand presence sensors? The Virtual Presence sensor in SmartThings acts as both a presence sensor and a switch, so what I'd expect is that it at least shows up as a switch in HomeKit, e.g. using HomeKit to toggle the switch on would reflect as on/present in SmartThings.

It looks like an Occupancy Sensor in Home Kit.  You can use it to set up automations.

On Oct 4, 2022, at 3:45 PM, Kendal Van Dyke @.***> wrote:
Thanks for doing this! I see all SmartThings presence sensors in HomeBridge, but nothing shows up in HomeKit. Guessing that HomeKit doesn't understand presence sensors? The Virtual Presence sensor in SmartThings acts as both a presence sensor and a switch, so what I'd expect is that it at least shows up as a switch in HomeKit, e.g. using HomeKit to toggle the switch on would reflect as on/present in SmartThings.
—
Reply to this email directly, view it on GitHub https://github.com/iklein99/homebridge-smartthings/issues/32#issuecomment-1267498696, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABG55EQR4DN2LGRXIKLKHGDWBSCNLANCNFSM6AAAAAAQSO3DMI.
You are receiving this because you commented.

I'm not seeing any of the SmartThings presence sensors show up as Occupancy sensors in HomeKit. I DO see them in my HomeBridge accessories list, though. Am I missing something?

If you go to add an automation in the Home app on your phone, and look at the sensors, you will see them.  You don't see them as devices in the app that you can control.  But you can select them when creating an animation.

Try looking at IFTTT.  What you want me to do is fairly custom.  What I implemented was to allow a presence sensor to act as an occupancy sensor in Home Kit.  This will allow you to automate something in Home kit.  You probably can get this to work with IFTTT.

On Oct 5, 2022, at 10:05 AM, Kendal Van Dyke @.***> wrote:
Figured out problem #1 https://github.com/iklein99/homebridge-smartthings/issues/1 - after updating the plugin I had to remove and re-add my HomeBridge for the sensors to show up (I had previously rebooted/restarted the bridge but that didn't work). I still can't do what I'm looking for in my original request - the virtual sensors in SmartThings have an on/off state (like a switch) that you can toggle to enable/disable presence. That on/off switch state is not available in HomeKit. What I want to happen is when an iPhone that's part of my family arrives or leaves, it toggles the SmartThings virtual presence sensor (exposed via HomeBridge) so that I can run presence-based automations in SmartThings. Is it possible to expose the virtual presence sensor's on/off switch to HomeKit?
Thanks again for continuing to work on this!
—
Reply to this email directly, view it on GitHub https://github.com/iklein99/homebridge-smartthings/issues/32#issuecomment-1268483108, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABG55EVM2QEN5GWOC66Q6LDWBWDK5ANCNFSM6AAAAAAQSO3DMI.
You are receiving this because you commented.

works for me, thanks 👍


[5.7] Update Aside to support custom titles

rdar://65856948

Explanation: Fixes a bug where custom aside titles aren't recognized by swift-markdown.
Scope: API breaking change, but doesn't break markdown parsing.
GitHub Issue: #59
Risk: Low
Testing: Updated test suite and tested manually that custom aside titles are parsed by swift-markdown.
Reviewer: @franklinsch

@swift-ci please test


Minify/Compress static CSS and JS Files

Subject of the issue
Currently, the static CSS and JS files: style.css and placepicker.js are not minified before sending to the client side. This could help us shave off valuable KBs to send over the network.
Your environment

Python 3
Chrome 68
MacOS Sierra 10.12.6

Steps to reproduce
Load page in browser, the static CSS and JS files: style.css and placepicker.js are not minified
Expected behaviour
If compressed, it would help us shave off valuable KBs to send over the network.
Actual behaviour
Static CSS and JS files: style.css and placepicker.js are not minified

I have started working on this using Django Compressor

@amits97  please have a look at #216


Following Link-Header / MultiPage-Requests (RFC5988)

Please implement RFC5988 Link Header
https://tools.ietf.org/html/rfc5988#section-5
Also see: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Link
I often do need this functionality.
And yes, I am know of:
https://github.com/httpie/httpie/issues/323

Ah okay, seems hypermedia is is not scope of httpie?
I found restish. https://dev.to/danielgtaylor/a-cli-for-rest-apis-part-1-104b

@blurayne It is currently a bit out of the scope. But we’re planning on bringing some of the higher-level API features from httpie/http-prompt directly to httpie, and then this will be relevant.


release 0.13.0

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

using he bot PR which reset the build number.


After YouTube update nothing works

After the lastest update i can't get videos from a channel
video_generator = scrapetube.get_channel(channel_id=channel_id, limit=5, sort_by="newest")
The generator gives an empty array

Stopped working for me too.

Yes I programmed my own now.

@Ivolution-dev What was the problem?

Not working

i pushed a fix, but i saw that some of the other stuff like sorting does not work anymore, ill try to fix it on the weekend

Alright everyone I have a fix for you. @dermasmid you can use my fix to help yourself
they just made changes to the JSON structure
First of all in the source code this change needs to be added
def get_channel( )
    # videos = get_videos(url, api_endpoint, "gridVideoRenderer", limit, sleep)
    videos = get_videos(url, api_endpoint, "richItemRenderer", limit, sleep)

Howerver this changes the output path of the dict so you have to do it this way
`for vid in videos:
#v_url = "https://www.youtube.com/watch?v=" + str(vid['videoId'])
v_url = "https://www.youtube.com/watch?v=" + str(vid['content']['videoRenderer']['videoId'])

# print("https://www.youtube.com/watch?v=" + str(vid['videoId']))
print("https://www.youtube.com/watch?v=" + str(vid['content']['videoRenderer']['videoId']))
`

I'm sure in the source code you could squish down the results dict so it repoints to to just videoId.... but this worked for me

Is it expected behaviour that it only returns "videos" and not livestreams ? @danielsauceda ??

Live streams are on a different tab on the website, so they would need a separate endpoint.

We definitely need live streams.


VSTS_AGENT_INPUT_PROXYURL does not take effect

After applying the variable, the agent does not use the proxy to browse.

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

ID: 0b2476ab-d8db-bd41-689c-8d3b7c4a16d8
Version Independent ID: 6d2e5dd0-8678-d850-a1f3-f664a653bac3
Content: Azure virtual machine scale set agents - Azure Pipelines
Content Source: docs/pipelines/agents/scale-set-agents.md
Product: devops
Technology: devops-cicd-agents
GitHub Login: @steved0x
Microsoft Alias: sdanie

@wasytb72 Thanks for your question. This looks like a support question, rather than an issue with the documentation. We might also need more information to address your issue.
Consider these resources:

Azure DevOps Services
Azure DevOps Support Bot
Azure DevOps on Stack Overflow

If this turns out to be an issue with the product itself, to make sure it gets in front of the right people, please submit your bug here.

Thanks Tim,
I will close this issue and I will submit a bug then. Thank you.


Update TMC5160.c

Correction of readInt function duplication readWriteArray

Hello,
the TMC5160 has the same datagram structure as the TMC5130.
Refer to #23 for details


Building with CMake (and other small tweaks to fix building)

Merging from the Visual Studio Code GitHub extension.


Release 0.1.2

Codecov Report

Merging #26 into master will decrease coverage by 3.68%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
- Coverage   71.77%   68.09%   -3.69%
==========================================
  Files           1        1
  Lines         163      163
==========================================
- Hits          117      111       -6
- Misses         46       52       +6

Impacted Files
Coverage Δ

src/ProgressLogging.jl
68.09% <0.00%> (-3.69%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5a900a5...76b1f6f. Read the comment docs.


unable to change pagination position (too close from page border)

Hi
I'm trying to use asciidoctor-pdf for a non profit literary association publication chain (asciidoc->html, epub and pdf), éditions moinsdecent, and it's really great
but...
I have an issue regarding the position of the page number, which is too close from the page border, therefore not printable.
Here is an example:
radioaktif15.pdf
You may see on the right bottom the page number "15"
Tried many things on the .yml file without any success, hereby (commented lines after l42)
page:
  layout: portrait
  margin: [2cm, 2cm, 2cm, 2cm]
  #size: Letter
  #task novel format
  size: [11cm,18cm]
font:
  catalog:
    FreeSerif:
      normal: FreeSerif.ttf
      italic: FreeSerifItalic.ttf
      bold: FreeSerifBold.ttf
      bold_italic: FreeSerifBoldItalic.ttf
base:
  font-color: #333333
  font-family: FreeSerif
  font-size: 9
  align: justify
  #tryes to get hyphenation in french, without success
  #hyphenation: auto
  #hyphens: auto;
  #word-wrap: normal
  #word-wrap / breakword css3 / hyphenation
  #word-wrap: normal|break-word|initial|inherit; ? auto
  #word-break: normal / break-all;
  #word-wrap: normal
  #word-break: break-all
  line-height-length: 10
  line-height: $base-line-height-length / $base-font-size
vertical-spacing: $base-line-height-length
heading:
  font-color: #262626
  font-size: 15
  font-style: bold
  line-height: 1
  margin-bottom: $vertical-spacing
link:
  font-color: #002FA7
outline-list:
  indent: $base-font-size * 1.5
footer:
  #try to move the page numbering without success
  #page-number:
  #margin: [2cm,2cm,2cm,2cm]
  #margin-bottom: 2cm
  height: $base-line-height-length * 2.5
  line-height: 1
  #margin: [0cm,2cm,0cm,0cm]
  recto:
    right:
      content: '{page-number}'
  verso:
    left:
      content: $footer-recto-right-content

Any clue please?

Correct me if I'm wrong, but I assume what you mean is that the page number is too close to the bottom of the page. That can be adjusted.
Your page margin is 2cm. Typically, you want your running content height to match this value. So first, you'd set the height of the footer to 2cm.
footer:
  height: 2cm
  ...

If you want to see the area that the footer takes up, you can shade the background temporarily.
footer:
  height: 2cm
  background-color: #CCCCCC

By doing that, you can see that the number is not quite at the top of the box. That's because there is a padding applied by default. You can remove that:
footer:
  height: 2cm
  padding: 0
  ...

Now the page number should be plenty far from the edge of the page. But you can continue to make adjustments.
For more info, refer to the theming guide for the running content: https://github.com/asciidoctor/asciidoctor-pdf/blob/master/docs/theming-guide.adoc#key-prefix-footer
(Keep in mind that while the theme looks like CSS, it's not CSS. It's just inspired by CSS).

you are great, exaclty that, a big thanks! and sorry for my poor english (natural-born french speaker)

Glad to hear it!


ARTEMIS-592 finer-grained security for queues

This was the simplest way I could think of to implement this feature.  It allows a security-setting to match to a particular queue by using the syntax "<address>.<queue>" in the match.  For example, if two queues  A & B each mapped to the same address Z each queue could have independent security-settings by matching "Z.A" and "Z.B".
If people are in favor of this implementation then I will write up some documentation and squash that with this commit so don't merge this until there is a satisfactory consensus and docs are written (if necessary).

@jbertram I'm not sure about using the queue name to control access.  It requires users to understand how subscriptions work internally and how the queue name is constructed, which might be different across protocols.
Perhaps a neater approach could be to allow all users of a particular role to share subscriptions, controlled by an address setting.  e.g.
User defines a role "production", all users within this role are able to share subscriptions between themselves.  Many roles could be created that are able to share subscriptions, "production", "test", "application-x", only users within the role are able to share the subscription.
Production Role: user1, user2
Test Role: user3, user4
user1 and user2 can share the subscription, user3 and user4 can also share a subscription, user1 and user3 can not share a subscription.
We could also create a new security-setting to limit which roles are able to share subsctipions and for which addresses, something like "sharedSubscriptionGroup" (or better name), which specifies which roles are allowed to share subscriptions.
e.g.
         <security-setting match="jms.topic.news.us.#">
            <permission type="createDurableQueue" roles="user"/>
            <permission type="send" roles="us-user"/>
            <permission type="shareSubscription" roles="production,test"/>
         </security-setting>

We already store which user created the queue "the queue owner", we could use this information to determine whether or not to allow another user to share this subscription.  You can get the queue owner roles and the current user roles to make the comparison and do a check on the security setting.
Does this make sense?  Any thoughts?

The task is about using he queue name also on the control.  So it has to do so by definition right?  Unless you close the Jira as won't fix.

This JIRA title is: Allow fine grain access control (durable subscriptions).  There is some discussion on the JIRA that you might find useful.

Also, I think this JIRA is only relevant when used in a shared subscription scenario.  See Lionel's comment about CERN's use case.

My understanding was. There was a similar feature in AMQ5 that needed to be similar here in which Lionel was using.if there is a way to not use the queue name it's better for sure.

@clebertsuconic sure, I think that similar feature is virtual topics, which solve the same problem as shared subscriptions.  The way it works in ActiveMQ 5.x is that the user specifies the virtual topic queue to allow the shared subscription.  This JIRA is with respect to virtual topics, so the first thing we need to do is actually an equivilent (shared subscription) support.  That's when this JIRA starts to become a problem.  Once we allow users to share subscriptions, how can we control access to the shared subscription.  Queues are just an implementation detail.

There's no way to eliminate the user's need to understand how non-core protocols map to the core implementation.  We have addresses and queues and just about all the configuration and management details relate to those two resources.
Also, a "subscription" isn't really a core idea. In core, a "subscription" is just a queue.  Core and JMS clients can already "share" queues.  I understand the need for users to control access to individual queues which are mapped to the same address (which is what this PR is meant to address).  I don't understand the whole "shared subscription" use-case.

To track our offline conversations.
For sake of conversation I'm describing the equivilent "virtual topics" feature as a "shared subscription".
We've established the use case for the linked JIRA: ARTEMIS-592 which is to do with securing "shared subscriptions" queues (Or what ever we want to call this functionality).  Justin has added the ability to secure individual queues in this PR.  This can be used to secure a shared subscription queue and also secure any other queue.  At this moment in time, we can't explicitly define a shared subscription queue (as ActiveMQ do with virtual topics).  But it may be possible to do something similar by connecting 2 clients with the same client ID to the broker (due to the way we internally create unique queueNames based on ClientID+SubscriptionName).  I'm not even sure if this is possible it needs testing.  I know with other protocols, for example MQTT, only a single client with the same ID can be connected at a time and allowing 2 clients to connect at the same time may not be a trivial change.
My comments above are an attempt to make this feature configurable in a more user friendly way.  Right now, with this solution the user is required to understand and construct the queueName and explicitly define it for every shared subscription.
The above solution I outlined allows admins to group users together and allow them to share subscriptions between themselves, on any address that matches the security-setting filter.  With out needing to deal with explicit queues, This is less explicit and more easily configurable imo.  It does however, introduce the concept of a subscription to Artemis configuration which seems to be a sticking point for both @jbertram and @clebertsuconic as it's not part of the Artemis Core.  (This could be configured in a non-core part of the broker config).
However, there is another use case for this patch, to do with securing queues on the core protocol.  So perhaps we merge it for that reason, with the added benefit that it adds the ability to secure a subscription queue.
@clebertsuconic and @jbertram I think I'm out numbered here, so I'll let you guys go ahead and do what you feel is best.
Thanks

I am not sure  would really be that user friendly as you defined. it could be confusing actually.
you already have permissions to createQueue, createDurableQueue and consume.
shareSubscriptions is exactly that... and it makes confusing to add an extra setting here.
Artemis is a multi-protocol broker.. we are making other protocols more mature and your definitions of shareSubscription there may not fit all the protocols.

There is one concept on core called createSharedQueue, which is a temporary queue that will exist as long as there is an user connect into it.
shared=true might confuse with that approach, unless this operation was specifically in regard to this type of shared queue. is that the case?

Look at ActiveMQServerImpl::createSharedQueue

@clebertsuconic, was your question for me or @mtaylor?  If it's for me can you elaborate a bit more.  I'm not clear on what you're asking.

@jbertram any one...
is this about Temporary Shared Queues? or anything in particular.
if this is just about shared temp queues, then Martyn's suggestion could make sense.. if not.. it makes it even more confusing.

The original use-case was related to Stomp durable subscriptions which in core terms is simply a durable, non-temporary queue.  Our Stomp implementation allows individual Stomp clients to connect to the same durable subscription by connecting with the same client-id and durable-subscription-name values, hence "sharing" the subscription.  The danger here is that a client which should not be allowed to connect to the durable subscription would in fact connect to it and essentially steal messages from the legitimate client.  However, by enforcing security on the individual queue that situation can be avoided.

@jbertram  got it.. thanks

Our Stomp implementation allows individual Stomp clients to connect to the same durable subscription by connecting with the same client-id  <<

Wouldn't be easier if we just failed more than one connection with the same client-id? We do the same on JMS, through the setClientID, and metadata

@jbertram @mtaylor  I will merge this for now. But this wouldn't stop us from finding a better solution later.

@clebertsuconic I think probably the best solution is to fail multiple clients with the same ID and find an alternate way to handle shared subscriptions consistently across all protocols.  For now though, this is the only way to share a durable STOMP subscription.
We can decide whether it needs improvement once we decide on said consistent approach.  For now this works and does what CERN require.
@jbertram Nice work on this, I think the discussion on this thread was valuable and has helped us get a better understand requirements and current restrictions.


Switch protobuf library to awakesecurity/proto3-suite

https://github.com/awakesecurity/proto3-suite
taken from rocketchat:
(1) we still use protofiles for the Network.ABCI.Types.Messages, and this library can still process those
so there's no difference there
(2) You can still do that for every other type that you want, i.e. ones that maybe you didn't define in your app
(3) Currently you need to write protobuf files by hand in order to make tx message types. This requires you to know protobuf well enough to model all your stuff consistently in proto that you eventually want to represent in haskell

[ ] integrate proto3-suite into namerservice app
[ ] define protobuf types for the messages and schema directly in haskell, remove old .proto files
[ ] replace the .proto files with the generated protofiles from the haskell types / remove the custom Setup.hs

for the wrapper types, by analogy as long as Cat and Dog have FromJSON instance, this works
data Foo = Foo
  { cat :: Cat
  , dog :: Dog
  } deriving Generic

instance FromJSON Foo where
  parseJSON = genericParseJSON defaultOptions

Link to the tutorial
At first glance, it seems that most field types have to use the low level types (e.g. Word32 and Int32, see here), with some flexibility around using another proto message type as a field.
Will look for further options.

This was also quite useful: Low level tutorial

See here for a running example (complete with encode/decode + .proto generation capabilities):
https://github.com/f-o-a-m/hs-abci/blob/test-proto3/hs-abci-examples/nameservice/src/Nameservice/Protogen.hs


TiCDC panic: checkpointTs is greater than resolvedTs

What did you do?
run cdc changefeed
What did you expect to see?
no panic
What did you see instead?
[root@bogon bigCluster]# kubectl --kubeconfig kubeconfig.yml -n cdc-kafka-big-cluster-tps-1712340-1-428 logs -p tc-ticdc-1
[WARN] TiCDC server data-dir is not set. Please use `cdc server --data-dir` to start the cdc server if possible.
panic: checkpointTs is greater than resolvedTs

goroutine 743 [running]:
go.uber.org/zap/zapcore.CheckWriteAction.OnWrite(0x2?, 0x2?, {0x0?, 0x0?, 0xc205230120?})
        go.uber.org/zap@v1.24.0/zapcore/entry.go:198 +0x65
go.uber.org/zap/zapcore.(*CheckedEntry).Write(0xc17e838410, {0xc23891d800, 0x2, 0x2})
        go.uber.org/zap@v1.24.0/zapcore/entry.go:264 +0x3ec
go.uber.org/zap.(*Logger).Panic(0xc000680c00?, {0x402b215?, 0x0?}, {0xc23891d800, 0x2, 0x2})
        go.uber.org/zap@v1.24.0/logger.go:258 +0x59
github.com/pingcap/log.Panic({0x402b215?, 0xc319be1d70?}, {0xc23891d800?, 0x7bec120?, 0x0?})
        github.com/pingcap/log@v1.1.1-0.20230317032135-a0d097d16e22/global.go:54 +0x8b
github.com/pingcap/tiflow/cdc/owner.(*changefeed).updateStatus(0xc060535340, 0x6215ce22ae8001a, 0x6215ce22ae80019, 0x6215ce22d40000a)
        github.com/pingcap/tiflow/cdc/owner/changefeed.go:1000 +0x192
github.com/pingcap/tiflow/cdc/owner.(*changefeed).tick(0xc060535340, {0x49668e0?, 0xc0fec17668}, 0x0?)
        github.com/pingcap/tiflow/cdc/owner/changefeed.go:500 +0x1f05
github.com/pingcap/tiflow/cdc/owner.(*changefeed).Tick(0xc060535340, {0x49667f0, 0xc0fec17638}, 0xc014826840?)
        github.com/pingcap/tiflow/cdc/owner/changefeed.go:239 +0x2d7
github.com/pingcap/tiflow/cdc/owner.(*ownerImpl).Tick(0xc067d4abd0, {0x7f03fa9b9a30?, 0xc067d49f60}, {0x4936960?, 0xc014826840})
        github.com/pingcap/tiflow/cdc/owner/owner.go:201 +0x46b
github.com/pingcap/tiflow/pkg/orchestrator.(*EtcdWorker).Run(0xc047d8f760, {0x7f03fa9b9a30, 0xc067d49f60}, 0xc0018f39e0, 0x2faf080, {0x3f7e53a, 0x5})
        github.com/pingcap/tiflow/pkg/orchestrator/etcd_worker.go:290 +0xfa6
github.com/pingcap/tiflow/cdc/capture.(*captureImpl).runEtcdWorker(0xc000536c40, {0x4966890?, 0xc067d49f60}, {0x7f03eea5af58, 0xc067d4abd0}, {0x4936960, 0xc014826840}, 0x0?, {0x3f7e53a, 0x5})
        github.com/pingcap/tiflow/cdc/capture/capture.go:522 +0x185
github.com/pingcap/tiflow/cdc/capture.(*captureImpl).campaignOwner(0xc000536c40, {0x4966890?, 0xc000d7e6c0})
        github.com/pingcap/tiflow/cdc/capture/capture.go:473 +0x814
github.com/pingcap/tiflow/cdc/capture.(*captureImpl).run.func3()
        github.com/pingcap/tiflow/cdc/capture/capture.go:328 +0x3c
golang.org/x/sync/errgroup.(*Group).Go.func1()
        golang.org/x/sync@v0.2.0/errgroup/errgroup.go:75 +0x64
created by golang.org/x/sync/errgroup.(*Group).Go
        golang.org/x/sync@v0.2.0/errgroup/errgroup.go:72 +0xa5

Versions of the cluster
TiCDC version (execute cdc version):
Release Version: v7.1.0-test
Git Commit Hash: 49faafdaa53d54ab817845af7517f90a8fe10623
Git Branch: heads/refs/tags/v7.1.0-test
UTC Build Time: 2023-05-26 06:53:18
Go Version: go version go1.20.3 linux/amd64
Failpoint Build: false

/severity critical


Allow to use !Tar command with local files

Trying to use the !Tar command defining a local URL give different errors: when defining the url parameter as out/nocona/initramfs.tar or ./out/nocona/initramfs.tar it throw a "bad address" error, with file:./out/nocona/initramfs.tar that "bad port spec", and with file://./out/nocona/initramfs.tar that "not an http or ftp url". Seems insternally it's being used the wget command, so I think this should be override when using a local URL since not always you'll want to use a remote tar file to initialize your filesystem but instead use a local one... Is there any other way to initialize it?

Yes, there is no way to do that currently (except starting a webserver for serving the folder).

Could it be possible to implement this? Seems it should be easy... I would do it myself, but I don't know Rust... :-/

Yeah, should be easy. I can help you (or someone) if you want to contribute. Or I can implement the feature for you if you describe your use case (just to satisfy my curiousity and may be we can find a better way).

I'm trying to use it in NodeOS as an alternative to Docker, since vagga don't needs root permissions. When the image is ready, just by executing npm start the system boots from the last generated files, and docker/vagga version is one of them, that's why I want to use the just generated tar file instead of download it from somewhere. I think I could start an ad-hoc web server so it can be downloaded, but seems somewhat hackish... :-/

Yeah, that is somewhat hackish, but is good enough to validate the idea. I've scheduled the feature for vagga 0.4.1, hopefully it will happen in a week or so.

Oh cool, thanks! :-D


Video einbauen

Is your feature request related to a problem? Please describe.
Display our explanatory video in the welcome screen sequence.
Describe the solution you'd like
Either embed the video or show a link (with icon) to a common platform (youtube).

Bitte Maßnahmenvideo einbauen in "What can I do" page


Cluster red state results in broken exporter

We lost an Elasticsearch cluster in our Acceptance environment during the AWS outage in Frankfurt availability zone C last tuesday. We had a couple of alerts setup to monitor clusters for red state, however the exporter is having some issues and we never received an alert till after all the dust settled. We found out that this exporter broke when the cluster turned red because we lost all of our data nodes.
These are the logs from the exporter:
level=warn ts=2019-11-15T09:43:44.572809589Z caller=cluster_health.go:258 msg="failed to fetch and decode cluster health" err="json: cannot unmarshal string into Go struct field clusterHealthResponse.active_shards_percent_as_number of type float64"
level=warn ts=2019-11-15T09:43:44.573312711Z caller=indices.go:409 msg="failed to fetch and decode index stats" err="HTTP Request failed with code 503"

exporter version:
1.0.2
How to replicate:

Startup an elasticsearch cluster
ingest some data in it
nuke all the data nodes

When i query this exporter i still get metrics, from the masters, one data node.
Some of these metrics are no longer available:
elasticsearch_cluster_health_number_of_nodes
elasticsearch_indices_docs_primary
elasticsearch_cluster_health_status
In our setup we use an Mesos / DCOS cluster, in this cluster we perform a HTTP check against all of our Prometheus exporters. We check the /metrics path for a 2xx return code. The return code of the /metrics path is still a 200 return code. Could this be a scenario where the return code changes?

Hey @a-nldisr,
I'm sorry you had issues with AWS ES and the exporter. However this problem can't be solved in the exporter itself. The logs complains about a 503 response code. This is the response code returned from the exporter-internal call to the ES API. If the API doesn't return a valid json, there's no way of reading the cluster status (green, yellow, red) from it.
In such a case the exporter will export the metrics elasticsearch_node_stats_up and/or elasticsearch_cluster_health_up to 0.
Please note that prometheus will continue to export the last known state of the metrics at least some time (don't know exactly for how long, you can read about it if you dig into the prometheus staleness handling). So my proposition would be to at least also alert on those _up metrics.
I know it is somehow unsatisfying that you can't alert on a critical cluster state in such a scenario. But it's part of the problem: If you can't query the status, you must assume the worst :/
The exporter itself never returns http status code other than 200 on the /metrics path

Hey @zwopir
Clear.
So i expected at least to have either elasticsearch_cluster_health_number_of_nodes or elasticsearch_cluster_health_status report when all fails, you tell me this has a dependency and i should use other metrics. You tell me now to either monitor for 2 others. I see also that i could have prevented this by looking at the https://github.com/justwatchcom/elasticsearch_exporter/blob/master/examples/prometheus/elasticsearch.rules
So ill close this ticket.


transfer learning process were wrong!!!

Your transfer learning process were wrong. You didn't retrain the pre trained model after importing it.

Hi @ZhikangLai, what transfer learning process are you referring to?

Hello @cchallu
I'm playing around with the library  with transfer learning problem and I think @ZhikangLai was reffering to the notebook/example - Transfer_Learning.ipynb
This is the Table of Contents:

Installing NeuralForecast/DatasetsForecast
Load M4 Data
Instantiate NeuralForecast core, Fit, and save
Load pre-trained model and predict on AirPassengers
Evaluate Results

What's missing is a case when you take the M4 trained model and re-fit on AirPassengers. As I understand all I would have to do is take that saved model, load, fit to AirPassengers train dataset and the predict on test the same way Pytorch lightning works, right?

@cchallu I'm also wondering if that's the expected workflow. If I want to predict on a new dataset (w/ different time series id's), I should fit and then predict?


[swift-4.0-branch][stdlib] Introducing the StringProtocol

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 5391cca844f3d5fa9bcadf1eed9f3d58cf7df073
Test requested by - @moiseev

Build failed
Jenkins build - Swift Test OS X Platform
Git Commit - 5391cca844f3d5fa9bcadf1eed9f3d58cf7df073
Test requested by - @moiseev

@swift-ci Please test

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 5391cca844f3d5fa9bcadf1eed9f3d58cf7df073
Test requested by - @moiseev

@swift-ci Please test Linux platform

Build failed
Jenkins build - Swift Test Linux Platform
Git Commit - 5391cca844f3d5fa9bcadf1eed9f3d58cf7df073
Test requested by - @moiseev


refactor: change GraphQL client for gql

TODO:

[x] see if we can remove the types.py
[x] enums.py too,
[x] remove the GraphQLError and replace them with TransportQueryError
[x] can we get rid of format_result?: no, we still need some smart cast to orm.labels and orm.assets (in format_json_dict)
[ ] replace the handcrafted subscriptionclient

[ ] test and update webwooks notebook

[ ] is KILI_SDK_TRIALS_NUMBER needed?
[x] run e2e tests: https://github.com/kili-technology/kili-python-sdk/actions/runs/4164362642

FYI, we now get:

a GraphQLError when local validation fails
a TransportQueryError when backend returns an error

we can start to review this, I will add the subscriptionGqlClient later since it's  a bit complicated
e2e: https://github.com/kili-technology/kili-python-sdk/actions/runs/4164362642

e2e: https://github.com/kili-technology/kili-python-sdk/actions/runs/4164862271

e2e: https://github.com/kili-technology/kili-python-sdk/actions/runs/4182144096

e2e ongoing: https://github.com/kili-technology/kili-python-sdk/actions/runs/4193060622


There are two many "MQueue(~s) drop ~s" logs if the message queue of session is small

comment the lager:error log
emqttd_mqueue add 'dropped' statistics


Add no_std support

Switch to allow #[no_std] support. Currently we're using thiserror which requires std support.

Done


Make "Service" actor smarter

We shouldn't be accessing MastodonAPI for most stuff. The Service actor should have easy to use APIs that let you fetch data…

Cache all objects (Statuses, Accounts, Relationships being the core objects). Store them in Storage object.
Fetch objects if not in cache (storing individual objects and pages of objects if using a paging api).
Provide didChange mechanism (Swift Async Algorithm channels) so that UI can handle changes automatically.

[ ] #21
[ ] #22
[ ] #23
[x] #24
[ ] #25

We have this partially working for timelines and relationships.


VDB Visualize Tree SOP Improvements

A fairly significant re-write of the VDB Visualize Tree SOP. Here are the changes summarized:

Remove logic for DWA-specific surfacing and region of interest (parameters are now obsolete)
Use multi-threading for the geometry generation
Introduce slicing and color remapping
Add gl_lit=0 detail attribute to disable gl lighting

Note: care has been taken to preserve the geometry and point ordering such that the output is identical to what it was before. For instance, there is still two-pass geometry generation where the leaf nodes and internal nodes are processed first and then the voxels and tiles (even though a simpler implementation would likely have been possible by combining them).
In terms of multi-threading performance, here's the full res Disney cloud asset visualized with leaf nodes, internal nodes and tiles as wireframe box and points as voxels:
Old implementation - 1 minute 9 seconds
New implementation - 13.8 seconds
The main change here is moving away from the "addPoint()" and "addBox()" calls to a method where the offsets are pre-computed and the point, vertex and polygon data generated in parallel. The only caveat is that the polygon generation is still single-threaded for now where the solid boxes and wire-frame boxes are mixed as part of the same pass (ie internal nodes shown as wireframe, leaf nodes as solid).
The slicing has been pretty closely modeled on the Volume Slice SOP where I tried to keep the same parameter names and layout (see parameter pane below). There are however three modes for slicing - one where only geometry that intersects a plane is generated, one where all voxels in an intersecting leaf are generated (sometimes useful visually) and finally one where the geometry is "flattened" to the plane so that a 3D box becomes a 2D square more akin to the output of the Volume Slice SOP.
Here is a side-by-side of a slice through the full res Disney cloud asset:

The left is the Volume Slice SOP with regular point spacing, the right is the VDB Visualize Tree SOP with geometry that matches that precise structure of the tree. Performance for this example:
Volume Slice SOP - 1.64s
VDB Visualize Tree SOP - 0.09s
The huge performance increase is primarily from avoiding the need to interpolate the VDB. Even with some very large VDBs, it's now possible to change the offset slider and have it update in real-time.
The offset defaults to a relative -1..1 range, however there is a "use world-space" toggle which changes the value to Houdini units relative to the VDB origin. The offsets are stored in the Node cache so providing the geometry has been generated once, clicking the toggle will translate the value seamlessly between the two - the key advantage being that the world space mode maps to the same plane even when the bounds of the VDB is changing (the node cache approach is similar to one used already in VDB from Particles SOP).
Finally, here's the new parameter pane:

The new parameters are all added to the bottom, but I'm open to changing the layout to make it more usable.

/home/jlait/dev_green/src/houdini/custom/DWA/vdb/SOP_OpenVDB_Visualize.C:1954:43: warning: suggest parentheses around ‘&&’ within ‘||’ [-Wparentheses]
style2 == STYLE_WIRE_BOX && (style1 != STYLE_SOLID_BOX)) {
~^~~~~~
/home/jlait/dev_green/src/houdini/custom/DWA/vdb/SOP_OpenVDB_Visualize.C:1965:51: warning: suggest parentheses around ‘&&’ within ‘||’ [-Wparentheses]
style2 == STYLE_SOLID_BOX && (style1 != STYLE_WIRE_BOX)) {
This seems suspicious, I think the warning is right and style2 should have had a preceding parenthesis?  At least from the structure it looks that way, I've not looked at the actual logic.

Note on GEO_Detail there are:
bool        setDetailAttributeI(const UT_StringHolder &aname, int v);
These make very quick ways to just splat stuff like gl_lit without so much code.

Why is there
"none", "No Mapping",
when that doesn't link to a valid UT_Color setting?  The switch to test this doesn't include "none".

Compiled and passes our reg tests after I suppressed gl_lit.  (I don't mind gl_lit being added, btw, just suppressed to make sure the rest matched.)

Thanks for those suggestions, I've addressed them now.

This seems suspicious, I think the warning is right and style2 should have had a preceding parenthesis? At least from the structure it looks that way, I've not looked at the actual logic.

Yeah. I think the code is correct because && precedence is before || but I agree that it's not clear, so I've tidied this up.

Why is there
"none", "No Mapping",
when that doesn't link to a valid UT_Color setting? The switch to test this doesn't include "none".

I don't have the source code of the Volume Slice SOP to look at here, but I was trying to match the implementation as closely as possible. There is not a "No Mapping" option under UT_Color::getRampColor() even though there is in the drop-down of the Volume Slice SOP, so instead the default value it uses (when "No Mapping" is selected) is UT_COLORRAMP_NUMMODES which appears to produce the correct output?

NONE is a special case to directly copy the value into Cd, which also implies no clamping.  NUMMODES triggers a hundred asserts for me as the lower level libraries are not happy, but try to fail-safe to something reasonable :>
                // Find the colour correlating to this value.
                if (sopparms.getVismode() == SOP_VolumeSliceEnums::Vismode::NONE)
                {
                    cd = v;
                }
                else if (color_ramp)
                {
                    float vals[4];
                    color_ramp->rampLookup(v, vals);
                    cd.assign(vals[0], vals[1], vals[2]);
                }
                else
                {
                    UT_Color::getRampColor((UT_ColorRamp) (int(sopparms.getVismode())-1), v,
                                    &cd.x(), &cd.y(), &cd.z());
                }

I'd actually suggest going straight to a Ramp and not passing UT_ColorRamp at all. We've since added all the standard vis as presets in the color ramp so it feels less necessary to have that specific drop down.  Volume Slice only has it because it predated having defaults on colour ramps.  But if a full ramp seems overkill, I won't press the point either.

NONE is a special case to directly copy the value into Cd, which also implies no clamping. NUMMODES triggers a hundred asserts for me as the lower level libraries are not happy, but try to fail-safe to something reasonable :>
                // Find the colour correlating to this value.
                if (sopparms.getVismode() == SOP_VolumeSliceEnums::Vismode::NONE)
                {
                    cd = v;
                }
                else if (color_ramp)
                {
                    float vals[4];
                    color_ramp->rampLookup(v, vals);
                    cd.assign(vals[0], vals[1], vals[2]);
                }
                else
                {
                    UT_Color::getRampColor((UT_ColorRamp) (int(sopparms.getVismode())-1), v,
                                    &cd.x(), &cd.y(), &cd.z());
                }

I'd actually suggest going straight to a Ramp and not passing UT_ColorRamp at all. We've since added all the standard vis as presets in the color ramp so it feels less necessary to have that specific drop down. Volume Slice only has it because it predated having defaults on colour ramps. But if a full ramp seems overkill, I won't press the point either.

Full ramp sounds fine to me, I'll make that change. Thanks for explaining.

@jmlait - I've made the changes to switch to a Ramp as you suggested, but I'm not sure that I've done it correctly, I couldn't find many examples of working with ramps in a verbified context. I also couldn't figure out how to apply the "infra-red" preset by default so that it matches the Volume Slice SOP, so I instead opted to just set the "rampcolordefault" spare data with infra-red values. Would you mind reviewing this change please?
https://github.com/AcademySoftwareFoundation/openvdb/pull/1138/commits/c098944d40de14c8dcd52e504b82490261e121d0

Regarding defaulting to infrared: to my knowledge that is the best way ATM.


Modify the grove/build/build_rpm.sh

Modify the grove/build/build_rpm.sh last 9 digit commit hash on the grove/ directory as the release
when building the grove rpm.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/1932/
Test PASSed.

Can you modify the title to describe the change?  something like 'change grove version format' would be better when looking at a long list of PRs.   And I assume this is to fix the issue @jhg03a filed on the grove version?  Put Fixed #xxxx in the description with that issue number so it'll be closed automatically when this is merged.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/1934/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/1977/
Test FAILed.

@dangogh  I re-worked the build_rpm.sh to use the functions.sh and build the rpm like the others are built.  The grove version number is different however and that should not be a problem.  the build number and git hash follows the same convention as other tc rpmbuilds.

[approve ci]

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/1983/
Test PASSed.


Corrected cleanup command in Readme

The incorrect command was defined to remove all unused services

Doh, my bad!
Thanks so much for your first contribution!  You rock, @rvanlaarhoven!


Fix the build script when cross-compiling

The target we're compiling to is not necessarily the same as the one of the build script.

Closed in favor of #12 .


Add crystal structure column

Hi again,
I think it would be nice to include a crystal structure column in the dataset.
Crystal structures are available for all elements, except for 113-117, which is great.
I propose using data from Wikipedia's article Periodic table (crystal_structure)

I appreciate your enthusiasm. I have no problem adding more accurate information to the dataset. If you have a few minutes tomorrow to talk, I'd have no problem making you a contributor to the project. Let me know, my email is<EMAIL_ADDRESS>Or if you'd like to PR and move on with your life too that's fine.

@andrejewski
Hello, just came across this repo and as a chemist-dabbling-in-coding, I'd love to help with some issues.
Please let me know if I can do this crystal structure column - if so, I can fork and make a PR, or if you want to discuss, I am open to that as well.


AOT setup questions

I've tried to plug-in third-party theme which uses Angular Material.
AOT stops work, it breaks in "style-loader" with "window is not defined" errors.
I can not wrap my head around this. Look, as far as I get, AOT should not be able to work with style-loader at all, because style-loader requires DOM to insert styles and can't do its work at the server.
So it leads me to next questions:

why it works with style-loader out-of-box at AngularWebpackVisualStudio?
how AOT should be set up at all? Is it true that it won't work if I reference ANY third-party module which use 'window' or 'document'?

Any update on this error. I am facing the same issue.

Here's and example of with Material
https://github.com/damienbod/AspNetCoreAngularSignalRSecurity/tree/master/DirectMessagesAngular


Sam/highlighted cfg paths

Add support for writing CFGs in which execution paths induced by a countermodel are highlighted.

Two things (at least) to discuss:

Adding tests for get_taken_edges
Whether Utils.print_diagnostics p.show overrides flags like --dump-cfgs when that condition is false

Update HTML documentation of --show=paths flag/argument:
https://github.com/draperlaboratory/cbat_tools/blob/master/docs/reference.html