Push docker images to Docker Hub from CI

This PR makes the CI system build docker images and push them to dedicated repositories on Docker Hub.
Example Repository
I decided to not push images directly to our existing Docker Hub repos because of security concerns; it is possible for a malicious actor to exfiltrate Docker Hub secrets from our workflows through the use of malicious code. It is therefore safer to use separate dev repos on Docker Hub for development images, as the worst case scenario, if they are compromised, is that we'll just wipe everything and start fresh. Critically no client systems will be compromised (ala supply chain attack).
airnode-examples now pulls from Docker Hub in scenarios where:

commands are executed in a clean repository (no changes to tracked files)
commands are executed for a commit that has a release tag

The CI system will now use the built images for e2e tests, effectively using Docker Hub as a cache (we have unlimited storage on Docker Hub, so this is cool).
To keep things simple I've used the full git commit hash, as anything other than that requires conversion everywhere.

Also, Why do I see all the checks as skipped?

Also, Why do I see all the checks as skipped?

I assume due to cache hit - they normally all get processed.

I agree with having a separate dev Docker repository for these images +1 Is that repository private though? I can't seem to access it.

Thank you :smile
I just checked now and they're all showing from an anonymous browser (when I checked earlier not all of them were visible but they were all pull-able):
https://hub.docker.com/u/api3
The anonymous browser can access them too, some links (I just tested):
https://hub.docker.com/r/api3/airnode-deployer-dev
https://hub.docker.com/r/api3/airnode-artifacts-dev
https://hub.docker.com/r/api3/airnode-admin-dev
https://hub.docker.com/r/api3/airnode-client-dev

What I really don't like is the "running the external commands and parsing the output" part. I would say that git is quite stable and the output will look the same. I wouldn't say the same about Docker though. Aren't there any wrapper libraries that can be used for that instead?

As part of the telemetry collector I used a library for interacting with git which worked well. I thought about doing that here, but going that route would introduce an external dependency, which seemed unnecessary given that we didn't need the full suite of git functions and that we also have access to the git executable. I accept that this is debatable. I don't think this PR is the place to change that though... we can swap this out at a later stage as I have two important tasks that I need to jump on to asap and this PR is already quite big.
I haven't looked into docker integration beyond the executable for JS/TS, but based on previous experience in another language any library would take the form of reading/writing to the docker socket if it didn't use the docker cli executable. Once again, this would also require an external dependency which I am trying to avoid. The docker commands in use currently are very minimal and implemented with no external dependencies. I don't mind if we swap this out, but it can be done at a later stage imo in a separate task/iterate.

But I actually think we don't even need that. Here's what I propose: Instead of using the COMMIT env variable to pass the hash around, we change run-airnode-locally so it can accept an argument, the said hash. When the argument is passed, that's a signal to use the hash as a tag and use the dev repository instead. The same can be done for e2e tests. So, nothing from the utils package will be actually needed, no git commands and no docker commands. But correct me if I'm wrong, maybe I'm missing something. I just think that we don't really need such a generic solution.
:exploding_head:
There are two needs, which probably should have been separate PRs given the above :stuck_out_tongue: :

Build docker images in the CI (which we did anyway)
Push the docker images to Docker Hub
Expose the Docker Hub images to the user in a friendly way (deploy-airnode)
and related, expose the built image to the tests (e2e airnode-examples)

Regarding the last two points:

The CI system always wants to test the current commit.
The Airnode developer probably wants to run a locally built image, not necessarily the committed version.
The API3 Airnode client/data consumer/end-user wants to be able to run airnode-examples, using my approach they'll always have access to a pre-built image, regardless of the commit or tag.
The API3 product tester wants to be able to run images for a specific commit or for the master branch.

So this was the thinking in building a set of decisions around (1) do we have uncommitted work, (2) is an image available for this (clean) commit, (3) is this version of the repo tagged. It's more nuanced than passing a hash around. Maybe the solution is architected inefficiently? Maybe we should require that the user is explicit about what image they want to run?
My goal currently is to have pre-built dev images available on Docker Hub and make it usable for all consumers. I want to do this quickly, but not poorly because Beacons are a priority but also another task. So if we can push this out and then split off tasks that are nuanced or opinionated, that's ideal.

There are (two) needs, which probably should have been separate PRs given the above stuck_out_tongue :
* (1) Build docker images in the CI (which we did anyway)

* (1) Push the docker images to Docker Hub

* (2) Expose the Docker Hub images to the user in a friendly way (`deploy-airnode`)

* (2) and related, expose the built image to the tests (e2e airnode-examples)

Regarding the last two points:
* The CI system always wants to test the current commit.

* The Airnode developer probably wants to run a locally built image, not necessarily the committed version.

* The API3 Airnode client/data consumer/end-user wants to be able to run airnode-examples, using my approach they'll always have access to a pre-built image, regardless of the commit or tag.

* The API3 product tester wants to be able to run images for a specific commit or for the master branch.

So this was the thinking in building a set of decisions around (1) do we have uncommitted work, (2) is an image available for this (clean) commit, (3) is this version of the repo tagged. It's more nuanced than passing a hash around. Maybe the solution is architected inefficiently? Maybe we should require that the user is explicit about what image they want to run?
My goal currently is to have pre-built dev images available on Docker Hub and make it usable for all consumers. I want to do this quickly, but not poorly because Beacons are a priority but also another task. So if we can push this out and then split off tasks that are nuanced or opinionated, that's ideal.

In that case, I propose doing (1) (by doing, I mean merging), as we all agree on that being what we wanted and discuss and come up with a solution for (2). Testers will be still able to pull a specific image while testing the PR. Granted, manually, but still better than building it locally.
I still feel like we don't need most of the code you introduced in the utils package. The default behavior for airnode-examples should be using the non-dev Docker image of the same version as the package. When you want to use a dev image you're either a developer, a tester, a CI, or generally someone who know what they're doing. So in that case, we don't need to check for uncommited work, or whether the image with such a hash is available. If the hash is provided we just try and fail if it doesn't exist.

In that case, I propose doing (1) (by doing, I mean merging), as we all agree on that being what we wanted and discuss and come up with a solution for (2). Testers will be still able to pull a specific image while testing the PR. Granted, manually, but still better than building it locally.

Okay great, that approach sounds logical to me. I'll split this out into another PR with limited changes and create an associated Jira task. Thanks for this @amarthadan :smile:


meta name intellisense

If I type <meta name=" it'd be great if it offered autocomplete options:
"application-name", "author", "description", "format-detection", "generator", "keywords", "publisher", "referrer", "robots", "theme-color", "viewport"

hey @aeschli - thanks for adding this! appreciated.
Is there support for extensions to add additional attributes and elements to HTML intellisense? I'm interested in adding support for https://schema.org (itemscope, itemtype, itemprop) markup.


V5 samplerate changes

Here's some work on fixing the problem of a static 44.1 rate. I think the main issue overall is using the default engine.mainMixerNode and letting the engine create it itself. I'm not sure but that seems to stay at 44.1 in my tests.
This isn't super elegant in terms of the changes to AudioEngine.output, but I believe it works. All of the tests are assuming a sample rate of 44.1k in their md5 hashes, so it's not possible to add a test that changes Settings.audioFormat at this time. I do have the test in there but it's commented out so the rest of the tests don't fail after that one is run.

my xcode indenting is set to tabs not spaces. I'm unclear if this isn't translating

With the changes to connections, does this break our "can't create an invalid graph" invariant? That was a really nice property to have. I think it would be a shame to loose it. What happens when you call detach while it's running? I'm having trouble understanding this PR because it makes various formatting changes (should be a separate PR), and other changes which don't seem to be central to its goal (what do connection changes have to do with sample rate?).


Setup Kanban Board

Hey Code Reviewer! 😄
You can check the Kanban board by clicking on this link
Team members
There are 3 people on our team

@dicodiaz (Team member 1)
@NicolasAndrehh (Team member 2)
@rashedarman (Team member 3)

Hi @NicolasAndrehh, @dicodiaz, @rashedarman,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Highlights
✔  Create Kanban board
✔ All cards have a description
✔ The tasks are divided fairly
Optional suggestions
Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Expose information about development dependencies in Dependabot alerts

Summary
In ecosystems like npm where developers can indicate that a certain dependency is used during development only (a devDependency), developers have asked for a way to understand when Dependabot alerts are related only to a development dependency. In this initial ship, we expect to add support for a label on alerts that concern development dependencies to make it easier to filter, triage, or sort alerts.

This has shipped to dotcom! 🚢 https://github.blog/changelog/2022-06-23-dependabot-alerts-filter-alerts-by-the-scope-of-the-dependency-runtime-and-development/

🚢 This has shipped with the GHES 3.7 release<EMAIL_ADDRESS>


Search code in repository

Gitea version (or commit ref): 1a83581

I have enabled search code in repository. I have few files from gitea like head.tmpl, app.ini, Default for labels etc in it.
If i search for enhancement, i get the following result.
#14dfd9 duplicate
#97df14 enhancement
#dfb014 api

But if i search for #97df14 or 97df14, it does not return anything. Nothing found.
Another example, i search for SECRET_KEY which is in app.ini, it returns nothing found.
Search for localhost return correct file and location which is app.ini.
Same for custom.css, which is in head.tmpl file, nothing found. But if i search for Custom it do return the correct files and code area.
Am i missing something here?

It could be that the indexing isn't fully complete. Have you run these same tests again later on?

Closing. Please re-open if you are still experiencing this.


Tweaked callgraph call for cross-platform temp dir and using PATH var

Repeating after-fork pull, see https://github.com/phacility/xhprof/pull/24
Fixes callgraphs on Windows.

@fabpot if it is good, why not merging it ?


Delayed grid rendering causing errors

In the setup that we have we need a grid container node as a parent of the grid, node which has a ngIf condition on it. This condition becomes true at some point so the parent node gets rendered and implicitly the grid starts rendering. In this setup, we get an error from the grid because it cannot find the function "focus" inside the uiGridCtrl.
The line that triggers the error is line 13446: uiGridCtrl.focus();
This line is executed in the post compile function for the uiGridViewport directive, but the focus function of the uiGridCtrl is defined in the post compile function for the uiGridRenderContainer directive.
Running a debug in both situations (with ngIf and without ngIf on the grid container element) we have found that the order in which these post compile functions of these two directives are executed is reversed when we have an ngIf on the container, therefore the function "focus()" is not found because it has not yet been defined.
I have created a plunkr by doing some minimal changes to the example from the cellNav tutorial page: http://plnkr.co/edit/QnTO3mOrhAkE762lpzXc?p=preview
When you hit the "Toggle ngIf condition" the grid will start to render and you will get the error. If the grid is rendered directly, the error cannot be reproduced because the order of execution for the post compile functions seems to be correct.
Did we do any setup mistakes with our grid instance or is this a bug somewhere?

I'm getting the same error. I'll let you know if I figure out how to resolve it.

@swalters: looking at the code, it looks like we call uiGridCtrl.focus() from the viewPort.  uiGridCtrl.focus is defined by the render container, and in this particular instance that line of code is running after the viewPort directive does.
Have you come across this before - is it expected?

For what it's worth, I noticed this bug after I updated from Angular 1.3.15 to 1.4.1. I also updated several other packages at the same time, including ui-router and angular-formly but those don't seem to be involved. Fortunately it doesn't seem to cause any issues with the app other than the error msg in the console, perhaps b/c I'm using pagination instead of infinite scroll.

The main problem that we have with this is that we are using cellNav, and when we update to the latest version (that contains the problem causing changes) the focus is not set on the first cell anymore.

Just updated to the latest version. Awesome fixes all-around, but this fix is still missing. The regression that this "bug" introduces is major for us; we cannot use cellNav anymore.
Is there anyway we can get around this situation?

I'd guess maybe some timeouts before setting focus to the first cell would give you what you need?  Perhaps wait for data to load, then a timeout, then scollToIfNecsesary?

We do wait for the data to load and do set the focus ourselves, so that is not the problem. The problem is with the line "uiGridCtrl.focus();" from the grid code, which causes an error because the function is not yet defined.
I was forced to comment out that line (I am completely unsure of what problems that may cause) because I needed to get the latest version installed.
Maybe we can add a simple test there if the function exists before executing it?

Experiencing this with angular-1.2.28

I'm also experiencing this with angular-1.3.16, so I think that it's not related to angluar-1.4 compatibility.
This bug has made me downgrade to ui-grid 3-rc21. I do think that this should be fixed before 3.0 is released

@iorzetic you could add if(angular.isFunction(uiGridCtrl.focus)), but then you will not know wheter it runs or not.
Maybe it could be possible to change the priority for the directives in question?
I see that both of these has "priority: -99999, //this needs to run very last"
uiGridViewport <- usese focus()
uiGridRenderContainer <- creates focus()
Or could it be possible to do the focus() in the linking function and not the compile function?

@rangoy Thanks for the suggestion. I know I can manually do that but I would rather not modify 3rd party libraries, that is usually not a wise path to go on.
I think that this change that you mentioned could be directly added into the ui-grid codebase.
By the way, I am able to reproduce this both on AngularJS 1.3.16 and 1.3.4

@iorzetic yes, this should be fixed and a pull request should be made.
@swalters - could you take a look at the change you did in aa56355 and see if you can take some measures to ensure that foucus() is registered before use?

I tried to change the priority, but it did not seem to have the desired effect.
Would this workaround be acceptable? I tested it a bit, and it seems to work. I think it will work reliable as it won't execute until next digest cycle, right?
//Wait for it to be defined
$timeout(function(){uiGridCtrl.focus});

Any progress on this?
Tried 3.0.1, and I see the same issue there.
Seems like the change referenced from #3896  changes the code a bit, and maybe this will solve the issue?

This is probably due to a change made between rc21 and rc22.
I've started getting these errors after updating from rc 20 directly to 3.0.1.
I then downgraded to rc22 and still got those errors.
I then downgraded to rc21 and everything is fine now.


ReferenceError: window is not defined

Describe the bug
$> is
/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1
........
........

ReferenceError: window is not defined
    at 226 (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:59021)
    at i (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:138036)
    at 92 (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:63176)
    at i (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:138036)
    at 295 (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:80366)
    at i (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:138036)
    at 744 (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:116918)
    at i (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:138036)
    at 969 (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:3196)
    at i (/usr/local/lib/node_modules/@microsoft/inshellisense/node_modules/xterm-headless/lib-headless/xterm-headless.js:1:138036)

Node.js v21.4.0

<EMAIL_ADDRESS>/usr/local/lib/node_modules/node-gyp
<EMAIL_ADDRESS>
To Reproduce
Steps to reproduce the behavior:

type is command

Expected behavior
A clear and concise description of what you expected to happen.
Environment

OS: macos 12.3
Output of is --version:
Nodejs Version: 21.4.0
Shell: zsh
Shell Version: zsh 5.8 (x86_64-apple-darwin21.0)

Additional context
Add any other context about the problem here.

app is terminal?iterm2?
It is recommended to add the app information.

app is terminal?iterm2?
It is recommended to add the app information.

I have the same problem, Hyper and Gnome terminals.

app is terminal?iterm2?
It is recommended to add the app information.
I think you can try using node v20.

I found this https://stackoverflow.com/questions/45964178/referenceerror-window-is-not-defined-at-object-anonymous-node-js, so i add const window = globalThis; to js file, got issue
$> is
inshellisense session [live]
__is_update_cwd:1: command not found: __vsc_escape_value

so it only working under vscode?

app is terminal?iterm2?
It is recommended to add the app information.
I think you can try using node v20.

I found this https://stackoverflow.com/questions/45964178/referenceerror-window-is-not-defined-at-object-anonymous-node-js, so i add const window = globalThis; to js file, got issue
$> is
inshellisense session [live]
__is_update_cwd:1: command not found: __vsc_escape_value

so it only working under vscode?

Same issue here.
The exception was thrown inside the dependency xterm-headless
https://github.com/xtermjs/xterm.js/blob/HEAD/src/common/TaskQueue.ts#L145
For some reason the isNode variable was false so that xterm-headless tried to access the browser only global object window which is not available in node.
The isNode is set here
https://github.com/xtermjs/xterm.js/blob/master/src/common/Platform.ts#L17
The code is correct. process is a nodejs only global object so that isNode should be set to true. There must be some other weird issues. I don't want to investigate it in depth.

Lower your node version,node 21+ is not support


[REEF-1017] TestDeserializationForServiceAndContext test fail when running all test together…

When running all the test together in test explore, VS doesn't copy data files to test folder unless DeploymentItem is specified. This PR is to fix it.
JIRA: REEF-1017
This closes #

The tests pass, I'll merge.

@anupam128 had some reservations about using DeploymentItem, as it won't be available in xUnit. Doesn't this patch make the situation worse?

Not really. We still need to figure out how to migrate DeploymentItem annotations to xUnit for tests which are already using it, in O.A.R.Tests\Functional and O.A.R.Tang.Tests. It's better to have more tests which we need to migrate than to have failing tests.


Add warning about XButton1 and 2 on X11.

[X] Has this change been discussed on the forum or in an issue before? Yes at https://en.sfml-dev.org/forums/index.php?topic=28414
[X] Does the code follow the SFML Code Style Guide?

Description
Adds a warning about the two XButtons not being polled on Linux. This closes a task for 2.6.0.

The linked forum post tells that XButton1 and XButton2 are not detected with isButtonPressed but work well with sf::Event. Only the real-time polling is not available, so a warning would maybe better fit in isButtonPressed documentation.

There is no chance I will get around to this before next week.

I've rebased your commit onto 2.6.x and updated the target branch 🙂

@MrZeusTheCoder: are you interested in continuing work on this PR?

No, sorry about this all. Life has been crazy!


Make fluentd forwarded logs more structured by default

Currently when fluentd log forwarding is active, the logs contain only these fields

source (stderr/stdout)
log (the log message)
@log_name or the tag (node.grid.stack.service.container_number)

However, fluentd is best served structured logs, especially when it is combined with ElasticSearch. The current format makes it a bit cumbersome and inaccurate to filter by stack (@log_name:*.mystack.*).
I propose adding node, grid, stack, service and cnt_no as fields in fluentd log forwarding so that we could make concise queries stack:mystack etc. Some of these fields could then be dropped from @log_name, shortening it and reducing it to eg. stack.service or even just kontena (remember syslog inputs are often tagged syslog or system).
This can of course be accomplished with a filter_parser in fluentd, but the logs should be as useful as possible by default.

Btw, this is how I accomplished the transformation in fluentd:
# Expose tag to next filter
<filter **>
  @type record_transformer
  <record>
    interim_tag_field ${tag}
  </record>
</filter>

# Parse tag into node, grid, stack, service and container number
<filter **>
  @type parser
  key_name interim_tag_field
  time_parse false
  format /^(?<node>[a-z0-9-]+)\.(?<grid>[a-z0-9-]+)\.(?<stack>[a-z0-9-]+)\.(?<service>[a-z0-9-]+)\.(?<container_no>[a-z0-9-]+)$/
  ignore_key_not_exist true
  reserve_data true
</filter>

# Drop extra field
<filter **>
  @type record_transformer
  remove_keys interim_tag_field
</filter>

@japsu we have open pr in Kontena Stacks repo for many log storage providers.. and there we parse tag like this:
<filter **>
  @type record_transformer
  <record>
    node "${tag_parts[0]}"
    grid "${tag_parts[1]}"
    stack "${tag_parts[2]}"
    service "${tag_parts[3]}"
    instance "${tag_parts[4]}"
  </record>
</filter>

@jakolehm cool, that looks slightly nicer


"tap" event only on left mouse button

fixes #75

i'd rename the function isLeftMouseButtonPressed to isLeftMouseButton (because technically, it's not pressed anymore on mouseup...) also if you return in _onMouseEvent (which is the right place), you don't need the additional condition in __normalizeMouseEvent.
General Question: Maybe this should be configurable? What if you want to write an application that does work with the right mouse button aswell? (ok, it might be very theoretical, as the handler is mostly for touch events... maybe we should offer first class mouse support via an additional Mouse event handler?


Can't find "themes" directory.

Greetings;
I am trying to install your theme pack, and after having downloaded the directory and rebooting, I've added the code to the configuration.yaml and am trying to reboot - but I keep getting this error message:
`
Logger: homeassistant.components.hassio
Source: components/hassio/init.py:383
Integration: Hass.io (documentation, issues)
First occurred: 12:49:42 PM (2 occurrences)
Last logged: 12:52:24 PM
Component error: themes - Integration 'themes' not found.`
Any idea why???

Nevermind, I got it. The reboot had to happen after adding the frontend code but before adding the input_select to the configuration.yaml file.
It all works now.


added timezone to directive

Added timezone to directive, so now we can pass timezone like when we do in filter

Hi and thanks for your contribution.
Can you remove the dist file from your commit in order to see clearer what changes you've made.


[ComboBox] Negating CSS variables in calc() breaks OptimizeCSSAssetsPlugin

What package is this for?

[x] React
[ ] Angular

Describe the bug
negating a var within calc breaks OptimizeCSSAssetsPlugin (which is used by CRA in production builds) with
Failed to compile.

Parse error on line 1:
-var(--cds-...
-^
Expecting "ADD", "SUB", "LENGTH", "ANGLE", "TIME", "FREQ", "RES", "UNKNOWN_DIMENSION", "EMS", "EXS", "CHS", "REMS", "VHS", "VWS", "VMINS", "VMAXS", "PERCENTAGE", "NUMBER", "dimension", got unexpected "FUNCTION"
CompileError: Begins at CSS selector undefined

Tracking down the error (which was not easy) finds the following line:
https://github.com/carbon-design-system/carbon-addons-iot-react/blob/c0328c3869cd9b2ecafbc13b3c04f63114e8a8db/packages/react/src/components/ComboBox/_combo-box.scss#L32
This is just the first of many in this particular file (and probably the entire project).
This particular line end up being interpolated into bottom: calc(-var(--cds-spacing-08, 2.5rem)) since $ai-apps-combobox-input-height is $spacing-08 and $spacing-08 is var(--cds-spacing-08, 2.5rem).
The best way to handle negating the value is to multiple by -1: https://github.com/css-modules/postcss-icss-values/issues/64#issuecomment-241285628
To Reproduce
Steps to reproduce the behavior:

create a new app with CRA
add ComboBox styles
run the production build
See error

cannot be recreated using codesandbox since it happens during production build
Expected behavior
No error is given and the production build produces the correct code.
Environment/versions:

OS: MacOS
Browser: N/A
carbon-addons-iot-react version: 2.144.0

Additional context
Current workaround, use CRACO remove / disable OptimizeCSSAssetsPlugin (which is not that great...)
Specific timeline issues / requests
N/A

@TheSharpieOne Friendly reminder... can you answer Kevin's question?

Sorry, I was out for a bit.
It seems that this is triggered by importing ~@console/pal/scss/theme first. We are using PAL, and the PAL theme seems to set some stuff up that causes this issue.
I am not sure if we are supposed to be using the PAL theme with this package or not. PAL is setting $spacing-08 which is being used by this package in the place that is breaking.
importing just ~@console/pal/scss/theme works fine. importing just ~carbon-addons-iot-react/scss/<stuff> works fine. Importing both (with pal first since it is setting vars used by carbon-addons-iot-react/scss) causes carbon-addons-iot-react/scss to break.
scss:
@import '~@console/pal/scss/theme';
@import '~carbon-addons-iot-react/scss/globals/vars';
@import "~carbon-addons-iot-react/scss/components/ComboBox/combo-box";

@TheSharpieOne Thank you! Where do you get the @console/pal package? I'm unfamiliar with it, but I do see references to it in other carbon issues.

It's available via IBM's artifactory.
More information:
https://github.ibm.com/console-pipeline/docs/tree/master/migrating-to-artifactory#instructions
https://github.ibm.com/ibmcloud/pal#how-to-install-and-use


Encryption support

It would be great if some kind of encryption support is offered.

Did you see https://github.com/drydart/flutter_sqlcipher ? Maybe we could offer a wrapper around this lib with an encrypted option. It's a possibility but the amount of work to make it possible has to be evaluated to see if it is worth it. I'm currently working on major features for the next release cycle but I keep the idea in mind and will investigate this

I'm fine with that yes. I have no idea on how to implement this feature so feel free to post details about your ideas and I'll help where I can.

It would be great if some kind of encryption support is offered.

Yes, I would also like that.

If we can somehow allow using already instantiated SQLite database instance than this instance can be easily encrypted. Makes sense?

If we can somehow allow using already instantiated SQLite database instance

You can: instantiate like this:
final db =  Db(sqfliteDatabase: myDataBaseObject)

where sqfliteDatabase is an Sqflite's Database object

+1

https://github.com/davidmartos96/sqflite_sqlcipher. this lib support encrypt.


Where should the temporal difference functions be integrated?

This should be added as a separate module in metrics


Move Adler32 and CRC32 to Digest

Adler32 and CRC32 interface are kept unmodified and hence they don't implement Digest::Base, but their results are 32-bit fixes intead of a slice/string; plus they support the combine alternative. I think the current API while simple is enough.
The top-level versions are deprecated.

docs_main.cr should be updated as well

The files are still there. And digest is included with require "./digest/**".
When the deprecated are effectively dropped, yes, the docs_main.cr should be updated.

I agree on moving Adler32 and CRC32 under a combined namespace. But I'm not sure they fit under the Digest namespace. As far as I am familiar with the matter, a (message) digest is usually associated with a cryptographic hash function (such as MD5 or SHA-1 which are currently available in Digest namespace; OpenSSL::Digest has even more).
Adler32 and CRC32 are not cryptographic hash functions but much weaker checksum/CRC.
We could still continue with this and accept there's some mismatch. Digest is not very specific and already established namespace in Crystal's stdlib.
Alternatively, we could consider a more broader term as top level namespace for hash functions. Hash is already taken, though ;)

I've found that many std-libs put CRC32 and Adler32 under Digest and none that uses another namespace ...

golang uses the hash namespace:

https://golang.org/pkg/hash/adler32/
https://golang.org/pkg/hash/crc32/

That said, I'm fine with digest

Some digest algorithms are cryptographically strong but that's hardly a requirement, otherwise both MD5 (broken) and SHA-1 (weak) wouldn't be digest algorithms anymore, which would be nonsense.
Don't use CRC32, Adler32, MD5 or SHA-1 for secure usages like verifying that a file wasn't tampered with. Use SHA-2, SHA-3 or BLAKE. But not all usages need to be secure (e.g. gzip, deflate).
This is similar to random number generators: some are them are cryptographically strong.

Sure we can say hash instead of digest, but the term would be confusing in Crystal (Hash).

I forgot to change the usages of them in the std-lib.
Rebased on master.

i dont notice this change.but  i dont' think is good idea to move A to B and move C to D 's breaking change like this.
thoght I admire your commits..but It's a wasting time i think... what I want is better "C" ..


Support less files

Is it possible add the intégration of "less" files in addition to css custom style path ?
For example, it will be easier to import other common styles files.
In my case, I try to have common styles between the preview of the MD files and the result of the PDF export.
In the same way, adding a specific ID or CLASS after the  would make the distinction (like for class .markdown-preview).

You need to precompile the CSS. I would not see the task in this plugin - sorry. Maybe gulp or a less package for atom is a help?

Good idea, I will search in this way. Thanks.


got animate terrible in my project

When I customize the expression panel, I like to switch between the panel and input. and the Input will flash his height like animate wrong, just like the video.
I hope the animation of input can be smooth.
https://user-images.githubusercontent.com/5283666/165905570-743bdab3-d3cb-4347-aac6-bc3c25d21a1b.mp4

Hi! This behaviour is now included in RN 0.68 and you don't need this library anymore. Refer to https://github.com/facebook/react-native/pull/31402. Thanks!


std.range stuff

This pull request fixes a few issues in std.range:  An unlisted bug in hasLvalueElements and removing a workaround for Bug 2443.

  I accidentally made this pull request by branching from the wrong place, so it includes the stuff at the beginning unintentionally.  What's the easiest way to fix this?

You can always push an entirely new branch to the branch for this pull request. It does risk losing some of the comments that way though, since it's effectively rebasing the branch on github. But the only way to remove the extra commits without rebasing in some manner is to use git-revert to uncommit the extra commits (or do the same manually).


is this suitable for building a collaborating text editor?

Meaning char-level syncing and merging using causal-tree merging strategy for CRDT, is this something supported by orbit? Thanks.

Yes, you could use OrbitDB for this, and in fact I believe some others have! For more information about what you might be able to use OrbitDB for, I'd recommend taking a look at at least the Introduction section of the new OrbitDB Field Manual. Feel free to open any issues there if things are unclear.


Support for Nuxt 3 Auto Import

Guide: https://nuxt.com/docs/guide/directory-structure/components#library-authors

Supported in v0.10.4 🎉.


test(cypress): add initial cypress tests!

What: Just for fun, I wanted to see what it would be like to add some cypress tests for the storybook. Turns out it was pretty easy and I want to do more!

Why: Increase our confidence that downshift works in a real browser

How:

Install cypress, eslint-plugin-cypress, and serve
Add a few scripts
Upgrade some deps (mostly just because I was getting some annoying warnings due to outdated packages)
Configure cypress (and eslint for the cypress folder)
Update the basic example to be more testable
Write tests for the basic example!

Checklist:

[x] Documentation
[x] Tests
[x] Ready to be merged

[ ] Added myself to contributors table N/A

cc @brian-mann :wink: This was a delight!

I added a few reviewers, but don't feel pressured. Also if I didn't add you and you would like to review, please feel free to do so :)

Codecov Report

Merging #341 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #341   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           4      4
  Lines         327    327
  Branches       84     84
=====================================
  Hits          327    327

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 a1bf4dd...7070e7a. Read the comment docs.

It's hard to tell from this gif, but cypress is pretty rad. Here's a recording it created when I ran it locally:

@brian-mann, maybe you could help me understand why I get the initial load -> refresh -> run tests experience... I seem to get this in every project I use cypress.

Thanks!

@kentcdodds Adding a baseUrl to your cypress.json should fix the 'flashing' of initial load -> refresh -> run tests. Cypress essentially does not know before opening where you are planning to visit (unless specified in cypress.json), so it initially opens on localhost + a random port, then switches to your localhost + port you specified in your visit.

Thanks @jennifer-shehane! I think you've told me that before actually. I still don't understand why that happens...

Cypress essentially does not know before opening where you are planning to visit (unless specified in cypress.json)

That makes sense

so it initially opens on localhost + a random port

This doesn't make sense to me. Could you help me understand why cypress opens to any port at all? Why doesn't it just wait until my cy.visit call before sending the browser anywhere? Also, it seems like the entire cypress app is refreshed, not just the browser. I think I'm missing something here 🤔

@kentcdodds So, this isn't evident in the video, but the url I'm talking about is the main Cypress browser url.
With baseUrl set -> loads main window in localhost set in baseUrl

Without baseUrl set -> loads main window in localhost + random port

Cypress internally switches to the domain that you use in your cy.visit() so that your application’s code will run under the current domain at all times.
We had a lot of CORS related issues before when we did not set the main window to the same url as the application under test.  Previously we implemented an endless amount of hacks and internal translations to figure out the domain you were supposed to be on without actually being on the domain. This caused code to behave different and caused subtle issues.
The entire proxy layer was written to handle https certificates, continue to inject (even on https pages), and know when to automatically bypass injection so you can open other tabs while testing in Cypress. This also allows us to unlock the ability to do things like whitelisting or blacklisting specific 3rd party domains, or even be able to stub not just XHR’s but any kind of HTTP request.
TLDR: iframes are complicated.

This makes total sense. Thank you for taking the time to explain! I'm sure it's somewhere, but somehow I missed this in the docs. If it's not there, then it would be a good idea to mention that 99% of the time people will want to set the baseUrl configuration option (whether that's via cypress.json or otherwise).
Thanks again!


Add coverage of static methods

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 61.14%. Comparing base (400a9da) to head (f81d25d).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage   61.14%   61.14%
=======================================
  Files          34       34
  Lines        4501     4501
=======================================
  Hits         2752     2752
  Misses       1749     1749

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Publish notebooks in hosted documentation

I'm aware that there is a way to automatically run and publish jupyter notebooks in Sphinx documentation. I think it's a plugin for Sphinx that makes this possible.
It would be a nice addition to the documentation to have the existing notebooks there, and further, would reduce friction when writing tutorial documentation, since the tutorial can be created and tested as a notebook, and then published in one step instead of copy-pasting code.

I use https://github.com/jupyter/jupyter-sphinx/ in many of my projects. You write in RestructuredText as usual but use the .. jupyter-execute:: directive instead of the standard code ones. This is my current project that uses it: https://moorepants.github.io/learn-multibody-dynamics/ if you'd like to see an example output.

Maybe install pandoc?

Good lord, what a tricky issue. Writing this down just to memorialize this process.
So, I wanted to host the notebooks and outputs in the documentation. But, I didn't want to rewrite the notebooks to be embedded in the sphinx documentation (which, @moorepants, turned out to be the most sensible thing).
Well, alright, there's plugins to convert them to rst -- then, they can get converted into html and github will host them. To do this, there's a thing called nbsphinx. nbsphinx works fine, if the notebooks are under the same root folder as the documentation. But, this isn't so. Our problem is that we have docs in pendsim/docs/ and notebooks in pendsim/notebooks. They're not in the same folder.
So, we actually can use a thing called nbsphinx-link to basically place a "link" to the notebooks in docs, so that nbsphinx thinks they're in there when the documentation is built.
That was yesterday.
Then, of course, this introduces a bunch of dependencies into the sphinx pipeline: you have to actually (?) run the notebooks when generating the documentation, or at least parse them. And then, you need to convert the markdown and output cells in the notebooks to rst. This was the origin of the missing pandoc dependency above. Another interesting thing that happens: when the notebooks are executed from the repo/notebooks folder, they're one level up from the repo; so if you want to import pendsim from the repo, you need to move one level up in the first cell of the notebook. BUT: if actually nbsphinx is running the notebooks, and they're in a different directory that's two levels up, you have a problem, because the interpreter is actually looking for pendsim in repo/docs. Now, you can jump to two levels up in the notebooks to fix this issue, but that will break them if you run them from the directory they're supposed to be running from, notebooks. Ask me how I know. The structure that works looks like this:
repo/
├─ notebooks/
│  ├─ experiment1.ipynb
├─ docs/
│  ├─ experiment1.nblink

Then, if you tell the interpreter to go one level up in experiment1.ipynb, that'll work whether you're in notebooks/ or docs/.
The fix is to uh... don't try to do it like this. Turned out to be a github actions learning experience for me, and one of those things where you waste 4.5 hours to save 45 minutes.
(?) or maybe just parse outputs? I'm still not sure.


json.Unmarshal:different with standard library

code
https://play.golang.org/p/LgYg4PUZNHs
package main

import (
	"encoding/json"
	"fmt"
	"github.com/json-iterator/go"
)

var jsonit = jsoniter.ConfigCompatibleWithStandardLibrary

func main() {
	str := `{"a":1,"b":2,"c":[3],"d":4}`
	mp := make(map[string]int)
	var err error

	fmt.Println("====== test for json-iterator ======")
	err = jsonit.Unmarshal([]byte(str), &mp)
	fmt.Println(err)
	fmt.Println(mp)

	fmt.Println("====== test for standard json ======")
	err = json.Unmarshal([]byte(str), &mp)
	fmt.Println(err)
	fmt.Println(mp)
}

output
====== test for json-iterator ======
readUint32: unexpected character: �, error found in #10 byte of ...|b":2,"c":[3],"d":4}|..., bigger context ...|{"a":1,"b":2,"c":[3],"d":4}|...
map[a:1 b:2 c:0]
====== test for standard json ======
json: cannot unmarshal array into Go value of type int
map[a:1 b:2 c:0 d:4]

as you can see:
json-iterator: map[a:1 b:2 c:0]
standard: map[a:1 b:2 c:0 d:4]

the result of json-iterator library miss the elements behind the key 'c'!

I think that's because json-iterator stop parsing when it meets an error while encoding/json just record the error and keep parsing the rest json string. Maybe json-iterator should provide an option to control if the parse should keep going when it meets errors.


cargo update can deal with some bad lockfiles

This is a continuation of @dwijnand work in #5809, and closes #5684
This adds a ignore_errors arg to reading a lock file which ignores sections it doesn't understand. Specifically things that depend on versions that don't exist in the lock file. Then all users pass false except for the two that relate to update command.
I think the open questions for this pr relate to testing.

Now that we are passing false in all other commands, do they each need a test for a bad lockfile?
Do we need a test with a more subtly corrupted lock file, or is this always sufficient for update to clean up?

Good thought! House that look?

Thanks! I think actually we may want to unconditionally ignore errors for these sorts of lockfiles. Cargo 99% of the time is about to regenerate a lockfile anyway, so the purpose of the previous lockfile is basically just there to influence the next build as much as possible. If it ends up being corrupt in some subtle ways then it should be fine to always discard as we'd be about to make a new one anyway

I'd like to be careful about updating dependencies without telling the user. Hence update will, but it was going to change the deps anyway, but build won't. If you think I am being too careful, then we can remove the error branch entirely.

Good thought! House that look?

So great.

@Eh2406 oh cargo build will actually update dependencies if you change Cargo.toml (silently currently). That's perhaps a bug and we should fix it, but I do agree that in general we probably shouldn't update much without telling the user!

So the error message is removed. I thinking this may lead to odd behavior. Take the motivating example link, If a atomatick merge makes a bad lockfile then CI will pass, by making a new file, but the next PR will see an unexpland change to the lock file.

I haven't heard that before, and the crate that reported the problem isn't using that. We should make sure that CI best practice makes it into some kind of documentation. cc #5656. But that seems like a reasonable solution.

For sure yeah we'd definitely want to mention this in our CI best practices documentation!
Are you ok landing this if we do that?

Yes.
I wonder if the transition period (between it lads and when we write best practices) will be painful. But I don't know. I will add it to the OP, and update the title.

@bors: r+
Ok! We can of course always revert if this causes problems!

:pushpin: Commit a418364ddab8583e3f7c95d17ea6f194cdaef97d has been approved by alexcrichton

:hourglass: Testing commit a418364ddab8583e3f7c95d17ea6f194cdaef97d with merge 63a08ee7d5f5bb06ebbafcfb921989ac06969f97...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 63a08ee7d5f5bb06ebbafcfb921989ac06969f97 to master...


Review conda path location

Currently, the conda path during training is implemented as ENV PATH=${PROJECT_ROOT}:${PATH}:/opt/conda/bin, which places the conda binaries at the end. I am not certain if this is as good an idea as I initially believed.

Reverted to having conda in the front during train as it makes no difference.


feature/SKOOP-129

SKOOP-129, SKOOP-130, SKOOP-135, SKOOP-136
API to create / update / delete and serve user publications.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@4803d6b). Click here to learn what that means.
The diff coverage is 88.88%.

@@            Coverage Diff            @@
##             master      #75   +/-   ##
=========================================
  Coverage          ?   78.12%
  Complexity        ?      540
=========================================
  Files             ?      145
  Lines             ?     2423
  Branches          ?       81
=========================================
  Hits              ?     1893
  Misses            ?      474
  Partials          ?       56

Impacted Files
Coverage Δ
Complexity Δ

...timonial/command/TestimonialCommandController.java
81.48% <ø> (ø)
5 <0> (?)

...in/java/com/tsmms/skoop/exception/enums/Model.java
100% <100%> (ø)
3 <0> (?)

...oop/publication/query/PublicationQueryService.java
100% <100%> (ø)
3 <3> (?)

...m/tsmms/skoop/publication/PublicationResponse.java
100% <100%> (ø)
1 <1> (?)

.../publication/query/PublicationQueryController.java
100% <100%> (ø)
2 <2> (?)

...lication/command/PublicationCommandController.java
83.87% <83.87%> (ø)
5 <5> (?)

...publication/command/PublicationCommandService.java
86.48% <86.48%> (ø)
8 <8> (?)

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 4803d6b...dbd3200. Read the comment docs.


Add Missing config enableOutOfMemoryTracking for iOS/Mac

Add an option filter to avoid registering out of error events if the user doesn't want it.
Partially solves #127

This option is missing in Capacitor docs (available in React Native docs)

Thanks for pointing about the Documentation.
You can track the changes here: https://github.com/getsentry/sentry-docs/pull/5118


Detect pedestrians

How do I detect multiple pedestrians?

This package isn't really intended for tracking pedestrians, however, it could probably be adapted to do so with some more advanced image processing. You are more then welcome to fork the repo and see what you can do!


Terminate fails

My coworker created a test cluster and the terminate is failing, when I check the google cloud console there are no VM's running but Cloudbreak UI seems to think its running and the terminate fails.

fixed


Improve user interface

Improve the frontend of the application

@hsalway1 can you take a look at my updated UI and see if it looks good?

The UI looks fire!!!!

Thanks! Closing this issue with satisfaction...


Update instructions for Ubuntu LTS 22.04

This page needs updating for Ubuntu LTS 22.04. Specifically, steps three and four in Manual Steps, which describes changes that should be made to an Ubuntu image's package libraries.
Ubuntu 22.04 LTS is officially available in the Azure VM image Marketplace, so this page should offer instructions on creating a custom image for 22.04

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

ID: 4138584e-7488-4750-84b8-9e00bc3cf975
Version Independent ID: d750001e-90ab-e1ec-ab35-8ef9a4b556a9
Content: Create and upload an Ubuntu Linux VHD in Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/create-upload-ubuntu.md
Service: virtual-machines
GitHub Login: @srijang
Microsoft Alias: srijangupta

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

@danielsollondon
Can you please check and add your comments on this doc update request as applicable.

@yobyot
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

@AjayBathini-MSFT Can you please reassign this to @srijang?

@AjayBathini-MSFT , I am not the ms.author.  Please assign to @srijang.  Thank you.

[like]  Cynthia Nottingham reacted to your message:

From: Delora Bradish @.>
Sent: Monday, September 25, 2023 8:56:21 PM
To: MicrosoftDocs/azure-docs @.>
Cc: Cynthia Nottingham @.>; Comment @.>
Subject: Re: [MicrosoftDocs/azure-docs] Update instructions for Ubuntu LTS 22.04 (Issue #114940)
@AjayBathini-MSFThttps://github.com/AjayBathini-MSFT , I am not the ms.author. Please assign to @srijanghttps://github.com/srijang. Thank you.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/114940#issuecomment-1734450798, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACCWJRBQAO23QONIBDNCZT3X4HVXLANCNFSM6AAAAAA47A27AU.
You are receiving this because you commented.Message ID: @.***>

Hello @yobyot ,
thank you for your feedback, I updated the document last week, and the intent is to provide a guide how to bring a machine from on-prem to Azure, if your interest is a guide how to create a custom image from a Marketplace offer it something we can definitely address in a different document.

This is already taken care. Closing this issue; should there be anything else that you need help with the documentation, please go ahead and open a new issue so that its easier to track afresh.
#please-close


Service specific update for /v1/end-subscription

Apart from generic changes, there are few updates made in /v1/end-subscription which are specific to this request

[x] Check for support to ApplicationLayerTopology for Continuous Integration
[x] Acceptance :: Gate :: Add check for ApplicationLayerTopology application
[ ] Acceptance :: Add FC-port deleted? testcase for LinkChangeNotification
[ ] Acceptance :: Add Delete FC-port notified? testcase to LinkChangeNotification

Delete FC-port notified? has been removed for ApplicationLayerTopology as topology change notification to self has been disabled in ALT to ALT itself


Rails 5.2 Support

Fixes #1496
Supporting Rails 5.2 required two small changes.
The less significant is working around ActiveModel's (totally reasonable, IMO) change to make the output of changed_attributes immutable. Very straightforward. Would like better names for these methods.
The more significant is the workaround for the error causing all of the recent CI failures. The way I did it was to define our own mutations_from_database. I know that we're testing aspects of ActiveModel::Dirty but I'm still concerned we might be missing out on expected behavior. I didn't have internet while working on this so I couldn't really dig into it. For that reason, I'd like some careful eyes on this before it's merged in.

@cheerfulstoic
Is there any new JRuby-specific code that I might have overlooked? All of the failures were there.

Uggg, jRuby.  Yeah, maybe, I'm not sure.
I've been testing it on ActiveModel 5.1 and it does seem to have an issue. I just made a commit to add a Travis build to test that.  I've also changed your changed_attributes_clear! and used clear_changes_information because that is (if I understand correctly) the official method from ActiveModel to reset changes.

Actually, it seems like the errors aren't in jRuby but with MRV 2.1.10...

Ok, well my change to clear_changes_information broke something.  Though I think it highlights the fact that as a gem which works on top of ActiveModel that we should be using the Attributes API.  The error is undefined method forgetting_assignment' for ["prop_with_default", "something"]:Array` and it comes from here:
https://github.com/rails/rails/blob/master/activemodel/lib/active_model/dirty.rb#L270
I think our @attributes is supposed to be a set of Attribute objects from ActiveModel.
Maybe your original fix is the thing to do for getting 5.2.0 compatibility ASAP, but I think there's a systemic, longer-term fix here.  Does that seem right to you?

Yeah, I think that’s why I did it the way I did. Really annoying. You are
100% correct: we’d do well to sync our concept of attributes with
ActiveModel’s, since that disconnect is the underlying issue. My first
impulse when working on this was to do just that but it’s very clearly a
bigger project that needs some consideration, as it will have far-reaching
consequences.
On Tue, Apr 17, 2018 at 10:12 PM Brian Underwood<EMAIL_ADDRESS>wrote:

Ok, well my change to clear_changes_information broke something. Though I
think it highlights the fact that as a gem which works on top of
ActiveModel that we should be using the Attributes API. The error is undefined
methodforgetting_assignment' for ["prop_with_default",
"something"]:Array` and it comes from here:
https://github.com/rails/rails/blob/master/activemodel/lib/active_model/dirty.rb#L270
I think our @attributes is supposed to be a set of Attribute objects from
ActiveModel.
Maybe your original fix is the thing to do for getting 5.2.0 compatibility
ASAP, but I think there's a systemic, longer-term fix here. Does that seem
right to you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neo4jrb/neo4j/pull/1499#issuecomment-382224140, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AD6E9_XymKfYHtB-xIc_IJsBg_L8yAPTks5tpqD7gaJpZM4TXfLc
.

Cool, glad we're on the same page.    I think I might work on a larger refactor to standardize on ActiveModel and at the same time make the id_property just a plain ActiveModel attribute.  It would probably remove a lot of code from the gem and it may even make things more efficient (one can hope... ;) ).  I think that would make a nice 10.0 change

I just changed the travis.yml to test Ruby 2.2.10 instead of 2.1.10.  Rails 5.0 requires at least 2.2.2, so probably ActiveModel 5.0 also requires it, but maybe other parts of Rails were using more modern versions of Ruby while ActiveModel didn't actually change anything requiring newer versions of Ruby until 5.2.  That's all just a theory, but it probably is not a big deal to require 2.2.2 as well.  Theoretically this might open the gem up to errors when people are using Ruby 2.1 with versions of Rails before 5.0, but I think that's a risk that we'd need to take given the part-time support of the gem ;)

I put in a conditional statement on if changed_attributes is frozen? which allows for support for versions before 5.2.  Everything's passed on CI, so I'm going to merge and release.  Thanks!

Released as 9.2.2, thanks again!


Use 4.x signal style

I don't know much about the audio stream player pooling but it seems my changes didn't break it

Thanks, I've merged these by hand and will be up soon!


Object not stable without surface detection

I am Placing 3D object in 0,0,-1 position as soon as launch ARScreen. It placed object stable but sometimes it moves around the room. We are placing the object in a static point based on device origin point. Then why it moves. Also I didn’t shake mobile, so there is no chance this issue occurs because of motion. Also no white background or similar patterns.Also I didn’t update Anchor on every update, just added one time only. Also I am using a Pixel 2 so there is no device capability issue.
Is it Anchor not stable without surface detection? Is it any workaround to fix this issue?
Is it stable only use Unity instead of Sceneform? Is it any fix we can expect from ARCore team?
I am trying to place 3D object stable for long time.But not able to anchor in stable place.Any technical limitations are not accepted by client as it is works good on ARKit.
Please provide you suggestions, best practices to place object stable without surface detection.

This is question better suited for the ARCore team: https://github.com/google-ar/arcore-android-sdk/issues
Sceneform leverages ARCore services, but is itself a 3D framework.

Closing due to inactivity.


Updated users are not updated in dojo's users list

I had a parent user[1] which created child accounts[2][3] using her name instead of using her children names.
She joined the dojo[4] and then she updated her children accounts with correct names.
Looking at account pages[2][3] they seems ok now but in the dojo's member list[5] the parent name is still reported instead of the children names.
dojo's members list should refresh with updated data.
[1] https://zen.coderdojo.com/profile/5c24dc33-aeea-4149-9b0d-79ad9b17db4b
[2] https://zen.coderdojo.com/profile/6e4e2552-8f0b-4e23-9691-b1b0d4390a89
[3] https://zen.coderdojo.com/profile/20629ae7-1048-41e1-9c24-d90de9fd81cd
[4] https://zen.coderdojo.com/dojo/b5eabc06-d7ea-42f4-ab98-e4f489765396
[5] https://zen.coderdojo.com/dashboard/my-dojos/b5eabc06-d7ea-42f4-ab98-e4f489765396/users

Hi Sandro,
You are right, it seems there is an issue when updating a profile name (cd_profiles), it's not reflected on the administrative user structure (sys_user).
We'll look into it asap
Thanks :+1:

Once this will be released, please simply save again the profiles to update the underlying info

@Wardormeur I would suggest to run a script as admin and do a mass save on all existing profiles.
It would be quicker than asking all registered users to re-save their own profile :-)

I'll check db-wise if the inconsistency is the story of 10 or 1000 users.
Resyncing the profile of 30k users won't go easy on our architecture...

I'm working on a backport script, shouldn't take long

The backfill has been replayed, this shouldn't be an issue anymore.
Thanks @sandrobonazzola :)

Thanks, looks ok to me now.


Go 1.9 RC-1 and dep 2e56bed87c736349a6e97da8bd2525affad1897b on Windows 10 64-bit (latest updates)
What dep command did you run?
go get -u github.com/golang/dep/cmd/dep
What did you expect to see?
Dep should install correctly
What did you see instead?
$ go get -u github.com/golang/dep/cmd/dep
# github.com/golang/dep/cmd/dep
D:\Work\go\src\github.com\golang\dep\cmd\dep\ensure.go:212:2: undefined: err
D:\Work\go\src\github.com\golang\dep\cmd\dep\ensure.go:213:5: undefined: err
D:\Work\go\src\github.com\golang\dep\cmd\dep\ensure.go:214:24: undefined: err
D:\Work\go\src\github.com\golang\dep\cmd\dep\ensure.go:221:22: undefined: err

Build is broken: https://travis-ci.org/golang/dep/builds/261230079

yeah, just fixed it - it was two unrelated merges that interacted poorly with each other. thanks!


SSL Support

Hi,
I'm using SSL support with letsencrypt for my mail server with your container and I've got an error with SSL.
When trying connect to secured communication I encounter an SSL handshake failure on SMPTS ports (465, 587).
openssl s_client -connect mail.domain.net:587
CONNECTED(00000003)
4294956672:error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown protocol:s23_clnt.c:794:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 7 bytes and written 306 bytes
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : 0000
    Session-ID:
    Session-ID-ctx:
    Master-Key:
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---

But this works fine with IMAPS port (993).
openssl s_client -connect mail.domain.net:993
CONNECTED(00000003)
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = mail.domain.net
verify return:1
---
Certificate chain
 0 s:/CN=mail.domain.net
   i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
   i:/O=Digital Signature Trust Co./CN=DST Root CA X3
---

*** OMMITTED FOR BREVITY***

* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot (Ubuntu) ready.
read:errno=0

Here is an extract of my container configuration:
volumes:
  maildata:
    driver: local
services:
  server:
    image: tvial/docker-mailserver:latest
    hostname: mail
    environment:
      DISABLE_AMAVIS: '1'
      DISABLE_CLAMAV: '1'
      ENABLE_FAIL2BAN: '1'
      ENABLE_FETCHMAIL: '0'
      ENABLE_LDAP: '1'
      ENABLE_MANAGESIEVE: '1'
      ENABLE_POP3: '1'
      ENABLE_SASLAUTHD: '1'
      LDAP_BIND_DN: cn=admin,dc=domain,dc=net
      LDAP_BIND_PW: XXXX
      LDAP_SEARCH_BASE: dc=domain,dc=net
      LDAP_SERVER_HOST: ldap
      ONE_DIR: '1'
      PERMIT_DOCKER: network
      POSTMASTER_ADDRESS<EMAIL_ADDRESS>      SASLAUTHD_LDAP_BIND_DN: cn=admin,dc=domain,dc=net
      SASLAUTHD_LDAP_FILTER: (&(|(uid=%u)(mail=%u))(objectClass=CourierMailAccount))
      SASLAUTHD_LDAP_PASSWORD: XXXXXX
      SASLAUTHD_LDAP_SEARCH_BASE: dc=domain,dc=net
      SASLAUTHD_LDAP_SERVER: ldap
      SASLAUTHD_MECHANISMS: ldap
      SA_KILL: '6.31'
      SA_TAG: '2.0'
      SA_TAG2: '6.31'
      SSL_TYPE: letsencrypt
      VIRUSMAILS_DELETE_DELAY: '30'
    external_links:
    - Authentication/slapd-server:ldap
    volumes:
    - maildata:/var/mail
    - /etc/letsencrypt:/etc/letsencrypt

Regards,

Can I see the startup log?  (you should edit and reformat your issue for more readability)

Yes sure,
This is my startup logs :
21/12/2016 13:26:31Registering check,setup,fix,misc and start-daemons functions
21/12/2016 13:26:31  * _check_environment_variables() registered
21/12/2016 13:26:31  * _check_hostname() registered
21/12/2016 13:26:31  * _setup_default_vars() registered
21/12/2016 13:26:31  * _setup_dovecot() registered
21/12/2016 13:26:31  * _setup_dovecot_local_user() registered
21/12/2016 13:26:31  * _setup_ldap() registered
21/12/2016 13:26:31  * _setup_saslauthd() registered
21/12/2016 13:26:31  * _setup_dkim() registered
21/12/2016 13:26:31  * _setup_ssl() registered
21/12/2016 13:26:31  * _setup_docker_permit() registered
21/12/2016 13:26:31  * _setup_mailname() registered
21/12/2016 13:26:31  * _setup_postfix_override_configuration() registered
21/12/2016 13:26:31  * _setup_postfix_sasl_password() registered
21/12/2016 13:26:31  * _setup_security_stack() registered
21/12/2016 13:26:31  * _setup_postfix_aliases() registered
21/12/2016 13:26:31  * _setup_postfix_vhost() registered
21/12/2016 13:26:31  * _setup_postfix_relay_amazon_ses() registered
21/12/2016 13:26:31  * _fix_var_mail_permissions() registered
21/12/2016 13:26:31  * _misc_save_states() registered
21/12/2016 13:26:31  * _start_daemons_sys() registered
21/12/2016 13:26:31  * _start_daemons_dovecot() registered
21/12/2016 13:26:31  * _start_daemons_opendkim() registered
21/12/2016 13:26:31  * _start_daemons_opendmarc() registered
21/12/2016 13:26:31  * _start_daemons_postfix() registered
21/12/2016 13:26:31  * _start_daemons_saslauthd() registered
21/12/2016 13:26:31  * _start_daemons_fail2ban() registered
21/12/2016 13:26:31Checking configuration sanity:
21/12/2016 13:26:31 >>>> Check that there are no conflicts with env variables [_check_environment_variables]
21/12/2016 13:26:31 >>>> Check that hostname/domainname is provided (no default docker hostname) [_check_hostname]
21/12/2016 13:26:31mail.ntic-infos.net
21/12/2016 13:26:31  * Hostname has been set
21/12/2016 13:26:31Setting up the Container:
21/12/2016 13:26:31 >>>> Setting up default variables [_setup_default_vars]
21/12/2016 13:26:31  * VIRUSMAILS_DELETE_DELAY=30 set
21/12/2016 13:26:31 >>>> Setting up Dovecot
21/12/2016 13:26:31Sieve management enabled
21/12/2016 13:26:31 >>>> Setting up Dovecot Local User
21/12/2016 13:26:31==> Warning: 'config/docker-mailserver/postfix-accounts.cf' is not provided. No mail account created.
21/12/2016 13:26:31 >>>> Setting up Ldap
21/12/2016 13:26:31sed: cannot rename /etc/postfix/sed6RUu3A: Device or resource busy
21/12/2016 13:26:31Configuring dovecot LDAP authentification
21/12/2016 13:26:31sed: cannot rename /etc/dovecot/sedlhyEOD: Device or resource busy
21/12/2016 13:26:31Enabling dovecot LDAP authentification
21/12/2016 13:26:31Configuring LDAP
21/12/2016 13:26:31 >>>> Setting up Saslauthd
21/12/2016 13:26:31Configuring Cyrus SASL
21/12/2016 13:26:31Adding user postfix to group sasl
21/12/2016 13:26:32 >>>> Setting up DKIM
21/12/2016 13:26:32No DKIM key provided. Check the documentation to find how to get your keys.
21/12/2016 13:26:32 >>>> Setting up SSL
21/12/2016 13:26:32Adding mail.ntic-infos.net SSL certificate
21/12/2016 13:26:32SSL configured with 'letsencrypt' certificates
21/12/2016 13:26:32 >>>> Setting up PERMIT_DOCKER Option
21/12/2016 13:26:32Adding docker network in my networks
21/12/2016 13:26:34bash: /etc/opendkim/TrustedHosts: No such file or directory
21/12/2016 13:26:34 >>>> Setting up Mailname
21/12/2016 13:26:34Creating /etc/mailname
21/12/2016 13:26:34 >>>> Setting up Postfix Override configuration
21/12/2016 13:26:34No extra postfix settings loaded because optional '/tmp/docker-mailserver/postfix-main.cf' not provided.
21/12/2016 13:26:34 >>>> Setting up Postfix SASL Password
21/12/2016 13:26:34==> Warning: 'SASL_PASSWD' is not provided. /etc/postfix/sasl_passwd not created.
21/12/2016 13:26:34 >>>> Setting up Security Stack
21/12/2016 13:26:34Configuring Spamassassin
21/12/2016 13:26:34Fail2ban enabled
21/12/2016 13:26:34 >>>> Setting up Postfix Aliases
21/12/2016 13:26:34==> Warning: 'config/postfix-virtual.cf' is not provided.

Are you trying from OSX?

No, i'm trying from Windows 10 on Cmder.

De : Thomas VIAL<EMAIL_ADDRESS>Envoyé : mercredi 21 décembre 2016 13:42:46
À : tomav/docker-mailserver
Cc : Kevin BEAUGRAND; Author
Objet : Re: [tomav/docker-mailserver] SSL Support (#417)
Are you trying from OSX?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/tomav/docker-mailserver/issues/417#issuecomment-268514193, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJEqox0I2bRTlLT_jlqRm2v8gHZPYx-tks5rKR7GgaJpZM4LS5Af.

Ok, I'll have a look. There might be an issue.

Just tried on your mail server and seems to work. Did you recently changed something?

I didn't changed anything. And for me it's still note working.
I know that you're french (I'm too), we can speak with IM if you want more reactivity...

De : Thomas VIAL<EMAIL_ADDRESS>Envoyé : mercredi 21 décembre 2016 17:03:30
À : tomav/docker-mailserver
Cc : Kevin BEAUGRAND; Author
Objet : Re: [tomav/docker-mailserver] SSL Support (#417)
Just tried on your mail server and seems to work. Did you recently changed something?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/tomav/docker-mailserver/issues/417#issuecomment-268560216, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AJEqo-zU1FPyquWwDaXZtUblYq7HHBCUks5rKU3SgaJpZM4LS5Af.

Try docker exec mail openssl s_client -connect mail.ntic-infos.net:587 -starttls smtp -CApath /etc/ssl/certs and paste the result here.

Hi, it seems taht everything is ok :
depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3
verify return:1
depth=0 CN = mail.ntic-infos.net
verify return:1
CONNECTED(00000003)
---
Certificate chain
 0 s:/CN=mail.ntic-infos.net
   i:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
 1 s:/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
   i:/O=Digital Signature Trust Co./CN=DST Root CA X3
---
Server certificate
-----BEGIN CERTIFICATE-----
MIIFCjCCA/KgAwIBAgISA51jfqOhNG8ap03V5mofBhXkMA0GCSqGSIb3DQEBCwUA
MEoxCzAJBgNVBAYTAlVTMRYwFAYDVQQKEw1MZXQncyBFbmNyeXB0MSMwIQYDVQQD
ExpMZXQncyBFbmNyeXB0IEF1dGhvcml0eSBYMzAeFw0xNjEyMTcxOTA0MDBaFw0x
NzAzMTcxOTA0MDBaMB4xHDAaBgNVBAMTE21haWwubnRpYy1pbmZvcy5uZXQwggEi
MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC05l5EzxUedDLOOgPn/Ud//YrP
7/jAByAw/atJ9GgFhyQYZSeft/5ReHGY3xllEY30OYGkYP5T+nsRWx+3jITPh5VQ
jgvGYH6ygapvOB3XyfzxQmJ92L/Eo9DbuhQfDypJaspnT+YQ+vWu9Us2s1zQ6vSf
baZjfGKN67cze0jh+zUw2nVphz9L43l19o/SGArKXUdPKd58t7VAlZ0yCe0qn1Ey
mwPx0CAYkWp3tDTH8MZ3z4112mLXk+vLy0cBLBARAG6+unYThxiG0nDrSqWYTdtp
CL6sIjdlZggEOSXz83eBptKYuCqKd6GRsnOK5lIIml8+oCJSWXBiYm2M9LXFAgMB
AAGjggIUMIICEDAOBgNVHQ8BAf8EBAMCBaAwHQYDVR0lBBYwFAYIKwYBBQUHAwEG
CCsGAQUFBwMCMAwGA1UdEwEB/wQCMAAwHQYDVR0OBBYEFN+rCGIgYiL4N1f0pfbb
6PF8ZrtVMB8GA1UdIwQYMBaAFKhKamMEfd265tE5t6ZFZe/zqOyhMHAGCCsGAQUF
BwEBBGQwYjAvBggrBgEFBQcwAYYjaHR0cDovL29jc3AuaW50LXgzLmxldHNlbmNy
eXB0Lm9yZy8wLwYIKwYBBQUHMAKGI2h0dHA6Ly9jZXJ0LmludC14My5sZXRzZW5j
cnlwdC5vcmcvMB4GA1UdEQQXMBWCE21haWwubnRpYy1pbmZvcy5uZXQwgf4GA1Ud
IASB9jCB8zAIBgZngQwBAgEwgeYGCysGAQQBgt8TAQEBMIHWMCYGCCsGAQUFBwIB
FhpodHRwOi8vY3BzLmxldHNlbmNyeXB0Lm9yZzCBqwYIKwYBBQUHAgIwgZ4MgZtU
aGlzIENlcnRpZmljYXRlIG1heSBvbmx5IGJlIHJlbGllZCB1cG9uIGJ5IFJlbHlp
bmcgUGFydGllcyBhbmQgb25seSBpbiBhY2NvcmRhbmNlIHdpdGggdGhlIENlcnRp
ZmljYXRlIFBvbGljeSBmb3VuZCBhdCBodHRwczovL2xldHNlbmNyeXB0Lm9yZy9y
ZXBvc2l0b3J5LzANBgkqhkiG9w0BAQsFAAOCAQEASbG6oReGoJVRHWPy9yb/XfYh
pjKBxDT5AD6XM2XRNOpBNDmOZUIPoUUy/tYVRe6qUqtU9tPxag3hEKrZAZS5Isq8
8ZT7W6jrHYrhQr4ZpZY4sDpdMuIquh18YEwY3pXtNMYRgTH68TluW9vgb0USnJPk
J+nCj8vbVjwsX6xi9Nde3eQ+C2CnNdPw18LfLCr55W+ueJexJzvLMC8aKVMz5//O
b4lb54AQA7FXY3CR5b8OmlmSGxcqyF2ifWumPs4hzP9Y01IVScq+y3iiS5Q6B8zv
iyOLSOQI6Hmf2mNdU0cAaoLdX9Qi9eBnumf298xU93L88YMF0EoQ6CIqg7gZCg==
-----END CERTIFICATE-----
subject=/CN=mail.ntic-infos.net
issuer=/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3
---
No client certificate CA names sent
---
SSL handshake has read 3203 bytes and written 456 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : ECDHE-RSA-AES256-GCM-SHA384
    Session-ID: 51C0330BEE430C99D587DE5E74F674AE7D5DCE8318642B3ABAA1AF4CF323273A
    Session-ID-ctx:
    Master-Key: 79A6F20C3FB293E724C87DE9C9E618BDBEDADCD4F544E5FEDB93AAA21A91CFE8359CB35BA6C2C767D032F090E9C2C623
    Key-Arg   : None
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 300 (sec)
    Verify return code: 0 (ok)
---
250 DSN

There are probably things to improve on SSL configuration, but currently this seems ok.
Feel free to reopen or open a new issue if needed.


update readme: remove npm ci in favor of npm i

Dev Summary

Mocks

Test Plan

repro steps:

localhost:3000
click X button
expected:

Resources

stackoverflow is cool

This PR includes unintended changes to README.md, which came from my VS Code setting that automatically applied formatting when I saved an update.   Closing this draft PR in favor of https://github.com/Nonprofit-Exchange-Hub/web-app/pull/323.


Animation Folders

I don't get payed enough to do this shi- oh uh Addresses #441

Hopefully it plays nice with animations with the same names and with deleting animations in-game. Will merge but I'll be on the lookout for issues


Goreleaser

Overview
This PR adds building binaries to the release process by using goreleaser.
The release process is largely unchanged. Releases can be trigger by either manually triggering the ci_release workflow, or they can be triggered by pushing a version tag.
I've included commented out code for how to enable signing the binaries if the team wishes to do that.
The .goreleaser.yaml file is 90% stock generated from goreleaser init. The celestia node specific items are:
env:
  - VersioningPath={{ "github.com/celestiaorg/celestia-node/nodebuilder/node" }}

builds:
  - main: ./cmd/celestia
    binary: celestia

    ldflags:
      # Ref: https://goreleaser.com/customization/templates/#common-fields
      #
      # .CommitDate is used to help with reproducible builds, ensuring that the
      # same date is always used
      #
      # .FullCommit is git commit hash goreleaser is using for the release
      #
      # .Version is the version being released
      - -X "{{ .Env.VersioningPath }}.buildTime={{ .CommitDate }}" -X "{{ .Env.VersioningPath }}.lastCommit={{ .FullCommit }}" -X "{{ .Env.VersioningPath }}.semanticVersion={{ .Version }}" # yamllint disable-line rule:line-length

Codecov Report

Merging #2661 (055b32a) into main (c146a0a) will decrease coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2661      +/-   ##
==========================================
- Coverage   51.00%   50.90%   -0.11%
==========================================
  Files         158      158
  Lines       10657    10657
==========================================
- Hits         5436     5425      -11
- Misses       4744     4754      +10
- Partials      477      478       +1

see 4 files with indirect coverage changes

A wild conflict arises

@MSevey resolved the conflict, can you give it a glance and verify it's still looking good? Then let's do it

@MSevey resolved the conflict, can you give it a glance and verify it's still looking good? Then let's do it

Thanks @ramin looks good 👍
Waiting for CI to pass


Add lake-filled land-sea mask

This artifact provides a land-sea mask computed from the 30 arc-second ETOPO2022 orography information.

landsea_mask.nc (30 arc-second, compressed, 2MB)

This mask is generated by identifying connected basins below a predefined sea-level (set as 0 in this artifact) and marking them as "land" if they smaller than a given size. The size is provided as fraction of the surface of the globe (where the ocean is 65 %). This artifact has all the lakes filled, so that itidentifies as land everything that is not ocean. Generating this mask is
memory-intensive: for the 30 arcsecond dataset, it requires 50 GB of RAM.
The name of the variable in the dataset is landsea and the data type is an Int8: 0 is ocean, 1 is land. In the future, we might include lakes as well.
Note also that the data is compressed. If this leads to problems, please open an issue. Uncompressed data requires 400x more space.

Checklist:

[x] I created a new folder $artifact_name

[x] I added a README.md in that that folder that

[x] describes the data and processing done to it
[x] lists the sources of the raw data
[x] lists the required citation, licenses

[x] If applicable (e.g., for Creative Commons), I added a LICENSE file
[x] I added the scripts that retrieve, process, and produce the artifact
[x] I added the environment used for such scripts (typically, Project.toml
and Manifest.toml)
[x] I added the OutputArtifacts.toml file containing the information
needed for package developers to add $artifact_name to their package

[x] I uploaded the artifact folder to the Caltech cluster (in
/groups/esm/ClimaArtifacts/artifacts/$artifact_name)
[x] I added the relevant code to the Overides.toml on the Caltech Cluster
(in /groups/esm/ClimaArtifacts/artifacts/Overrides.toml)
[x] I added a link to the main README.md to point to the new artifact

Closes #36
cc: @sriharshakandala @ph-kev

Fixed the typos


Support for SystemVerilog interfaces as ports in the top level module + test case

This PR introduced a whole bunch of additional attributes. Can we have another PR that adds short descriptions of those attributes to the attributes section in the README file? @rubund Thanks!
Also: How hard would it be to extend this to also support SV structs?


[FEAT] Filtering Manage Permissions

Hi there - apologies, won't be much help in actually implementing this as my TS knowledge is zero.

However, some suggested improvements for the Manage Permissions app so that it only shows what is relevant to the user. That is:
Admins

Can see everything as is currently presented across all tabs (User Permissions, Experiment Permissions etc)

Manage Users

Remove ability to see User Permissions (this should just be for admins)
Filter experiments under Experiment Permission tab to be only those experiments they have MANAGE access on (currently everyone can see all experiments and are presented a 403 error if they click into something they don't have manage permissions for)
Same for Model Permissions
Haven't used Group Permissions yet so not sure what this should be

Edit Users and Read Users

Remove ability to see User Permissions (this should just be for admins)
Remove all experiments in Experiment Permission (unless they are a MANAGE user on one/more)
Remove all models in Model Permission (unless they are a MANAGE user on one/more)
Haven't used Group Permissions yet so not sure what this should be

hi @mshodge, could you please check 3.2.0? how it matches to your request?


Moves ArcpyHelper import into constructor

Importing arcpy takes approximately forever; ideally, we'd like to
parse the config file, show usage, etc as quickly as possible.  This
commit deferrs the import until we have done both of those things, by
moving it into the publisher constructor.

@cwalv, I think this is a cleaner approach to #29, and seems to work perfectly.  Any problems with this?


Fix pointer address validation instead of value

We're going to stop gpdb 5 support. So, I'll close it.


Text not changing red

Challenge Name

Issue Description

Browser Information

Browser Name, Version:
Operating System:
Mobile, Desktop, or Tablet:

Your Code

Screenshot

@teachinggeek Thank you for reporting this issue.
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the "help" button on the challenge on Free Code Camp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I'm wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding!


Add title option to view

import panel as pn
from lumen.layout import Layout
from lumen.pipeline import Pipeline
from lumen.sources import FileSource
from lumen.views import Table

pn.extension("tabulator")

data_url = "https://datasets.holoviz.org/penguins/v1/penguins.csv"

pipeline = Pipeline(source=FileSource(tables={"penguins": data_url}), table="penguins")
pipeline.add_transform("iloc", end=5)

table1 = Table(pipeline=pipeline, title="Title 1", download="csv")
table2 = Table(pipeline=pipeline, title="Title 2")
table3 = Table(pipeline=pipeline)
table4 = Table(pipeline=pipeline, download="csv")

Layout(views=[table1, table2, table3, table4], title="Tables")

[ ] Need to write some unit tests
[ ] Document it somewhere in the docs

Codecov Report

Merging #430 (abb9595) into main (f0ed415) will decrease coverage by 0.03%.
The diff coverage is 54.54%.

@@            Coverage Diff             @@
##             main     #430      +/-   ##
==========================================
- Coverage   69.10%   69.08%   -0.03%
==========================================
  Files          76       76
  Lines        8724     8733       +9
==========================================
+ Hits         6029     6033       +4
- Misses       2695     2700       +5

Impacted Files
Coverage Δ

lumen/views/base.py
63.65% <54.54%> (-0.32%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

If you find somewhere in the docs submit a new PR. For now I'd like to merge and cut a dev release.


Connection refused

getting this problem running python3 main.py and selecting top
Traceback (most recent call last):
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/connection.py", line 174, in _new_conn
    conn = connection.create_connection(
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/util/connection.py", line 95, in create_connection
    raise err
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 703, in urlopen
    httplib_response = self._make_request(
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 386, in _make_request
    self._validate_conn(conn)
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 1042, in _validate_conn
    conn.connect()
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/connection.py", line 358, in connect
    self.sock = conn = self._new_conn()
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/connection.py", line 186, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPSConnection object at 0x7f57355079a0>: Failed to establish a new connection: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/requests/adapters.py", line 489, in send
    resp = conn.urlopen(
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/connectionpool.py", line 787, in urlopen
    retries = retries.increment(
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/urllib3/util/retry.py", line 592, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='www.torrentgalaxy.to', port=443): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f57355079a0>: Failed to establish a new connection: [Errno 111] Connection refused'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/elon/stream-cli/main.py", line 130, in <module>
    main()
  File "/home/elon/stream-cli/main.py", line 87, in main
    get_top(hosts)
  File "/home/elon/stream-cli/main.py", line 14, in get_top
    1: apprun(torrent_galaxy()),
  File "/home/elon/stream-cli/stream_cli/runner.py", line 51, in apprun
    movies = start_scrawling(scraping_class)
  File "/home/elon/stream-cli/stream_cli/runner.py", line 35, in start_scrawling
    response = requests.get("https://www.torrentgalaxy.to/").status_code
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/requests/api.py", line 73, in get
    return request("get", url, params=params, **kwargs)
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/requests/api.py", line 59, in request
    return session.request(method=method, url=url, **kwargs)
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/requests/sessions.py", line 587, in request
    resp = self.send(prep, **send_kwargs)
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/requests/sessions.py", line 701, in send
    r = adapter.send(request, **kwargs)
  File "/home/elon/stream-cli/venv/lib/python3.10/site-packages/requests/adapters.py", line 565, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='www.torrentgalaxy.to', port=443): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f57355079a0>: Failed to establish a new connection: [Errno 111] Connection refused'))

using npm 8.15.1; node 18.7.0 and webtorrent 4.1.0 (1.8.26).
love the project concept, thanks in advance

can you view this website from a browser? https://torrentgalaxy.to/
this project uses this website.

sadly not this might be why

you can try a vpn or proxy network. i was trying this evening how to implement proxy internally and i didn't succeed. maybe someone else will do it?

@kaboussi
you might recheck leet.py file. i hope this is the file to work with 1337x but i made some changes drastically and seems like it has no effect at all.

@kaboussi you might recheck leet.py file. i hope this is the file to work with 1337x but i made some changes drastically and seems like it has no effect at all.

what changes, can you share them?

i changed the urls for categories, some choices etc.

i changed the urls for categories, some choices etc.

Cool, if you noticed that something needs to be improved or some changes feel free to open a PR or an issue.
Thanks in advance.


patch missing token on youtube

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
Fixes #20758, building on @sandsmark 's patch.

Works fine for me now, thanks.


Update fingerprint-server-api.yaml

Add a section for 'auxiliaryMobile'.

@leenasudhakar can you please add this section to the examples?
At least to get_event.json and webhook.json

@leenasudhakar can you please add this section to the examples? At least to get_event.json and webhook.json

@ilfa - Added now.


Initializing an ensemble and not providing ColumnMapper entry (e.g., provenance)

When initializing an ensemble and not providing a column, the entries get filled with the default value. For instance, provenance gets filled with survey_1. This is confusing; rather I propose that the column is not created in such a case, or filled with None.

I think this was a special case for provenance, which is no longer in TAPE. Any other columns you've encountered this with @nevencaplar ? Otherwise think this can be closed.

Closed, as recommended by the comment above.


Proxy handled differently when adding new organization

Operating System:

[x] Windows
[ ] Linux/Ubuntu
[ ] macOS
I've tested it with v2.5.0-beta as well as v2.3.82.

It's me and my strict proxy environment again.
We encountered a new issue: When adding a new organization the client tries to reach the url to check if it's an actual Zulip instance. This only works only with a specific, open proxy that not everyone has access to within our network.
Interestingly, once the org is added the other proxies work fine as well. It's only the initial check that doesn't work properly.
What's the difference between that check and the tab with the webview containing Zulip? I've looked at the code but haven't found it yet.
If there is an obvious difference, it might be possible to fix this, so the proxies get applied the same way to everything.

@zulipbot claim

@schrej I've been trying to figure this out but I don't think there's much I can do without your proxy env. :)
Can you log the response status code when the app makes a request to the .ogg file?
Specifically,
return new Promise((resolve, reject) => {
		request(checkDomain, (error, response) => {
		console.log(response.statusCode);
		// If the domain contains following strings we just bypass the server

I'm guessing that this is because of problems in our validation logic. It'd be great if you could confirm that in your environment.

Ok, the issue here seems to be that the proxy that isn't working requires authentication. The working one doesn't.
Unfortunately I'm not 100% sure how the proxy authentication works usually, afaik it uses the Windows login somehow. The difference here might be that for the WebView a full chrome tab is used but for the connectivity check it's nodejs that does the request.
Error: tunneling socket could not be established, statusCode=407
  at ClientRequest.onConnect (C:\Users\A33438080\D…-agent\index.js:166)

I did some digging and it looks like Atom also suffers from a similar problem, mostly because handling proxy auth in npm is troublesome.
Anyway, based on what worked for other people online, I suggest running:
$ npm config set https-proxy http://<username>:<password>@proxyaddress.com:[Port]
$ npm config set https-proxy http://<username>:<password>@proxyaddress.com:[Port]
$ npm config set strict-ssl false

It might be easier to place them in ~/.npmrc, but you get the idea. I'm guessing you'll have to use some combination of the above, depending on your configuration.

Apparently our normal proxies are using NTLM for authentication, which is quite common. While the WebView does support it apparently, as chrome does it as well, the authentication works fine for already added organizations. Nodejs on the other hand doesn't support it natively and therefore doesn't authenticate against the proxy and gets rejected.

Okay, that's pretty helpful. Thanks @schrej!

I'm not sure it would be worth adding support for NTLM in the nodejs part of zulip desktop.

@akashnimare should be able to answer this better, and I'd be glad to take this up if we do decide on implementing support for NLTM.
Until further discussion, it's best if I abandon the issue.
@zulipbot abandon

Not familiar with the NLTM proxy, gotta look into it.

Abandoning the issue until we're clear on NLTM.
@zulipbot abandon

@schrej  I am not familiar with NLTM proxy, but can you try this (some nltm modules seems to get it working by doing this) -
Below this line add two parameters -
username: 'username',
password: 'password'

This should probably authenticate the domain addition requests.

One of the core features with NTLM is, that it uses the windows credentials automatically. Also, request doesn't support NTLM (https://github.com/request/request/issues/808).
Adding the request options doesn't help.


ID can only be an Integer

Thank you for writing this and saving me so much time.
I actually have a couple things.
I store data as guids.  In order for the click function to work, I need the ID to be a guid.  I know I can work around it but it would be nice if that was an option.

sorry, I completely forgot your message. You are right, we have to find a general solution


can't run yarn build

It looks like it's not parsing TypeScript, but trying to parse Javascript instead. As far as I know, parcel should auto-detect it. Can you verify that the problem is present when you use npm?

use npm also have the same problem，sad QAQ

Thank you very much for this.


⚠ Bofrost.at has degraded performance

In 11565b4, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1367 ms

Resolved: Bofrost.at performance has improved in 207b21f.


Timeout support for Orquesta tasks

I have found missing the implementation of timeout logic for the Orquesta tasks.
It would be really nice to have something like this:
...
tasks:
  my_task:
    action: mypack.myaction
    retry:
      delay: 10
      count: 3
    timeout: 120
    next:
       - when: <% timedout() %>
          do: task_for_managing_timeout
...

I would like it too

Every action/task in ST2 has a timeout so that value can be set on the action itself.  Not quite the same as the task level but it does make the "failure" criteria more clear as it remains a function of the action itself.


External parameter clarification

Hey, from both doc sites I have several questions regarding external parameters for ZeRO stage 3 usage.
When external parameters are involved in a model, is it possible that the code works even when they aren't registered? Would I get a warning? Or will my model fail silently? Or may it crash if my chosen parameters randomly partition the parameters the wrong way?

@janEbert in most cases if its not setup properly it will crash. If the parameter is partitioned when its about to be used, then the mismatch in shape will often cause it to crash.
However, there are cases where there can be silent failures. partitioned parameters in ZeRO-3 are represented by a scalar value but the scaler values are broadcastable, so if a parameter is used in element wise operations, it can fail silently for example.
We are thinking about what might be a good way to address this. One thing we have been thinking about is to use an odd shaped tensor to represent partitioned parameters, so that it will reduce the chances of silent failures.
For example:
Full parameter:
param.data = [1024,1024]
Current partitioned parameter representation
param.data = 1.0
Silent faliure case :
result = torch.rand([1024,1024]) + param (this will fail silently because 1.0 is broadcastable to [1024,1024])
Possible fix using an alternate partitioned parameter representation
param.data=[5,2,3] (some wierd shaped tensor)
So torch.rand([1024,1024]) + param will fail.
We will this to our TODO list, but very happy to get contributions.

Hey @samyam, thank you for the detailed explanation! That really helps.
It sounds like the possibility of the program not failing is rather low.
I still have to dive into the codebase to understand what is happening in the background better. For now, your answer definitely helps; if I get the time I'm happy to look into this further.
@cli99 are you going to add this to the documentation?

Hi @janEbert, I am working on a PR as @samyam suggested. https://github.com/microsoft/DeepSpeed/pull/981

All right, thanks! Looking forward to stumbling upon some errors when you're done. ;)

I just read this while informing myself about ZeRO-Infinity (in ./docs/_tutorials/zero.md):

Registering external parameters
Deprecated: DeepSpeed version 0.3.15 introduced automatic external parameter registration and this step is no longer needed.

I'll close this, then. Thanks for all your support!


Release 2.5.1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2679

Relevant Lines:
3571

💛  - Coveralls


[Button] Secondary - Pipe color

Secondary button

Update the color of the pipe character on the "Go back" button to match the rest of the button. It looks like it's currently getting a lighter blue.

Context: https://github.com/cfpb/sbl-frontend/pull/430#issuecomment-2111513007

Did you end up resolving this one with Natalia @shindigira?


Documentation update for options missing in targetGlobalSettings()

Description
The solution to the customer issue logged in the ticket below is to configure the pollingInterval setting in targetGlobalSettings(), however that was missing from the documentation. This PR adds that setting, along with propertyToken and artifactLocation to the documentation.
Related Issue
https://jira.corp.adobe.com/browse/TNT-46359
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Closing to add reviews to a new pull request

Hi @judy-kim looks like we are good from our side - would you be able to review this when you have the chance? Thanks!