Chef server's API auth failed then updated 12.0.2 to 12.0.3

Ohai,
I updated chef server 12.0.2 to 12.0.3, then API auth by "pivotal.pem" is failed.
On 12.0.2
[root@db01 tmp]# chef-server-ctl user-list
the ffi-yajl and yajl-ruby gems have incompatible C libyajl libs and should not be loaded in the same Ruby VM
falling back to ffi which might work (or might not, no promises)
d-user
dd-user
h-arai
h-arai-test
h-urasoko
pivotal

On 12.0.3
[root@db02 ~]# chef-server-ctl user-list
ERROR: Failed to authenticate to https://<IP_ADDRESS>:443 as pivotal with key /etc/opscode/pivotal.pem
Response: An error occurred while trying to find 'pivotal'. Please contact support.

Sincerely.

@urasoko Thanks.  Can you briefly describe the steps you took to upgrade this cluster?  For instance, did you run chef-server-ctl upgrade after installing the 12.0.3 package?

@stevendanna Thanks for your quick reply.
And I didn't run chef-server-ctl upgrade then, only run chef-server-ctl reconfigure.
Now I tried again  install 12.0.3 to a machine that be installed 12.0.2, and run chef-server-ctl upgrade.
The error is changed, but not fixed.
[root@db01 tmp]# chef-server-ctl user-list
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 1/5
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 2/5
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 3/5
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 4/5
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 5/5
ERROR: Network Error: Connection refused - Connection refused connecting to https://<IP_ADDRESS>/users, giving up
Check your knife configuration and network settings

Regards.

@urasoko Please run chef-server-ctl status and ensure that all of the services are started.  If any are listed as down try running a chef-server-ctl start.

@stevendanna Oh, very sorry... you are right, and error has just fixed.
Thank you for your help and sorry about my operation's lack.
Cheers.

I tried all the steps mention below, but unable to create user admin.

I have started all the services which were down
[root@chefserver ~]# chef-server-ctl start
ok: run: bookshelf: (pid 14391) 0s
ok: run: nginx: (pid 14428) 0s
ok: run: oc_bifrost: (pid 14430) 1s
ok: run: oc_id: (pid 14459) 0s
ok: run: opscode-chef-mover: (pid 14461) 0s
ok: run: opscode-erchef: (pid 14463) 0s
ok: run: opscode-expander: (pid 14466) 0s
ok: run: opscode-expander-reindexer: (pid 14491) 0s
ok: run: opscode-solr4: (pid 14494) 1s
ok: run: postgresql: (pid 14354) 44s
ok: run: rabbitmq: (pid 14503) 0s
ok: run: redis_lb: (pid 14505) 0s
[root@chefserver ~]# chef-server-ctl status
run: bookshelf: (pid 14391) 39s; run: log: (pid 7413) 4344s
run: nginx: (pid 14850) 1s; run: log: (pid 7595) 4324s
run: oc_bifrost: (pid 14430) 32s; run: log: (pid 7156) 4360s
run: oc_id: (pid 14459) 31s; run: log: (pid 7200) 4355s
run: opscode-erchef: (pid 14463) 31s; run: log: (pid 7452) 4343s
run: opscode-expander: (pid 14466) 31s; run: log: (pid 7361) 4346s
run: opscode-expander-reindexer: (pid 14491) 31s; run: log: (pid 7367) 4345s
run: opscode-solr4: (pid 14494) 31s; run: log: (pid 7255) 4350s
run: postgresql: (pid 14354) 74s; run: log: (pid 7089) 4361s
run: rabbitmq: (pid 14503) 30s; run: log: (pid 7074) 4362s
run: redis_lb: (pid 14505) 30s; run: log: (pid 7562) 4338s

But still showing the same error
chef-server-ctl user-list
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 1/5
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 2/5
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 3/5
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 4/5
ERROR: Connection refused connecting to https://<IP_ADDRESS>/users, retry 5/5
ERROR: Network Error: Connection refused - Connection refused connecting to https://<IP_ADDRESS>/users, giving up
Check your knife configuration and network settings

$chef-server-ctl tail nginx
2015-07-03_07:38:21.24862 nginx: [emerg] server name "" is invalid in /var/opt/opscode/nginx/etc/chef_https_lb.conf:3
2015-07-03_07:38:22.27220 nginx: [emerg] server name "" is invalid in /var/opt/opscode/nginx/etc/chef_https_lb.conf:3
2015-07-03_07:38:23.30000 nginx: [emerg] server name "*" is invalid in /var/opt/opscode/nginx/etc/chef_https_lb.conf:3
....
if the server does not use public IP or DNS, check /etc/hosts.
add "IP HOSTNAME" onto that file. and restart nginx
chef-server-ctl restart nginx


ISPN-5232 Entry iterator returns entries created in current TX but does

not apply the filter/converter

Fixed issue so entries returned from iterator are not filtered and
converted twice

https://issues.jboss.org/browse/ISPN-5232

Looking ...

Integrated. Thanks!


The data file direct download link does not work

It looks like the direct link to download the data is broken: https://www.dropbox.com/s/731h2wudstm3zvh/Toehold_Dataset_Final_2019-10-23.csv?dl=0, error message: This item was deleted. May you double check the link?

Please use this updated link
https://drive.google.com/file/d/1t_OXvtW-hEGRt3-mgNlyBKHBqro2Z572/view?usp=sharing


SDL doesn't handle any input

Environment

Visual Studio 2017
Platform toolset - v141
Windows SDK version - 10.0.17763.0
Used VCPKG version of SDL2 (linked it properly, skipped tests)
Built in Debug x86

Expected behavior

User can input anything to the window, and it should handle it appropriately
Window should be draggable, resizable and closable

Result

User can't input anything to the window
User can't close the window, can't move it, when it's in background, user can't focus it

Notes

The emulator seems to run just fine, it's just I can't input anything, so therefore I can't test stuff.
I haven't modified the source code, besides making it load a ROM from hardcoded path and making the vector<uint8_t> _ram fixed size (_ram.resize(RAM_SIZE); on first line of nes_memory::power_on(nes_system*))
I wanted to do some developement on this emulator, but I can't get it properly to work, so sorry for bumping inactive repo

EDIT:
I actually noticed that its not the SDL issue, but rather the emulation being awfully slow. Any idea why? Im still trying to figure it out.

EDIT:
I actually figured out that its the Debug mode that makes things awfully slow. lmao
Sorry to bother anyone 😳


.NET 7 or 8?

Changelog for latest say

Move to .NET 8 Desktop Runtime, instead of .NET 7 (Download it here)

but installing it shows

.NET 8 my bad 😅
Fixed it

Oh, by the way: it would be good practice to remove the en-us/ part from links


When cards are loading, they should have a fixed height (per viewport) depending on whether it's an indicator or a chart

As the data populates, the cards expand in size. You can see it happen by reloading a project page.

@ccerv1 also needs to fix the cards with "placeholder" text instead of loading circles

Update: there should also be a fixed width. Given that some cards load faster than other, the resizing that happens when cards load in different orders is very distracting

Update: look for something less obnoxious than spinning circles as a loading symbol. (And double check there are no more "placeholder" texts being displayed.)

2 things I did:

Move the spin progress bar inside the card, so that the card is always showing, reduces the shift
Set ignoreLoading inside the area charts, so that we just show "No data" until the data is ready. Then it animates.

This is already much better, we can file more issues if we have better ideas


feat: create organim sign up with funcionality

Changes

Create  organism sign up

Author
@Edwardb11
#6

#7


[Addon] metrics addons

Description of your changes
Add three metrics related addons:

kube-state-metrics
node-exporter
prometheus-server

The kube-state-metrics and node-exporter are stateless addons. By default, they are installed to all clusters.
The prometheus-server addon provides core server part for prometheus installation. Persistent storage is not supported yet. If thanos=true is set, the prometheus-server will be installed together with the thanos sidecar component, and the thanos-query will be installed in the hub cluster to aggregate all the thanos sidecars.

How has this code been tested?

Checklist

I have:

[x] Title of the PR starts with type (e.g. [Addon] , [example] or [Doc]).
[ ] Updated/Added any relevant documentation and examples.
[ ] New addon should be put in experimental.
[ ] Update addon should modify the version in metadata.yaml to generate a new version.
[ ] Any changes about verified addons should be tested with CI script.

@barnettZQG @charlie0129 I was discussing the CUE rendering process of Application with @wangyikewxgm previously. I think for pure-cue application rendering, we should make less black box logic in vela addon enable command. Instead, let the CUE do the rendering work.
So for parameters like clusters and namespaces (which are previously controlled by metadata.yaml) are moved into parameter.cue.
The name of the addon application, in my opinion, should be decoupled with the fixed metadata. "THE NAME OF THE ADDON" and "THE NAME OF THE ADDON APPLICATION" now uses the "addon-" prefix as a convention, but in a more explicit and transparent rendering architecture of application, the logic should also be exposed to user I think.
Even though metadata.name in template.cue does not work now (since it will be overrided by the vela addon enable), I would recommend this to be included in vela addon enable in the future.

BTW, if metadata.name is not needed in template.cue, then "apiVersion", "kind" are all not needed as well.


When the sql file has been executed,somebody changed it,then the project goes wrong

why don't we do such things that after reading and executing the sql file,then change it into a pdf file or other file which is read only.
cause we can't make everyone to avoid to change the executed sql files.
since the sql files which have executed just realized their aim,so they should be just read only to avoid being changed by mistake.

However, we can make everyone who use flyway to execute their own maked sql files,if the executed sql files changed into other read only files,then other people in project can't change these executed sql files by mistake.

This does not seem an appropriate process for Flyway to perform.
However, if you are having issues with changed SQL scripts getting into your deployment I would recommend integrating the command validate which would fail ahead of deployment if changes have been made to previously deployed Flyway version scripts.
Additionally, you may want to look at Flyway Desktop as a way of managing your Flyway development environment if you wish to have more restrictions.


IMPRO-1642: Factor interpolation out of phase-change-level plugin

Factors horizontal interpolation out of the phase-change-level plugin. Moves the unit tests to cover this standalone function. Add a few extra unit tests. Adds extended help to capture details of the method being used in the phase-change-level plugin that were previously recorded in the doc-string of the horizontal interpolation method.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- improver/utilities/interpolation.py  6
- improver_tests/utilities/test_interpolate.py  1

Clones added
============
- improver_tests/utilities/test_interpolate.py  4

Clones removed
==============
+ improver_tests/psychrometric_calculations/test_PhaseChangeLevel.py  -7

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

Complexity increasing per file
==============================
- improver/utilities/interpolation.py  6
- improver_tests/utilities/test_interpolate.py  1

Clones added
============
- improver_tests/utilities/test_interpolate.py  4

Clones removed
==============
+ improver_tests/psychrometric_calculations/test_PhaseChangeLevel.py  -7

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

Complexity increasing per file
==============================
- improver/utilities/interpolation.py  6
- improver_tests/utilities/test_interpolate.py  1

Clones added
============
- improver_tests/utilities/test_interpolate.py  4

Clones removed
==============
+ improver_tests/psychrometric_calculations/test_PhaseChangeLevel.py  -7

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

Complexity increasing per file
==============================
- improver/utilities/interpolation.py  6
- improver_tests/utilities/test_interpolate.py  1

Clones added
============
- improver_tests/utilities/test_interpolate.py  4

Clones removed
==============
+ improver_tests/psychrometric_calculations/test_PhaseChangeLevel.py  -7

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

Complexity increasing per file
==============================
- improver/utilities/interpolation.py  6
- improver_tests/utilities/test_interpolate.py  1

Clones added
============
- improver_tests/utilities/test_interpolate.py  4

Clones removed
==============
+ improver_tests/psychrometric_calculations/test_PhaseChangeLevel.py  -7

See the complete overview on Codacy


Logging

fixes #60
Uses the build-in Nest-Logger.
In case we want to extend Logging we should use a external logging-package like winston.
Logging can be turned on by setting environmentvariable DEBUG=true.

Looks great 👍 . Could you add a screenshot with and without DEBUG=true
Also could info be added to the README about this feature please, because I know I will forget in the future lol 😂

When Logging is disabled, there are just the Logs Nest.js makes when starting the App

When Logging is enabled you will see ALL incoming Requests with the scheme
<statusCode> | [<method> <originalUrl> - <body>


Not working in Vue Composition API - Vue 3

Thank you for your contribution to the community <3. We hope you can continue to develop this thing!

@harrytran998 I'd love to do so myself!!
I'm looking forward to try more edge cases. Can you give me an example Vue file where you use composition API where it's not working?

Actually, I run this on recursive mode --> Throw error.
Case 1: I tried your suggestion command

Cas 2: I change a little bit the command
vue-int --input ./src/components --output vetur --recursive

Hope you can fix it!

Can you share that file with the error : ChangePasswordForm.vue

@harrytran998 latest v0.1.2 that's live now has a fix that might solve your issue as well.
Can you try and let me know? Thanks!!

@harrytran998 latest v0.1.2 that's live now has a fix that might solve your issue as well.
Can you try and let me know? Thanks!!

closing because of inactivity


Extend URL with tracking parameter

It would be great to have a way to exten the URLs that are generated in the feed with tracking parameters.
Example: https://www.betterplace.org/c/neues/feed.xml
Instead of
<link href="https://www.betterplace.org/c/neues/erste-fremdsprache-coden" rel="alternate" type="text/html" title="Erste Fremdsprache: Coden!"/>
The output should be something like
<link href="https://www.betterplace.org/c/neues/erste-fremdsprache-coden?utm_campaign=atom-feed&utm_medium=atom-feed&utm_source=atom-feed&utm_term=generated-2018-02-22--06-49" rel="alternate" type="text/html" title="Erste Fremdsprache: Coden!"/>
There are two parts to this, having just static params added. Or alternatively having the params dynamic. The static part could be a lot easier and would be enough IMO.
Any ideas how this could be solved nicely?
And what steps to go through to get in in the plugin?
Thanks!
Other resources

WordPress Feed Plugin with Campaign Params http://joshledford.com/how-to-add-google-analytics-campaign-tracking-to-your-wordpress-rss-feed/
Google Analytics Campaign Params https://support.google.com/analytics/answer/1033863

Personally, I don’t like URLs that have been muddied up that way. If I share a link from my feed reader, it makes it difficult for the recipient to see what the relevant part of the URL is, not to mention that all that referral information becomes irrelevant if somebody is clicking a link in their Twitter client that I shared from my feed reader.
I don’t think this would be technically difficult to implement, but I don’t see the value it adds.

The value is, that I can see in my analytics what users came via RSS. Simple but powerful as that. Campaign tracking is one of the most powerful parts of analytics software.
Google Analytics is actually smart enough to change the tracking information internally when the referrer is Twitter etc (AFAIK). The UseCase you describe is very common with every email-campaign-link that has campaign tracking on it and then gets shared on other channels.


Doc: Services exposed externally as cluster IPs

New How to:

Can merge at any time
Approved by Casey and Spike
Policies verified

Deploy preview for calico ready!
Built with commit c5748398bd7bcb2a306a184cde3ecc89670280bf
https://deploy-preview-2755--calico.netlify.com


Expand destination selection for 'show logs'

Summary

Hi! :)
We would like to request more possibilities when it comes to Show logs option.

Currently we can either create a new notebook by clicking on New notebook or select existing one from the drop down menu.

Feature Suggestion

It would be nice to have additional option such as log explorer or its 3rd gen alternative when its available in the 3rd gen.
Possible Implementation

Context

We would like to have more option to explore logs, such as log explorer from 2nd gen.

Thank you for the idea! We will revisit it once the 3rd gen Logs app becomes available.


Anchor element properties

Basic info:
Creating an anchor element and assigning a href to it should affect in parsing the other properties but it doesn't. I'm not sure if it's a bug or missing feature - if the second one, is there a possibility that it will be implemented in the future?

Node.js version: 6.9.0
jsdom version: 11.3.0
Mocha

Minimal reproduction case
let urlParser = document.createElement('a');
urlParser.href = "http://example.com?query=1#hash";
// "hash": "",
// "search": "",
// ... etc.

How does similar code behave in browsers?
In browsers, anchor's properties are parsed properly, e.g:
https://jsbin.com/qocucihute/1/edit?js,console
Thanks,
Milosz

This is not a minimal reproduction case, because when I put that in a file and do node file.js, I get an exception saying document is not defined.
Let me close this until such a case is provided. Please edit and ping this thread when you have done so and I will reopen.

Faced a similar problem when tested my code with jest. I was not able to change link.search prop if link.href === '/'.
This is because url is null here: https://github.com/tmpvar/jsdom/blob/2d51af302581a57ee5b9b65595f1714d669b7ea2/lib/jsdom/living/nodes/HTMLHyperlinkElementUtils-impl.js#L222-L228
because parser returned failure here:
https://github.com/tmpvar/jsdom/blob/2562b8e146aefc7b7077aed9742c648dde4c9b53/lib/jsdom/living/nodes/HTMLHyperlinkElementUtils-impl.js#L282-L292
But jest uses the old jsdom now (9.12.0). Hope the next release will fix this.
Current workaround is to set testURL in jest configuration.
Hope this will help someone.

here you go @domenic
const dom = new JSDOM(`<a href="/test.php?key=abc" title="abc" class="blue">`);
let search = dom.window.document.querySelector('a').search;
console.log('search:', search);
// how/why I wanted to use HTMLAnchorElement.search
console.log('key:', new URLSearchParams(search).get("key"));

output:

search:
key: null

I love using jsdom to write scraping scripts quickly, because I get to use querySelector|All with CSS selectors (which I got good at making) and incrementally test in the browser's devtools.
so TIL that jsdom's (pure js) implementation of WHATWG DOM and the HTML Standard|s is not as perfect as Chromium's, which is fine, that's no easy feat, i'm just mentioning it as a future note.

(Your example seems unrelated to the OP and would be better in a new issue.)
That's working as expected. You have no base URL for your JSDOM, so /test.php?key=abc does not resolve to a valid URL, and so anchEl.search returns the empty string. You can see the same behavior in your browser if you navigate to about:blank (i.e. the default URL) and run the code.


avoid defining empty interface for bootstrap command options

Looks like this is fixed on main already 🙃

Ah yeah, but we should probably lint on PRs


ci: tweak the Python workflows

Remove manual installations of PyTorch everywhere, as the latter should
be handled while installing the library through pip. Remove -e flag
while installing our packages, and refer to them with ./. Remove
s3torchbenchmarking unit tests runs, unnecessary for now. Reformat
some workflow files (cosmetic).
Drop support (in worfklows) for macOS x86_64 architecture, since PyTorch
dropped support to since v2.3
(https://dev-discuss.pytorch.org/t/pytorch-macos-x86-builds-deprecation-starting-january-2024/1690),
and future DCP implementations will require that version.

By submitting this pull request, I confirm that my contribution is made under the terms of BSD 3-Clause License and I agree to the terms of the LICENSE.

Cancelling with PR: will include changes within the feature/dcp branch.


difference table displays columns in the reverse order of their difinition.

problem:
when Quick compares two rows it displays the columns in the reverse order of defined by the user.
solution:
when Quick compares two rows it should display the columns in the same order of defined by the user.

closed in a27791f


Russian letters are not displayed in the dialog box

The problem
Describe the bug
A clear and concise description of what the bug is.
System (please complete the following information):

OS: [Windows 11]
Godot Version: [3.5]
Dialogic Version: [1.4.4]

I changed the font and it worked
But maybe this situation need add to the FAQ or change the default font.

In 2.0 we use the built-in font I believe. I think it supports most common letters, but I haven't tried yet.


ShouldNot does take  seconds when executed on an element which parent does not exist.

In our code we frequently use nested Find() calls; e.g. By.Selene: (By.Selene: (By.Selene: (NSelene.SeleneDriver).Find(By.XPath: .//descendant-or-self::*[@data-ta = 'reports-list'])).Find(By.XPath: .//*[(contains(@class, 'grid-row') or contains(@class, 'row') or contains(@class, 'list-group-item') or @data-ta='grid-row' or self::form) and not (contains(@class, 'grid-header') or @data-ta='header' or @data-ta='grid-header' or contains(@class, 'report-header'))]/self::*[descendant-or-self::*[@data-ta = 'name' and .//text() = 'Inrichtingsjaarrekening 2020 beperkt']])).Find(By.XPath: .//descendant-or-self::*[@data-ta = 'name'])
When such an element is validated with a ShouldNot, then the timeout is only used on the final element of the search expression. I reproduced this in a simple testcase below:
The nested p is commented out, but we check on the nested a. This is valid, but it takes the full timeout to validate this.
        [Test]
        public void WaitForVisibility_OnElement_WhichParent_DoesNotExist()
        {
            Given.OpenedPageWithBody(@"

Heading 2

"
            );

            DateTime start = DateTime.Now;
            S("p").Find("p").Find("a").ShouldNot(Be.Visible);
            Assert.Less(DateTime.Now.Subtract(start).TotalSeconds, Configuration.Timeout);
        }

Maybe related to #3

@wjgerritsen-0001, Sorry, I did not get what do you mean here:)
I checked this code in my editor:
            Given.OpenedPageWithBody(@"

Heading 2

"
            );

            DateTime start = DateTime.Now;
            S("p").Find("p").Find("a").ShouldNot(Be.Visible);
            Assert.Less(DateTime.Now.Subtract(start).TotalSeconds, Configuration.Timeout);

It passes without waiting, and this is as expected. The  element in your html - is not visible. And our assert S("p").Find("p").Find("a").ShouldNot(Be.Visible); just checks the same, that it is not visible. And it passes. Everything as it should be from the User perspective.
If you change the code so it asserts visibility:
S("p").Find("p").Find("a").Should(Be.Visible);

Then it will fail as expected, telling that the
 element is not visible:
Timed out after 4s, while waiting for:
   Browser.Element(p).Element(p).Element(a).Should(Be.Visible)
Reason:
   no such element: Unable to locate element: {"method":"css selector","selector":"p"}
 (Session info: headless chrome=91.0.4472.114)
 ----> OpenQA.Selenium.NoSuchElementException : no such element: Unable to locate element: {"method":"css selector","selector":"p"}

By the way... this is an interesting case, because we don't see from the error message, which among two "p" elements is not visible... Probably we have to file new issue for this and try to improve...
P.S.
One more thing - the ShouldNot(Be.Visible) syntax is obsolete now, the recommended way is: Should(Be.Not.Visible)

Thanks for looking into this ticket. Indeed with the latest code base I also experience the same. So we are upgrading now.
The message in the past was like:
    OpenQA.Selenium.WebDriverTimeoutException :
    Timed out after 4 seconds
    while waiting entity with locator: By.Selene: (By.Selene: (By.Selene: (NSelene.SeleneDriver).Find(By.CssSelector: p)).Find(By.CssSelector: p)).Find(By.CssSelector: a)
    for condition: Visible
      Expected : True
      Actual   : False
      ----> OpenQA.Selenium.WebDriverTimeoutException :
    Timed out after 4 seconds
    while waiting entity with locator: By.Selene: (By.Selene: (NSelene.SeleneDriver).Find(By.CssSelector: p)).Find(By.CssSelector: p)
    for condition: Visible
      Expected : True
      Actual   : False
      ----> OpenQA.Selenium.NoSuchElementException : no such element: Unable to locate element: {"method":"css selector","selector":"p"}
      (Session info: chrome=91.0.4472.164)```

Guess the fix came with alpha7: https://github.com/yashaka/NSelene/commit/a7f113b974ee9fd3c5ac3cf67b402d244f552dc3


"Sartăș" is listed in the drop-down menu

Description:
"Sartăș" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Sartăș" in the search bar.

Expected results
The location is listed in the drop-down menu as "Sartăș, Alba (Baia de Arieș)".


OpenVPN 2.4 Script Error

--2017-03-05 21:32:18--  https://github.com/OpenVPN/easy-rsa/releases/download/3.0.1/EasyRSA-3.0.1.tgz
Resolving github.com (github.com)... <IP_ADDRESS>, <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-cloud.s3.amazonaws.com/releases/4519663/9dab10e8-7b6a-11e5-91af-0660987e9192.tgz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20170305%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170305T193219Z&X-Amz-Expires=300&X-Amz-Signature=b4786b817ecde82af276b0f62745ea14b5d2778ff1dbbdbff336784539530ca2&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DEasyRSA-3.0.1.tgz&response-content-type=application%2Foctet-stream [following]
--2017-03-05 21:32:19--  https://github-cloud.s3.amazonaws.com/releases/4519663/9dab10e8-7b6a-11e5-91af-0660987e9192.tgz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAISTNZFOVBIJMK3TQ%2F20170305%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170305T193219Z&X-Amz-Expires=300&X-Amz-Signature=b4786b817ecde82af276b0f62745ea14b5d2778ff1dbbdbff336784539530ca2&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3DEasyRSA-3.0.1.tgz&response-content-type=application%2Foctet-stream
Resolving github-cloud.s3.amazonaws.com (github-cloud.s3.amazonaws.com)... <IP_ADDRESS>
Connecting to github-cloud.s3.amazonaws.com (github-cloud.s3.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 40960 (40K) [application/octet-stream]
Saving to: ‘/root/EasyRSA-3.0.1.tgz’

100%[=======================================================================================================================================================================>] 40,960       140KB/s   in 0.3s

2017-03-05 21:32:20 (140 KB/s) - ‘/root/EasyRSA-3.0.1.tgz’ saved [40960/40960]

Note: using Easy-RSA configuration from: ./vars

init-pki complete; you may now create a CA or requests.
Your newly created PKI dir is: /etc/openvpn/easy-rsa/pki

unable to create curve (sect571r1)

Easy-RSA error:

Curve sect571r1 not found. Run openssl ecparam -list_curves to show a
list of supported curves.

Note: using Easy-RSA configuration from: ./vars

Easy-RSA error:

Missing expected CA file: serial (perhaps you need to run build-ca?)
Run without commands for usage and command help.

Note: using Easy-RSA configuration from: ./vars

Easy-RSA error:

Missing expected CA file: serial (perhaps you need to run build-ca?)
Run without commands for usage and command help.

Note: using Easy-RSA configuration from: ./vars

Easy-RSA error:

Missing expected CA file: serial (perhaps you need to run build-ca?)
Run without commands for usage and command help.
cp: cannot stat ‘pki/ca.crt’: No such file or directory
cp: cannot stat ‘pki/private/ca.key’: No such file or directory
cp: cannot stat ‘pki/issued/server.crt’: No such file or directory
cp: cannot stat ‘pki/private/server.key’: No such file or directory
cp: cannot stat ‘/etc/openvpn/easy-rsa/pki/crl.pem’: No such file or directory
chmod: cannot access ‘/etc/openvpn/crl.pem’: No such file or directory
450
success
success
success
success
331
Job for<EMAIL_ADDRESS>failed because the control process exited with error code. See "systemctl status<EMAIL_ADDRESS>and "journalctl -xe" for details.
cat: /etc/openvpn/easy-rsa/pki/ca.crt: No such file or directory
cat: /etc/openvpn/easy-rsa/pki/issued/client.crt: No such file or directory
cat: /etc/openvpn/easy-rsa/pki/private/client.key: No such file or directory

Finished!

I have tested it on 4 different KVM VPS'es, all of them running CentOS 7, and this has happened on all of them :(.

Please just read before reporting bugs. Also, I never said my PR was working, so please keep the discussion here.

Oh, shit, sorry man. Still learning GitHub :D.
Sorry.

You are forgiven 😉


Use memcpy instead of strncpy to silence compiler warning (MEGH-5483)

The old version triggers a stringop-truncation compiler warning. According to the GCC manual, memcpy is the suggested fix in this exact scenario.
Curious: the warning seems to be only triggered in esp-idf's CONFIG_COMPILER_OPTIMIZATION_PERF mode (which corresponds to GCC's -O2 flag). It seems that GCC triggers the warning for -O2, but not for -O1 (demo).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I think this is now obsolete: https://github.com/espressif/esp-rainmaker/pull/297/


Update UI theme

Add more of our brand colour into the UI
Create a logo (not that great so change it if you'd like)

Here is what it looks like:
Home Page with Scrolling

Home Page No Scrolling

Contact Details Page

Codecov Report

Merging #241 (65894fd) into master (32248ed) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #241   +/-   ##
=========================================
  Coverage     56.73%   56.73%
  Complexity      688      688
=========================================
  Files           118      118
  Lines          2709     2709
  Branches        318      318
=========================================
  Hits           1537     1537
  Misses         1065     1065
  Partials        107      107

Impacted Files
Coverage Δ

src/main/java/seedu/address/ui/UiManager.java
0.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 32248ed...65894fd. Read the comment docs.


Set a default collection

Add the ability to add a default collection to store links to.

Ok, will add this

Consider it done
9ccf7cd


RequestKernelInfo hangs when sent to CompositeKernel within VS Code

@jonsequitur : Trying to understand the impact of this - how often /when do we expect users to request kernel info?

It's possibly going to be common in automation and extension scenarios. This was working at one point (when only the .NET-based kernels were handling this command) and I believe the root cause here is #2081.


Use Relational Data Modeling Techniques to design the content of the Work Zone Data Specification

What:  Use Relational Data Modeling Techniques (RDMT) to design the content of the Work Zone Data Specification.
Why:  Version 1 of the Work Zone Data Specification relies on data dictionary, markup, and exchange languages (TMDD, XML, JSON) to define content and formatting.  It does not employ well established data design methods to define how data should be stored.
Using Relational Data Modeling Techniques to design the Work Zone Data Specification will;
•	Organize the data more efficiently
•	Increase consistency
•	Ease data retrieval
•	Enable a flexible and scalable data model
•	Promote Standards-Centric development of applications
Using Relational Data Modeling Techniques to design the Work Zone Data Specification will not;
•	Dictate how data is managed at the source
•	Change the specifications content
•	Prohibit publishing content according to the TMDD
•	Prohibit publishing content according to version 1 of the specification
Normalized Common Core Table using RDMT

Data Name
Data Type
Description
Conformance
Notes

geometryType
Enum:   Multipoint   Or   LineString
May be represented as a linestring or a   multipoint as defined in the geoJson specification.
Optional

geometry
coordinate(s)
A coordinate pair or an array of coordinates.  In either case, the first coordinate is the   beginning point and the last coordinate is the ending point.
Required if geometry type is not null
Coordinate pairs and coordinate arrays are   formatted according to the geoJson spec

eventType
Enum
A description of the event type
Required

Identifier
Data Element
A unique identifier issued by the data   feed provider to identify the work zone project or activity
Required
Request that this be a standardized   identifier for a future version

Subidentifier
Data Element
A unique identifier issued by data feed   provider   that provides additional references to   project or activity
Optional
This identifier may be used in more   than one feed as a reference to an   agency project number or permit ID

roadName
Data Element
The name of the road on which   the work zone applies which is   known by the public
Required
Add a business rule that   pulls data from a specified   list or formal naming   conventions, for example,   (1) arterials comply with the USPS   Street Suffix Abbreviations (USPS Pub   28); (2) all Interstates will   be abbreviated as I-#, state route with   the   state abbreviation and then the number,   etc.

roadNum
Data Element
The road number designated   by a jurisdiction such as a   county, state or interstate
Optional
Examples I-5, VT 133

roadDirection
Data Element
The designated direction of the   roadName that is impacted by   the work zone activity
Required
Example North (for I-5 North)

beginningDemarcation
Enum:   Estimated or Verified
Indicates how the beginning coordinate   was defined.
Required if geometry type is not null

endingDemarcation
Enum:   Estimated or Verified
Indicates how the ending coordinate was   defined.
Required if geometry type is not null

beginCrossStreet
Data Element
The cross street along the  roadway where the event begins

Required when Road   Classification is arterial

endCrossStreet
Data Element
The cross street along the   roadway where the event ends

Required when Road   Classification is arterial

beginMilepost
Data Element
The linear distance   measured against a milepost marker   along a roadway where the work zone begins

A milepost or mile marker is a surveyed   distance posted along a roadway measuring the length (in miles or tenth of a   mile) from the south west to the north east. These markers are typically   notated on State and local government digital road networks. Provide link to description   of milepost method in metadata file (see Section 2.7).

endMilepost
Data Element
The linear distance   measured against a milepost   marker along a roadway where   the work zone ends

A milepost or mile marker is a surveyed   distance posted along a roadway measuring the length (in miles or tenth of a   mile) from the south west to the north east. These markers are typically   notated on State and local government digital road   networks. Provide link to description   of milepost method in metadata file (see Section 2.7).

beginMpDemarcation
Enum:   Estimated or Verified
A measure of the accuracy of the   milepost value

endMpDemarcation
Enum:   Estimated or Verified
A measure of the accuracy of the   milepost value

startDateTime
Data Element
The time and date when a work zone is   established
Required
All date/time formats shall use ISO   8601 Data elements and interchange formats – Information interchange

startDateTimeAccuracy
Enum:   Estimated or Verified
A measure of how accurate the start   Date Time is.
Required

endDateTime
Data Element
The time and date when a work zone   is removed
Required
All date/time formats shall use ISO   8601 Data elements and interchange formats – Information interchange

endDateTimeAccuracy
Enumeration:   Estimated or Verified
A measure of how accurate the end Date   Time is.
Required

Status
Enum
The status of the work zone
Optional
See Enumerated Type Definitions

totalLanes
Data Element
The total number of lanes associated   with the road segment designated by the workzone geometry
Optional
A segment is a part of a roadway in a   single direction designated the work zone geometry

openLanes
Enum
The laneType that is opened on the road   segment   designated by the work zone geometry
Optional

closedLanes
Enum
The laneType that is closed due to the   work zone on the road segment designated by the work zone geometry

More detailed lane   impacts / status will be described in   Version 2 of the specification

closedShoulders
Enum
An enumerated type identifying the   shoulder lanes that are closed
Optional
To explicitly state that no   shoulders are closed,   use none

workersPresent
Data Element
A flag indicating that there are   workers present in the work zone
Optional

reducedSpdPosted
Data Element
The reduced speed limit posted in the   work zone
Optional

roadRestrictions
Enum
One or more roadRestriction flags   indicating restrictions apply to the work zone road segment associated   with the work zone bounded by the   work zone geometry
Optional
More details may be added to future   WZDx versions; these are included as flags rather than detailed restrictions

Description
Data Element
Short free text description of work   zone
Optional
This will be populated with formal   phrases in a later WZDx version

issuingOrganization
Data Element
The organization issuing the data feed
Optional
Will create a list in a future version

timestampEventCreation
Data Element
The time and date when the activity or   event was created
Optional

timestampEventUpdate
Data Element
The time and date when the activity or   event was updated
Optional

20191021 @ 1425 - Updated PR with a Normalized Common Core Table.

It should be noted that ISO TC 204 (Intelligent Transport Systems) WG 1 (Architecture) is leading an effort to create an ITS-wide logical data model for the explicit purpose to define how data from different protocols can be shared across protocols, domains, etc. We are currently working with the Smart City and Internet of Things community to ensure our approach to defining this data model is consistent with those much larger efforts that we will eventually need to link to.
There are also ongoing discussions about how these data models might be linked into the National ITS Architecture (http://arc-it.org).
It would be useful if any data models produced by the WZDx team were coordinated with these broader efforts. This likely suggests using UML as the data modeling language and eventually producing traces from each element within the WZDx model (which would be a "physical data model") to the ITS logical data model. These efforts are just getting started and are currently hosted at https://github.com/k-vaughn/its-reference-model (likely to be moved to the ISO-TC204  page in the future)

@k-vaughn - Happy to model in UML.  Hope to have it done my Wednesday.

The rich text formatting for road_events (Formerly Common Core Data Dictionary) table is not working. We need to get this clean up before voting. It's very hard to follow in the current state.

Yes.  I’m trying to clean it up this afternoon.
Derald Dudley
NGDA Transportationhttps://communities.geoplatform.gov/ngda-transportation/ Theme Lead
FGDC Transportation Subcommitteehttps://communities.geoplatform.gov/ngda-transportation/transportation-subcommittee/ Chair
Phone:<PHONE_NUMBER>
Pronouns: he/him/his
The Office of Spatial Analysis and Visualizationhttp://maps.bts.dot.gov/
Bureau of Transportation Statisticshttp://www.rita.dot.gov/bts/
Office of the Assistant Secretary of Transportation for Research and Technologyhttp://www.rita.dot.gov/
United States Department of Transportationhttp://www.transportation.gov/
From: CraigMoore-Sea<EMAIL_ADDRESS>Sent: Friday, November 08, 2019 2:31 PM
To: usdot-jpo-ode/jpo-wzdx<EMAIL_ADDRESS>Cc: Dudley, Derald (OST<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [usdot-jpo-ode/jpo-wzdx] Use Relational Data Modeling Techniques to design the content of the Work Zone Data Specification (#50)
The rich text formatting for road_events (Formerly Common Core Data Dictionary) table is not working. We need to get this clean up before voting. It's very hard to follow in the current state.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/usdot-jpo-ode/jpo-wzdx/pull/50?email_source=notifications&email_token=AB2LFGQMZU7SDQS2SG4F5HDQSW5ADA5CNFSM4JCWU3T2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDTD7QA#issuecomment-551960512, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB2LFGTEC3ARIAW3ECGFLKLQSW5ADANCNFSM4JCWU3TQ.

I suggest we define the allowed geometry types to be LineString, MultiPoint, MultiLineString, and GeometryCollection; any collection must at least include a MultiPoint or Linestring feature.

Consider adding new travel_path_effect field to the lanes table. We would move the shift-left and shift-right values to this table from the lane_status field. We would add the following values:
•	alternating-one-way
•	merge
•	merge-left
•	merge-right
•	shift
•	unknown
We may want to add an open-with-restrictions value to the lane status field. This would serve as notice that related restrictions records exist.

Consider adding new travel_path_effect field to the lanes table. We would move the shift-left and shift-right values to this table from the lane_status field. We would add the following values:
• alternating-one-way
• merge
• merge-left
• merge-right
• shift
• unknown
We may want to add an open-with-restrictions value to the lane status field. This would serve as notice that related restrictions records exist.

Would shift, shift-left, and shift-right be more explicit?

I'm in the process of reviewing this currently.
Overall, I fear that not many people will have time to review in the depth that they should considering several new commits are being pushed every day. I support the relational data model conceptually and believe it should be implemented in the v2 release as now is the time for large changes like this. However, I think this PR is making too many changes (new commits every hour today, one day before voting [Nov 18]) and is thus not yet stable enough to review and be ready for voting by tomorrow (Nov 19). If I had to vote now, I would vote "no" for this reason, not because I don't agree with the idea or your implementation.
Additionally, I don't think it was a good decision to address other issues (#44, #45, #48) in this PR as it broadens the PR's scope and doesn't allow for voters to accept some of these and not others. This PR should be specific to the restructuring/relational data model until it is approved, after which it can implement the other issues.
Relatedly, there was much discussion followed by a passing vote on #33 to define the enumerated types (called activity_type in this relational data PR) for a work zone event_type, however, that doesn't seem to be referenced here. Even event_type, which is critical to this PR being completed, is not yet defined. Ideally, defining that would require some discussion which doesn't seem possible given the current timeline (one day until voting). There may be more "missing pieces" like this; when I finish my review I will note all that I have found here.

I've completed my review and compiled my comments below:
Actions

The activity_type enumerations for a "Work Zone" event_type should be included in (enumerated_field_definitions.md)[https://github.com/DeraldDudley/jpo-wzdx/blob/master/data-tables/enumerated_field_definitions.md] as approved in #33.
*The full event_type enumeration needs to be defined, though potentially non-blocking for WZDx v2. Relatedly, an activity_type enumeration for each event_type will be necessary. These should be a future item for completeness and adoption of this structure in other contexts.
The full-spec and child full-spec.md should be removed, as they are no longer relevant and all data-tables references no longer exist.
The content of the create-feed directory needs to be updated. Having examples (e.g. JSON and XML) of the new models/field names in use is important; this information was critical for me when first getting to understand the WZDx v1.1 spec.
The content of the sample-files directory needs to be updated.
The project root README.md references to full-spec.md and “common core” should be edited/removed, as both are no longer relevant.
Fix typo in the ERD diagram; event_subidentifieer to event_subidentifier.

Comments

The road_name and road_number fields are “new” in the sense that before they were part of the BeginLocation data frame in v1.1. This approach has a flaw in that the user can't specify if the EndLocation roadway is different than the StartLocation. However, it was at least clear at which point in the road event the road name referred to. Following the changes proposed in this PR, if the road event spans multiple roadways, it will be unclear where the road_name and road_number refer to. There are a few ways to solve this (see #52), but ideally, the solution would be the result of its own discussion and this PR would just match v1.1. To do that, these fields would be chang to start_road_name and start_road_number.
The description of event_begin_mp_demarcation and event_end_mp_demarcation in the road events table is inconsistent with the field name.
There is inconsistency between the ERD diagram road_event_feed_info in the diagram has event_issuing_organization while the data table uses feed_publisher.
In v1.1, issuingOrganzation was a field on the road event and in this PR it has been moved to the road_event_feed_info table which was previously the header. This means that road events cannot have different issuers which may be fine (and is cleaner, if it’s fine) but is a larger change than just being part of the relational data model. Ideally, all breaking changes like this which were included as part of this PR should be separate PRs and up to their own discussion and voting.
It would be very helpful if the enumerations for each enumerated type were hyperlinked to from their respective data table.
Overall, this is a lot cleaner—more consistent naming and field type clarity—than v1.1.

Questions

What is the source of the “demarcation” terminology and fields in v1.1?
Why is v1.1’s roadDirection renamed to event_direction when roadName and roadNum translate pretty directly to road_number and road_name?
I think it would be helpful to have a “migration guide” which indicates the mapping between new fields in this PR to the old common core data.

Let me know if you need any clarification on any of this. I see

Hi Jacob - thanks for this super comprehensive review. We agree with your suggestions on a streamlined approach for review and will put that forward shortly. Thank you for weighing in, and look forward to continued discussion.

I've completed my review and compiled my comments below:
Needs Action

The activity_type enumerations for a "Work Zone" event_type should be included in enumerated_field_definitions.md as approved in #33.
The full event_type enumeration needs to be defined, though potentially non-blocking for WZDx v2. Relatedly, an activity_type enumeration for each event_type will be necessary. These should be a future item for completeness and adoption of this structure in other contexts.
The full-spec and child full-spec.md should be removed, as they are no longer relevant and all data-tables references no longer exist.
The content of the create-feed directory needs to be updated. Having examples (e.g. JSON and XML) of the new models/field names in use is important; this information was critical for me when first getting to understand the WZDx v1.1 spec.
The content of the sample-files directory needs to be updated.
The project root README.md references to full-spec.md and “common core” should be edited/removed, as both are no longer relevant.
Fix typo in the ERD diagram; event_subidentifieer to event_subidentifier.

Comments

The road_name and road_number fields are “new” in the sense that before (v1.1) they were part of the BeginLocation data frame. This approach has a flaw in that the user can't specify if the EndLocation roadway is different than the StartLocation. However, it was at least clear at which point in the road event the road name referred to. Following the changes proposed in this PR, if the road event spans multiple roadways, it will be unclear where the road_name and road_number refer to. There are a few ways to solve this (see #52), but ideally, the solution would be the result of its own discussion and this PR would just match v1.1. To do that, these fields would be changed to start_road_name and start_road_number.
The description of event_begin_mp_demarcation and event_end_mp_demarcation in the road events table is inconsistent with the field name.
There is inconsistency between the ERD diagram road_event_feed_info in the diagram has event_issuing_organization while the data table uses feed_publisher.
In v1.1, issuingOrganzation was a field on the road event and in this PR it has been moved to the road_event_feed_info table which was previously the header. This means that road events cannot have different issuers which may be fine (and is cleaner, if it’s fine) but is a larger change than just being part of the relational data model. Ideally, all breaking changes like this which were included as part of this PR should be separate PRs and up to their own discussion and voting.
It would be very helpful if the enumerations for each enumerated type were hyperlinked to from their respective data table.
Overall, this is a lot cleaner—more consistent naming and field type clarity—than v1.1.

Questions

What is the source of the “demarcation” terminology and fields in v1.1?
Why is v1.1’s roadDirection renamed to event_direction when roadName and roadNum translate pretty directly to road_number and road_name?
I think it would be helpful to have a “migration guide” which indicates the mapping between new fields in this PR to the old common core data.

Let me know if you need clarification on any of this.

Thank you @j-d-b !
I've numbered the bullets for clarity.
Actions

Activity Type Enumerations - Agree.
Work Type Enumerations - Agree.

The only event_type being considered now is Work Zone; It is an enumeration of 1 value right but has room to grow.
Agree that conditional Activity Types, dependent on Event Types, are necessary.
Are you proposing that activity types not be considered for this version?

Removal of full_spec and full-spec.md - Agree
Update Create Feed Directory - Agree
Update sample-files directory - Agree
Update root README.md - Agree
Fix typo in ER Diagram - Good Catch, will do. Thank you.

Comments
8. Providing start_road_name, end_road_name, start_road_number, and end_road_number:

One proposed solution to accommodate Road Concurrency included allowing a string of separated values to indicate multiple street names and numbers.
E.g. "US12N; US70E; US220N; US421S; I40E; NC85N" or "Tamiami Trail; North Tamiami Trail; Cleveland Avenue"
The proposed solution of a start_road_name, end_road_name, start_road_number, and end_road_number does not accommodate Road Concurrency and does not capture all road names along an event.
Technically, to achieve normalization, the road names should be in a related table; this is probably a good place not to normalize the data.

The field names event_begin_mp_demarcation and event_end_mp_demarcation are awful. I agree!
I changed the accuracy descriptor because the information being conveyed is not a measure of accuracy; Its an indication of whether or not the provided information have been verified. How do you feel about using a boolean is_verified flag for "accuracy" fields?

event_beginning_is_verified
event_ending_is_verified
event_start_date_is_verified
event_end_date_is_verified
event_beginning_milepost_is_verified
event_ending_milepost_is_verified

event_issuing_organization/feed_publisher discrepancy

Good catch, thank you

In v1.1 issuingOrganzation was a field on the road event and in this PR it has been moved to the road_event_feed_info table which was previously the header. This means that road events cannot have different issuers.

This is not true.  The road_event_info_feed table can accommodate more than one issuing organization.  The subsequent road events would be related to the road_event_info_feed by the feed_id.
A JSON Example:
{
"road_event_feed_info": [{
"feed_id": 1,
"issuing_organization": "State DOT",
"timeStampUpdate": "time",
"metadataURL": "url",
"versionNo": "1"
},
{
"feed_id": 2,
"issuing_organization": "County DOT",
"timeStampUpdate": "time",
"metadataURL": "url",
"versionNo": "1"
},
{
"feed_id": 3,
"issuing_organization": "Local DOT",
"timeStampUpdate": "time",
"metadataURL": "url",
"versionNo": "1"
}
]
}
The issuing_organization field belongs in the road_event_feed_info table because its a more efficient method of storing the data.

Hyperlinked enumeration to and from their respective data tables. - Agree

Overall, this is a lot cleaner—more consistent naming and field type clarity—than v1.1. - I agree

Questions
14. What is the source of the “demarcation” terminology and fields in v1.1?

latitude-est, latitude-ver, longitude-est, and longitude-ver
I was trying to find clarifying language to indicate if how location where marked.
Item 9 above is a better solution.

Why is v1.1’s roadDirection renamed to event_direction when roadName and roadNum translate pretty directly to road_number and road_name?

Events like, work zones, are mapped in each direction.  So each event would have a single direction.
Road name and number apply to the whole road and not just the event.

I think it would be helpful to have a “migration guide” which indicates the mapping between new fields in this PR to the old common core data. - I agree.


Add flags to usrsock daemons

Summary

Add flags to usrsock daemons
Fix coding style

Impact
usrsock drivers can be process recv() flags.
Testing
Tested by spresense:wifi

LGTM.


"We stopped hearing from agent Hosted Agent..."

Agent Version and Platform
Version of your agent? 2.173.0
OS of the machine running the agent? Windows
Azure DevOps Type and Version
dev.azure.com (formerly visualstudio.com) or on-premises TFS/Azure DevOps Server?
If dev.azure.com, what is your organization name? https://dev.azure.com/arup-dds-aus
What's not working?
Release pipeline fails with this error usually when agent runs over an hour or so doing builds:
"We stopped hearing from agent Hosted Agent. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error"
screenshot:

Agent and Worker's Diagnostic Logs
Logs are located in the agent's _diag folder. The agent logs are prefixed with Agent_ and the worker logs are prefixed with Worker_. All sensitive information should already be masked out, but please double-check before pasting here.
ReleaseLogs_76.zip

For issues with the hosted service, please create a report on Developer Community. You'll want to provide details about the frequency with which you are seeing disconnects and whether it happens consistently on the same builds and jobs.


Support Base64 Encoded Message Payloads

Add decoding for binary messages encode in base64

Closes https://github.com/openwhisk/openwhisk-package-kafka/issues/125

@bjustin-ibm, subclassing the Consumer class is not currently possible. There was a update to the Confluent Kafka library recently to allow subclassing of the Consumer and Producer. However, that change is not in a released version of the library, it is only in master. See: https://github.com/confluentinc/confluent-kafka-python/commit/864a9358a6464a1a8aa50743859fe13e9d85381d

@dubeejw As nice as this test is, I would really like to try it with a message value that we know will cause an exception without this code. I am a little skeptical that this current approach actually solves that issue.
According to @glikson, he found the problem using a gzipped JSON array.

@bjustin-ibm, was an exception the result, or just malformed user input?

Uncaught exception: 'utf8' codec can't decode byte 0x8b in position 1: invalid start byte

IIRC that exception was thrown from poll() but I can't be sure. My gut feeling is that the exception is thrown from inside the Python kafka consumer.

See my comments in the code -- this is not solving the problem I am facing. The format transformation should happen in the opposite direction -- from binary (not utf-8 compliant, so can't be passed in the trigger payload JSON) to base64 (which is utf-8 compliant, and the conversion is lossless), rather than from base64 to utf-8.

I believe the error happens as a result of this line in the consumer:
'value': self.__parseMessageIfNeeded(message.value())
it assumes that the right-hand side is a JSON string (utf-8 compliant), while causes an exception if the message is binary.

@bjustin-ibm, ready for review.

@bjustin-ibm, isBinaryKey and isBinaryValue added.


FPE in sixel_encoder_do_resize, encoder.c:636

Description
There is a floating point exception error in sixel_encoder_do_resize, encoder.c:636 in img2sixel 1.8.6. Remote attackers could leverage this vulnerability to cause a denial-of-service via a crafted JPEG file.
Version
$ img2sixel -V
img2sixel 1.8.6

configured with:
  libcurl: yes
  libpng: yes
  libjpeg: yes
  gdk-pixbuf2: no
  GD: no

Reproduction
# img2sixel -h 128 poc /tmp/foo
ASAN:DEADLYSIGNAL
=================================================================
==363283==ERROR: AddressSanitizer: FPE on unknown address 0x55890ff6ea81 (pc 0x55890ff6ea81 bp 0x7ffc4b1bb790 sp 0x7ffc4b1bb760 T0)
    #0 0x55890ff6ea80 in sixel_encoder_do_resize /root/cov_test/libsixel/src/encoder.c:636
    #1 0x55890ff6fdf0 in sixel_encoder_encode_frame /root/cov_test/libsixel/src/encoder.c:968
    #2 0x55890ff743a9 in load_image_callback /root/cov_test/libsixel/src/encoder.c:1679
    #3 0x55890ffca596 in load_gif /root/cov_test/libsixel/src/fromgif.c:671
    #4 0x55890ffc3f92 in load_with_builtin /root/cov_test/libsixel/src/loader.c:908
    #5 0x55890ffc4936 in sixel_helper_load_image_file /root/cov_test/libsixel/src/loader.c:1418
    #6 0x55890ff7480c in sixel_encoder_encode /root/cov_test/libsixel/src/encoder.c:1743
    #7 0x55890ff6aa0e in main /root/cov_test/libsixel/converters/img2sixel.c:457
    #8 0x7f02f1eebc86 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21c86)
    #9 0x55890ff68359 in _start (/root/cov_test/libsixel/build_asan/bin/img2sixel+0x39359)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: FPE /root/cov_test/libsixel/src/encoder.c:636 in sixel_encoder_do_resize
==363283==ABORTING

poc.zip
Platform
# uname -a
Linux 4a409ce47130 5.4.0-70-generic #78~18.04.1-Ubuntu SMP Sat Mar 20 14:10:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

https://github.com/libsixel/libsixel


Updating payment dependence to ^2.1.0

This new version of payment solves the "WARNING" problem with webpack:
WARNING in ./~/payment/lib/payment.js
Critical dependencies:
1:459-466 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
 @ ./~/payment/lib/payment.js 1:459-466

BTW: Valew João pelo excelente trabalho. Um Abraço!
;)

Hey, looks good, this is an upgrade of 2 majors, just checking that you are using this in a project and did some testing? I'll be doing some testing too and merging this if it looks good. :+1: Obrigado, abraço!

Looks good, published as 0.20 :beers:


Docs request: Single-file lona app example in docs

Is it possible to make a Lona app in a single file?
For trying out the framework, setting up an entire project tree seems excessive.
If it is possible to do in a single file, I really think the docs should include a quick start which does this.

Hi @laundmo,
I am sorry but currently its not possible to run Lona from a single file.
To play around with it without setting up everything your self you can use the project template described in https://lona-web.org/end-user-documentation/getting-started.html. Just clone it and run "make server"

thats unfortunate, i could well imagine using this for microprojects instead of Flask, but those rarely exceed 200 lines and for that its not worth the entire project structure.
well then, im changing the title to feature request.

I thought about your request and actually that`s a great idea! I started working on this this morning.
This is the wrong repository for this kind of feature discussion, could you close this issue and reopen it on github.com/fscherf/lona ?

can you not transfer tge issue, i know thats a option sometimes.
i have to admit, i fully thought i was in the main repo, not this one. sorry.


An error occurred while Style/GuardClause was inspecting rescue statement

Expected behavior
Rubocop should analyze the ruby code without errors unrelated to the code itself.
Actual behavior
Rubocop fails due to GuardClause cop:
» bundle exec rubocop . --debug --config=.rubocop.yml
configuration from /Users/brandontrautmann/Development/mobile/flutter/.rubocop.yml
Default configuration from /Users/brandontrautmann/.rbenv/versions/3.0.3/lib/ruby/gems/3.0.0/gems/rubocop-1.40.0/config/default.yml
...
14 files inspected, no offenses detected

1 error occurred:
An error occurred while Style/GuardClause cop was inspecting /Users/brandontrautmann/Development/mobile/flutter/app/ios/fastlane/Fastfile:124:4.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop/rubocop/issues

Mention the following information in the issue report:
1.40.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.24.0, running on ruby 3.0.3) [arm64-darwin21]
Finished in 16.153554999968037 seconds

Steps to reproduce the problem
The offending code seems to be:
  rescue StandardError => e
    if e.message.include? 'Another build is in review'
      exit(0)
    else
      raise
    end
  end

RuboCop version
1.40.0 (using Parser <IP_ADDRESS>, rubocop-ast 1.24.0, running on ruby 3.0.3) [arm64-darwin21]

This issue has been resolved in the latest RuboCop (1.44.1) . Can you upgrade RuboCop to the latest version?

Yes, that worked! Thanks @koic!


Github Actions And Getting Started Updates

The build was failing because the new docker jobs were referencing a job that was not defined.


rake destroy:all does not free all EC2 resources

Output of running rake destroy:all:
(originally created using the EC2 driver)
$ rake destroy:all
Starting Chef Client, version 12.4.3
[2015-09-30T15:35:06-04:00] WARN: Run List override has been provided.
[2015-09-30T15:35:06-04:00] WARN: Original Run List: []
[2015-09-30T15:35:06-04:00] WARN: Overridden Run List: [recipe[delivery-cluster::destroy_all]]
resolving cookbooks for run list: ["delivery-cluster::destroy_all"]
Synchronizing Cookbooks:
  - delivery-cluster
  - chef-server-12
  - chef-ingredient
  - git
  - apt
  - yum
  - delivery_build
  - chef-splunk
  - packagecloud
  - hostsfile
  - apt-chef
  - yum-chef
  - build-essential
  - dmg
  - windows
  - yum-epel
  - chef-sugar
  - push-jobs
  - chef-vault
  - omnibus
  - chef_handler
  - 7-zip
  - homebrew
  - wix
  - windows-sdk
  - runit
Compiling Cookbooks...
[2015-09-30T15:35:12-04:00] WARN: You are overriding windows_package on {:os=>"windows"} with Chef::Resource::WindowsCookbookPackage: used to be Chef::Resource::WindowsPackage. Use override: true if this is what you intended.
[2015-09-30T15:35:12-04:00] WARN: You declared a new resource Chef::Provider::GitClient::Source for resource git_client, but it comes alphabetically after Chef::Provider::GitClient::Package and has the same filters ({:os=>"linux"}), so it will not be used. Use override: true if you want to use it for git_client.
[2015-09-30T15:35:16-04:00] WARN: You must provision an Analytics Server before be able to
[2015-09-30T15:35:16-04:00] WARN: destroy it. READ => delivery-cluster/setup_analytics.rb
[2015-09-30T15:35:16-04:00] WARN: You must provision an Supermarket Server before be able to
[2015-09-30T15:35:16-04:00] WARN: destroy it. READ => delivery-cluster/setup_supermarket.rb
Converging 7 resources
Recipe: delivery-cluster::_settings
  * link[/Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data] action create (up to date)
Recipe: delivery-cluster::destroy_builders
  * machine_batch[Destroying Build Nodes] action destroy
    - [build-node-test-1] delete node build-node-test-1 at https://<IP_ADDRESS>/organizations/test
    - [build-node-test-1] delete client build-node-test-1 at clients
Recipe: delivery-cluster::destroy_delivery
  * machine[delivery-server-test] action destroy
    - delete node delivery-server-test at https://<IP_ADDRESS>/organizations/test
    - delete client delivery-server-test at clients
  * file[/Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data-test/test.creds] action delete
    - delete file /Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data-test/test.creds
Recipe: delivery-cluster::destroy_chef_server
  * machine[chef-server-test] action destroy
    - delete instance aws_instance[chef-server-test] (i-0ee3f2cb) in VPC vpc-2229ff47 in us-west-2
    - waited 0/300s for i-0ee3f2cb status to terminate...
    - waited 5/300s for i-0ee3f2cb status to terminate...
    - waited 10/300s for i-0ee3f2cb status to terminate...
    - waited 15/300s for i-0ee3f2cb status to terminate...
    - waited 20/300s for i-0ee3f2cb status to terminate...
    - waited until instance aws_instance[chef-server-test] (i-0ee3f2cb) is :terminated
    - delete node chef-server-test at chefzero://localhost:8890
    - delete client chef-server-test at clients
Recipe: delivery-cluster::destroy_cluster_data
  * link[/Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data] action delete
    - delete link at /Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data
  * directory[/Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data-test] action delete
    - delete existing directory /Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data-test
[2015-09-30T15:36:04-04:00] WARN: Skipping final node save because override_runlist was given

Running handlers:
Running handlers complete
Chef Client finished, 6/7 resources updated in 61.075592 seconds

Expected result: all of the EC2 resources should be terminated.
Actual result: only the Chef server was terminated.

Ran rake destroy:all a second time, nothing else was terminated.
$ rake destroy:all
Starting Chef Client, version 12.4.3
[2015-09-30T15:46:08-04:00] WARN: Run List override has been provided.
[2015-09-30T15:46:08-04:00] WARN: Original Run List: []
[2015-09-30T15:46:08-04:00] WARN: Overridden Run List: [recipe[delivery-cluster::destroy_all]]
resolving cookbooks for run list: ["delivery-cluster::destroy_all"]
Synchronizing Cookbooks:
  - delivery-cluster
  - chef-server-12
  - chef-ingredient
  - git
  - apt
  - yum
  - delivery_build
  - chef-splunk
  - packagecloud
  - hostsfile
  - apt-chef
  - yum-chef
  - build-essential
  - dmg
  - windows
  - yum-epel
  - chef-sugar
  - omnibus
  - push-jobs
  - chef-vault
  - chef_handler
  - 7-zip
  - homebrew
  - wix
  - windows-sdk
  - runit
Compiling Cookbooks...
[2015-09-30T15:46:13-04:00] WARN: You are overriding windows_package on {:os=>"windows"} with Chef::Resource::WindowsCookbookPackage: used to be Chef::Resource::WindowsPackage. Use override: true if this is what you intended.
[2015-09-30T15:46:13-04:00] WARN: You declared a new resource Chef::Provider::GitClient::Source for resource git_client, but it comes alphabetically after Chef::Provider::GitClient::Package and has the same filters ({:os=>"linux"}), so it will not be used. Use override: true if you want to use it for git_client.
[2015-09-30T15:46:17-04:00] WARN: You must provision an Analytics Server before be able to
[2015-09-30T15:46:17-04:00] WARN: destroy it. READ => delivery-cluster/setup_analytics.rb
[2015-09-30T15:46:17-04:00] WARN: You must provision an Supermarket Server before be able to
[2015-09-30T15:46:17-04:00] WARN: destroy it. READ => delivery-cluster/setup_supermarket.rb
Converging 6 resources
Recipe: delivery-cluster::_settings
  * link[/Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data] action create
    - create symlink at /Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data to /Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data-test
Recipe: delivery-cluster::destroy_builders
  * log[Skipping Build Nodes deletion because missing delivery.pem key] action write

Recipe: delivery-cluster::destroy_delivery
  * log[Skipping Delivery Server deletion because missing delivery.pem key] action write

Recipe: delivery-cluster::destroy_chef_server
  * machine[chef-server-test] action destroy (up to date)
Recipe: delivery-cluster::destroy_cluster_data
  * link[/Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data] action delete
    - delete link at /Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data
  * directory[/Users/thomaspetchel/Development/chef-cookbooks/delivery-cluster/.chef/../.chef/delivery-cluster-data-test] action delete (up to date)
[2015-09-30T15:46:17-04:00] WARN: Skipping final node save because override_runlist was given

Running handlers:
Running handlers complete
Chef Client finished, 4/6 resources updated in 11.838637 seconds

:awyeah: that is a great feedback! Thank you so much @tpetchel


Update README.md

Missing a a "j" in the maven repository

Coverage remained the same at 83.972% when pulling cf04ca76643c546c5da8eda5b0ec59ec95dd7eba on augcampos:patch-1 into 204f9597bd80512f87cfa02d3febadc03fc70903 on aenniw:master.


Adapt slice count to the width/height/bitdepth of input

Idea:

have some SIMD compatible slice count (e.g. AVX-512 has 16 32-bit blocks, let's take multiples of 16)
each slice has around 256 KiB of data, there is a similar risk of losing 1 LTO block (correction code per block, to be confirmed but looks like a 256 KiB block size is classic)

This leads to:
SD: 16 slices (10-bit) or 32 slices (16-bit)
HD/2K: 64 slices (10-bit) or 128 slices (16-bit)
UHD/4K: 256 slices (10-bit) or 512 slices (16-bit)

Just wondering: have you done some benchmarking? In the past (i.e. two years ago or so), the formula about the relation between slices and cores I published gave us the best results on both our renderfarm and our workstations. I’m asking, because 512 slices seems to me to be a lot.

Or do you program «only» on CPU, without using the GPUs computing power?

I did quick benches (CPU only, I don't have any GPU encoder/decoder), without seeing big difference, but nothing scientific.
I was focused more on not having big loss of data if we lose 1 slice (1 LTO block?), so risk is similar between losing DPX content or FFV1 content with LTO tapes (but... It is also theory, I don't find documentation about what happens when a LTO block is lost, still trying to find doc)
And I have great expectations on an AVX-512 or GPU accelerated encoder/decoder, for that I need lot of slices (of small size else memory usage explodes, and memory on GPU is limited, I need to store both encoded and decoded content, for thousands of slices if I want to fill the GPU with enough content)
Example of file :<PHONE_NUMBER>-bit*4-component= 200 KiB/slice.
If we work with ~256 KiB of content: with a GeForce GTX 1080 Ti, it is ~1 GB of decoded content, 0,5 GB of encoded contend for feeding all CUDA core in 1 shot, multiplied by a couple of instances in order to optimize (memory transfer while computing), we are touching the limits of the card with memory. but theory currently, for sure, at least on my side.
Note that FFmpeg accepts now 1024 slices, I guess that someone else found useful to have so many slices.
I am adding an option for letting the user decides of slice count. there are so many cases that I just put a default value, and user should be able to change.

Changed to:
SD: 16 slices (10-bit) or 24 slices (16-bit)
HD/2K: 64 slices (10-bit) or 96 slices (16-bit)
UHD/4K: 256 slices (10-bit) or 384 slices (16-bit)
Because e.g. 512 slices is a bit high number, and x2 too much increase when going from 10 to 16-bit, and actually FFmpeg does not like 512 (as well as 128...), it requests another count of slices (impossible to set x and y count of slices, so we need to fit in FFmpeg limitations about slice count)


"IN" animation

@dimapaloskin can you please re-submit your PR that adds this feature? I moved the repository and the PR was lost. Thanks!

@caiosba done.

@caiosba also, can you open issue in the js.coach and update repo url?

Thanks!
It's there already: https://js.coach/all/react-native-share-menu


IDokanFileInfo is now the parameter for IDokanOperations(Unsafe)?.

All implementations of IDokanOperations will need to change their final
parameters to accept IDokanFileInfo instead of bare DokanFileInfo.
New class: MockDokanFileInfo This is accepted by implementations of
IDokanOperations and IDokanOperationsUnsafe as their final
parameters.  You can set all of the values of the public
interfaces of IDokanFileInfo (which itself was extracted from the
publicly accessible fields of DokanFileInfo), and specify the
mock behavior of both .TryResetTimeout() and .GetRequestor().
To use this, your unit test mock code needs to behave as though it is
Dokan, calling into your IDokanOperations implementation with
various parameters and testing the expected behaviors and return
values.  Integration tests with Dokan still need to use something
like DokanNet.Tests.

Associated with #183.  Appveyor actually ran on this one, after commit 9f0933a.

Thank you @kyanha for the PR ! very appreciated and I am sure some people will be glad to finally using unittest 👍

Ah I tought I would be able to squash all the commit but looking at the history you also have the commit from https://github.com/dokan-dev/dokan-dotnet/pull/238 Can you recreate the PR with only the IDokanFileInfo changes ?

I put the target moniker changes in #243, so I'll redo this PR without them.

Superseded by #244


Small context independence bugs

There are two issues in the code that is generated right now for a TLM application, e.g.:
let regex =
  /* open Pervasives to ensure context independence */
  Pervasives.(
    /* open $regex's Dependencies, again insuring context indepedence
       (RelitInternalDefn_regex is Relit's internal way of saying $regex) */
    Regex_notation.RelitInternalDefn_regex.Dependencies
      .(
      () => (
        Regex.Or(
          Regex.Str("a"),
          Regex.Star(Regex.Str("b")),
        /* a type assertion that the expansion is the type the notation definition specified */
        ): Regex_notation.RelitInternalDefn_regex.t
      )
    )
  )();

First, the module Regex_notation in the path to the dependencies will be resolved relative to Pervasives, which is incorrect. Second, the expansion type annotation will be resolved relative to the Dependencies, which is also incorrect. Very unlikely to encounter either bug, but we should fix this. I think the correct code that should be generated is:
let regex = {
  module RelitInternalDependencies = Regex_notation.RelitInternalDefn_regex.Dependencies;
  Pervasives.(
      RelitInternalDependencies
      .(
      () => (
        Regex.Or(
          Regex.Str("a"),
          Regex.Star(Regex.Str("b"))
        )
      )
    )
  )() : Regex_notation.RelitInternalDefn_regex.t;
};

Fixed :)

Opening Pervasives after Dependencies doesn't work. Then stuff in Pervasives will shadow dependencies. Need to give a unique name to Dependencies and then do it in the original order.

Whoops true... I think I fixed it with e669937cf0b1581c87422af3ff5b271954120641! Think of any ways that could go wrong?

Won't opening Regex_notation.RelitInternalDefn.regex bring all of the misc stuff in that module into scope, e.g. the Apply exception and the type t.
I think you really do need to do a let module, which is definitely a thing you can do in the OCaml AST. I assume Reason will pretty-print it with a block like in my initial post in the issue?

Yeah it will, but those names can't conflict with anything in pervasives, nor can the expanded code reference any of them, since we typecheck it separately. It's a strange solution, but it's simpler and I'm fairly confident it's correct.

Ah okay. Can you write a test that shows that you can't refer to type t accidentally in the expansion if its not in the dependencies?