Cockroach support

Hi !
In our apps, we have scalability problems, we actually used PostgreSQL Databases.
Cockroach DB seems a technology that can solve our problems :

distributed SQL
support data locality (multi-datacenters)
read / write on each nodes
Easy to deploy / maintain

It is PostgreSQL based
Is it possible to support this database ?
https://www.cockroachlabs.com/
We also look at Tidb which is already supported, but it seems very hard to deploy and maintain.

@miton18 I think it should be supported but I haven't test Cockroach DB. I will test it or maybe try to add it to CI.

Hope support CockroachDB ASAP. Thanks!

+1 Waiting for cockroachdb support :)

I need to change the circleci to version2 and add cockroachdb docker and then add the test to check anything break.

Any ETA? :)

hi! does cockroach with xorm is ready to use or not?

The related issue on cockroach's tracker was marked as completed, just haven't tested things yet.

can @techknowlogick and @lunny share some info about feature steps to get cockroach support in xorm?

We have a PR in #896, but I think it needs more work.

Can you say what is missing, may be i can helps

You can see https://circleci.com/gh/go-xorm/xorm/975?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link I'm trying to make cockroach pass all tests that postgres/mysq/mssql/sqlite Passed.


Block selection to-EOL is possible with cursor not at EOL, to-EOL state of block selection is not exposed to scripts

Steps to reproduce

Create these mappings

map <f2> <cmd>echom $"'< = {getpos("'<")}, '> = {getpos("'>")}"<cr>
xmap <f2> <cmd>echom $"v = {getpos("v")}, . = {getpos(".")}"<cr>

Optionally, :set noshowmode to prevent the mode indicator from hiding these messages in visual mode. Otherwise, :messages is necessary to see them.

Create a buffer with this text

abcde
fgh
ijkl

Place cursor on b
Type <C-V>G$
Press <f2> and observe the message v = [0, 1, 2, 0], . = [0, 3, 5, 0]
Exit visual mode, press <f2> and observe the message '< = [0, 1, 2, 0], '> = [0, 3, 5, 0]
Type hm>, then <f2> and observe the message '< = [0, 1, 2, 0], '> = [0, 3, 3, 0]
Type gv and observe that the blockwise selection includes all the text in column 2 and beyond

The cursor, however, is on line 3, column 3, which is not normally possible, given the displayed blockwise region.
The only cursor positions matching the displayed region are:

Line 1, column 6 (one past the end)
Line 3, column 5 (one past the end)

Because o in blockwise visual mode disables to-EOL selection (which is surprising but probably not a bug), neither of these positions are valid:

Line 1, column 2
Line 3, column 2

Type <f2> and observe the message v = [0, 1, 2, 0], . = [0, 3, 3, 0]
Exit visual mode, press <f2> and observe the message '< = [0, 1, 2, 0], '> = [0, 3, 3, 0]
Type gvd and observe that all text in column 2 and beyond is deleted

This matches the displayed selection, but not the range specified by '< and '>, or v and ..

The '[ and '] marks are also ambiguous when the last change affected a blockwise region.
Expected behaviour
There's room for interpretation, but probably:

When the previous selection was blockwise to-EOL, getpos("'>")[2] should return v:maxcol to be consistent with linewise selection
getpos("']")[2] could also return v:maxcol after e.g. deleting blockwise to-EOL, though there might be issues with this
Manually setting '> with m> or any other means should clear the to-EOL state of the selection

Version of Vim
9.1.0697
Environment
Arch Linux x86_64 up-to-date as of 2024-08-23
Alacritty 0.13.2 (bb8ea18e)
$TERM = alacritty
zsh 5.9
Logs and stack traces
No response

The width of the solution is exposed via getregtype()

I presume blockwise to-EOL-ness is a specific flag in the state of the visual selection, but I don't believe this is ever exposed to scripts directly. Apart from it being very weird to be able to have a blockwise selection with the cursor not on any of the corners of the selection, this means it is difficult for a script to:

Determine the to-EOL-ness of the the current or previous blockwise selection
Implement an operatorfunc that correctly replicates the behaviour of any of the built-in operators that can act on a blockwise region (and care about the right edge, unlike e.g. >)

One workaround for scripts would be to yank the selection, then add the left column of the selection to the width specified in getreginfo(reg).regtype. This is unwieldy and requires saving and restoring the used register to avoid visible side effects. It also doesn't distinguish between a to-EOL selection and one where the boundary happens to be on the last column within the region.
Another workaround is to execute gv and call getcurpos(), where curswant is v:maxcol if the selection is to-EOL, but this only works if '> has not been set manually. This is probably the best workaround I can think of, but it's still awkward.


talk to M or other standards mavens about how to treat 'open specifications'

Yeah, this is the MAPI question.

For FTP_ITC.1.3 add assignment list to the selection to include [any other protocol].  Also need to say something about authentication since this is about authentication and not about the protocol being used. Perhaps: The email client shall initiate authentication and communication via the trusted channel for [protocol options].

So far the only update here is an assignment for other protocols was added to account for open specifications.

Recommend close


Environment variables for Scale REST API server

Add two new environment variables to handle the following settings related to the Scale REST API server:

An env to control the number of gunicorn workers (-w arg which we currently set to 4, which is a small default)
An env to specify the timeout threshold for REST API HTTP requests. This would need to affect both gunicorn and Apache.

The stack mentioned in this issue is somewhat out-of-date (using mod_wsgi with apache now), but the desired functionality is still relevant - environment configuration of worker count and API timeout.

I'm going to mark this OBE as API cleanup is ongoing to reduce need for high timeouts. Workers can already be upped by increasing the number of CPUs allocated to the web server (SCALE_WEBSERVER_CPU).


Update Apache Rewrite rule

This was working previously because there was a symbolic link: CoVizu -> covizu
Adding the following Rewrite rule:
    RewriteMap lowercase int:tolower
    RewriteCond %{REQUEST_URI} [A-Z]
    RewriteRule ^(.*)$ /${lowercase:$1} [L,R=301]


(do not merge) M-x whitespace cleanup

this is mainly for testing upgraded FreeBSD build slave(s)

hmm, no luck.. maybe trying again another time...


ES6 Template Literals

Week 1:- (Frontend development with ReactJs)
Added clear explanation of ES6 Template Literals.

Type of change 📝

[x] Doc#umentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[x] Frontend Dev React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[ ] I follow Contributing Guidelines & Code of conduct of this project.
[ ] I have performed a self-review of my own code or work.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Clear explanation of ES6 Template Literals.

@SakshiMishra1 can you please mention in which issue you worked

@anandhu720 It was mentioned in week 1 under frontend dev with react.

@SakshiMishra1 Is this work assigned to you

this work has already assigned to someone else and already merged to repo.Please follow the rules he have provided it discord.


cCAD (Canadian Dollar) stable asset on Celo

Explore potential opportunity to drive adoption with Canadian students by helping them save (and thus pay off their debts) through merchant rebates. There is an opportunity to reduce fees and improve the user experience using crypto vs. the current system. The main benefit would allow to access their rebates immediately vs. have to wait months if not years.
This work would be part of the additional stable assets initiative.

Will not support for now. Payd to run their own pilot.


Fix compilation for IDLs that use relative paths in includes

Fixes #5

Hi @stefanodacchille, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

Thanks for contributing!  This is a very straightforward change; the only change I'd request is moving the test from a custom Gradle task to a junit test case in thrifty-schema/src/test/.../LoaderTest.java, which is set up for just this sort of thing.
Once that happens and you do the CLA thing, I'll be more than happy to land this.

No worries! I made the changes you proposed. I didn't see those unit tests for the Loader class, I'm completely new to the codebase. I agree it's much better than relying on gradle tasks.
I've got to clarify to whole CLA thing with my current employer, shouldn't be an issue though.

Not sure why the integration tests are failing. I performed a clean build locally and everything works for me.

Awesome!  One more comment, then it's just up to the CLA process.  There aren't any surprises in there, so hopefully your employer is understanding.
Re: the test failure, the integration tests are just janky right now and sometimes time out on Travis.  I'm not sure what the actual issue is, but the tests involve local TCP communication so who knows which part of the CI system might be slowing that down.  I'll open an issue to investigate.

@stefanodacchille, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Thanks!

Glad I was able to help!


Change property typeprivate with protected.

Q
A

Bug?
no

New Feature?
no

Version Used
0.6.0

FFmpeg Version
FFmpeg version 3.4

OS
Linux dec9410c9e72 4.4.0-119-generic #143-Ubuntu

Could you please change private properties in FFMpeg/FFMpeg.php on protected?
It helps easy to extend the class for more/custom functionality.
FFMpeg/FFMpeg.php
    /** @var FFMpegDriver */
    private $driver;
    /** @var FFProbe */
    private $ffprobe;

FFMpeg/FFProbe.php
    /** @var Cache */
    private $cache;
    /** @var OptionsTesterInterface */
    private $optionsTester;
    /** @var OutputParserInterface */
    private $parser;
    /** @var FFProbeDriver */
    private $ffprobe;
    /** @var MapperInterface */
    private $mapper;

Could you please explain me a use-case for this? In general, you should inject them via the class construct parameters and won't modify them later.


fix(react-router): fix explicitUndefined links never matching

Small follow-up to #2592, as I noticed that it doesn't quite seem to work as I think would be expected - it does correctly exclude the route when the parameter exists, however it doesn't match the route when it doesn't. In other words, there's currently no way for explicitUndefined links to ever match a route. This PR fixes that.

@schiller-manuel Thanks so much for making that change - noticed a small issue when trying to use it in my project that this should fix. Lmk if I'm missing anything!

whoops, thanks for fixing this 👍


Syntax error within macro using $(expr)

Just encountered a bug very similar to #23, just using $(expr) inside the html instead.
#[test]
fn foo() {
    macro_rules! to_string {
        ($($x:tt)*) => {{
            let mut s = String::new();
            html!(s, $($x)*).unwrap();
            s
        }}
    }

    let name = "Lyra";
    let s = to_string!(p { "Hi, " $(name) "!" });
    assert_eq!(s, "
Hi, Lyra!
");
}

gives
tests/tests.rs:324:47: 324:48 error: expected `*` or `+`
tests/tests.rs:324     let s = to_string!(p { "Hi, " $(name) "!" });

As a test I tried changing it to $(name)* and got a syntax error from mauds parser. With a bit of work I managed to get it working with that syntax with both identifiers or expressions inside the () as a workaround 3d8763b.

The workaround doesn't seem to always work, not sure exactly what triggers the error but when I tried using it in some more complicated macros I would sometimes get error: attempted to repeat an expression containing no syntax variables matched as repeating at this depth. I'm guessing it's ok when it's at the terminal of the macro expansion, but if you have any repetition sequences at the same level it errors out.
I guess the best fix would be very similar to the fix for #21. Although with this it has the additional problem that it's in the usage of the macro, rather than the definition that you'd have to stop using $, i.e.
let s = to_string!(p { "Hi, " #splice (name) "!" });

in the above example. Maybe it would be worth dropping $ entirely and finding an alternative shorthand interpolation syntax to better interact with macro_rules?

I tried a basic replacement $ → # and it seems to work (602fdc).  The main issue is that it would make any of the special cases like #call basically be keywords, so if you had something like
let (animal, call) = ("cow", "moo");
let s = to_string!(p {
  "The " #animal " says " #call
}

it would fail to parse (or potentially parse with an incorrect output depending on the exact context). I think this is probably ok as it can be worked around with
let (animal, call) = ("cow", "moo");
let s = to_string!(p {
  "The " #animal " says " #(call)
}

and I assume there won't be many special cases added. Any special case where it uses a keyword (like #if let) would be fine anyway as these need to be wrapped already.

To be honest the only reason why I used # in the first place was because it had nice syntax highlighting. My editor would think that #call is a Rust attribute and draw it in a bright red. I used $ for a similar reason.
Without that constraint, I think it's better to use ^ for splices and @ for keywords. The former has a connotation of "lifting", and the latter is reminiscent of annotations in Python. This change will free up # for an ID shorthand as well.
Actually it would be cool to have & splice a value by-reference and ^ splice a value by-move. That would cover the use case from #24 very nicely.
What do you think about these ideas?

Those both sound good to me, I could open a PR with the changes in a couple of hours if you want (unless you wish to do it yourself)?


Replace Tabs component

Replace usage with blueprintjs
https://blueprintjs.com/docs/#core/components/tabs
I think in this case we can remove the stories.

to become

Since there is built-in support for "tags", we can use that to show the number of spectra loaded for each type.

To check:

Does it look better than the current implementation in the context of an application? => can be tested in the demo app.
Is it widely used in NMRium? => can we make breaking changes to the API?

There's only one use of the Tabs component from here in NMRium. All the others still use the old internal implementation.

There's only one use of the Tabs component from here in NMRium. All the others still use the old internal implementation.

👍🏻 we are free to just use the blueprintjs implementation then if it matches our needs


tools/ci: Update arm toolchain to 12.3rel1

Summary
and skip the build if the change is under tools/ci/docker/linux
Impact
12.2rel1 to 12.3rel1
Testing
ci

This patch updates the docker image which should be done by https://github.com/apache/nuttx/pull/10348, but not really finish the intent job because it was merged too quickly. So, I have to merge this patch by self to unlock ci.


⚠ Samsung has degraded performance

In 9375b58, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 3298 ms

Resolved: Samsung performance has improved in a8fef2c.


Adding context.message.age.ms field

Implementing the latest requirement in https://github.com/elastic/apm/issues/143 for the addition of a context.message.age.ms field.
Checklist

[x] Implement code
[x] Add tests
[ ] Update CHANGELOG.asciidoc

Codecov Report

Merging #970 into master will decrease coverage by 0.3%.
The diff coverage is 52%.

@@             Coverage Diff             @@
##             master    #970      +/-   ##
===========================================
- Coverage      63.5%   63.2%   -0.31%
  Complexity       85      85
===========================================
  Files           245     245
  Lines         10172   10080      -92
  Branches       1351    1335      -16
===========================================
- Hits           6460    6371      -89
  Misses         3326    3326
+ Partials        386     383       -3

Impacted Files
Coverage Δ
Complexity Δ

...m/agent/jms/JmsMessageConsumerInstrumentation.java
14.65% <0%> (-1.09%)
0 <0> (ø)

...m/agent/jms/JmsMessageListenerInstrumentation.java
20% <0%> (-1.74%)
0 <0> (ø)

.../apm/agent/report/serialize/DslJsonSerializer.java
90.76% <100%> (+0.08%)
0 <0> (ø)
:arrow_down:

...ava/co/elastic/apm/agent/impl/context/Message.java
96.96% <100%> (+0.67%)
0 <0> (ø)
:arrow_down:

...astic/apm/agent/impl/transaction/AbstractSpan.java
80.15% <0%> (-3.44%)
0% <0%> (ø)

...va/co/elastic/apm/agent/impl/transaction/Span.java
77.52% <0%> (-2.04%)
0% <0%> (ø)

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 b8de6f7...8c16bea. Read the comment docs.


Feature: Add specs for ApplicationController#access_denied

Our current implementation doesn't actually work and mine doesn't feel right 🤔

The original code looks like it wants to render a page.
It feels silly to output the error message to the user.

Think I just wanna head the status?

The thing that should happen in this situation is very app-specific so I think what you're doing here is a reasonable default for a template to have.


Centres loading and error components for re-designed components

Description
Fixes #1362 -  center vertically all loaders (menu and content) + errors
Notes (out of scope, known isues, hints for reviewing code, ...)  (optional)
Done for pages that already re-designed
Test cases
Branch for test this page

The "loading the task" is still not v-centered.

The "loading the task" is still not v-centered.

Fixed by PR


Subsume lagom-scala-openshift-smoketests

https://github.com/lagom/lagom-scala-openshift-smoketests was unarchived because it's useful to have a small Lagom app to use to get going with deploying to Openshift, for newly upgraded Openshift clusters (no unnecessary complications like Postgres, etc).
But it should live in this repo.

I think we've decided to manage it externally.


Scan and hold actual devices list

Sorry for my bad eng, but I have one issue and I didn't find any solution and my options were not so good.
The issue is next: I need to scan BLE devices and show all scanned in the same view list for a user. The list must be actual (if a device was lost, it must leave from the list, if mobile was found a new device, this device adding in the list). You can imagine a simple Bluetooth (BL) page in Android settings when BL is turn on and there is a list with available BL devices.
In docs this library I found this function: bleManager.startDeviceScan. there is a listener, which has device and error. This listener is working for each device a lot of times. In theory, we can to do something here...
My first idea was filtering all devices from the list in this listener. For recognizing lost devices I added in my list for each device time (in ms), when it was last scanned. I updating time for the current device (parameter of function) in this listener and remove old devices if time now - time last scanned > 5s (for example) It good worked for all situations, except if I have just 1 device. This device was well added in the list and a good updated. But when a device is lost and the list had just that lost device, the listener is not called and we cant remove it from the list and this device is in the stored list but not scanned yet.
My second idea was to parallel process adding in the list and process remove lost devices. I'm using sagas, redux in my project and decided to use the listener just to add devices and scan-time in the list. And special cyclic saga for check all list and remove old. I used delay 1000ms in this cycle and expected that its a better idea and will be working. But as a result, I had a bad situation with the callbacks queue (in js low-level). I saw by console.log that first called listener, it added device in the list. Then called 4-5 cycle actions for clear old devices and no listeners (each iteration of the cycle has delay 1000ms in end)! Then, when the device was deleted because the listener didn't call all the time, the listener working one time and add my device and then cycle with 4-5 iterations and listener and ...
Can you help me resolve this problem? Probably I can improve my ideas or use some other things (API what I don't know or some another algorithm)... Now I have no ideas about what I can to do.

Ok, I found a solution using recursive setTimeout for each device, and if the device was not found any time, it deletes itself from the list.
I hope it'll help someone!

Hello, I try to make like you a list of devices found arround the phone, but I can't find any examples... do you have some advices or exemples with you that can help me? thank you
fun fact: it's been a year to the day since this issue was written!

Hello, I try to make like you a list of devices found arround the phone, but I can't find any examples... do you have some advices or exemples with you that can help me? thank you
fun fact: it's been a year to the day since this issue was written!

Hello! Yeah, I resolved this issue just using recursive setTimeout for each found device. I'll try to explain the logic below:

I have some internal array width objects of found devices. Each object has deviceId and timerId and lastScan date-time.
in a callback which is calling every time when some device was found:

check if in our internal array is an object with the same deviceId.
if there is such object, then update lastScan  date-time to current
if not - add new object with deviceId and current date-time.
timerId - id that return setTimeout. We set this set timeout when found this device first time. Then inside setTimeout we check the current date-time and date-time from object in array. If the difference is greater than, for example, 5sec, we think that the device was missed and remove from the array-list. If not - set new setTimeout and write id in timerId

I'm not sure that explained it clear, just give you my part of code with recursive setTimeout logic:
import moment from 'moment';
import { path, propIs } from 'ramda';

// structure of item:
// deviceId => {
//     lastScan: int,
//     timerId: timeoutId,
// }
let localDevicesList = {};

export const getActualityDeviceChecker = (deviceTimeout, checkTimeout, removeDevice) =>
  function checkActualityOfDevice(deviceId) {
    const timeNow = moment().valueOf();
    const timeOld = path([deviceId, 'lastScan'], localDevicesList);

    if (timeNow - timeOld < deviceTimeout) {
      localDevicesList[deviceId].timerId = setTimeout(
        checkActualityOfDevice,
        checkTimeout,
        deviceId,
      );
    } else {
      delete localDevicesList[deviceId];
      removeDevice({ deviceId });
    }
  };

export const isDeviceInList = deviceId => propIs(Object, deviceId, localDevicesList);

export const addDeviceInList = (deviceId, timerId) => {
  localDevicesList[deviceId] = {
    lastScan: moment().valueOf(),
    timerId,
  };
};

export const updateDevicesTimeInList = deviceId => {
  if (isDeviceInList(deviceId)) {
    localDevicesList[deviceId].lastScan = moment().valueOf();
  }
};

export const clearDevicesList = () => {
  localDevicesList = {};
};

Hi, where does the prop deviceId for the checkActualityOfDevice - function come from? And where do you call the getActualityDeviceChecker  - function exaclty?


problem with firebase auth when i added to pubspec.yaml

Launching lib\main.dart on Android SDK built for x86 in debug mode...
Running Gradle task 'assembleDebug'...
Parameter format not correct -
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':firebase_core:javaPreCompileDebug'.

Could not resolve all files for configuration ':firebase_core:debugCompileClasspath'.
Could not find firebase-common.jar (com.google.firebase:firebase-common:16.1.0).
Searched in the following locations:
https://dl.google.com/dl/android/maven2/com/google/firebase/firebase-common/16.1.0/firebase-common-16.1.0.jar
Could not find legacy-support-v4.jar (androidx.legacy:legacy-support-v4:1.0.0).
Searched in the following locations:
https://dl.google.com/dl/android/maven2/androidx/legacy/legacy-support-v4/1.0.0/legacy-support-v4-1.0.0.jar

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 13s
The built failed likely due to AndroidX incompatibilities in a plugin. The tool is about to try using Jetfier to solve the incompatibility.
Building plugin firebase_auth...
Running Gradle task 'assembleAarRelease'...
FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring root project 'firebase_auth'.

SDK location not found. Define location with sdk.dir in the local.properties file or with an ANDROID_HOME environment variable.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 1s
Exception: The plugin firebase_auth could not be built due to the issue above.

Hi, it seems that you are facing issues with AndroidX, have you tried to migrate to Androidx?
Maybe the following link could help:
https://flutter.dev/docs/development/androidx-migration
There are a few versions of Firebase plugins that are only compatible with Androidx.

@Alifyz
nothing change

So it's a common bug where the android studio says "No usage found in the project ". So in this condition, you have to  manually migrate to android
here is a link where you can migrate it to androidX manually
https://flutter.dev/docs/development/androidx-migration

@ahmadshihab any progress on your problem?

Hi @ahmadshihab
for what I can see the issue is related to a FlutterFire plugin, please open the issue in the dedicated GitHub.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
thank you


AWS Amplify gets error when running "amplify push"

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
d2jtcbjir93tmj
Region
us-west-2
Amplify Console feature
Backend builds
Describe the bug
Unable to run amplify push after either modifying graphql schema or making any amplify update api change. Keeps returning this error message below then rolling back.
Error Message:
UPDATE_FAILED               authboredyetmeb57b6dd5           AWS::CloudFormation::Stack Thu Sep 09 2021 19:45:51 GMT-0700  (Pacific Daylight Time) Parameters: [hostedUIDomainName, authProviders, hostedUI, oAuthMetadata, authProvidersUserPool, hostedUIProviderMeta, aliasAttributes, hostedUIProviderCreds] must have values
URL generated for events also comes in completely blank:
https://console.aws.amazon.com/cloudformation/home?region=us-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aus-west-2%3A646082359734%3Astack%2Famplify-boredyetme-develop-30227%2Fcd4d0110-686a-11eb-9129-029323e94e8b/events
Deployment status constantly says fetching logs, unable to see recent logs.

*not working for develop, test, and prod environment
Expected behavior
amplify push should update the specified environment with modified changes from local
Reproduction steps

modify graphql schema (made a property nullable)
run amplify push

Build Settings
No response
Additional information
No response

Hi 👋, thanks for raising. I'm going to transfer to the CLI repo to get some more eyes on it.
In the meantime, do you mind verifying that:

You're you're using the latest version of the Amplify CLI (). Run amplify version to check.

I did update to version 5.5.0 amplify CLI and re-ran the same steps and faced the same error.

Hi 👋, thanks for raising. I'm going to transfer to the CLI repo to get some more eyes on it.
In the meantime, do you mind verifying that:

You're you're using the latest version of the Amplify CLI (). Run amplify version to check.

@siegerts  any updates on the above issue?

Hey @Vindi-Van as a temporary workaround can you try running amplify update auth and following the prompts? Then, may you post the diff of your auth resource's parameters.json file omitting sensitive information?

@josefaidt We've hit the same problem and the solution you suggested doesn't help.
We're on v6.0.0
Specifically, we're running into this error:
Parameters: [aliasAttributes] must have values
If we take your suggestion and run:
$ amplify update auth
We get:
TypeError: Cannot read property 'length' of undefined
    at Object.run (/Users/cody/.nvm/versions/node/v14.17.5/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-auth/lib/commands/auth/update.js:38:56)
    at Object.executeAmplifyCommand (/Users/cody/.nvm/versions/node/v14.17.5/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-auth/lib/index.js:294:25)
    at /Users/cody/.nvm/versions/node/v14.17.5/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:180:51
    at executePluginModuleCommand (/Users/cody/.nvm/versions/node/v14.17.5/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:164:11)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async Object.executeCommand (/Users/cody/.nvm/versions/node/v14.17.5/lib/node_modules/@aws-amplify/cli/lib/execution-manager.js:35:9)
    at async Object.run (/Users/cody/.nvm/versions/node/v14.17.5/lib/node_modules/@aws-amplify/cli/lib/index.js:162:9)

If we manually add
"aliasAttributes": [], to parameters.json
We get:
Existing schema attributes cannot be modified or deleted.
When trying to push the changes.
We're pretty much dead in the water until this gets resolved.

Hey @CodySwannGT :wave: thanks for adding your notes. I believe this issue you are experiencing regarding aliasAttributes is new and has a different root cause. Would you mind filing a separate bug report?

Done

Hey @Vindi-Van :wave: just wanted to follow up and see if you are still experiencing this issue with the latest version of Amplify CLI (v6.0.0) and whether the proposed workaround alleviated your issue in the meantime?

Closing due to inactivity. @CodySwannGT if you are still experiencing this issue please reply back to this thread and we can re-open to investigate further 🙂


Unable to change width/height of datepicker

I am unable to figure out how to change the width/height of the datepicker.  If this functionality exists, then it would be helpful to have it in the documentation.

I discovered that you can update the width/height of the datepicker with the following code:
.vdp-datepicker input{
    width: 75px;
    height: 20px;
}

This is basic css.
I offer only minimal styling so you can style the datepicker as you wish.

The css is basic, but where you have to put it is not intuitive.  You have to dive into the code to figure out that the css needs to be on the .vdp-datepicker class.

It can be done by using calendar-class.
<template>
  <datepicker class="my-datepicker" calendar-class="my-datepicker_calendar" />
</template>

<style scoped>
.my-datepicker >>> .my-datepicker_calendar {
  width: 100%;
  height: 330px;
}
</style>


method <SmoothGraphics.bezierCurveTo> error

use  method<SmoothGraphics.bezierCurveTo> get error ,
[.WebGL-00007230029B8E00] GL_INVALID_OPERATION: Internal error: 0x00000502: Vertex buffer is not big enough for the draw call.
index.html:1 WebGL: too many errors, no more errors will be reported to the console for this context.

Please share some code with me that allows me to reproduce this error.

OMG how! please demo

@ivanpopelyshev Today a non-polygon hole in a polygon shape was giving me the same error. I tracked that down to the fact that the holes use the line command of the shape instead of the one matching its type. Fixed that. But then I noticed why it failed so terribly: because data.closeStroke was false. Then I tried to draw non-closed polygons: those are not rendering at all. Something goes wrong in PolyBuilder#line if closeStroke is false.
let p = new PIXI.Polygon([0, 0, 100, 0, 100, 100, 0, 100]);

p.closeStroke = false;

let g = app.stage.addChild(new PIXI.smooth.SmoothGraphics()
        .lineStyle(1)
        .beginFill(0xffffff)
        .drawPolygon(p)
        .endFill());

Oh, interesting

@ivanpopelyshev I figured out why this error happens and fixed it with a19cda74e20960ff0a0b372650b227f281257032: joint should be endJoint. The code produced a FILL joint, because it increased a NONE joint by one if closeStroke was false; therefore hasTriangle became true in the segment packer, which corrupted index buffer.
But after changing joint to endJoint there is still something wrong with the MITER joint:

I'm not quite sure what exactly is happening here in this part of the code. If I comment it out, the line is rendered correctly.
https://github.com/pixijs/graphics-smooth/blob/a19cda74e20960ff0a0b372650b227f281257032/src/shapes/PolyBuilder.ts#L284-L297

@ivanpopelyshev I'm considering to remove this code entirely: https://github.com/pixijs/graphics-smooth/blob/994fb4ded0b495cf937f3e12be4c822c6bc341cd/src/shapes/PolyBuilder.ts#L260-L305
It seems to work fine without it, and it is flawed, but I'm not so sure exactly what it is supposed to do. Do you think it's save to delete this code?

Oh, hi! Thanks for checking up on me.
Yes, its one of things i coded in beginning that i didnt fix yet. You can remove it if you test degenerate cases like "line goes there and back"

Yes, it was there to save vertices. I agree to remove it because , whether instancing is implemented or not - it will make this "optimization" worseless soon


[Debug] Without the app.log file, the app.py and the docker will exit

[Debug] Without the app.log file, the app.py and the docker will exit

@fengsh27 could you please check if this is fine to merge?

@xiaoranzhou great work! I suggest adding a file called logs/placeholder instead of logs/app.log. This change will help prevent accidentally committing our own app.log to the repo. Additionally, please update .gitignore file to include logs/*.log.

@fengsh27 @xiaoranzhou is this just about keeping the folder, i.e., the actual file is not important? If that is the case, I usually add a .gitkeep file, which has the same function as a placeholder would have, but is more self-explanatory as well as hidden.

Yes, I believe it exited due to failing to write app.log to folder ./logs. In this case, .gitkeep is a better option.

As this is under the scope of development, I will close this issue. 😄

@xiaoranzhou you also closed the PR, was that your intent?

Yes, this will be solved by using empty folder and .gitkeep right 😄 ? So I closed it.

You also changed some logic in the conversation manager in this PR

Also, why not implement the .gitkeep solution in this PR and then merge?

I added this quick and dirty solution to make sure biochatter-server run. 😄
The wasm was relying the biochatter-server. If biochatter-server does not run, you will not be able to test the wasm part.
Now I have changed the wasm part to make it independent of the biochatter-server.
So I will only get back to the biochatter-server, when you finshed the debug.
There are currently also other issues with the port setting the respons format.
Maybe finish "port" and "respons" first.

https://github.com/biocypher/biochatter-server/issues/6 created, I will add more debug information after the wasm merge finished 😄


Links on the forms page 404

http://alphagov.github.io/digitalmarketplace-frontend-toolkit/forms/
links to:

http://alphagov.github.io/forms/selection-buttons.html
http://alphagov.github.io/forms/list-entry.html
etc…

Also there's no way to get back to the index page from the forms page.

Hey @quis.
https://github.com/alphagov/digitalmarketplace-frontend-toolkit/pull/323

Think this is fixed, the links now work so closing this.


Result type

Replaces Promissum's result type with the one defined by Swift itself. The enum cases are now called success and failure, and as far as I know there is no way for users of the library to migrate to this automatically. Using @available() doesn't seem to be an option because we don't own the Result enum anymore.

This looks great!
I'll try it out in a few projects and then release this as a new major version, since it contains breaking changes.


No way to exit out of progress box for many uploads

Currently, if a user uploads a bunch of files on the dashboard, the progress box on the bottom right expands to show the progress. Right now, if there are too many, it's not possible to scroll or exit the box.

Complete, handled by @clacladev


Added support for "pastDaysCount" calendar configuration option

This PR addresses issue #48.

Added pastDaysCount but past events are still not showing up..

hi! Thank you for submitting a pull request to add support for the new setting. I appreciate your contribution to the project.
Indeed, I noticed that pastDaysCount is not working properly, It looks like there is a separate bug related to past events that needs to be addressed.
I will take a look at this issue and try to come up with a solution as soon as possible. In the meantime, thank you for bringing this to my attention and for helping to improve the project.


Compilation with TypeScript

This moves to compiling the packages with TypeScript into the esnext module format. We now also emit type definitions and source maps.
So ultimately this goes something like:
Reads source SVG files from src/svg and compresses them with SVGO into build/svg, the build script then runs and emits custom tsx files for each one into build/src. Then we compile that with tsc into dist including the package.json for it. CI runs all this and semantic-release runs inside of the dist directory and publishes it as a package.
The git diff carnage here is mostly because I had compressed SVGs checked into the repo.
cc @noahschechter

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

@noahschechter ^ try out 2.0.0?

Will do, thanks again!


PieChart's "sectionAutoFocus" and "focusOnPress" don't work in Web

I'm building a React Native app for iOS and Web platforms, and the PieChart doesn't support interactivity in Web. I'm using your example:

However, the onPress event is not supported in browsers. You must use onClick internally as the fallback. Or maybe the problem is caused by smth else. Can you fix this?
I love your library, it's really great. But I can't make it interactive for Web. Please help.

Hi @Demven How are you using react-native on web? Are you using expo or something else?
If you have a ReactJS project, you can use the react-gifted-charts library for charts.

@Abhinandan-Kushwaha Yes, I use Expo.

@Abhinandan-Kushwaha I'm trying to bypass this limitation by moving the interactivity out of the chart, so that you can select chart segments from the list of categories on the left. Then I pass data prop to the PieChart with focused: true/false.
However, each segment when focused has the same color (url(#grad0) which is red), it's the reference to the color of the first segment, if you inspect it in the DevTools.
See the demo:
https://github.com/user-attachments/assets/58788c63-4667-4ebc-a922-8151d4e6cdc9
Is this a bug? Any way to make the focused segment to maintain the original segment color?
Thank you very much for all your help and work in maintaining this library.
Best,
Dmitry

Hi @Demven The issue is with the react-native-svg library which does not allow onPress events on web. See https://github.com/software-mansion/react-native-svg/issues/1483
Your workaround should work correctly from versions 1.4.31 onwards. Please use the latest version of the library.

Thank you!

@Abhinandan-Kushwaha I upgraded to v 1.4.36, and both focusOnPress and sectionAutoFocus still do not work for me.


Submit to npm?

Hi there, awesome project! While reading through your installation instructions I wonder why it's not submitted to the npm repository? "dasher" seems to be registered but not used: https://www.npmjs.com/package/dasher I guess if your contact them you could get access to it: https://www.npmjs.com/policies/disputes
Greets, pattyland

Mostly because the project isn't packaged to run in the background on its
own like some other things.
You have to clone it and run it per the instructions.
Pulls welcomed for this though!!
On May 7, 2017 at 4:21:01 PM, pattyland<EMAIL_ADDRESS>wrote:

Hi there, awesome project! While reading through your installation
instructions I wonder why it's not submitted to the npm repository?
"dasher" seems to be registered but not used:
https://www.npmjs.com/package/dasher I guess if your contact them you
could get access to it: https://www.npmjs.com/policies/disputes
Greets, pattyland
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/maddox/dasher/issues/77, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABBK_KA9ks2FKzZinRHwVNVbpXWw2gks5r3ietgaJpZM4NTSL5
.


Update virtual-machines-windows-prepare-for-upload-vhd-image.md

Fixed dispart san policy=onlineall typo

Hi @rkyttle, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@rkyttle : Thanks for your contribution to the Azure documentation! The author, @genlin, has been notified to review your proposed change.

@rkyttle Thank you very much for pointing our the typo.
@Ja-Dunn , please help merge the PR.

#sign-off


Updated icons

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/vdc/images/vdc-components.svg
:white_check_mark:Succeeded
View

docs/vdc/images/vdc-deck.png
:white_check_mark:Succeeded
View

docs/vdc/images/vdc-lift-and-shift.png
:white_check_mark:Succeeded
View

docs/vdc/images/vdc-network.png
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


document remaining function

Bump. Ready to pull.

@ArthurGuibert
To be clear, are you still accepting contributions to this project?? If so is this PR in scope to be merged?

I'm still accepting PR. This PR is still lacking a bit of context though. I would appreciate a short description in the commit message that's it 🙂

You got it. New PR at https://github.com/ArthurGuibert/FSLineChart/pull/42


Update Flight Implementation Status

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

We should update https://arrow.apache.org/docs/status.html with the parts of Flight and FlightSQL that are supported
Describe the solution you'd like

Describe alternatives you've considered

Additional context

FYI @avantgardnerio @alamb

I can take a shot at this.
also cc @roeap

triage: Should this be completed now that the arrow docs have been updated?
https://github.com/apache/arrow/pull/39959

Yes thank you 🙏


intermittent etcd failures post build

Ansible version (ansible --version): 1.9.4
Python version (python --version): 2.7.6
Git commit hash or branch: master
Cloud Environment: gce, aws
Terraform version (terraform version): v0.6.11

Over the last few builds, across platforms, I have occassionally seen some worker nodes come up with a failing etcd distributive check:
{"message":"Internal Server Error"}

On the affected node, the etcd service is running but there are lots of errors like this in the logs:
Apr 21 13:05:33 resching-gce-worker-02 etcd-service-start.sh[7696]: 2016/04/21 13:05:33 rafthttp: failed to find member 96bed1dbce03eb25 in cluster 7eda40fd26f24de5

This does not happen every time so I am not sure yet how to reproduce consistently.
We should figure out how to prevent this and document how to fix it if it does occur.

hm, after about 45 minutes, the problem resolved itself:
Apr 21 12:23:32 resching-gce-worker-02.c.asteris-mi.internal etcd-service-start.sh[7696]: 2016/04/21 12:23:32 rafthttp: failed to find member beed3541e47a9276 in cluster 7eda40fd26f24de5
... (lots of rafthttp errors) ...
Apr 21 13:08:08 resching-gce-worker-02 etcd-service-start.sh[7696]: 2016/04/21 13:08:08 rafthttp: the connection with fe4d96286d46b0e6 became active
Apr 21 13:08:12 resching-gce-worker-02 etcd-service-start.sh[7696]: 2016/04/21 13:08:12 etcdserver: publish error: etcdserver: request timed out
Apr 21 13:08:12 resching-gce-worker-02 etcd-service-start.sh[7696]: 2016/04/21 13:08:12 etcdserver: published {Name:resching-gce-worker-02 ClientURLs:[http://resching-gce-worker-02:2379]} to cluster 7eda40fd26f24de5

And the service is healthy in consul now.

I just saw this problem, and I believe it is due to etcd not running on every node in the defined ETCD_INITIAL_CLUSTER= during initial boot up of the cluster.
This can happen on existing clusters if you don't push etcd to all the nodes.
Should we make the initial etcd cluster more like consul and only require quorum from the control nodes?
It feels like the non control nodes should be running as proxies and not part of the raft election: https://coreos.com/etcd/docs/latest/proxy.html

Seeing this in the newest build.  When i access the mesos ui, it frequently says the server is not available.  The /var/log/messages log is scrolling with this message:
Jun  3 04:52:09 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:09 rafthttp: failed to dial a43f56d4501b2085 on stream MsgApp v2 (dial tcp <IP_ADDRESS>:2380: i/o timeout)
Jun  3 04:52:09 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:09 rafthttp: failed to dial a43f56d4501b2085 on stream Message (dial tcp <IP_ADDRESS>:2380: i/o timeout)
Jun  3 04:52:11 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:11,346] INFO Received resource offers (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:82)
Jun  3 04:52:11 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:11,347] INFO No tasks scheduled or next task has been disabled.
Jun  3 04:52:11 mantl-do-nyc2-worker-005 journal: (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:131)
Jun  3 04:52:11 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:11,347] INFO Declining unused offers. (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:89)
Jun  3 04:52:11 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:11,348] INFO Declined unused offers with filter refuseSeconds=5.0 (use --decline_offer_duration to reconfigure) (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:97)
Jun  3 04:52:11 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:11 rafthttp: failed to dial a43f56d4501b2085 on stream Message (dial tcp <IP_ADDRESS>:2380: no route to host)
Jun  3 04:52:11 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:11 rafthttp: failed to dial a43f56d4501b2085 on stream MsgApp v2 (dial tcp <IP_ADDRESS>:2380: no route to host)
Jun  3 04:52:12 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:12,349] INFO Received resource offers (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:82)
Jun  3 04:52:12 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:12,350] INFO No tasks scheduled or next task has been disabled.
Jun  3 04:52:12 mantl-do-nyc2-worker-005 journal: (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:131)
Jun  3 04:52:12 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:12,350] INFO Declining unused offers. (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:89)
Jun  3 04:52:12 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:12,350] INFO Declined unused offers with filter refuseSeconds=5.0 (use --decline_offer_duration to reconfigure) (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:97)
Jun  3 04:52:12 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:12 rafthttp: failed to dial a43f56d4501b2085 on stream Message (dial tcp <IP_ADDRESS>:2380: i/o timeout)
Jun  3 04:52:12 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:12 rafthttp: failed to dial a43f56d4501b2085 on stream MsgApp v2 (dial tcp <IP_ADDRESS>:2380: i/o timeout)
Jun  3 04:52:13 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:13,349] INFO Received resource offers (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:82)
Jun  3 04:52:13 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:13,350] INFO No tasks scheduled or next task has been disabled.
Jun  3 04:52:13 mantl-do-nyc2-worker-005 journal: (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:131)
Jun  3 04:52:13 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:13,350] INFO Declining unused offers. (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:89)
Jun  3 04:52:13 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:13,351] INFO Declined unused offers with filter refuseSeconds=5.0 (use --decline_offer_duration to reconfigure) (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:97)
Jun  3 04:52:14 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:14 rafthttp: failed to dial a43f56d4501b2085 on stream MsgApp v2 (dial tcp <IP_ADDRESS>:2380: no route to host)
Jun  3 04:52:14 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:14 rafthttp: failed to dial a43f56d4501b2085 on stream Message (dial tcp <IP_ADDRESS>:2380: no route to host)
Jun  3 04:52:15 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:15,562] INFO <IP_ADDRESS> -  -  [03/Jun/2016:04:52:15 +0000] "GET / HTTP/1.1" 200 3492 "-" "Consul Health Check" (mesosphere.chaos.http.ChaosRequestLog:15)
Jun  3 04:52:15 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:15 rafthttp: failed to dial a43f56d4501b2085 on stream MsgApp v2 (dial tcp <IP_ADDRESS>:2380: i/o timeout)
Jun  3 04:52:15 mantl-do-nyc2-worker-005 etcd-service-start.sh: 2016/06/3 04:52:15 rafthttp: failed to dial a43f56d4501b2085 on stream Message (dial tcp <IP_ADDRESS>:2380: i/o timeout)
Jun  3 04:52:16 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:16,353] INFO Received resource offers (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:82)
Jun  3 04:52:16 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:16,354] INFO No tasks scheduled or next task has been disabled.
Jun  3 04:52:16 mantl-do-nyc2-worker-005 journal: (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:131)
Jun  3 04:52:16 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:16,354] INFO Declining unused offers. (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:89)
Jun  3 04:52:16 mantl-do-nyc2-worker-005 journal: [2016-06-03 04:52:16,355] INFO Declined unused offers with filter refuseSeconds=5.0 (use --decline_offer_duration to reconfigure) (org.apache.mesos.chronos.scheduler.mesos.MesosJobFramework:97)

i couldnt get the worker nodes to come back online.  When i dug deep, i found that one of the control nodes ( the one in the error message above ) was not reachable.  I then rebooted the node and after reboot, the consul piece would not come back online.  The worker nodes continued to fail ( rather than switch control nodes? ).  At this point three worker nodes and one control node were not working.  Guessing the cause was the control node not coming back online.
I destroyed the environment and rebuilt it.  After rebuild, two of the worker nodes showed the same issue.  Again, one control node wasnt reachable.  I was able to restart the control node without issue though.  It was fully functional after reboot.  What i did observe this time though was that i could not ping on the private network to the control node from the two worker nodes( or vice versa, as expected ).  I was able to ping all the other nodes from the control node and the worker nodes as well, it was just that those particular worker nodes wouldnt talk to that particular control node.
I put the two worker nodes in consul maintenance mode, but was unable to get them into mesos maintenance mode ( is there a guide here somewhere as killing the process doesnt work since it restarts ).  I went to bed, then when i woke up this morning, the servers were all able to talk with each other.
So this leads me to believe there is some sort of temporary firewall rule that is being activated during install, probably not intentionally, but perhaps its being triggered?
At this point the environment is green.

The next time anyone sees this, please try #1616


Update Travis Badge

:+1:

Will merge as soon as ive fixed travis compiling

ACK

Is there a reason why we are using an IP address in $(package)_download_path?


Add information in README.md on how to receive support

To help Developers, DevOps, DevSecOps, etc. with incorporating, deploying, and securing the Senzing library,  information on how to get help should be readily available in each repository's README.md.

A prior post in https://github.com/Senzing/aws-cloudformation-ecs-poc-simple/issues/87

Please update the readme to reflect that users of this project are able to have free support by filing a get issue on the project.
Location:
Banner at the top of the readme
Message:
"Free support is available on this project by using git issues for any product use questions, bugs on the project, or requests for guidance."
Handling:
Senzing community team and product management shall review, answer, and forward as appropriate to tier 2 support.
Please check to ensure this project is indexed by search crawlers to ensure answers given are findable via search engines.


NUTCH-2279 LinkRank fails when using Hadoop MR output compression

read output directory of link counter job to determine output file name (fail if there is none or more than one file)
determine output codec and use it to read the output

I've never come across this issue. What is the error trace like when this is encountered? Is a test required?

@naegelejd added the stack trace in Jira. A test isn't really necessary, just tried it in local mode with mapreduce.output.fileoutputformat.compress enabled or disabled. Will also test later in pseudo-distributed mode when testing the release candidate.


April 2019 Endgame

This is the endgame schedule for April 2019 Iteration.
Schedule

End game master: @aeschli / Zurich
End game buddy: @RMacfarlane / Redmond
05/06 Code freeze for the endgame
05/10 Endgame done
05/17 Expected release date (this may change)

Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame.

Monday 05/06

[ ] Run OSS tool @aeschli

The LCA review of the ThirdPartyNotices.txt files is not needed anymore

[ ] Code freeze at 5pm PT
[ ] Ensure we have a green build on all platforms at 5pm PT
[ ] All test items contain test meta data by 5pm PT and sufficiently comprehensive test descriptions by 8am CET
[ ] Update your availability for testing here - https://vscode-tools.azurewebsites.net/

Tuesday

[ ] Test plan items assigned (using https://vscode-tools.azurewebsites.net/)

Run the tool multiple times to balance load if test items come in later and assignments are already made

[ ] All closed feature-requests either have a verification-needed or on-testplan tag
[ ] Test build starts at 7am CET
[ ] Test plan ready by 8am CET
[ ] Testing
[ ] Verification needed

Wednesday

[ ] Testing
[ ] Remind team members to assign issues that they intend to fix to the current milestone
[ ] Fixing (self-assigned, milestone assigned)
[ ] Verification

Thursday

[ ] Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
[ ] Verification
[ ] Run OSS tool and pass list of changed OSS usage (https://github.com/Microsoft/vscode-build-tools/blob/master/distro-tools/license/third_party_1.nn.0_diff.txt) to @isidorn for verification @aeschli

Friday

[ ] Pause scheduled insider builds @aeschli
Satellite modules/npm packages ready, version updated, smoke tested

[ ] vscode @bpasero
[ ] yo generator @aeschli
[ ] vsce @joaomoreno
[ ] node debug @isidorn
[ ] node debug2 @roblourens
[ ] node debugadapter node @isidorn
[ ] debug-adapter-protocol @isidorn

[ ] All issues verified
[ ] Fixing (only critical bugs - no string changes)
Smoketest (⚠ MUST run with --stable-build argument ⚠ )

[ ] Windows
[ ] OS X
[ ] Linux

[ ] All release notes updated

release notes are collected in a file named Month_Year.md in this repo directory. ⚠We are now doing release notes via Git LFS. Please read what this means here: https://github.com/Microsoft/vscode-docs/blob/vnext/README.md#git-lfs-setup⚠
[ ] @aeschli
[ ] @alexandrudima
[ ] @alexr00
[x] @bpasero
[ ] @chrmarti
[ ] @dbaeumer
[x] @deepak1556
[ ] @egamma
[ ] @isidorn
[ ] @joaomoreno
[ ] @jrieken
[ ] @kieferrm
[ ] @mjbvz
[ ] @octref
[ ] @rebornix
[ ] @rmacfarlane
[ ] @roblourens
[ ] @sandy081
[ ] @sbatten
[ ] @tyriar
[ ] @weinand

[ ] Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. Use the thankyou tool to generate the initial contents of the section. owner

[ ] vscode @aeschli
[ ] vscode-node-debug @isidorn
[ ] vscode-node-debug2 @roblourens
[ ] vscode-debugadapter-node @isidorn
[ ] debug-adapter-protocol @isidorn
[ ] vscode-languageserver-node @dbaeumer
[ ] language-server-protocol @dbaeumer
[ ] vscode-textmate @alexandrudima
[ ] vscode-loader @alexandrudima
[ ] vscode-generator-code @aeschli
[ ] vscode-vsce @joaomoreno
[ ] vscode-docs @gregvanl
[ ] vscode-css-languageservice @aeschli
[ ] vscode-json-languageservice @aeschli
[ ] vscode-html-languageservice @aeschli
[ ] jsonc-parser @aeschli
[ ] vscode-jscs @chrisdias
[ ] vscode-tslint @egamma
[ ] vscode-eslint @dbaeumer
[ ] vscode-jshint @rmacfarlane
[ ] vscode-recipes @auchenberg
[ ] localization @shawndon
[ ] vscode-github-issues-prs @chrmarti
[ ] inno-updater @joaomoreno

[ ] Review pull requests acknowledgements with NOT MERGED - PLS REVIEW. @aeschli
[ ] Acknowledge issue trackers from the community @chrmarti
[ ] Add notable fixes to the release notes all
When done fixing/verifying and there are changes since last build at the end of day PT

[ ] Trigger new insider build and publish it manually @aeschli

Friday/Monday

[ ] Branch code to `release/<x.y> @aeschli
[ ] Bump up the version in package.json - @aeschli
[ ] Announce master is open for business @aeschli
[ ] Polish release notes redmond

Monday - Wednesday

[ ] Polish release notes redmond
[ ] Cherry-pick hand-picked and reviewed changes to release/<x.y> @aeschli
[ ] Build Insider from release/<x.y> @aeschli
[ ] Manually release Insider @aeschli
[ ] Build stable for all platforms as new candidate issues come in @aeschli
[ ] Documentation updated

[ ] @aeschli
[ ] @alexandrudima
[ ] @alexr00
[ ] @bpasero
[ ] @chrmarti
[ ] @dbaeumer
[ ] @deepak1556
[ ] @egamma
[ ] @isidorn
[ ] @joaomoreno
[ ] @jrieken
[ ] @kieferrm
[ ] @mjbvz
[ ] @octref
[ ] @rebornix
[ ] @rmacfarlane
[ ] @roblourens
[ ] @sandy081
[ ] @sbatten
[ ] @tyriar
[ ] @weinand

Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame.

Wednesday/Thursday

[ ] Build stable for all platforms @aeschli
[ ] Make rpm signing request @RMacfarlane
[ ] Sanity check of installable bits

[ ] Windows

[ ] signed installer 32-bit
[ ] signed installer 64-bit
[ ] signed user installer 32-bit
[ ] signed user installer 64-bit
[ ] zip 32-bit
[ ] zip 64-bit

[ ] OS X
[ ] Linux

[ ] deb package 32-bit
[ ] deb package 64-bit
[ ] rpm package 64-bit
[ ] rpm package 32-bit
[ ] archive 32-bit
[ ] archive 64-bit

[ ] Publish website @gregvanl
[ ] Publish Localization language pack @shawndon
[ ] Publish to stable @aeschli
[ ] Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download)  @aeschli
[ ] Publish<EMAIL_ADDRESS>@octref
[ ] Publish rpm to repository manually @RMacfarlane
[ ] Enable scheduled insider builds @aeschli
[ ] Twitter announcement @auchenberg


Resize the videos

Hi,
I just have a quick question.
Do we need to resize the videos before we run preprocess_data.sh?
Or preprocess_data.sh would also handle the resize of the videos as well when we run face detector?
I can not find the code you resize the image. This is the closest thing I find in your code.
https://github.com/selimsef/dfdc_deepfake_challenge/blob/ef703c2745bd0615fef6e03c2a519cd59273f9ff/preprocessing/face_detector.py#L67
Thank you!

Hi,
I did that in kernel during inference. See https://github.com/selimsef/dfdc_deepfake_challenge/blob/ef703c2745bd0615fef6e03c2a519cd59273f9ff/kernel_utils.py#L227


👷 Specify HUGO_VERSION environment variable once in netlify.toml

What does this PR do?
Fixes redundant environment variable specification across contexts.
Explanation
The environment variable HUGO_VERSION holds the same value for all contexts (production, deploy-preview, and branch-deploy). Specifying it separately for each context becomes redundant.
Specifying it once under [build.environment] should be enough.
Reference
From https://docs.netlify.com/configure-builds/file-based-configuration/#deploy-contexts :

any property of a context-aware key, such as [build] or [[plugins]], will be applied to all contexts unless the same property key is present in a more specific context.

Thanks, I'm happy to merge this in.


ci/cd: fix env vars, add parameters to charts and docker files

Manual Deployment. Will be replaced soon.

@theoriginmm
Thank you for PR!
Don't you want to move registry host also to variables?
Also, I can see dependencies from internal EPAM artifactory, should we move it into ECR?

@khyurri  Thank you for the comment.
This  PR simplifies manual deployment, eliminates artifactory url from default variables.
We need a default value  as image name for makefiles.
Yes,  it's possible. Moved to ECR.


pkg/admission/reservedmetadata: optimize allocations

Summary
Follow-up of https://github.com/kcp-dev/kcp/pull/1343#discussion_r905976617
Related issue(s)
https://github.com/kcp-dev/kcp/pull/1343, https://github.com/kcp-dev/kcp/issues/1138
/cc @sttts

/lgtm
/approve


[#51] Teach Likely to work with History API

@iamakulov The first approach to solve the problem. Check this out and let's discuss this.

To test this you can open test-history-api.html and look at this manually (until we have autotests).

Wow, a great work! I’ll look into this deeper in the new few days.

@vitkarpov, took a quick look and added some low-level notes.
I still don’t know about how this is acceptable from the high-level (architectural) point of view, and I hope I’ll find some time to think about it soon. Feel free not to implement the low-level notes yet because the code will require major changes if we find the architecture inappropriate.

Yep. I made the pr just to take a look at it. Let's talk about architecture and then I'll make right implementation.

OK, let’s start discussing the architectural decisions. (It’d be a bit slow at first as I have university exams at the moment).
I’ll mark these discussions with :chicken: emoji to prevent them from mixing up with low-level ones.

@vitkarpov, added a few questions (one, two, three).

It’d be a bit slow at first as I have university exams at the moment

I'm glad you're back :) Hope you've passed all the exams.

I'm glad you're back :) Hope you've passed all the exams.

Thanks :–) Not passed them yet, will be busy till the end of June.

@iamakulov fixed according what we've discussed.

Wow, lovely.

Seems it's more clear now: all the logic is inside the module and on load we init likely and history in an explicit way.

@vitkarpov, added a nit. Apart from that, everything is just great.

@iamakulov Done

@vitkarpov, added two more notes.

@iamakulov Done

Great, thanks a lot!


Configuration Variables are not substituting .env file

Here is a screenshot of the config:

And here is the environment variable from the Configuration tab:

My local.env file has SECRETS_DIR=/originalSecretDir When I run my application, I get:
Caused by: java.nio.file.NoSuchFileException: /originalSecretDir/rollbar-api.txt

Why is the configuration environment variable not replacing the env file?

I wasn't able to reproduce this. Have you figured out what was wrong?

@ashald I'm experiencing this problem too, with IDEA 2020.1 and version 3.2.1 of your plugin.
For me, it was easy to reproduce on a toy project:

Create a python file which prints an environment variable, e.g.

import os

print(os.getenv('FOOVAR'))

Run that to generate a run configuration - it will print 'None'
In the run configuration, add an environment variable of FOOVAR=foo - running it now prints 'foo'
In the run configuration again, enable envfile and add a file with FOOVAR=bar in it, making sure not to change any other settings, and that this file is below <Run Configuration Env Vars> in the list - running the script now prints 'bar', even though it should print 'foo'

Playing with the settings (e.g. turning on environment variable substitution, changing the priority order of environment variable sources) doesn't seem to have any effect - the only ways I've found to achieve the desired behaviour are to either delete the env file from the list, or disable the plugin.
I hope that help you to get to the bottom of this. Let me know if I can provide any more detail.


Enhance address request and response

Address signing and verification has already done a lot and peer disconnection if not pass some checks has been done as well. There are no many updates have to be done :)
Updates:

Do not send peerInfo message if errors
Check client ip address in the server side for safety
Use p2pState

Thanks for the review! merging now!


jsonapi: return totp in the api response to enable 2FA use in gopassbridge

See: https://github.com/gopasspw/gopassbridge/issues/87
This returns the OTP code, if available over the jsonapi.
This is done in a way so as to be minimally invasive: we either return a good totp, or we return the original payload. This has the side effect of swallowing errors, but errors are effectively swallowed in this path anyway due to how gopassbridge presents errors.

Codecov Report

Merging #975 into master will increase coverage by <.01%.
The diff coverage is 71.43%.

@@            Coverage Diff             @@
##           master     #975      +/-   ##
==========================================
+ Coverage   63.67%   63.67%   +<.01%
==========================================
  Files         171      171
  Lines        9870     9876       +6
==========================================
+ Hits         6284     6288       +4
- Misses       2799     2800       +1
- Partials      787      788       +1

Impacted Files
Coverage Δ

pkg/jsonapi/responses.go
74.78% <71.43%> (-0.45%)
: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 5aee64c...e7822e0. Read the comment docs.

All green, test added, thanks again for the fast review!


Support wider versions of Rails

This project was born from a rails 3.2 project so it'd be nice to pull it down. Additionally test on edge rails.

The more I think about it, it doesn't make sense to go back and support Rails 3.2. Seems to work on Rails 4.1 and 4.2 so let's stick with that unless there's a request for it.


Add support for gaana.com

Hi!
As per request of Gaana Support #12575, I have tried to add the support of gaana.com. It's the third time to make a better PR.
It currently support three types of url:
https://gaana.com/song/-------------
https://gaana.com/album/-------------
https://gaana.com/artist/-------------

For single song:
youtube-dl https://gaana.com/song/mera-dil-bhi-kitna-pagal-hai-1 -f best
For all songs in the album:
youtube-dl https://gaana.com/album/saajan-hindi -f best
For all songs of the artist:
youtube-dl https://gaana.com/artist/kumar-sanu -f best
It will download song in .mp4 format.
Gaana.com uses various server as vodhls-vh.akamaihd.net, cloudfront.net and some others for hosting purpose and uses different algorithm to get it as far I have come to know. This infoextractor works only with 'vodhls-vh.akamaihd.net'. Support for other server will be implemented soon. The code has been checked with flake8. I have tested it from INDIA and works fine.
One more thing, I have just coded first time in Python, so the code may be non-smooth. It's a appeal to all maintainers and moderators of youtube-dl to guide and help me to make myself suitable in this platform.
Thanks all.

Sir,
Thanks for your helpful review.
As much I've understood your guidence, I've reconstructed the code.
Supported url type:
https:/gaana.com/song/------
https:/gaana.com/album/------
https:/gaana.com/artist/------
https:/gaana.com/playlist/------

Basically, the webpages of above-said url-types are delivered in same way and style. It contains the related data of underlying songs in json format which are partially encrypted(method:CryptoJS.AES.encrypt, mode:CBC, pad:Pkcs7). Static key & iv are involved for decryption. But a few json info doesn't contain the urls of media. Then the media urls are usally captured in json format by posting a dymanic md5 string and some other data to a specific url. If I create a seperate info-extractor for playlist and call url_result() to create entries (i.e downloading the webpage for each song to get the info that are already in main webpage), then the process will consume data, time and much more. For this reason, I have written a single info-extractor that can deliver dynamic playlist result when required (means if the webpage contains more than one song's info).
For your reference:
https://css375.gaanacdn.com/min/?b=js&f=gaana.min.js&version=980.27&980.27
This js includes all the above-said method.
All print() function, used for debug, has been removed.
I know that my writing is also non-smooth like my code. Sorry for that.
Now, I am just waiting to hear you.
Thank you.

@GourangaDas can you provide a build for testing this?

@arizzubair chiming in here. How can I help to get this merged into the core?

Never mind. I can simply check out this branch and run python -m youtube_dl to check whether gaana.com urls are working or not.

Have a look at this PR instead: https://github.com/ytdl-org/youtube-dl/pull/22095
I know 2 PRs for the same extractor, but could not push to this PR obviously.

@GourangaDas Are you still working on this?


Fix typo

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master        #4   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           28        28
=========================================
  Hits            28        28

Impacted Files
Coverage Δ

src/KMLTracks.jl
100.00% <100.00%> (ø)

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 cfde354...fe5a0e4. Read the comment docs.


Slider not able to slide on Touchscreen Devices

Godot version:
3.1.2 stable official
OS/device including version:
Mac which I am coding on 10.14.6
Issue description:
Hslider not sliding on touchscreen devices.
Device Information:
iphone 6, software version 12.4.5
Steps to reproduce:
(Run this project on an iPhone or similar touchscreen device)
GodotTester.zip
The video showing that it doesn't work:
video.zip
Minimal reproduction project:
GodotTester.zip

You say it affects Godot 3.1.2. Does this problem occur in Godot 3.2.1?

You say it affects Godot 3.1.2. Does this problem occur in Godot 3.2.1?

Yes, this problem still occurs in Godot 3.2.1.

Emulate Mouse From Touch options seems to be disabled in test project. Slider and almost any other GUI element seems to be handling mostly mouse events, so this options should be enabled for GUI to work on touch devices.


Reduce number of required command line arguments

At the moment, ~10 command line arguments need to be provided in order to run Main.kt. This seems overkill especially when considering that most of these will be the same for every region (in- and output directories) or at least for every run for a specific region (all the other arguments).
Suggestion:

Have a file from which the arguments are pulled upon running Main.kt (analogous to config.py in osmPreparation). This way, only the parameter "region" has to be provided and the other values can be edited in the aforementioned file as desired before running Main.kt.
Include (empty) I/O directories in the project (with a .placeholder for git) so that the user doesn't have to figure out for herself where to read from/write to.

Default values for almost all arguments are defined in here: https://github.com/simra-project/osmColoring/blob/master/src/main/kotlin/main/CommandLineArguments.kt
If some defaults are missing, feel free to add them :).

If you think there are still thinks open for discussion, just re-open the issue @MeerkatPerson


Add testcase to the existing store

What does this PR do?
Add action, reducer test case to existing store peer and doc.
Any background context you want to provide?
https://redux.js.org/recipes/writing-tests#action-creators
Checklist

[x] Added relevant tests
[x] Didn't break anything

I will put it back in the necessary situation.

I will put it back in the necessary situation.


KeyError: "The name 'Placeholder:0' refers to a Tensor which does not exist. The operation, 'Placeholder', does not exist in the graph."

Following steps from https://docs.microsoft.com/en-us/azure/cognitive-services/custom-vision-service/export-model-python leads to error "KeyError: "The name 'Placeholder:0' refers to a Tensor which does not exist. The operation, 'Placeholder', does not exist in the graph.".
Looks like some of the internal tensor names in the CV graph have changed?  When I change
input_node = 'Placeholder:0' to input_node = 'data:0', the error changes to complain about the loss:0 not existing.
So when I further change "output_layer = 'loss:0'" to "output_layer = 'model_output:0'" it works.

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

ID: 754dd7d5-dd8b-4a75-5d79-0ba621a847cd
Version Independent ID: 3cca3535-1c16-2da1-46c6-421cbf808bc3
Content: Tutorial: Run TensorFlow model in Python - Custom Vision Service - Azure Cognitive Services
Content Source: articles/cognitive-services/Custom-Vision-Service/export-model-python.md
Service: cognitive-services
Sub-service: custom-vision
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

@krisbock Thanks for the feedback. We are investigating the issue and will update you shortly.

@PatrickFarley The error could be replicated with newer projects which are exported with custom vision metadata version 1.2
For older 1.1 the snippets work as expected. Could you please review the same and update as required?

I have the same problem. Please prioritise and communicate a fix to it. Thanks

Thanks for the feedback! This documents are for the "General (compact)" domain. For newer domains, please visit https://github.com/Azure-Samples/customvision-export-samples
There is a PR to fix the doc #76090

@shonohs Thanks for the update.
We will now proceed to close this thread as the same works with General Compact domain. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply.

@RohitMungi-MSFT
Hi, Thanks for working on this ... but ...
It's not clear ( to me as a user ) from the very brief comments what the problem is and how it can be resolved.
Perhaps you can help ;-
As far as I can understand ...
It seems that there are different python scripts for use with different model versions ?
I am using Visual Studio 2019 on an Intel based laptop.
I need to be able to train and then download a tensorflow model, and later use it locally , using Python code.
I am using Python 3.7
That worked in the past, about 2 - 4 months ago, but now something has changed / or is broke within Azure's model creation , or use of a downloaded model with python ??
The link provided (  https://github.com/Azure-Samples/customvision-export-samples  )   as part of the comments above  link to 2 tables, which in turn then link to various python scripts. That's a bit confusing.
Can you help by telling me ( and other users ) what python code I need to use if I create and download a tensorflow type model, using the  general compact (s1) domain setting  ?
Many thanks for your excellent help on this

@AgribotGit F0 and S0 are the pricing tiers that are available for a custom vision resource. You can change between these two tiers as seen. Where is the reference to change the tier to S1?
The steps to download the trained model for tensor flow are the same as "General (compact)" domain. For example, I have a trained an iteration with my project setting of "General (compact) [S1]". During export of the model for tensorflow there are options to select the format.

These formats are directly mapped to the different folders listed on the github repo. I have downloaded my model with "tensorflow" and extracted the zip file locally to test the model.
The mappings for tensorflow in the repo also contains the predict.py scripts for different types of models i.e based on your project settings. Since, I have used a project for classification with "General (compact) [S1]" domain I have used the script under classification_S1 folder.
The usage of all the scripts in the repo is the same:
python predict.py <model_filepath> <image_filepath>
The model file path should point to the exported model and image file path to the image that needs to be classified. The response should display the score for each label that the model is trained on.
Sample run on python version 3.7.3 for predict.py

@shonohs Please correct me if I am wrong with any of the steps to use the files in the repo. Thanks.

Thank you very much !
I can conform that the python code and the generated tensorflow model work correctly in my Visual Studio IDE and python environment.
many thanks for your quick and helpful support.


Meetups: add links to GitHub

The Meetup page should point to the GitHub repo. Otherwise some people will never know that such a repo exists.
Perhaps we could also link directly to the individual folders within the repo from the individual meetup pages (e.g. Meetup 1 on PyCon page points to Meetup 1 on GitHub -- would be nice and easy to find materials). Any volunteers? :-)

Thanks a lot! Didn't know the meetup had its own repo.
mn
On Thu, Feb 4, 2016 at 10:56 AM, Jan Gondol<EMAIL_ADDRESS>wrote:

The Meetup page https://pycon.sk/sk/meetup.html should point to the GitHub
repo https://github.com/pyconsk/meetup. Otherwise some people will
never know that such a repo exists.
Perhaps we could also link directly to the individual folders within the
repo from the individual meetup pages (e.g. Meetup 1 on PyCon page
https://pycon.sk/en/ba-01-meetup.html points to Meetup 1 on GitHub
https://github.com/pyconsk/meetup/tree/master/Bratislava/201507 --
would be nice and easy to find materials). Any volunteers? :-)
—
Reply to this email directly or view it on GitHub
https://github.com/pyconsk/pycon.sk/issues/12.

I'll take it, if there are no other takers :)
Would it be sufficient to put on Meetup page above individual meetups line like this:
Github Meetup repo: https://github.com/pyconsk/meetup
And on individual meetup pages similar line to individual neetup repo, that would be located above line
Contact:
I'll create branch for this feature, then rebase it into master as single commit (in case there are multiple).

@mbag Thanks! :) If you want, consider adding a GitHub icon or some other way to highlight this, so it's more visible and not overlooked. Your call.

@mbag yes I think it would be enought, possibly look at bootstrap icons if there is github icon, if not text with link is fine I guess...

Added new branch add_meetup_links. Please try running it, to see if this style is acceptable.
If it's OK, please don't merge this branch :) I would like to rebase it, so that we have straight commit history. Furthermore I haven't done a rebase in a while :)


Decouple client setting and initialisation

The ShakaPlayer currently provides a single initializer: init(client: ShakaPlayerClient!) where ShakaPlayerClient is a protocol with all its methods marked as optional.
After inspecting the code:

The player initialisation may fail. In this case the player client is informed of the failure through the onPlayerError(_ error: ShakaPlayerError!) method. This means that you are forced to create a client if you want to know about the error in case of failure.
The initialisation requires you to provide the client. But the methods of the client don't include the player in their parameters. That means you have two options:

either make the class directly using the player implement the ShakaPlayerClient protocol, keeping a reference to the player in an instance variable that can be later accessed inside the methods (see #94, not good from a responsibility separation point of view)
or create a separate object implementing the ShakaPlayerClient. In that case that object may need the player we are creating to extract information from it in several methods, so we must inject it. So we have to: create the client, create the player using the client, inject the player into the client

All the methods in ShakaPlayerClient are optional, so it does not make sense to require a client to initialise the player: what would be the difference between providing no client or providing a client with no methods? You could think that the code requires a non nil client to be there, but that't not the case: the reference to the client is stored in a NativeClient which later forwards the events to the original client  using the DispatchObjcEvent method, which checks if the client is nil before invoking any method. Taking this into account it seems the only reason to require the client in the initializer is to be able to inform of a initialisation error.

Could you please decouple initialisation from client setting? This way:

Player and client creation could be completely decoupled if #94 is fixed
Initialisation success could be easily determined if initialisation used a initializer which throws an error as described in the Error Handling guide. In this case we have the error information more clearly provided and related to the initialisation operation with no need for any third object
You wouldn't be forced to create a client if you aren't interested in receiving player events
You would be able to use third party libraries which rely on classes adopting the delegate pattern (for example RxCocoa reactive support for classes with delegates)

I'll be fixing #94 to add the ShakaPlayer instance to the callbacks; but note that for initialization errors, the value passed will probably be nil.  This is because the object failed to initialize, so the object is unusable.
The client can be nil (though that may not appear in Swift), and I'll add an empty init method for convenience.
I don't think we can use Swift error handling since that wouldn't work well in Objective-C.  Exceptions in Objective-C are supposed to be programming errors and fatal errors; most apps won't catch them.  An alternative would be to use an NSError** pointer to set the error in init.  Then you could do something like:
var err: ShakaPlayerError = nil;
guard let player = ShakaPlayer(client: self, error: &err) else {
  print("Error: \(err.message)")
}

Hi @TheModMaker Having a parameter of type NSerror** as the last parameter of any Objective-C method (including an initialiser) translates into a Swift method with that last parameter removed and with a throws. That's why in #116 I requested ShakaPlayerError to inherit from NSError
Regarding throwing an exception in this case... you would only throw it in Swift. In Objective-C you would be passing back the error in the NSError** parameter.

With the modification provided in the #119 PR, the init method from Swift is seen as init() throws, while you can still use the initWithError:(NSError **)error signature when used from Objective C.


Set up CodeBuild for pull requests

See "cicd/README.md" for an overview of the setup.
There are three categories of resources we need to deploy

Global resources, created once, may require admin permission to deploy, as this includes IAM Roles
CICD resources, created once per deployed branch (main plus adhocs)
App resources, created once per environment (dev, test, prod)

Immediate Next Steps:

Merge this PR into main
Manually deploy "setup" stack to AWS Prod
Manually deploy the "cicd" stack to AWS Prod
Remove JavabuilderCodeBuildRole from "iam.yml", updating usage to use the role defined in "setup"

Bigger Next Steps

Build a environment-parameterized version of "template.yml" in "cicd/3-app"
Create a CodePipeline project in "cicd/2-cicd/pipeline.template.yml" which builds, tests, and packages the app cloudformation template.
Deploy the app stack to a Test environment
Configure a CodePipeline step to run integration/acceptance tests in the Test environment
Plan the deployment of the app stack to the Prod environment (fully converting the root "template.yml")

The build status indicators in this PR are coming from an AWS Dev instance of this codebuild project. They are failing as expected because the template.yml has linting errors.


6.3.5 .array() throws error

hey Manuel, i've been using this for a very long time now. Started an app recently but with new version 6.3.5 it always throws error on using .array(). I have only got it to work by dropping to version 6.3.4.
Error is that .array is not a function. Hope this helps. Best Regards.
Template.test.viewmodel({ 	test1: ["test1","test2","test3"], 	onCreated: function(){ 		console.log(this.test1()); 		var test = this.test1().array(); 		console.log(test); 	} })

We updated Coffeescript on viewmodel, viewmodel-debug, and reactivearray ;
so be sure to update those as well.
On Apr 8, 2018 3:52 PM, "AON"<EMAIL_ADDRESS>wrote:
hey Manuel, i've been using this for a very long time now. Started an app
recently but with new version 6.3.5 it always throws error on using
.array(). I have only got it to work by dropping to version 6.3.4.
Error is that .array is not a function. Hope this helps. Best Regards.
Template.test.viewmodel({ test1: ["test1","test2","test3"], onCreated:
function(){ console.log(this.test1()); var test = this.test1().array();
console.log(test); } })
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/305, or mute the thread
https://github.com/notifications/unsubscribe-auth/AED31o3AGglhvzVbwLJyC5Qev5WbzGAaks5tmoaHgaJpZM4TLuct
.

Please make a repro.