Pull down source file locally before segmenting

This was due to observed issues where FFMPEG would become very slow to segment and make large numbers of range requests per segment when segmenting remote files.
We now download the file to a local temp directory (with a deferred step to remove it afterwards) before segmenting.

Added 2 comments. Apart from that, what happens if we store too many big files in /tmp directory? Don't we need to increase the storage capacity or mount a volume?

We only allow 8 concurrent uploads at the moment and from looking at the pods, we're running at ~250Gb of free space, so should be good but definitely something to keep an eye on. I believe we already have disk usage as a metric with alerting etc.


Fixed Angle

hi @eleurent , when i set "scaling": 2.5, How to view results from a fixed perspective.
Because my scenario is multi-agent，I can't observe the situation of the later agents.
Looking forward to your reply！

Hi!

Because my scenario is multi-agent，I can't observe the situation of the later agents.

For multi-agent scenario, there are two things we can consider

agents' observations: these should already be agent-centric if you use the MultiAgentObservation. They are the most important, as they condition the policy being learned.

the environment rendering: this is just for visualisation purposes, so it is not that important. By default, the window is centered on the position of the first controllable vehicle, see:

https://github.com/eleurent/highway-env/blob/742ce2e69bf00169f2b250e0388c6b9926c026ec/highway_env/envs/common/graphics.py#L149
you can instead focus on another vehicle by manually setting the env.viewer.observer_vehicle field, or to a fixed position (as you suggested) by editing the viewer's window_position() method (just return np.array([x, y]))


Install ps command required by the celery script.

Coverage remained the same at 89.534% when pulling ebf1276c2fbcd73b830a07dd3a120446b65af070 on johngian:fix-celery-script into 47670e534762f233ac528cd1d8670f6121b6114a on mozilla:master.


Refactor how genesis file overrides are applied

PR description

keep a reference to the overrides map on GenesisConfigFile
separate the apply overrides logic from the getConfigOptions() logic
added tests for genesis overrides in BesuCommandTest

Fixed Issue(s)
fixes #7439
Thanks for sending a pull request! Have you done the following?

[ ] Checked out our contribution guidelines?
[ ] Considered documentation and added the doc-change-required label to this PR if updates are required.
[ ] Considered the changelog and included an update if required.
[ ] For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

[ ] unit tests: ./gradlew build
[ ] acceptance tests: ./gradlew acceptanceTest
[ ] integration tests: ./gradlew integrationTest
[ ] reference tests: ./gradlew ethereum:referenceTests:referenceTests

LGTM, just few dup lines that can be removed


iOS not reproduce m3u8

Is only an issue for me or the player not support this code m3u8 ?
This work fine on android
Trying this on iPhone device 6s , SE and 8
The same issue

Which player? What version of flutter? What plugin are you using? What's the output of flutter doctor? Where is a reproducible example?
Please feel free to ping this issue if you can update it to add these things - I'm going to close it as either not actionable or a stackoverflow type question for now.  If it turns out there's a bug in a plugin we can reopen.

There is the player package video_player 0.10.5+1 link https://pub.dev/packages/video_player
To reproduce the error use an m3u8 link
And replace bug bunny video
This source code VideoPlayerController.network(
'http://www.sample-videos.com/video123/mp4/720/big_buck_bunny_720p_20mb.mp4')
For VideoPlayerController.network(
'M3U8 VIDEO')
Flutter doctor and console debug not show  errors

Could you share a m3u8 link that reproduces this?

Could you share a m3u8 link that reproduces this?

try this https://content.uplynk.com/channel/92c7be9fb47143a58683d202e321e571.m3u8

Related #48670 #21932 #35402

Closing as duplicate of https://github.com/flutter/flutter/issues/48670
@jjuandiaz please follow up on the issue


Building Docker with dextr fails with 503 Error

Trying to build docker with dextr support fails with
--2019-05-21 21:49:26--  https://download.01.org/openvinotoolkit/models_contrib/cvat/dextr_model_v1.zip Resolving download.01.org (download.01.org)... <IP_ADDRESS>, 2600:1406:3f:39d::ae6, 2600:1406:3f:38d::ae6 Connecting to download.01.org (download.01.org)|<IP_ADDRESS>|:443... connected. HTTP request sent, awaiting response... 503 Service Unavailable 2019-05-21 21:49:27 ERROR 503: Service Unavailable.
In the dockerfile, it says #TODO: CHANGE URL. What is the proper URL to use so that we can use semi automatic segmentation?

@erosten
I suppose resource was temporary unavailable. Now it works for me. Please try to build the container again.

Looks like it was. Thanks for getting back to me.


Does the atomic load in backtrace need to be SeqCst?

I don't believe its necessary for correctness in any meaningful sense, we could use Relaxed or AcqRel.
I believe that reducing it to AcqRel would be a strict performance improvement; I believe AcqRel is enough to make sure that is_backtrace_enabled only runs once. However, as with atomics always, I am not confident that I am right.
Lowering it further to Relaxed might be worth it; occassionally running is_backtrace_enabled more than once could be worth having cheaper loads over the whole course of program execusion.
cc @alexcrichton who wrote the original code

I believe that as currently written, your code can already run is_backtrace_enabled more than once. This is true even under sequentially consistent execution:

Thread 1 comes in, loads the value of ENABLED (0), and blocks.
Thread 2 comes in, loads the value of ENABLED (still 0), and does the remainder of the initialization
Thread 1 wakes up and repeats the initialization work that was done by thread 2

If you really wanted to make sure that initialization is never carried out more than once, you would need to mutate the value of ENABLED with a read-modify-write instruction in order to tell the next thread that you are doing some work and it should wait. But then you would be getting dangerously close to what std::sync::Once does, and it would be harder to justify rolling your own version.
As long as duplicate initialization is safe, cheap, and generally considered an acceptable risk, I would personally not bother, and just make the atomic operations Relaxed. The other orderings are for cases where you access multiple memory locations and need to synchronize these accesses with each other. When you only access a single shared memory location, atomicity is all you need, so Relaxed is the correct choice.

@alexcrichton As an aside, I would respectfully disagree with your decision of using SeqCst as a default. Personally, when I meet SeqCst ordering in someone's code, what I get out of it is that at least one of the two following properties must hold true:

The synchronization protocol is complicated and depends on precise execution ordering characteristics, rather than simpler message-passing semantics (which only require Acquire/Release).
The person who implemented the synchronization protocol did not have a firm understanding of it and used SeqCst as a magical incantation to be on the safe side.

I am wary of complicated interleaving-sensitive synchronization protocols, because they are both less efficient on the machine side and harder to reason about on the human side (consider that for N concurrent instructions, there are N! possible interleavings). And for obvious reasons, I am even more wary of people who play with atomics without a firm understanding of what they are doing. So already, when I see this ordering, I know that I will have a hard time trusting the code.
In constrast, I think that a simpler synchronization protocol based on Relaxed, Acquire and Release inspires more confidence, because it is easier to see what the author intended (as the desired synchronization is documented in the memory orderings), and to check whether the resulting synchronization protocol is correct or not.


Read from compacted topic ledger if available and enabled

If a topic has been compacted and the client has enabled reads from
compacted topics, try to read from the compacted ledger if the cursor
position lands before or within the range of message IDs in the
compacted topic ledger. If the cursor position lands after the message
IDs, in the compacted topic ledger, read from the cursor as normal.

@merlimat

I need to fixup tests on this, I think some mocks are missing implementations

retest this please


Fails if used behind a reverse proxy with a sub path

If Grafana is behind a reverse proxy with a subpath, then getdash.js fails as it eventually starts querying without the subpath. In window.grafanaBootData  I can see it has the sub-path in most locations, but not for the settings.datasources.*.url  which all start with /api/

Thanks for reporting. I'll try to fix it during upcoming weekend.

Thanks, I'm fairly new to Grafana, but might see if I can figure out a fix on Friday.

@jshumaker I suspect that the issue might be in this function: https://github.com/anryko/grafana-influx-dashboard/blob/master/getdash.app.js#L721-L771. This is the only place where urls are constructed. If you would like to fix it, that would be the place to start debugging.


top pods/nodes view

Is your feature request related to a problem? Please describe.
i cannot keep track of my resource usage in kubectl.nvim
Describe the solution you'd like
either a new view for kubectl top pods and kubectl top nodes
or refresh the float forever
Describe alternatives you've considered

Additional context
we can discuss the right solution here

Yeah good points, it definitely needs to be live data


DeveloperGuide: Update Use cases

Coverage remained the same at 92.159% when pulling ca45612a4e55828823eeec860a3d84ff1466f81a on Lenaldnwj:master into aa4e78edbfbc8e92cf1c100a50366b479de829fe on CS2103AUG2017-T16-B2:master.

Coverage remained the same at 92.159% when pulling ca45612a4e55828823eeec860a3d84ff1466f81a on Lenaldnwj:master into aa4e78edbfbc8e92cf1c100a50366b479de829fe on CS2103AUG2017-T16-B2:master.

Coverage remained the same at 92.159% when pulling 996eb0f0a44a996df7d67a052117467f188d0f50 on Lenaldnwj:master into aa4e78edbfbc8e92cf1c100a50366b479de829fe on CS2103AUG2017-T16-B2:master.


UWP Crash in 2.2.10-pre408

at FFImageLoading.Forms.WinUWP.CachedImageRenderer.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.b__6_0(Object state)
at System.Threading.WinRTSynchronizationContext.Invoker.InvokeCore()
change source in reuse list cell: null, fileSource, null, fileSource

2.2.10-pre-438 without changes
Also occurs when resizing

I'll need full stack trace or reproduction to debug this. Please reopen if there are more details. Thanks.


[WIP] Go CI

The CI workflow includes:

building the client
running unit tests
go vet and staticcheck as Go linters
the lint-rust workflow

Does CI include linter?

Does CI include linter?
Yep!

Couple related questions:

There's a few dependencies that are required to build the client, create a test report, and lint the Go code. What is the criteria for assessing whether they are okay to use with regard to licensing?
One recommendation with the Go project layout is to include an internal directory at the root of the Go project that contains private library code. Code in this directory cannot be imported by packages outside the source subtree in which they reside. For the public code that is meant to be used by others, we can either have it at the top level in the go directory or put it in a pkg directory. If we put it in pkg the top-level will not mix Go files and project files like .gitignore, Cargo.toml etc, but the downside is that users will need to include "pkg" in the module import path. Go developers seem to be pretty divided on which way is preferred. More details here: https://github.com/golang-standards/project-layout/issues/10


How to filter document before sending to MeiliSearch?

Currently the plugin will sync every single records to MeiliSearch by default. How do we limit or exclude certain document from sending to MeiliSearch?
For example I want to exclude all document from a collection type "book" with the column status of "deleted" from getting indexed.
Thanks

Hello @tention ! We should create another method similar to transformEntry that does not sanitize the content of the entries but give the possibility to filter some documents out.  It should be named filterEntry (or other if a better idea is suggested).
For the implementation we can reproduce the same as the one of transformEntry
transformEntry method (example) is taken from the config file and [used in the transformEntries method] (https://github.com/meilisearch/strapi-plugin-meilisearch/blob/main/connectors/collection.js#L132).
transformEntries is called in addCollectionInMeiliSearch  function here (and also another one above).
Following this implementation of transformEntry, filterEntry should not be hard to implement and should be used the same way as the standard javascript array .filter() method.
Example of usage
module.exports = {
  meilisearch: {
    filterEntry({ entry }) {
      return entry.role === 'admin'
    },
  },
}

This whould be a great feature. Any updates on this?

Hello! It is already added in the v4 migration. Which comes out this week!


If PulsatorLayout goes out of window due to scroll, on coming back in window, doesn't animate.

I have 3 scenarios where PulsatorLayout doesn't animate as stated in the issue title:

inside ScrollView
inside ListView
inside RecyclerView

Already tried onDraw, onAttachedToWindow, onFocusGained etc, but no help.
Note that this issue doesn't happen on all devices.

I'm submitting a pull request with a fix for the same


Doc typo in layer.dart

Fix typo in comments.

@dnfield This PR appears to be empty, no files changed.

Ah! Apparently I landed this separately. ok.


Remove ES6 Syntax

Remove ES6 template strings & arrow functions to help with issue #31
choojs/object-change-callsite dependency will also need to be updated because it also still has the same issue (uses ES6 Proxy without a polyfill). I'll be working on a pull request for that next.

sweet! I don't know if object-change-callsite is polyfillable but we can always make it a noop when Proxy is unavailable.
CI is failing because of some style issues, could you fix those? running npm test will list them.

@goto-bus-stop I didn't notice the style lint—I just updated the style issues :)
As for Proxy, would this proxy polyfill work: https://github.com/GoogleChrome/proxy-polyfill
I've never used proxy, but I was planning on just dropping that in if Proxy doesn't exist.

thanks!
that polyfill doesn't support properties being added or deleted unfortunately, which are things you can do with a choojs state object.

:package: 2.5.1


-- and - do not work in Windows Terminal (do work in standalone pwsh)

The -- and - works on my machine. The version is:

Windows Terminal: 1.3.2651.0
PowerShell: 7.0.3

I think there are two possible causes for your problem:

PowerShell is old
The DockerCompletion uses Register-ArgumentCompleter cmdlet internally. It does not work well for -- and - in Windows PowerShell 5.1 and earlier versions. See the issue  https://github.com/PowerShell/PowerShell/issues/2912 .

PSReadLine is old
The above issue derives from the old version of PSReadLine.

Please check the version of PowerShell and PSReadLine on your Windows Terminal and update to the newer version.

yes.
is it possible to show warning during install or import about that in old ps shell? or prevent installing into old ps?

PowerShellVersion = '5.0' is set in the manifest file (DockerCompletion.psd1). The setting prevents importing in the Windows PowerShell 4.0 or earlier.
I will not bump up the PowerShellVersion = '5.0' to 7 or higher until PowerShell Core become the default shell for Windows.

I see. Anyway just may be put -- - issue higher in readme. Thanks.


[Turbopack] lint TP1004 fs.realpathSync(???0) is very dynamic

What version of Turbopack are you using?
1.6.3
What package manager are you using / does the bug impact?
Yarn v2/v3 (node_modules linker only)
What operating system are you using?
Windows
Describe the Bug
When using a package which depends on temd-dir, turbopack can't compile the app.
It fails with the following output:
  \\?\C:\Users\anhge\Desktop\Developemt\nextjs-template\node_modules\temp-dir\index.js
    \\?\C:\Users\anhge\Desktop\Developemt\nextjs-template\node_modules\temp-dir\index.js:9:9  lint TP1004 fs.realpathSync(???*0*) is very dynamic
         5   const tempDirectorySymbol = Symbol.for('__RESOLVED_TEMP_DIRECTORY__');
         6
         7   if (!global[tempDirectorySymbol]) {
         8      Object.defineProperty(global, tempDirectorySymbol, {
         9 >            value: fs.realpathSync(os.tmpdir())
        10      });
        11   }
        12
        13   module.exports = global[tempDirectorySymbol];

    - *0* ???*1*()
      ⚠  call of unknown function
    - *1* os*2*["tmpdir"]
      ⚠  unsupported property on Node.js os module
    - *2* os: The Node.js os module: https://nodejs.org/api/os.html

Expected Behavior
file building error
To Reproduce
Checkout the repo below. It's an exceedingly minimal Next 13 project.
next dev works as intended.
next dev --turbo --show-all will produce the aforementioned error.
Reproduction Repo
https://github.com/filename24/nextjs-template/tree/nextjs13

I have the same issue with Prisma + Postcss

I have the same issue, its postcss that does it. But it says Turbopack cant "analyze function calls" which is most likely the problem

the same issue trying installing tailwind CSS with turbo mode.getting 3 warnings

any update on this? still facing this issue with postcss and tailwind installed

same issue with the tailwind CSS aswell

It is PostCSS that causes this error when being used with Turbopack

same issue with tailwind CSS + pnpm

Removing my PostCSS config removes this error, so yes - definitely seems like a PostCSS issue

Hey, @ai. Any thought on this one ?

bump

Having the exact same issue with a clean create-next-app install using npm.

Same here, just did created a new project, didn't change a single line of code, just ran next dev --turbo and I'm now getting 3 warnings all about this

Hey guys I have observed that I only got the same error after updating create-next-app to latest version. Otherwise with provious versions, even with postcss, it was not throwing this very dynamic error. I can confirm that postcss may not be issue as i also have tried without postcss and tailwind and got same error again. So there seems to be problem with create-next-app@latest

Hey guys I have observed that I only got the same error after updating create-next-app to latest version. Otherwise with previous versions, even with postcss, it was not throwing this very dynamic error. I can confirm that postcss may not be issue as I also have tried without postcss and tailwind and got same error again. So there seems to be problem with create-next-app@latest

which version u r using, i m using<EMAIL_ADDRESS>and got this issue

well, not sure why this is happening but if you downgrade Next to the version 13.4.10 the issue disappears.
"next": "13.4.10",

well, not sure why this is happening but if you downgrade Next to the version 13.4.10 the issue disappears.
"next": "13.4.10",

still has ths issue in "13.4.10"

Verified this no longer happens on the latest version: https://codesandbox.io/p/github/filename24/nextjs-template/csb-l4ksvh/draft/distracted-einstein?file=%2Fnext.config.js%3A15%2C1
If you're still running into problems please open a new issue with another reproduction so that we can verify it 🙏

@ChetSocio which version are you on currently? It seems this PR should have addressed the problem you're seeing: https://github.com/vercel/next.js/pull/58835

Upgraded to<EMAIL_ADDRESS>same error happens.

@dcodesdev please open a new issue with a reproduction.

What's the ???*0* ?


Fixin passive min max

What type of PR is this?
feature

Which issue(s) this PR closes:
none

For future reference:
git rebase origin/main
git push --force


about the scale

As your paper, input 512x512 images, the output is 64x64. But which is not according the train.prototxt. So for the training, the input is also 900x900? Thanks.

The current released model is for testing, normally called deploy.prototxt, instead of training. The training network will be released. Please stay tuned.


Feature request: settings to ignore and hide files

It would be nice if the settings panel provides an input to enter the files or folder to be ignored.
Example :  .git repository folder

Thanks for your advice. This feature is added with the new release of 1.4.0.
You can use the setting of pin-up.list.ignore (array) to hide files or folders on the pinned list by RegExp.
For example (default):
// VSCode settings.json
{
    "pin-up.list.ignore": [
        "\\.git/"
    ]
}

Thank you 🎉🎉🎉.

Unfortunately this feature seams not to work for me.
.git folders are still visibles. All settings are defaults.
The only difference is that I use workspaces.
I also tried with this:
// VSCode settings.json
{
    "pin-up.list.ignore": [
        "\\.git/",
        "\\.DS_Store/"
     ]
}


Included Singapore in the list of examples

The proposal was recommended by a customer who observed that Singapore had less latency to their tenant in EMEA than Hong Kong and asked why Singapore is not on the list. I explained the list is not all-inclusive.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@scotvidican Please merge this PR. Thanks


Refs #26167 -- Changed defaults of DatabaseFeatures.supports_expression_indexes and DatabaseFeatures.collate_as_index_expression to True.

cc @timgraham

I agree with Tim, let's change defaults to True and document both feature flags.

I agree with Tim, let's change defaults to True and document both feature flags.

If collate_as_index_expression applies to a minority of databases, I'd leave the default as False.

If collate_as_index_expression applies to a minority of databases, I'd leave the default as False.

If collate_as_index_expression applies to a minority of databases, I'd leave the default as False.

Makes sense. I'll fix it.

If collate_as_index_expression applies to a minority of databases, I'd leave the default as False.

Makes sense. I'll fix it.

@timgraham thanks for the report, @felixxm thanks for the review! 👍

@timgraham thanks for the report, @felixxm thanks for the review! 👍


#3 Add navigation

Value Proposition
As a user
I want to I want to see a navigation
So that I can switch between the create page and the home page
Description

Acceptance Criteria

[ ] An icon and title("Home") for the home page
[ ] An icon and title("Create") for the create page
[ ] When clicking on a nav button, change the page belonging to the button
[ ] When clicking on a nav button, the icon is filled and the other is unfilled
[ ] The navbar sticks on the bottom of the viewport
[ ] The titles of the respective pages are at the top

Tasks

[ ] Create a Navbar component
[ ] Add icons and titles to navbar
[ ] Fix the navbar at the bottom of the viewport
[ ] Add onClick function to toggle between filled and unfilled
[ ] Add function to switch between pages
[ ] Add page titles
[ ] Write test to check if onClick the respective page is shown
[ ] Write test to check if onClick the icon is filled and other unfilled

Complexity
L

Nice work  ✅
Minor detail: Try not to use "could/should/would..."
The navbar should stick on the bottom of the viewport.
➡ The navbar sticks to the bottom of the viewport.

Looks good.
In the Value Proposition you write "I want to" two times.

You got already some great suggestions :) just wanted to add that everything which is visible in the scribble does not need to be inside your acceptance criteria, e.g. :

An icon and title("Home") for the home page
An icon and title("Create") for the create page


Container view for multiple containers at the same time

I have a use case were we can to show to software systems in the container view like so:
I know this is not entirely aligned with the C4 model but it's a use case that I have.
When using container and system landscape views I haven't found a way to make it work, only one of the software systems is expanded, even when listing all containers instead of using include *.
Is there a workaround to make this work ? I was checking custom views but I haven't found much information about them.
Example DSL:
workspace {

    !identifiers hierarchical

    model {
        A = softwaresystem "A" {
            app = container "app"
            db = container "db"
        }

        B = softwaresystem "B" {
            app = container "app"
            db = container "db"
        }

        A.app -> B.app
    }

    views {
        container A {
            include *
            autolayout
        }

        theme default
    }
}

Actual result:

Expected result:

even when listing all containers instead of using include *

That should work, for example:
        container A {
            include A.app A.db B.app B.db
        }

Ahhh I see, I was also including the software systems:
container A {
    include A B A.app A.db B.app B.db
}

Which resulted in:

On a separate note, is there a way to show relations between software systems in container views ? Take the same example and add a new relation A -> B, when using the container view it's not displayed:

Generated from:
workspace {

    !identifiers hierarchical

    model {
        A = softwaresystem "A" {
            app = container "app"
            db = container "db"
        }

        B = softwaresystem "B" {
            app = container "app"
            db = container "db"
        }

        A -> B
    }

    views {
        container A {
            include A.app A.db B.app B.db
        }
    }
}

On a separate note, is there a way to show relations between software systems in container views

No, it's the containers that are the focus of the diagram.

Is the ordering in the include statement important ?
When switching the order of the elements I get different diagrams:
container A {
    include A.app A.db B.app B.db A B
}

Renders:

But when the software systems are at the beginning:
container A {
    include A B A.app A.db B.app B.db
}

It renders:

Is that intended ?

Is that intended ?

Yes.

Could we add that to the language reference documentation ?
Explain that ordering matters and how it impacts rendering ?


Remove the .zip method from OSUtils, as it was not used

We used to use zip to verify the integrity of downloaded zip archives, but we now use unzip. This removes the .zip method from OperatingSystemUtils.

LGTM
Do we document this as a system requirement on the website?

No, we didn't, even when we would throw it wasn't installed.

LGTM
Do we document this as a system requirement on the website?

No, we didn't, even when we would throw it wasn't installed.

Oops, actually I guess it's listed for macos (though not linux). I'll open a PR for that too.


localhost site can get other site's cookie

I started my site on localhost:8080，it fetches data from url(http://demo.com/api/xxxxx)，I found I can get http://demo.com cookie.   But when I use axios.js to send my request，I can't get http://demo.com cookie。my broswer: Chrome

Sorry, this is a bug tracker for a polyfill of fetch() functionality, not a place to ask support questions on how to implement requests in your app. All modern browsers now implement fetch() natively, so it's likely that the code of our polyfill doesn't even run in this case. Cookies are handled exclusively by the browser's internal protected mechanisms. Please ask usage questions on more appropriate forums such as Stack Overflow.


[WIP] Integrate all aggregation layers with AttributeManager

For #3583

Background
WIP

Change List

Coverage increased (+2.7%) to 82.833% when pulling 8575a6b8b142471b2ddd846e108f4884484f248c on AggregationLayer into d5b5d5c3515f80a25f72633e7813fb21cc7a8233 on master.


[SYSTEMML-1377] Add processing of custom configuration file for GDFO …

…tests
This patch allows tests that provide their own configuration to have the file processed by base test class which may relocate the scratch_space.  This prevents potential test failures in global data flow optimization tests due to folder hierarchy not publicly accessible.

Other unit tests which require custom configuration can be addressed in separate PR.

thanks @gweidner - could you please also modify the tests in codegen?

  The first commit passed all unit tests in PR build 1195.

LGTM - thanks @gweidner


Getting: bundling failed: TypeError: Cannot read property 'replace' of undefined

I'm getting:
bundling failed: TypeError: Cannot read property 'replace' of undefined
when

Bundling index.js  [development, non-minified]  0.0% (0/1), failed.

Enviroment:
"react": "16.0.0",
"react-native": "0.51.0",
"metro-bundler": "^0.22.1",
"react-native-typescript-transformer": "^1.1.4",
"typescript": "~2.3.4"

There's not much info to go on here. react-native-typescript-transformer doesn't use a .replace method anywhere directly. Can you provide a repository which reproduces the issue, by any chance?

react-native 0.52.0-rc.0
source-map-consumer.js
bundling failed: TypeError: Cannot read property 'sections' of undefined
function SourceMapConsumer(aSourceMap) {
var sourceMap = aSourceMap;
if (typeof aSourceMap === 'string') {
sourceMap = JSON.parse(aSourceMap.replace(/^)]}'/, ''));
}
return sourceMap.sections != null
? new IndexedSourceMapConsumer(sourceMap)
: new BasicSourceMapConsumer(sourceMap);

@ds300 it happens with latest version of the boilerplate. basically i tried this:
ignite new OKKAMI3 --b ignite-typescript-boilerplate --min
it all went well, but as soon as i start the packager :
` ┌────────────────────────────────────────────────────────────────────────────┐
│  Running Metro Bundler on port 8081.                                       │
│                                                                            │
│  Keep Metro Bundler running while developing on any JS projects. Feel      │
│  free to close this tab and run your own Metro Bundler  instance if you    │
│  prefer.                                                                   │
│                                                                            │
│  https://github.com/facebook/react-native                                  │
│                                                                            │
└────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
/Users/shroukkhan/works/OKKAMI3
Metro Bundler ready.
Loading dependency graph, done.
Bundling index.js  [development, non-minified]  0.0% (0/1), failed.
error: bundling failed: TypeError: Cannot read property 'replace' of undefined
at asyncify (/Users/shroukkhan/works/OKKAMI3/node_modules/metro-bundler/src/JSTransformer/worker/index.js:141:16)
at /Users/shroukkhan/works/OKKAMI3/node_modules/async/asyncify.js:82:27
at /Users/shroukkhan/works/OKKAMI3/node_modules/async/internal/initialParams.js:11:12
at exports.transformAndExtractDependencies (/Users/shroukkhan/works/OKKAMI3/node_modules/metro-bundler/src/JSTransformer/worker/index.js:178:3)
at handle (/Users/shroukkhan/works/OKKAMI3/node_modules/metro-bundler/src/worker-farm/lib/child/index.js:50:8)
at process. (/Users/shroukkhan/works/OKKAMI3/node_modules/metro-bundler/src/worker-farm/lib/child/index.js:56:3)
at emitTwo (events.js:125:13)
at process.emit (events.js:213:7)
at emit (internal/child_process.js:768:12)`

I'm going to close this issue due to inactivity. If you're still having trouble with bundling, please feel free to open another issue and link to this one :pray:


Update Acodus Chrome

Features

Update background image of the chrome. (Still awaiting for a larger image).
Adds full screen icon to the acodus chrome.
Updates sound on and off buttons.

Closed as moved into ozaria.


Using FromCacheAsync doesn't set navigation/relation properties

I have the following in latest versions of EF Core and Z.EntityFramework.Plus.EFCore:
var entityOnes = await dbContext.EntityOnes.Where(blah)
    .Include(a => a.EntityTwos)
    .Include(a => a.EntityThrees)
    .ToListAsync();

After this executes, the following works fine, as expected:
var test = entityOnes[0].EntityTwos[0].EntityThree.PropertyOne;

However, if I change this query to use EntityFrameworkPlus, EntityThree becomes null.  It no longer automatically sets the navigation property:
var entityOnes = await dbContext.EntityOnes.Where(blah)
    .Include(a => a.EntityTwos)
    .Include(a => a.EntityThrees)
    .FromCacheAsync(new MemoryCacheEntryOptions() { AbsoluteExpiration = DateTimeOffset.Now.AddHours(1) }, cancellationToken);

Now the following throws a null exception because the EntityThree property is null:
var test = entityOnes[0].EntityTwos[0].EntityThree.PropertyOne;  // EntityThree property is null.

Hello @joshmouch ,
Do you think you could provide us a test project with this issue?
It will make easier/faster for my developer to getting started for investigating it.
We now always ask for a project since we found out that most issues are missing some essential information or are resolved by the requestor when creating it
(Even if the issue seem very easy to reproduce, by getting a test project, it allow us to give a faster support and better experience for the support of all our free libraries)
Best Regards,
Jonathan

@JonathanMagnan Do you have a template I can use and modify?

Here is the template we normally use when replicating an issue
using System;
using System.Collections.Generic;
using System.Data.Entity;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace Request
{
    public static class Request
    {
        public const string connection = "Server=<IP_ADDRESS>;Initial Catalog=Z;Integrated Security=True;";

        public static void Execute()
        {
            // CLEAN
            using (var context = new EntityContext())
            {
                context.EntitySimples.RemoveRange(context.EntitySimples);
                context.SaveChanges();
            }

            // SEED
            using (var context = new EntityContext())
            {
                context.EntitySimples.Add(new EntitySimple() { ColumnInt = 1 });
                context.EntitySimples.Add(new EntitySimple() { ColumnInt = 2 });
                context.EntitySimples.Add(new EntitySimple() { ColumnInt = 3 });
                context.SaveChanges();
            }

            // TEST
            using (var context = new EntityContext())
            {
                var list = context.EntitySimples.ToList();
            }
        }

        public class EntityContext : DbContext
        {
            public EntityContext() : base(connection)
            {
            }

            public DbSet<EntitySimple> EntitySimples { get; set; }

            protected override void OnModelCreating(DbModelBuilder modelBuilder)
            {
                modelBuilder.Types().Configure(x =>
                    x.ToTable(GetType().DeclaringType != null
                        ? GetType().DeclaringType.FullName.Replace(".", "_") + "_" + x.ClrType.Name
                        : ""));

                base.OnModelCreating(modelBuilder);
            }
        }

        public class EntitySimple
        {
            public int ID { get; set; }
            public int ColumnInt { get; set; }
        }
    }
}

Thank a lot ;)

Hello @joshmouch ,
This issue will be closed since we haven't heard back from you.
Feel free to reopen it if you can provide the information we asked.
Best Regards,
Jonathan

OK.  I have it on my task list to give you an example, but it probably won't be for quite a while.  I'm just not going to use the Cache for now until I can get back to it.


Manage UI when performing several operations at the same time

Check UI during performing of several operations (two or more tasks at the same time) and correct the behavior.
E.g. if there is VM stopping for changing SSH keys, then do not propose to stop VM if clicking on changing affinity group just after resetting SSH key.
Connected feature ID: pending

duplicates #712


Unmarshal block buffer into a separate block

With the introduction of interface{} based message passing
in the RPCBus, unmarshalling the received block into the blk variable
caused a mutation in its underlying slices. This affected future verification
as the data was no longer consistent. Fixes #331

Codecov Report

Merging #336 into master will increase coverage by 0.00%.
The diff coverage is 88.88%.

@@           Coverage Diff           @@
##           master     #336   +/-   ##
=======================================
  Coverage   54.21%   54.21%
=======================================
  Files         127      127
  Lines        7161     7162    +1
=======================================
+ Hits         3882     3883    +1
  Misses       2773     2773
  Partials      506      506

Impacted Files
Coverage Δ

pkg/p2p/peer/processing/chainsync/sync.go
78.66% <88.88%> (+0.28%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #336 into master will increase coverage by <.01%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##           master     #336      +/-   ##
==========================================
+ Coverage   54.21%   54.21%   +<.01%
==========================================
  Files         127      127
  Lines        7161     7162       +1
==========================================
+ Hits         3882     3883       +1
  Misses       2773     2773
  Partials      506      506

Impacted Files
Coverage Δ

pkg/p2p/peer/processing/chainsync/sync.go
78.66% <88.88%> (+0.28%)
:arrow_up:

Continue to review full report at Codecov.

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


Send custom Tags in logs

Hello,
We have a datadog set up where logs are filtered by tags meaning that I can only see logs with some specific tags.
Is it possible (makes sense) to send also custom tags on logs and not only in metrics?
Best regards
Ricardo Mano

We are also looking for this exact feature for our JMeter logs. Datadog support has suggested a workaround for this, which involves cloning and editing the JMeter pipeline, and using processors. However, it would still be very helpful to allow users of this listener to use it to add custom tags to logs.

Hi,
I have the same requirement as I have to filter the jmeter logs based in tags - env. Can you please suggest what is the workaround? Only the logs are not getting the customTags but the metrics of this listener are.


Migrating from /api to /ajax-api endpoint

The /ajax-api prefix is used by Dagshub to connect to the REST API. This is giving exactly the same responses as the previous /api prefix. This solves https://github.com/JuliaAI/MLFlowClient.jl/issues/35#issuecomment-1880158336.
I don't know the existance of both, but we must go through the one that is compatible with both solutions. In the future, if there's a case that is breaking this, we should think in a way to separate each different platform.

Thanks! Merged and triggered a new release: https://github.com/JuliaRegistries/General/pull/98410

This makes implementing GitLab support a lot harder as Gitlab is unaware of the undocumented (a search on the mlflow page found no mentions of this endpoint) ajax-api end point.


Cannot view workbook that was shared with me

This might be related to #150?

I believe it is related to 150 but is a different issue.  Can you list the actions to recreate this issue?

I share a workbook using one user account, then when I click on the link in the email, I get this error page.
But when I log in normally, I can see it in my workbooks.

Can you share it with me so I can take a look

Shared. also, the share button doesn't appear right away. I have to edit it and then it appears.


Usersnap Feedback - Please clean up this 404.

Sender<EMAIL_ADDRESS>Comment: Please clean up this 404.
Open #11 in Usersnap Dashboard

Download original image
Browser: Chrome 58 (macOS Sierra)
Referer: https://participedia.xyz/case/1403
Screen size: 2560 x 1440 Browser size: 1211 x 1338
Powered by usersnap.com

duplicate of #317


Weight sharing implementation

Thanks again for the great work. I have two questions related to the weight sharing implementation:

In the original Perceiver, there are n blocks and each with m self-attention layers, with the i-th self-attention layer in each block sharing weights (https://github.com/deepmind/deepmind-research/blob/826ff89f21e5143dc68ff7cb33f01cc6e237844d/perceiver/perceiver.py#L392)
How does it work in your implementation (https://github.com/lucidrains/perceiver-pytorch/blob/2d59df42ebb0b7538af77d584f5ae5b50759618b/perceiver_pytorch/perceiver_pytorch.py#L193) from the second block and on? For example, does the 2nd self-attn layer in the 2nd block share weights with the 2nd self-attn layer in the 1st block or does it also share weights with the 1st self-attn layer in the 2nd block?
Weight sharing is done by repetitively calling the same nn.module in the original paper(https://github.com/deepmind/deepmind-research/blob/826ff89f21e5143dc68ff7cb33f01cc6e237844d/perceiver/perceiver.py#L470); while here it uses cache_fn to achieve that. I'm not so sure if they are equivalent and if so, do you see any performance benefit of using cache_fn  method?

@yuanmao Hi there! You caught a bug, my apologies in advance if this caused any inconveniences for your research :cry: I have fixed it in 0.8.1 https://github.com/lucidrains/perceiver-pytorch/releases/tag/0.8.1


fix(TDI-40795) uncheck set header as default as migration not work

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-40795
What is the new behavior?
https://jira.talendforge.org/browse/TDI-40795
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Pull request test result: success :star:
Sonar results


Client: Add 30s HTTP header timeout for image download

Fixes #10279
This is to avoid LXD holding the image download lock too long when a remote source is not responding in a timely manner.
This can occur when the remote image server is up and running, but is not generating the HTTP header response due to internal I/O issues.

Testsuite passed


Add support for 10.0.17063.1000

termsrv_x64.zip

I was binary patching termsrv.dll right up to build 10.0.17046, but it looks like the code has changed a lot between 10.0.17046 and 10.0.17063.1000 as the data at the similar address is wildly different. Adding just the values for 10.0.17063 as per build 10.0.17004 will not work, even if RDPConfig is all green... the account I'm RDP-ing to/from has full access rights and in correct groups.

Here's termsrv (17035, 17040, 17046 versions, x64 dll) which worked with patching and I assume RDPWrap too once manually added to the .ini...
termsrv.10.0.17035-17040-17046.zip


Various traits.dd fixes

Replaced writefln with writeln, as that kind of writefln usage no longer compiles.
DMD uses __ctor and __dtor for the allMembers and hasMember traits, not _ctor and _dtor, as the documentation claims and implies.
__traits returns tuples, not arrays.
Updated some examples still relying on __traits returning arrays.

There are a couple of $(V1 ...) tags in there, but there is no concerted effort to remain compatible with older versions. I suggest they just be removed as they cause nothing but confusion.

The D1 documentation is built out of this; please do not break it.

@WalterBright, ah, thanks, that's the kind of information I wanted to hear. I didn't get a very clear answer from Andrei earlier.
I'll fix it up so it's correct for both D1 and D2. It wasn't correct for either before.

Thank you.

@WalterBright, it now uses writefln and says array when built for D1, and uses writeln and says tuple for D2. The examples which try to catch the return of __traits into an array now do the right thing for both (uses [__traits(...)] in D2, and __traits(...) in D1).
I've gone over it once in both D1 and D2 mode, and it looks ready.

Note, getOverloads is entirely wrapped in a V2 block, which is why it unconditionally says "tuple". I'm not sure if this is intentional. Does D1 __traits not have getOverloads?

D1 doesn't have __traits.

@donc, that's what I thought too, so why does traits.dd have $(V1) blocks with the old behaviour of __traits?

@jakob That must be a mistake. All the $(V1) blocks should be removed. They've never been part of D1.

Removed all version blocks. I can always erase the latest commit in the unlikely case that it's not a mistake.
@WalterBright, about your comment earlier: this pull request edits only the traits page. The traits documentation is linked from the D1 language table of contents, but it is a dead link.
I am confused as to what the intention is here. I always thought __traits was a D2 feature and was never back-ported to D1. I never heard of an intention to back-port it to D1. The D1 table of contents links it, but only in the main page, not the sidebar. traits.dd had V1 version blocks containing the old behaviour using arrays and didn't list some of the traits available, but it was not consistent throughout.
If all this is indeed a mistake, then the pull request is correct now, otherwise, some clarification would be appreciated.

There were 4 D2 specific pages (const/immutable, traits, C++ interfacing, SafeD) unconditionally linked in spec.dd. They are all dead links on the D1 website. I wrapped them in V2 blocks.


No english description

Is it really mandatory to have a description in English for every object? I'm getting the 'TOBCT no english description' error for some objects.
METHOD lif_object~serialize.
  ....
  SELECT SINGLE * FROM tobct INTO ls_tobct
    WHERE oclss = ms_item-obj_name
    AND langu = mv_language.
  IF sy-subrc <> 0.
    lcx_exception=>raise( 'TOBCT no english description' ).
  ENDIF.

  io_xml->add( iv_name = 'TOBC'
               ig_data = ls_tobc ).
  io_xml->add( iv_name = 'TOBCT'
               ig_data = ls_tobct ).
ENDMETHOD.                    "serialize

nope, I have recently removed a few of this kind of errors from the code. Feel free to submit a pull request, if you like?

Already working in this change (I'm new to git so I hope I get all right).


dfp: adding timing information about DNS resolution

Risk Level: low
Testing: new unit, integration tests
Docs Changes:
Release Notes:
Part of https://github.com/envoyproxy/envoy-mobile/issues/1520

Hey @mattklein123 pinging you for high level API thoughts.
The linked envoy mobile bug includes some other timing characteristics I'm going to add in follow-up PRs, namely time for the usptream connection to connect (start/ end) and time for SSL handshake (start/end)
right now I'm using the filterstate as it seems the simplest way to be extensible but if you have improvements to suggest I'd definitely prefer them earlier in this PR chain rather than later :-)

Hey @mattklein123 pinging you for high level API thoughts.

At a high level I think using filter state is fine for this, but I have 2 questions/comments:

We should think about how to document this. Our filter state documentation is a bit haphazard and I want to make sure that people know about this.
Do we think there will be multiple related items that could be packaged together in a struct within a single key? I.e., instead of having a key per uint, etc. have a key per related data / struct that we could add on to? That might be a bit easier to understand.

Agree this should have docs, but I wanted to make sure we agreed on where the info was stored, then sort out a doc location :-)
I like the idea of having a general struct.  What do we think of a hash map from timing string to ms_since_epoch or ms_since_start?   We could even TODO moving the backing store of the existing stream into metrics over to that and maybe even remove the timings APIs?  Then we can doc up a well known filter states doc parallel to well known dynamic metadata?  I think if we went that route I would lean towards adding it as a first class member to stream into APIs, but I'm good with whatever.

I like the idea of having a general struct. What do we think of a hash map from timing string to ms_since_epoch or ms_since_start? We could even TODO moving the backing store of the existing stream into metrics over to that and maybe even remove the timings APIs? Then we can doc up a well known filter states doc parallel to well known dynamic metadata? I think if we went that route I would lean towards adding it as a first class member to stream into APIs, but I'm good with whatever.

Sure this sounds fine to me. The only thing I'm not sure of is whether we should key by string vs. just have some type of timing object that avoids hash lookups?

if we want it to be extensible, what would you suggest other than hash map?  Given we're updating once per request/response I'm not worried about the hash lookup cost.
we already have an UpstreamTimingInfo struct.  I could instead move the downstream constructs to a DownstreamTimingInfo struct add extensible functions to both?

we already have an UpstreamTimingInfo struct. I could instead move the downstream constructs to a DownstreamTimingInfo struct add extensible functions to both?

Ah OK got it. sure makes sense to me.

@alyssawilk do you want @mattklein123 to take a pass, or do you want me to now that you two discussed high level API concerns?

yeah if you'd be up for a pass that'd be great


routerDirection not working like push or pop

Bug Report
Ionic version:

[x] 4.x
Current behavior:
I think routerDirection does not have the same behavior as the push or pop that exists in ionic 3.
It's not working well with the browser history when using back or forward as the property value.
Expected behavior:
When I use forward, It's working fine, but when using back, It should simulate the back button of the browser.
Related code:
<ion-button routerLink="/support" routerDirection="back">
	<ion-icon slot="icon-only" name="arrow-forward"></ion-icon>
</ion-button>

Thanks for the issue. Is this still an issue using the latest version of Ionic Framework? If so, please provide a repo with the code required to reproduce this issue. Thanks!


Ender IO Reservoir Recipe

Recipe isn't working.

Recipe works fine. Double check materials. 1x Cauldron 2x Quarzt Glass 6x Glass(OreDict)


fix: catch ELOOP

fs.realpath has been optimized to utilize uv_fs_realpath(), a new api
in libuv. The libuv api has slightly different behavior. There are two
particular issues that are causing problems for glob

ev_fs_realpath() throwing before fs.readdir ELOOP
The removal of the cache

In the past glob was relying on fs.readdir to throw when handling
recursive symbolically linked directories. It is now possible that the
call to libuv can throw before. The behavior is currently different on
osx and linux causing the test suite to fail on all of the flavors of
linux we are running in CI.
This commit adds an extra check for 'ELOOP' and sets appropriately.
The commit includes an extra check to make sure that real is truthy
Without that extra check the test suite was reporting garbage data in the results.
This was only happening with the async implementation.
This commit has not done anything regarding the removal of the cache
As long as the cache doesn't include a value called "encoding"
everything will be fine.
There has not been any benchmarking done on this change.
ref: https://github.com/libuv/libuv/pull/531
ref: https://github.com/nodejs/node/pull/3594

/cc @jasnell who did all the dirty work in solving this one.

s/ev_fs_realpath/uv_fs_realpath/

Wow, didn't notice that uv has realpath now.
Someone should confirm that it's not using the realpath(3) UNIX function, since that's notoriously insecure. (That's why node had a realpath in JS in the first place.)
If it is, then it's better for glob to refuse to use realpath in those versions of node.

@isaacs it is using realpath(3). I see you've joined the discussion in https://github.com/nodejs/node/issues/2680#issuecomment-213368900
I'll keep this thread updated with what happens in the Node projet

@isaacs if we update the version of libuv in node to include the fix for realpath(3) would you be opposed to this landing in node-glob?

@TheAlphaNerd I haven't followed the conversation in depth, but I see the some ^Lift folks got involved.  If @jlamendo is happy with where node 6 lands on this, then I'm happy supporting it.

@TheAlphaNerd From my understanding, node 6 is landing on throwing an error when PATH_MAX is undefined.
If that's correct, I'm ok with that solution.  While I don't want to break anyone's build, it's better to do that than deal with a compromised machine. There seems to be a few conflicting threads on that, so I'm not sure what the actual accepted solution was.
That said, I do have a concern with the comment about encoding being in the cache. Unfortunately I didn't have time to root this out on my own today, so hopefully you know, but are there any controls in place to prevent that from happening, and are such controls possible? If it does happen, what is the impact?

the changes to libuv landed in v6.2. Any system that does not have PATH_MAX will have an error thrown during compilation
@jlamendo can you elaborate on what you meant by encoding in the cache?

ping @jlamendo
@isaacs this is still breaking CI for most flavors of linux for catching cycles

Digging into this more, it's almost impossible to fix without either (a) making a significant breaking change to glob, or (b) porting the pre-node6 fs.realpath into a standalone module and using that instead.  Both options are nontrivial.
The tests are breaking because Node broke behavior.  fs.realpath no longer works like it used to, and any module that exposed any kind of realpath API surface is almost certainly failing tests as well (provided that their test coverage was sufficient to detect it.)
The patch here simply ignores ELOOP errors that are raised by the fs.realpath call.  That does work in the one case where a test is failing, but digging in a bit deeper, I'm not convinced that it's the correct solution in every case.  In Node 6, node-glob simply cannot do what it used to be able to do.  I am concerned that ignoring ELOOP will violate its contract.  (Also, what about ENAMETOOLONG?  It's purely lucky happenstance that the test is not raising that instead.)
It's going to take some time to fix issues like this.  In the meantime, in my opinion, people should either know that they're using a not-ready-for-prime-time version of the platform (and thus, expect test failures), or avoid Node 6 until it and the ecosystem have had time to get stable.  This new work lands on the laps of many part-time maintainers who weren't planning for it.  I have no idea when I'll even get to it, but it's not at the top of my list.  I've already spent several hours debugging new issues that Node 6 raised.
Breaking changes  break stuff.  This is what it looks like when a platform is unstable.  It's costly.

@TheAlphaNerd
I was referring to the statement you made - 'As long as the cache doesn't include a value called "encoding" everything will be fine.'
What is the impact if it is included in the cache, and are there any mechanisms in place to detect that before it causes problems or prevent it from being there in the first place?
It may be a minor issue, and I suspect that it is the case, but I wanted to be sure.


Where is admin login url

Hi,  i installed oro platform last version but i don't know how can i access to admin page!
I don't install orocrm or other things,  just installed oro platform.  Can you tell me please how can i access admin page on oroplatform?!

The home page is an admin page.
Please follow the Installation Guide.
Pay attention to Configure Web Server step. After this you will be able to access the admin page by <your_domain_name>/ URL.


Validating required array items

I have a field containing internationalized strings of the form:
{
  name_intl: [ { locale: 'en', value: 'foo' }, { locale: 'ja', value: 'bar' } ]
}

Is there a way to use SimpleSchema validation to make some locales required and some not? In other words, when validating a document or modifier against the schema, I would like to throw an error if, say, the name_intl array has no item with a locale equal to en. Is this possible?

Oh never mind, I was playing with optional/required but it looks like I need a custom validation function instead:
https://github.com/aldeed/simple-schema-js#custom-field-validation

Related question: is it possible to throw one separate error for each missing translation, even though they are all technically on the same field? It seems like the custom function only accepts one return value?

I ended up serializing a JSON object and returning it as a string, and then deserializing it on the other end. Pretty hacky but it works.

I ended up serializing a JSON object and returning it as a string, and then deserializing it on the other end. Pretty hacky but it works.


postman failure for: /curriculum/id/:curriculumId

{
			"id": "98bfc68a-e965-4d0a-8a35-2715e5d9ac97",
			"name": "/curriculum/id/:curriculumId",
			"url": "https://dcox0bl0me.execute-api.us-east-1.amazonaws.com/Prod/curriculum/id/2",
			"time": 1246,
			"responseCode": {
				"code": 400,
				"name": "Bad Request"
			},
			"tests": {
				"response must be valid and have a body": false
			},
			"testPassFailCounts": {
				"response must be valid and have a body": {
					"pass": 0,
					"fail": 1
				}
			},
			"times": [
				1246
			],
			"allTests": [
				{
					"response must be valid and have a body": false
				}
			]
		}

adjusted params to be for an id that currently exist in the database. this did solve the problem
recommend reevaluate response for incorrect params... up for discussion


[SPARK-20060][Deploy][Kerberos][Spark Shell] Obtain credentials for proxy user before talking to hive metastore

What changes were proposed in this pull request?
For Spark on non-Yarn mode on a  kerberized hdfs, we don't obtain credentials from hive metastore, hdfs, etc and just use the local kinited user to connecting them. But if we specify the --proxy-user argument on non-yarn mode, such as local, standalone, after we simply use UGI.createProxyUser to get a proxy ugi as the effective user and wrap the code in doAs, the proxy ugi has no credentials to talk to hive metastore. Thus, we need to obtain credentials via the real user and add them to the proxy ugi.
How was this patch tested?
unit tests
manual tests on kerberized metastore service and hdfs

Can one of the admins verify this patch?

@jerryshao This may also fix issue SPARK-19995 and SPARK-19997 on yarn with those apps which take SparkSQLCLIDriver.main as entrance,  plz take a look.
@vanzin @tgravescs @mridulm @dongjoon-hyun  can you help to review this, thanks.

I didn't think Spark officially supported kerberos in standalone mode. I'm pretty sure it doesn't work at all even if kinit'd due to a change that went in a long time back in runAsSparkUser, unless that changed fairly recently. This was brought up before as well but would have to dig up those details as to why it didn't go in.  I think it was because if we are going to add support we should do it fully and document support for it and such.
I'm definitely fine with adding it, this would just be a feature vs a bug.

Here is a jira from a long time back: https://issues.apache.org/jira/browse/SPARK-2541

Does kerberos authentication really work in non-yarn cluster mode? AFAIK I don't see any code which will ship delegation tokens to executors other than yarn.

yes，this seem only fix the local mode，in standalone mode it still got problems of hdfs token lost @tgravescs @jerryshao .

cc @tgravescs, tested with a secured HDFS with standalone and works fine. And this pr has a lot of yarn specified security arguments to rename.
cc @jerryshao plz take a look.

@yaooqinn normally such a big behavior change requires design doc and well discussion. It is not a good idea to push bunch of codes silently without any discussion.
Besides, we're working on refactoring current credential mechanism to support push tokens from external service and get rid of distribution of keytab, please see SPARK-19143. I think after that supporting kerberized services for standalone mode and others are much more easier and straightforward.

Yeah if you plan on adding support for secure hdfs access in standalone mode, it needs a feature jira, probably go through SPIP and make sure everything truly works and is documented.  I remember someone in the past tried to just revert that jira that broke it but others wanted to make sure it was fully supported.
I also think there is a jira for adding kerberos support to the mesos side.
So I think we should start with more design in the jira and SPIP to make sure people agree with this.

@yaooqinn I'm trying to add Kerberos support for Mesos, and creating HadoopRDDs fail for me because YARN isn't configured: https://issues.apache.org/jira/browse/SPARK-20328
Did you run into this?

@yaooqinn Shall we listen to @tgravescs and start with more design docs and SPIP?

@yaooqinn I think the patch here is quite old and cannot be merged anymore, can you please close it.
If you still want to address this issue, can you please create a new PR, thanks!


Remove appId as a requirement

What's done

appId is not really required in frint as a framework
So removed

Coverage decreased (-0.02%) to 96.452% when pulling 5cfb3493f6b17853389c1ccffd65db9f30c32df2 on remove-appid into dd30cdfe31b42951e70f065b8b5f16dfaa7ee396 on master.

Coverage decreased (-0.02%) to 96.452% when pulling f5d7cbfc315fb15b5c80e0c54415759ed47ce11f on remove-appid into 2d10526ccc57d719729f65070c0d0aecbb70b2c2 on master.


Show version in console

Show GridEngine version in console for debugging purposes.

It would be also great if you could put the number inside a property of the GridEngine instance as well. It would be very helpful for feature detection, for example in the DevTools, where I currently test for the presence of a method before using it.

Yes, good point. I will expose the version as a string. For example "2.14.1".

Will be part of next release


Create Basic User Model and Views

Description
I need to create the initial User Model and rudimentary User Views so that I can provide the user framework.
Requirements

[x] The User Model is created and is integrated with the database
[x] A create user view is created
[ ] A login user view is created
[ ] Upon login, a user session is established

Started work:
Created model and create user together.
We have decided to do authentication first, then integrate authorization later with pages.
To be continued..

@Bennm23 looks good now! Logged in and works fine too. Closing this issue.


Separate 1x1 convolution for skip connection

One of the authors mentioned that the skip connections are connected to a separate 1x1 convolution than the one which output goes into the add block.

That's good to know, thanks!
So adjusting the diagram in the paper, it would look like the following, right?

I like that better. If someone is going to put this in anytime soon please chime in so we don't duplicate effort.

I could add this once #39 is merged.

This has been fixed by #70


Add data with new Saskatchewan boundaries as an API endpoint or parameter

This should eventually be integrated into the timeseries route, but for now these data live at the sknew route.


Consider deprecation/removal of delphi_epidata.R client

Reasons to remove, deprecate, or at least just stop supporting the delphi_epidata R client:

it is superseded by the actively- and well-maintained epidatr package

even the covidcast R client has been documented as deprecated in favor of epidatr, and the covidcast R client has been better maintained than this delphi_epidata R client; compare:

https://github.com/cmu-delphi/covidcast/commits/main/R-packages
https://github.com/cmu-delphi/delphi-epidata/commits/dev/src/client/delphi_epidata.R

its presence adds dependencies and slows the build+test process while adding to docker image sizes

this can improve the development cycle, in the spirit of #1308 and #1372

it is fairly safe to do so because:

it doesn't provide backing (ie, serve as a dependency) for the covidcast R client (unlike the covidcast python client, which is built upon the delphi_epidata python client)
the only way anyone uses this client is if they pull it directly out of this git repo (as opposed to epidatr and the covidcast r client which are published on cran), which seems unlikely/rare

according to logs, we've only had 5 non-affiliated users total (none of which were api keyed) in the past 8 months (since we made this client's user agent string identifiable).

the changeset is small:

one file for the client
one file for its tests
some r installation commands in a Dockerfile (this is the main thing i would like to remove (to speed up builds))
a directive for running the tests in a Makefile (which becomes useless if we remove the above commands from the Dockerfile)

I've never used this client so it would not affect me. Seems safe, really determined users can just switch to pulling this old client out of Git history, but the majority have likely switched away by now.


optionally embedd images as base64

It's possible to embed images via data URLs in base64. For example
![Image](data:image/png;base64,SOMEBASE64STRING)

It would be nice if copy-selection-as-markdown would support this functionality as well.
This way it would be easier to have a full backup of an article that might be deleted later on, including it's resources.
PS: Thank you for this extension :pray:
PPS: There are also browser extensions like img2base64, that allow to copy an image as base64 directly. Maybe it would be possible to take that logic from there?

There's also a tool for backing up Medium articles called medup that's doing this.
What I like about the approach in medup is, that the images are only inlined at the end and there are only references to them within the regular text flow.

@alexanderadam: Thanks a lot for your suggestion! I don't have your use case but interesting enhancement. challenge accepted!

Will update this issue after release.

@alexanderadam: Just released v0.20.4 which contains this feature. Grub your update and let me know if you found any issue. Thanks!

Check Embed imgs (.gif, .jpg, .jpeg, .png, and .webp) as base64 text as possible at Advanced setting to enable the feature. It requires additional permission to access referenced images.

@0x6b, Thank you so much for working on this. :raised_hands:
Unfortunately it didn't work properly when I just tested this.
I marked your avatar here on this issue page and I got a reference but it wasn't base64 encoded.
It looks like this:
[![@0x6b][img1]](https://github.com/0x6b) [ 0x6b](https://github.com/0x6b)

[img1]: https://avatars0.githubusercontent.com/u/679719?s=40&v=4

Or did I miss a setting?

Maybe I somehow misunderstand the optional permission concept. I also see permission error in the console like:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://github.githubassets.com/images/spinners/octocat-spinner-32.gif. (Reason: CORS header ‘Origin’ cannot be added).

Will work on this again. Thanks for testing!

Easiest solution is to add <all_urls> permission request by default, but it's too open for advanced options.

I absolutely agree and I value your concerns in this regards. :+1:
More people should focus which permissions their extension or app is using.


Old punishments are unstyled

Expected behavior
Get better styling and details about passed punishments
Actual behavior
Non styled and parsed passed punishments
Steps to reproduce
If you look at a delegate account with a passed punishment it shows no styling nor time details.
delegate with old punishment
Which version(s) does this affect? (Environment, OS, etc...)
all

Passed punishments block heights should be changed to dates


run tile server with python3

Traceback (most recent call last):
File "/opt/TileStache/scripts/tilestache-server.py", line 56, in
app = TileStache.WSGITileServer(config=options.file, autoreload=True)
File "/usr/local/lib/python3.5/dist-packages/TileStache-1.51.6-py3.5.egg/TileStache/init.py", line 369, in init
if type(config) in (str, unicode, dict):
NameError: name 'unicode' is not defined
python3

Python 3 support appears to be a work in progress. See #279

I suspect that some of Tilestache's dependencies have dropped python 2 support.  werkzeug as an example.


[WIP] Test with real Stackdriver

https://github.com/istio/istio/issues/29284

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
2a6b79085fa8e29663e31e1870aa5be670f4cccb
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
cbeeedccf3b8eccb501176afcfd05d738cb780e8
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
f7a9f26d53fe21ff4a692d3e12b04c769682efce
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
8a9fb7cae8d1540bf4a75f13c43c2b959720ff7c
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
ba959cfa62e6347d176ff3f0432fcdfa2505571e
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
2ad3ee9ca05ecb8ff3f55a39ea994c9de7585ca4
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
a86cbf47f9f111d0b8bcc62feb3cca5e542bbfa5
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
5ab84401e5d115a4d513344bc340d72b2388246a
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
c221c6d6f4e372e9aa8a5371f915e840aa1214a9
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
d02f240589540336a5fad40c56dc2e13d9975d95
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
d02f240589540336a5fad40c56dc2e13d9975d95
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
d02f240589540336a5fad40c56dc2e13d9975d95
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
6daa09ad5d867f752e0b41810bb4ab1644a9f65b
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
9b2f282f6cfae237c71aac57ee71d80fd4e2c2a7
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
531452c66f4179cde55ba08bf75447f7eb1ce6be
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
4c37eb206ac94649be05d86039cb8451501ebeba
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
fd50c70052a342381f97a2a35838c3cfac35c1b5
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
76edd92083cb0d499a60e8f697b1d2422778a1e8
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
28d79b56f29377e8c931f1b51662fcf4813ca22c
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
8e078bda798090625e0f593df677e9cdcaaaaaf3
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
fb1af020e2d5fcb4b5d0b1a9b76eb3ba11f38a54
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
bde665c66c5b7467c19a6497c18cc8e7083dfb8e
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
927e5513714e09e57128a2f68796664ecdb9650a
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
3df688b4de397524ab23789ed7fc6a184ebc5e88
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
403bedbb6b19076eaded7eca3bd9e72938be6a4e
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
67e04387a698f1ae51cd3a7da3fcc128f785b7b1
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
ebf6e90cf243a736ebdf2748ddd7be19729fec2a
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
80ed9be43783a72949fa4883ef82efa0868ff00b
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
d3a7cb595bc259a121ec6ee12ce5306e113d8439
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
f96d6c0f27d0d2b4d3bf7a99a6eaed04d4243ec1
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-telemetry-k8s-tests_istio

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
658f695ebcf2f07daf3f614100f8a5f707a49e68
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


fix: remove unnecessary section argument from query

Section argument is deprecated, has no effect on results and shouldn't be used.LiveURL: https://smartfaq-remove-unused-section-arg.surge.sh

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Schedule same notification multiple times without make it appear twice

I would like to schedule a notification that triggers multiple times, like after one hour and then after 3 hours.
From my understanding, I can't schedule the same notification with repeat options, because the interval is not constant, 1h and then 2h later, nor there is an option to give a List of DateTimes to when trigger them.
So, I have to schedule the same twice with different id.
But, if the first notification wasn't used and is still there when the second triggers the user will have it twice in the notification list.
I can't give an expiration date to the first one, because is not supported.
Do you have some suggestions?

Hi! Sorry for taking so long to respond to your issue on GitHub. I was focused on releasing the new 0.7.0 version of awesome_notifications and awesome_notifications_fcm and i didn't had time enough to do both. But now I can answer all your questions.
So now i'm asking you to recreate this topic using the new issue template. There's a lot of missing informations that i need to understand your problem, and all the instructions are already in the new issue template. Also, remember to check beforehand if your issue was posted by another user.
So I will automatically close all previous issues so far.
Sorry for the inconvenience and i will be waiting for your new issue request.
Thank you so much for your support!


Made grpc_core::Mutex compatible to absl::Mutex

Made following classes compatible to absl::Mutex so that those will be able to be replaced completely in future. Currently
Abseil's ones are used only when GPR_ABSEIL_SYNC is defined.
using Mutex = absl::Mutex;
using MutexLock = absl::MutexLock;
using ReleasableMutexLock = absl::ReleasableMutexLock;
using CondVar = absl::CondVar;

Since the existing ones are not exactly compatible to Abseil's, following are added to fill the gap.

MutexLockForGprMu: To use MutexLock for gpr_mu.
LockableAndReleasableMutexLock : To call Lock function with ReleasableMutexLock.
WaitUntil, WaitUntilWithTimeout, and WaitUntilWithDeadline: To support WaitUntil for CondVar.
GetUnderlyingGprMu: To get gpr_mu from Mutex.

grpc_build_artifacts_multiplatform: running


Fix confusing implementation of try_limit in Promises

The __init.py__ method of the bok-choy Promise class has a default value for timeout. This means that when you pass a value for try_limit, it will stop when the first of the limits (tries or time) is reached, which could have been at 30 seconds (the default value) rather than after the number of tries that you had intended. :(
If you only specify try_limit I would assume that your intention is to actually use the value you gave it, not a mysterious default timeout.
We should be careful with a fix tho, because if we change the behavior now it could cause existing tests (not just ours, as edX is not the only org using bok-choy) to fail.
@benpatterson @nedbat @clytwynec Thoughts?

@cgoldberg tagging you also for any thoughts/input you might have on this one.

I'm not sure what the desired semantics were. I can see arguments on both sides, but the doc says, "will poll until either A, B, C", which makes it sound like it was supposed to stop after the default 30 seconds even if the number of tries hadn't been reached.  Perhaps the simplest thing to do is to add some clarifying text to the docstring.

For me the confusion was in the default timeout of 30s, and how selenium also uses a 30s timeout when trying to instantiate the browser. So I just happened upon a fun and special situation last week since I was working on the Promise that deals with starting the browser itself.
Back to your question though, if we go with an either/or, my concern would be for try_limits that get hung...there would be no default timeout that stops the test.

oh, that's right @benpatterson
Now I remember why we did that, so you wouldn't hang yourself accidentally.
@nedbat I like your idea about a better docstring.
I think that's what we should do. I'll put in a PR when I get a chance.
Thanks guys for helping to think this through. 👍

Addressed in #167


Job List Conflicts

In older versions the job list used the temp directory as a name. But now in the newest version (using 1.7) the job list uses the settings directory as a name. This causes a major conflict and overrides the encode settings with any files named the same, despite being in separate directories, or different temp directories. Please fix.

La La Land (2016)_temp works fine here

with <IP_ADDRESS>.0-stable

However when encoding multiple movies in 1 directory you WILL get issues...the program takes the parent directory as name usually

So when that name_temp already exists the following movie temporary will be called temp and any sequencial ones as well

So it's just a matter of putting each encoding in it's own parent directory

I hope for you they will fix it....but it's not really an error you can't work with.


Fix Ruby formatter

The new Prettier version requires us to explicitly call out plugins using a .prettierrc.

So were we not actually linting lots of stuff? is that why there are so many changes?

@benilovj only for the last couple of weeks since Prettier 3.0.0 came out. All the changes are related to changes in that period