Add printing benchmarks and rearrange some things

First stab at investigating #542, but the results aren't very surprising / helpful:
Benchmark                                     Mode  Cnt      Score      Error  Units
PrintingBenchmark.printBooleansToByteBuffer  thrpt   20  31892.871 ± 2119.524  ops/s
PrintingBenchmark.printBooleansToString      thrpt   20  37532.772 ± 3550.116  ops/s
PrintingBenchmark.printFoosToByteBuffer      thrpt   20   2839.652 ±  221.515  ops/s
PrintingBenchmark.printFoosToString          thrpt   20   3496.935 ±   39.529  ops/s
PrintingBenchmark.printIntsToByteBuffer      thrpt   20  17816.349 ± 1988.353  ops/s
PrintingBenchmark.printIntsToString          thrpt   20  17039.468 ± 4612.298  ops/s

It's quite interesting that string-based print is nearly always better. My guess is byte-buffers are faster when the data set is big enough.

Added a small optimization for JSON arrays (Vector#iterator seems a little faster than iterating over indices by hand).

Current coverage is 82.66% (diff: 100%)

Merging #544 into master will increase coverage by 0.13%

@@             master       #544   diff @@
==========================================
  Files            71         71
  Lines          1981       1979     -2
  Methods        1842       1838     -4
  Messages          0          0
  Branches        139        141     +2
==========================================
+ Hits           1635       1636     +1
+ Misses          346        343     -3
  Partials          0          0

Powered by Codecov. Last update 5239b2e...d644bb6

@travisbrown I was playing with this yesterday and although it doesn't change anything for the benchmarks I wonder if it would make sense to change Printer.MemoizedPieces to always return the same instance when indent.isEmpty or somehow inject the pieces member so that only one is ever used for the noSpaces case.

@jonas Makes sense—I've just pushed a new commit with that and a few other little changes.


Crash report

can you give more details? version, frequency etc.

StepSlider Version : 1.3.0
Language : Swift 5
Crash Device : iPhone X (13.1.3)

It was fixes in version 1.5.0. You should update to this version.

The issue still exists. The crash occurs when you hold the thumb, and drag and release it fast, as if you're swiping, instead of slowly dragging it along. The issue seems to be occurring because oldPath gets deallocated.
The crash is fixed when getting the value of oldPath from a copy of _trackLayer, instead of from _trackLayer itself.
CAShapeLayer * trackLayerCopy = [NSKeyedUnarchiver unarchiveObjectWithData:[NSKeyedArchiver archivedDataWithRootObject:_trackLayer]];
    CGPathRef oldPath   = trackLayerCopy.path;

instead of
CGPathRef oldPath   = _trackLayer.path;

The same problem exists in 1.5.0.

@spongemook setting animation false worked for me.


Document that deployment requires stopping the app

Fixes #3301
Adds a blurb to three:

aspnetcore/publishing/iis.md - There's also a bad section heading that I fix in passing.
aspnetcore/publishing/web-publishing-vs.md
aspnetcore/tutorials/publish-to-azure-webapp-using-vs.md - Azure peeps might not look at either of the other two topics, so I surface the info here at the top of the deployment step.

cc/ @danroth27 @Rick-Anderson @tdykstra

@guardrex,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@Rick-Anderson Done :+1:


Support Istio 1.7.x and above

Environment:
We are using Istio 1.7 version running on K8s 1.18;
Feature request:
Support Istio 1.7.x using Cilium

Is there any effort from Istio side needed to help make this possible?

Is there any effort from Istio side needed to help make this possible?

Recent versions Cilium should be compatible with recent versions of Istio.


hi im arcturus963 and valkyrien skie and eureka dont let me start my server in aternos

https://mclo.gs/jrQA84U

If you look at the bottom you can see it is missing dependencies that are requires, like cloth config, kotlin for forge, and architectury. Also this is the wrong repository.


Pre-release Suggestions

Some minor suggestions to GH-18.

integrated the CONTRIBUTING changes, etc. in 6184fd7... i've left the author as the "contributors" we use throughout


chore: Update jsrsasign due to CVE-2024-21484 Marvin attack of RSA and RSAOAEP decryption

Fixes CVE-2024-21484
The same thing as this one, but probably will be merger faster :slightly_smiling_face:

up!


webpack 4 -> 5 : several typescript issues

Bug report
webpack version:  beta 15
Node.js version: 10.xxx
Operating System: windows
1. ModuleOptions is not exported
2. ResolveOptions is not exported

fix:
export them at the end of the file
3. EntryObject is wrong
type Entry =
	| string
	| (() => string | EntryObject | [string, string] | Promise<EntryStatic>)
	| EntryObject
	| [string, string];
declare interface EntryObject {
	[index: string]: string | [string, string] | EntryDescription;
}

but doc says here :  https://webpack.js.org/configuration/entry-context/#dependencies
module.exports = {
  //...
  entry: {
    app: { import: './app.js', dependOn: 'react-vendors' },
    'react-vendors': ['react', 'react-dom', 'prop-types']
  }
};

which triggers a typescript error
there should be some | string[] somewhere
4. no migration Guide
(bug found in some code I maintain)
- ... extends CompilationHooks -> ... extends CompilationHooksJavascriptModulesPlugin
- compilation.Chunk->Chunk
- compilation.Compilation->Compilation
- Module -> ModuleOptions
- Resolve -> ResolveOptions

I'm happy that webpack 5 has its own generated types.
However I used these types from webpack (back when using @types/webpack 4), how to make this work with webpack 5 beta 15? All these types are now missing when installing the new package:
import webpack = require('webpack');

webpack.RuleSetRule

webpack.RuleSetLoader

webpack.Plugin

webpack.Output

webpack.Resolve

webpack.Options.Optimization

webpack.Stats.ToJsonOutput

webpack.loader.LoaderContext

@rvion Do you use @types/webpack? Because yes, webpack now provide own types

/cc @sokra Looks we missing some types

While we're at it, can we have a new publish of webpack-dev-server which accepts the webpack 5 generated types?
Let's say a version 4 beta of webpack-dev-server which depends on webpack 5 instead of @types/webpack, because this is also happening in my project:

@evilebottnawi I was using webpack own types when I opened the issue
@ryanelian some types have been renamed (e.g. Resolve  => ResolveOptions)
some types are not exported in beta15 (e.g. ResolveOptions). With beta 15, you need to manually edit they libdef file and add missing exports at the bottom

@rvion What is missign?

@evilebottnawi  Sorry, my response was a bit late.
I didn't notive sokra alrady pushed some changes when I replied 3 hours ago.
I was responding to your initial question here: https://github.com/webpack/webpack/issues/10757#issuecomment-618500848
I don't know what is now missing on master after his recent commits, I switched back to using webpack 4 because of https://github.com/webpack/webpack/issues/9802#issuecomment-601911417 and don't have the time to check right now.
thanks anyway for the quick support !

@rvion Thanks for the link, WIP on this

@evilebottnawi

What is missing in master?

I've not found Loader type and LoaderContext. So, it's quite difficult to write own loader with typescript using webpack beta 15 right now.

@artem-malko Can you import type {TheOneYouWant} from 'webpack/declarations/WebpackOptions'?

@chenxsan
Loader from webpack/declarations/WebpackOptions
export interface Loader {
	[k: string]: any;
}

Loader from @types/webpack
interface Loader extends Function {
            (this: LoaderContext, source: string | Buffer, sourceMap?: RawSourceMap): string | Buffer | void | undefined;

            /**
             * The order of chained loaders are always called from right to left.
             * But, in some cases, loaders do not care about the results of the previous loader or the resource.
             * They only care for metadata. The pitch method on the loaders is called from left to right before the loaders are called (from right to left).
             * If a loader delivers a result in the pitch method the process turns around and skips the remaining loaders,
             * continuing with the calls to the more left loaders. data can be passed between pitch and normal call.
             */
            pitch?(remainingRequest: string, precedingRequest: string, data: any): any;

            /**
             * By default, the resource file is treated as utf-8 string and passed as String to the loader.
             * By setting raw to true the loader is passed the raw Buffer.
             * Every loader is allowed to deliver its result as String or as Buffer.
             * The compiler converts them between loaders.
             */
            raw?: boolean;
        }

Quite big difference)

@artem-malko Let's open a new issue about improving types

@evilebottnawi ok)

In 5, what replaces:
import { Plugin } from 'webpack';

Because for the code above I get:
/webpack-5-ts/node_modules/webpack/types"' declares 'Plugin' locally, but it is not exported.

There are additional 30 errors, 29 of which are:
node_modules/schema-utils/declarations/validate.d.ts:2:34 - error TS2307: Cannot find module 'json-schema'.

2 export type JSONSchema4 = import('json-schema').JSONSchema4;

And the other one is:
node_modules/webpack/types.d.ts:62:8 - error TS2307: Cannot find module 'estree'.

62 } from "estree";

To reproduce
package.json:
{
  "license": "MIT",
  "scripts": {
    "build": "tsc example.ts"
  },
  "devDependencies": {
    "@types/node": "^13.13.5",
    "nodemon-webpack-plugin": "^4.3.1",
    "typescript": "^3.8.3",
    "webpack": "5.0.0-beta.16"
  }
}

example.ts:
import NodemonPlugin from "nodemon-webpack-plugin";

Then:
yarn build

No errors if I remove this line:
import { Plugin } from 'webpack';

There is a temp solutions, who want use webpack beta 15 and higher and rich typings from @types/webpack:
tsconfig.json
"compilerOptions": {
    "paths": {
      "webpack"<EMAIL_ADDRESS>    },
}

@artem-malko What types are missing?

@Izhaki schema-utils will be fixed today

@sokra look like same problem with estree

@evilebottnawi https://github.com/webpack/webpack/issues/10828 for example)

Sorry to revive the discussion here, but the question remains:
In 5, what replaces:
import { Plugin } from 'webpack';

?
Latests types.d.ts does not export a Plugin definition. So not quite sure how to support both webpack 4 and 5 in my plugin's type definition

Sorry to revive the discussion here, but the question remains:
In 5, what replaces:
import { Plugin } from 'webpack';

?
Latests types.d.ts does not export a Plugin definition. So not quite sure how to support both webpack 4 and 5 in my plugin's type definition

More of a note to self: html-webpack-plugin does not import the type from webpack, rather it declares its own.

More of a note to self: html-webpack-plugin does not import the type from webpack, rather it declares its own.

https://github.com/webpack/webpack/blob/v5.13.0/types.d.ts#L10473, not sure you can have types for webpack@4 and webpack@5 without problems, because it is breaking change

https://github.com/webpack/webpack/blob/v5.13.0/types.d.ts#L10473, not sure you can have types for webpack@4 and webpack@5 without problems, because it is breaking change


MASS should be able to assume white noise when no noise files are given

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

Right now, you can open a mass.TESGroup with a set of LJH pulse files but no noise files. If you do that, then lots of features work correctly, but several usual pulse analysis features will raise errors, including:

TESGroup.compute_noise_spectra()
TESGroup.compute_filters()
TESGroup.compute_ats_filters()
TESGroup.compute_5lag_filters()

Often, that’s what we want to happen. But there should be a way for the user to signal “I have no noise data, but I don’t mind proceeding with an analysis that assumes the noise is white.” Proposal:

A method MicrocalDataSet.assume_white_nose(noise_rms=1.0) (with an @_add_group_looper decoration). When called, they set the MicrocalDataSet.noise_autocorr[:] to the value [noise_rms,0,0,...]. This allows compute_filters and compute_ats_filters and compute_5lag_filters to work correctly.
compute_noise_spectra() should still raise an error, because of course computing noise is impossible.
Why not add TESGroup.compute_noise() as an alias for compute_noise_spectra, which is not accurately named (b/c it computes spectra and autocorrelation). But keep the latter, for reverse compatibility. Ooh! We could add a deprecation warning to compute_noise_spectra.
Add appropriate tests.

@{61ef26a2138863006a92f113} got me thinking about this feature.

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Add MicrocalDataset.assume_white_noise()
Allows users to make optimal filters even when no noise files are available, by assuming white noise. Fixes #223.


Add the  dependency to python rosdep yaml file

Close and reopen again in a new branch to make the history clear


Add async variants of Atomics.wait

Atomics.waitAsync now has reasonable support in most browsers with Firefox being the notable exception, however they have a bug report for implementing it.
I used the binding for Atomics.wait as a reference and one thing that seems off to me is that the typed_array argument for the bigint varieties of these functions take an Int32Array, instead of a BigInt64Array/BigUint64Array. It seems to me that the most correct thing to do here is two make further variants of this function, e.g., add the *_biguint variants, which also take u64 as their value argument. If there is a consensus on this, I can add the variants and we can rename this PR to something like "Clean up Atomics.wait and Atomics.waitAsync".

Actually, at least according to the docs that I can find, BigUintArray is not supported, only BigIntArray.

I was thinking about using this here:
https://github.com/rustwasm/wasm-bindgen/blob/29205c51b0d617ec6fef17df859e7ac4429746bb/crates/futures/src/task/multithread.rs#L189-L190
But it wouldn't help much because we need the binding to detect support anyway. We also want to have the custom return type to avoid the overhead of Reflect, something we won't add in js-sys because we don't do this in general there.

But it wouldn't help much because we need the binding to detect support anyway. We also want to have the custom return type to avoid the overhead of Reflect, something we won't add in js-sys because we don't do this in general there.

Yep, I was thinking that/stumbled across that when I was checking whether waitAsync was already implemented.
Regarding the non-async variants of wait, shall I put together a PR that fixes type_array for the _bigint variants? It would be a breaking change, although I guess no one is using this API...

I'm fine with such breaking changes. It won't be the first time we made breaking changes to API that no one is/should be using (as an example, removing interface types comes to mind)


Update office-store-approval.md

I have added more details to some of the sections here. Regards, Priya Koshy

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

Docs Build status updates of commit 49df1e3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/publishing/office-store-approval.md
:white_check_mark:Succeeded

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

I made some minor grammatical changes.

Docs Build status updates of commit 5739c79:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/publishing/office-store-approval.md
:white_check_mark:Succeeded

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


Gatsby build error

npm run build and npm run start are throwing an error due to something about how nodes are getting created?
"gatsby-transformer-json" threw an error while running the onCreateNode
lifecycle:

Plugins creating nodes can not set data on the reserved field "fields"
      as this is reserved for plugins which wish to extend your nodes.

It is failing here in GitHub Action land too:
https://github.com/umd-mith/mith-static/runs/3115069012?check_suite_focus=true

After my fix for #10, presist.js was outputting to much of the AirTable raw data. https://github.com/umd-mith/mith-static/commit/c89a8c43fea367343b5fb13b2ec27f6fee73bd6f should fix it.

Thanks for the quick attention @raffazizzi ; I hope everything is going well at home! :baby_bottle:


Getting commands from the joystick

Hi,
Is it possible to log commands from the controller? I was checking `/dev/input/' but could not find a joystick input.

Have you tried this example?https://github.com/unitreerobotics/unitree_legged_sdk/blob/master/examples/example_wirelessHandle.cpp
This joystick data stream is directly from udp which sent by our controller board.

thank you, that works! I was wondering if it is possible to directly access it without passing for udp.

The joystick is not a Linux peripheral equipment here.

ok, great, thanks!


Field for content-type, plus base64 support

I'll default it to text/plain

I'm going to add a base64 option too, so you can serve images out of the database (in a way that mirrors how that feature works for configuring endpoints).


initial_state on ignored

Home Assistant release with the issue:
0.77.3
Last working Home Assistant release (if known):
0.60 according to https://github.com/home-assistant/home-assistant/issues/11421
Operating environment (Hass.io/Docker/Windows/etc.):
ArchLinux
Component/platform:
https://www.home-assistant.io/docs/configuration/customizing-devices/#initial_state
Description of problem:
Same as https://github.com/home-assistant/home-assistant/issues/11421
I want to have a switch that mutes/unmutes my sound via a bash command. I can assume that normally sound is ON, so after a hass restart it should show the switch ON. But the initital_state seems to be ignored.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
configuration.yaml
switch:
  platform: command_line
  switches:
    rtp_receiver_zebes:
      command_on: "pactl --server zebes.local set-sink-mute rtp-receiver 0"
      command_off: "pactl --server zebes.local set-sink-mute rtp-receiver 1"
      friendly_name: Zebes RTP Receiver

customize.yaml
switch.rtp_receiver_zebes:
    # Make button a toggle switch instead of 2 icons
    assumed_state: false
    # TODO Initial state is always assumed off for some reason. Bug!?
    # https://www.home-assistant.io/docs/configuration/customizing-devices/#initial_state
    initial_state: on
    icon: mdi:volume-high

initial_state: in customize: is only supported for automations, not switches. input_boolean supports an initial: setting, so you could use one of those and use an automation to fire the commands when it changes if needed.

But isnt that the bug I describe? This should be fixed in my opinion.


[FEA] Inference Support

As part of the 0.4 Release, we need to add a solution for using NVTabular with inference servers like Triton or TF Serving

[x] Evaluate the requirements for integration with Triton Inference Server and draft a plan for integration ( #476 )
[x] POC Integration with Triton Inference Server ( #477 )
[ ] POC Integration with TF Serving ( #186 )
[x] Example notebooks ( #478 )
[x] NVTabular Inference Container ( #479 )
[ ] Benchmarking script for inference, integrated with nightly CI ( #480 )

The  benchmarking scripts will be done in 0.5, and the TF Serving POC will be done at an even later date - closing


Added setting UseSystemTextJsonPolymorphicSerialization

Fixes #459 and Unknown subtype causes Stackoverflow exception at deserialization
Loosely based on Add support for STJ-native C# code gen
When UseSystemTextJsonPolymorphicSerialization is set to true
a CustomTemplateFactory is used that overrides the NSwag DefaultTemplateFactory behavior.
The STJ polymorphic attributes are rendered instead of NSwag own polymorphic attributes.

@ryanheath Thanks for taking the time to investigate and implement this. I'll start reviewing this immediately

@all-contributors please add @ryanheath for code

The tests are still failing because of a static template dictionary deep down in the nwag or nschema sources.
I'll see want can be done.

I have added a lot more override and custom implementation of NSwag/NSchema generators and models.
NSwag/NSchema is not extensible friendly regarding this point, or I must have overlooked an easy way to access settings in the template files ... 😅

I have added a lot more override and custom implementation of NSwag/NSchema generators and models. NSwag/NSchema is not extensible friendly regarding this point, or I must have overlooked an easy way to access settings in the template files ... 😅

Yeah, I agree. It looks needlessly complicated and harder than it should be.
Let's merge this in

Thank you @christianhelle!

@christianhelle what else should we do to get a new (pre) release nuget?

@christianhelle what else should we do to get a new (pre) release nuget?

I can create a pre-release now as it is so that you can use it

@ryanheath I was planning to update the docs tonight but then I can just do another pre-release with the new docs


Project Addition/ unit converter

Unit converter Added
Related Issue

Description

Screenshots

@priyankarpal Please Check

@priyankarpal can you see Now


FancyZones across TaskView Multi-Desktops

Description of the new feature / enhancement
Can we have it so that FancyZones can be saved per TaskView multi-desktops? I'd like to have different layouts per saved virtual desktop.
Scenario when this would be used?
TaskView multi-desktops
Supporting information
I feel like this proposal worked in past versions. Maybe the feature function is broken?

I actually experience this same issue across multiple monitors. Especially when using shortcut keys. There does not seem to be a way to have a shortcut with different layouts per monitor.

This issue #24869 sounds like the same issue, but that it is already supported. Can you include a /bugreport for further investigations.

PowerToysReport_2024-01-15-13-14-41.zip
Here is the bug file.

My issue is with FancyZones when you press win+tab and then switch across virtual desktops. FancyZones only saves one layout configuration. I'm hoping it can save a different layout per virtual desktop.


Installing Button component requires you to also install Spinner

npx @park-ui/cli components add button

 ⨯ ./components/ui/button.tsx:3:1
Module not found: Can't resolve './spinner'
  1 | import { forwardRef } from 'react'
  2 | import { Center, styled } from 'styled-system/jsx'
> 3 | import { Spinner } from './spinner'
    | ^
  4 | import { Button as StyledButton, type ButtonProps as StyledButtonProps } from './styled/button'
  5 |
  6 | interface ButtonLoadingProps {

https://nextjs.org/docs/messages/module-not-found

It works if I run this after:
npx @park-ui/cli components add spinner

This is more so a documentation issue that will be fixed! However, the code itself isn't experiencing an issue. I anticipate they will implement this into the cli to only have to run one command as well in the future. Thoughts @cschroeter?


DOC: Fix license metadata

The license inside the metadata has been wrong: It stated MIT instead of MIT-0. This fixes the corresponding metadata fields to use the correct trove classifier and SPDX identifier. Closes #1314.

Thanks.  I appreciate that.


Fix lack of printing of steps beginning/end in CL2 (release-1.17)

After https://github.com/kubernetes/perf-tests/pull/1494 was merged, we stopped getting a notice of when a particular step begins/ends in the build logs of 1.17 jobs. This PR will bring it back.
/assign @wojtek-t

/lgtm
/approve


Added Bus number to nvme drives

Hi Chris,
This patch adds Bus number to nvme drives.  As there was already one testcase for nvme drives. I just modified the existing testcases.
Please let me know if you want me to add more test cases or need to change anything else.
-Rachit

Thanks Rachit!  Closing this one since the upstream patch has been submitted.


Feedback form on pages includes clicks from bots in Google Analytics

This is a Bug Report
Looking at the data from out feedback form, it appears that a lot of data is from bots. Google Analytics has a way to filter bot activity, https://support.google.com/analytics/thread/16422940?hl=en. But we do not have that enabled
It looks like bot activity is turned off by default in the next version of Google Analytics, https://support.google.com/analytics/answer/9888366?hl=en. We are in the process of migrating to this version in https://github.com/kubernetes/website/issues/35299.

Problem:
It looks like bot activity is throwing off users feedback in out feedback forms. For example, in the screen shot, this page has 41 response on the feedback form, but they are all from the same day.

Proposed Solution:
Exclude bot data from the charts, https://support.google.com/analytics/answer/9888366?hl=en.
Page to Update:
This would be a change in Google Analytics.

also, feedback for is located on the bottom of doc pages: https://kubernetes.io/docs/tutorials/. and tracks "Was this page helpful".
Until we get the filtering figured out, we aren't able to accurately see if pages are helpful/unhelpful.

i tried adding the filter, but still saw the same results. Going to keep researching this to see if there is a better answer

Thanks @chalin!

This is still relevant. /cc @a-mccarthy

/remove-lifecycle stale


grey screen

same here - nothing but a grey screen, shows a "play button" animation as the the "taskbar" icon.
Ubuntu 18.04.03


GQL-Playground: Schema tab crashes but doc works

This issue pertains to the following package(s):

[ ] GraphQL Playground - Electron App
[ ] GraphQL Playground HTML
[x] GraphQL Playground
[ ] GraphQL Playground Express Middleware
[ ] GraphQL Playground Hapi Middleware
[ ] GraphQL Playground Koa Middleware
[ ] GraphQL Playground Lambda Middleware

What OS and OS version are you experiencing the issue(s) on?
Mac OS X Catalina
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
1.16.12
What is the expected behavior?
My schema is valid, I can query & mutate. I can look at docs. However when I select the schema tab, the browser reloads to a blank page. I have introspection set to true.
What is the actual behavior?
I should be able to look at the schema from GQL Playground
What steps may we take to reproduce the behavior?
I am using these to get to the GQL Playground
"graphql-tag": "^2.10.3",
"graphql-yoga": "^1.18.3",
Please provide a gif or image of the issue for a quicker response/fix.

This also happens for me. For some reason it seems like all lines that should be type *typename* {are just missing.

Observing same issue.
I have referred the static html with CDN resources https://github.com/prisma-labs/graphql-playground/blob/master/packages/graphql-playground-html/minimal.html

I am also observing same issue.
Had referred https://github.com/prisma-labs/graphql-playground/blob/master/packages/graphql-playground-html/minimal.html

I am here just to reference the same issue
https://github.com/prisma-labs/graphql-playground/issues/1252

FYI i think https://github.com/prisma-labs/graphql-playground/pull/1245 fixes this

Any ETA on when this fix will be deployed?

I found using Apollo-Server-Express to solve this. Now more graphql-yoga for me!

dupe, fixed in last release


Default datasets button

Allow users to use a default dataset. I have a few already on hand.

Doing this today!


Embedding mem fix

Added an aggregator process to prevent using too much memory. Memory usage slowed down loading the full embedding matrix a great deal.

Thanks for the quick PR. Can you provide a benchmark (using timeit) for load_embedding with and without vocabulary?

#9 #27

I don't know how to easily do a timing with the vocabulary/index, but I have run it for the full one:
#!/bin/bash

time python << EOF_PY

from timeit import default_timer as timer
from asr import load_embedding

start = timer()
x = load_embedding("../wiki.en.vec", n_jobs=1, verbose=True)
end = timer()
print(end-start)

EOF_PY

time python << EOF_PY

from timeit import default_timer as timer
from asr import load_embedding

start = timer()
x = load_embedding("../wiki.en.vec", n_jobs=6, verbose=True)
end = timer()
print(end-start)

EOF_PY

Output:

Reading 2519370 vectors with 300 dimensions.
Found 2519370 word vectors.
276.64790950399765
real	4m52.106s
user	5m8.645s
sys	0m41.747s

Reading 2519370 vectors with 300 dimensions.
Found 2519370 word vectors.
95.74964433399145
real	1m57.146s
user	9m26.305s
sys	1m1.783s

After putting a sys.exit() just after loading the embedding and setting n_jobs to 4:
time python -m asr simulate --embedding ../wiki.en.vec ../data/datasets/ptsd_review/schoot-lgmm-ptsd.csv

Start review in 'simulate' mode.
Reading 2519370 vectors with 300 dimensions.
Found 16584 word vectors.
real	0m41.077s
user	1m36.311s
sys	0m18.005s

Okay, so I tried with try/except, and it doesn't find any ValueError's. Also, it's 4 times as slow that way, so I won't commit it.
I think I have an idea how it might work? Arabic is written from right to left, no? So maybe that's why all the minus signs are after the numbers... And it also makes sense that the name is not on the "first" column, at least for us Europeans... It doesn't make sense to me that it's not at the complete end, but I suppose it could be that half the row is right to left, and the other half left to right... Talk about confusing!
Anyway, I think there should be no issue, so you can merge the pull request.

In [1]: import asr

In [2]: %timeit asr.load_embedding("/Users/jonathan/asr_data/fasttext.cc.en.300.vec", n_jobs=6)
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
38.8 s ± 912 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)

In [4]: %timeit asr.load_embedding("/Users/jonathan/asr_data/fasttext.cc.en.300.vec", n_jobs=1)
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
Reading 2000000 vectors with 300 dimensions.
Found 2000000 word vectors.
1min 47s ± 1.09 s per loop (mean ± std. dev. of 7 runs, 1 loop each)


linarith can no longer solve a simple problem

Adapted from zulip:

This works in mathlib3:
import data.real.basic

example (a b c d e : ℚ)
    (ha : 2 * a + b + c + d + e = 4)
    (hb : a + 2 * b + c + d + e = 5)
    (hc : a + b + 2 * c + d + e = 6)
    (hd : a + b + c + 2 * d + e = 7)
    (he : a + b + c + d + 2 * e = 8) :
    e = 3 := by
  linarith

but no longer works in mathlib4:
import Mathlib

example (a b c d e : ℚ)
    (ha : 2 * a + b + c + d + e = 4)
    (hb : a + 2 * b + c + d + e = 5)
    (hc : a + b + 2 * c + d + e = 6)
    (hd : a + b + c + 2 * d + e = 7)
    (he : a + b + c + d + 2 * e = 8) :
    e = 3 := by
  linarith (config := { oracle := .fourierMotzkin })

Possibly related to #2717

The example works now, probably thanks to #12014.

Indeed; I've edited the test-case to avoid the effects of that PR. The bug is still present, but it's now opt-in.


BUG: Nav Bar in mobile view overlaps with Login Button

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Nav Bar in mobile view overlaps with Login and Register button. When transition from small screen to large screen mobile view Nav Bar remains open.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a SWOC24 contributor
[X] I want to work on this issue

@dhruvdy assigning it to you✅, do drop a star on this repo 🫱🏼🫲🏼


Metadata specification version is non-compliant with pact specification

JVM expects a metadata spec. version section that has this format:
"metadata": {
        "pact-specification": {
            "version": "x.x.x"
        }

But pacts generated from Ruby look like:
"metadata": {
    "pactSpecificationVersion": "x.x.x"
  }

Looking at https://github.com/pact-foundation/pact-specification/tree/version-2, i'm assuming the fault is here?
See https://github.com/pact-foundation/pact-node/issues/34#issuecomment-300473768 for background.

I don't think that matters. The underlying issue that I can see from the original issue is that the mock server needs to be able to serialise a string as well as a map.
How annoying that the spec version keys are different. I think they should be camel case personally, not sure where the dashed version came from.

I've fixed the problem that you raised this issue for @mefellows but I'll leave this here for later.

This needs to be made consistent, as the pact specification version is important when loading a pact file so you know how to interpret it.

Yup. Is there any other metadata that we'd put in the pact-specification section apart from the version? I'm just not sure why it needs it's own node. I don't mind changing the ruby impl, because it doesn't use or care about the version yet, but for consistency, it would be nice to camel case it. What do you think @uglyog? If it's too annoying to change the jvm code, I'll make the ruby code match.

It should be camel case, so the JVM version must be updated, as well as the Rust one. No issues there, but we will have to be able to read both formats to support existing pact files.
Aside from that, no other important data is put into that section atm. Just the version of the library that generated the pact file.

So, I guess my query is - should we just use pactSpecificationVersion, or do we want to future proof it with pactSpecification.version ?

I would vote for pactSpecification.version, but I wouldn't vote that strongly for it.

Ok, let's do that then. I'll update ruby.

👍
On Fri, May 12, 2017 at 10:38 AM, Beth Skurrie<EMAIL_ADDRESS>wrote:

Ok, let's do that then. I'll update ruby.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/realestate-com-au/pact/issues/137#issuecomment-300953056,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADSjFBqOfVq1gCpETdHrkOwi1xU_uzGks5r46oegaJpZM4NWpDA
.

--
Matt Fellows

http://www.onegeek.com.au/

Done!
https://github.com/pact-foundation/pact-mock_service/commit/5b89d95167013ac4b11030b362c439f5632e7540

pactSpecification.version is the one we want to go with as far as I can remember. @uglyog ? Can you update the jvm?

Please ensure the spec is updated in all versions also (as you might imagine, it's frustrating to write an implementation to the spec only to get bug reports around things like this.)

 I apologise for the mess.

I've updated all the examples in the READMEs of the pact spec branches to be "pactSpecification.version". Is that the only place it's in, or is it also in the test cases?

@richard-reece is there an actual behavioural defect because of the mistmatch?

Thanks, @bethesque! None of the test cases embed a version.
The issue we have is that we verify pacts from a variety of sources, some of which implement different versions of the spec, so we have to switch behaviour in our verifier accordingly.

Which verifier is it? The Ruby one should pick up the version from each of the potential locations. If it doesn't, please raise an issue for it.

It's a (currently) in-house verifier which now picks up the metadata from both locations.

:cry:


Make error reporting more robust.

Reported by jesus on 1 Jan 1970 00:19 UTC
Error reporting should show compile and runtime errors the same and it should display the contents of perl modules if they are the culprit (not just ASP pages).

Make the case of a compile error (which appear to not follow $SIG{DIE}
catch and create a hash and "original die" that.
Make the error printer inspect the first element of the callstack and
try to pretty print everything.  Added two more error tests:
error0001.asp (existed and checks compile errors)
error0002.asp (new and checks for runtime "in ASP" errors)
error0003.asp (new and checks for runtime errors in a called module)
refs #3

Comment by jesus on 1 Jan 1970 00:19 UTC
(In [9]) Require 'PerlSetVar Debug 1' to get nice (and revealing) debugging output, refs #3

Comment by jesus on 1 Jan 1970 00:19 UTC
(In [10]) So, this magic DIE overloading has caused the expected behanviour
or die to not work within normal evals.  This is bad.

Modified by clinton on 1 Jan 1970 00:20 UTC


(#148) Comments test

Unit tests for Comments service

This PR will be closed, as all the test should be run on the development environment firstly.


⚠ Bofrost.es has degraded performance

In 9de4ae6, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1647 ms

Resolved: Bofrost.es performance has improved in f124484 after 51 minutes.


Support inserting facts with Datomic map syntax

{:db/id 123
  :foo "bar"
  :baz "quux"}

Should be the same as:
[[123 :foo "bar"]
 [123 :baz "quux"]]

And
[{:db/id 123
  :foo "bar"
  :baz "quux"}
  {:db/id 234
   :foo "bar"
  :baz "quux"}]

Should be the same as:
[[123 :foo "bar"]
 [123 :baz "quux"]
 [234 :foo "bar"]
 [234 :baz "quux"]]

For the time being we will not support nesting. For one we want to encourage data models that are flat as possible. Further, we want to be compatible with Datomic's semantics on this:

Either the reference to the nested map must be a component attribute, or the nested map must include a unique attribute. This constraint prevents the accidental creation of easily-orphaned entities that have no identity or relation to other entities.

So also we do not want to introduce a change here that would break once this is implemented.

Merged in PR #84


Add a mechanism to trace edgedb queries and their performance

In practice we are going to start a phase where we start to see "real" database queries against more realistic data - and we are going to start to ask "why is that slow?".
Can we put some sort of intereceptor on the edgedb client that does wall clock measurements and logs TRACE messages?
Or is there something we can get out of the EdgeDb deployment itself that we could easily correlate with UI activity (i.e at time XYZ - go and look at the edgedb logs).
Just need some plausible mechanism here to help us isolate are we missing indexes, doing double queries etc.

Yep - Marco has added some AWS stats monitoring on the RDS. I think the difficulty will be that presumably EdgeDb turns its queries into multiple actual SQL - so might be difficult to split them out as to what was caused by what. I mean getting some sort of correlation id that extends all the way from our EdgeQl execution - through into the backend SQL monitoring would be brilliant..

For this ticket I was thinking something super simple - like literally some sort of code pattern that logs - whether by interceptor or just even a code convention we use.
-- starting EdgeQl 'extract_patient_ids'
..
-- 'extract_patient_ids' took 151ms
That way when users say something is slow we could look at the logs and find edgeql where time > 1second (say).
I mean we should probably log things with a proper JSON format and then we can literally do the looking with Cloudwatch query.


Server stops connecting

I have a weird issue.
So servers are running fine then suddenly server goes "down"
I checked my linux and saw that server process was still running fine, I could even connect to the screen and send commands etc and there was 0 errors. I checked log file also 0 error. And stats port worked fine. Basically everything working fine but no one can connect to that server and i had to restart to fix it. Even PM2 doesnt report an error..
Any idea what this bug is? Even port was still open..

same error

with what command do you start your server when this happen?

@systemroot  i star my server without pm2 and i have same error

@VexxusArts I cannot help you as it is not a server-sided problem. Check if there is something wrong with the client you are using, your network, check if your ports are set up correctly, try using a different browser, or disable extensions/scripts

other people have the same error tho..

@VexxusArts If they are all using the same client that you are using to connect to the server with, and they can't connect either, then it is a problem with the client. Either that or you don't have your ports setup correctly.

I have tested with multiple clients. Server is running fine then suddnly no one can access.

@VexxusArts Then it is either your network or the way you have your ports setup, I cannot help you with this problem because this has nothing to do with MultiOgar.


Add Examples of the Camera Section

Fixes #1093
Changes:

Fixes issue #1093
Added Examples to Camera Section
Screenshots of the change:

Thanks @Devesh21700Kumar for working on it. I will close this PR since it hasn't been active for a while. Please feel free to submit a new PR with JavaScript syntax as @limzykenneth commented above. Thanks.


storageType = "none"

I set options.storageType to <any>"none" so that ng2-ui-auth doesn't set any cookies/storage as I handle authorization in my own interceptor. Up to now, this has been ok (apart from the console warning "none is not available") and with 8.0 it still works but both interceptors (mine and ng2-ui-auth's) are setting the authorization header, which isn't great.
Could an official storageType of "none" be added? The handling would be limited to the storage service I think - get would always return null/undefined, set and remove would do nothing. And the interceptor would be deactivated as shared.isAuthenticated would be false.

Done, try beta 6

Really sorry, but I realize now that this won't work. I call AuthService.getToken to get the token produced by AuthService.authenticate. I was conflating two separate requirements in an effort to simplify things and confused myself in the process! What I'd like is:

a clean way to tell the StorageService to use its internal store rather than storage / cookies
a way to deactivate the interceptor processing

Can I suggest reverting the current changes and doing the following (I've tested locally this time to be sure that what I'm asking for actually works)

use internal store

add a new storageType 'internal'
at the top of BrowserStorageService.checkIsStorageAvailable add:

if (options.storageType === 'internal') {
    return false;
}

in BrowserStorageService.constructor change the if test for the "storage available" warning:

if (!this.isStorageAvailable && config.options.storageType !== 'internal') {
    console.warn(config.options.storageType + ' is not available.');
}

deactivate interceptor

add a new config option deactivateInterception
at the top of JwtInterceptor.intercept add:

if (this.config.options.deactivateInterception) {
    return next.handle(req);
}

try beta.7, you can use storageType=MEMMORY and in the forRoot you can choose not to inject the interceptor by setting the second parameter to false (Ng2UiAuthModule.forRoot({... options}, false))

Thanks, sounds good. MEMMORY should be MEMORY, right?
I've npm updated and the Ng2UiAuthModule.forRootWithoutOptions entry point seems to have gone? The sources on github aren't up to date as I write so not sure exactly what's going on there.

*thanks... beta.8...
I've removed the forRootWithoutOptions just set undefined as the first parameter and it should work the same.

All working nicely, thank-you very much!


Automated cherry pick of #4450: rpc batch opertaion bugfix

Cherry pick of #4450 on release/2.13.
#4450: rpc batch opertaion bugfix

/lgtm

/approve

/approve


Add qubit_map parameter to TrialResult

Summarize the task
SimulationTrialResult has the following line:
https://github.com/quantumlib/Cirq/blob/839ebb141bf8932ef3a277e87cd2a5f1ba9ef1c8/cirq-core/cirq/sim/simulator.py#L1013
However _final_simulator_state is of type TSimulatorState, which is a template with no bound type. So this is a dynamic call, and is not reflected in the type system of SimulationTrialResult. Changes in #5260 made this apparent, and required TSimulatorState to be explicitly bound to Any.
To improve this, Initially I thought we should create an interface with qubit_map and bind TSimulatorState to that. However on second thought, I think it's best to add an explicit qubit_map parameter to the SimulationTrialResult initializer. This allows more flexibility in how users implement simulators: this way it doesn't necessarily require carrying qubit_map as part of the simulator state.
Acceptance criteria - when is the task considered done?
TSimulatorState should not be bound to Any anymore.
Related
Related issues: #5260

I may have changed my mind again on this. #5317 is an example of adding qubit_map to the TrialResult constructor. It's pretty invasive and requires a deprecation cycle that messily intertwines with another deprecation on that function.
Just creating the interface is completely backwards-compatible (though requires implementations to actually inherit that interface, to satisfy mypy. Or we can just keep it as-is.


Snippet tests work around fix

Type of change

Bugfix

Description

Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests testcase=FirefoxConsoleTest#testAddressSpaceSnippetStandard+testAddressSnippetStandard+testAddressSpaceSnippetBrokered+testAddressSnippetBrokered test_only

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: pr
TEST_CASE: FirefoxConsoleTest#testAddressSpaceSnippetStandard+testAddressSnippetStandard+testAddressSpaceSnippetBrokered+testAddressSnippetBrokered
TOTAL: 4
PASS: 4
FAIL: 0
SKIP: 0
BUILD_NUMBER: 75


support for S3 query string authentication url

When hosting jdk on S3, java.jdk.< version >.< arch >.url doesn't support query string authentication style. More info at: http://s3.amazonaws.com/doc/s3-developer-guide/RESTAuthentication.html

Is your node on EC2? If so I think you can use an IAM role to provide access to the S3 bucket.
Or maybe try the aws_s3_file LWRP from the aws cookbook to download it.

hum...not sure how to incorporate aws_s3_file, and IAM into downloading oracle flavour
https://github.com/agileorbit-cookbooks/java/blob/master/recipes/oracle.rb#L53
I'll explore the suggested further, thanks.

You basically use aws_s3_file to download the oracle jdk yourself, and the URL you feed into this java cookbook should point to that file you already downloaded using file://
See this for more details:
https://github.com/burtlo/ark/pull/54

thanks for the pointer, makes sense.

I'd accept a PR that gave the flexibility, but IAM roles are really the way to go.
Also this work around is fine approach too

nice! @erichelgeson


Allow DKG key vector submissions after DKG is finished

Context
The current behaviour of the FlowDKG and EpochLifecycle contracts is to stop the DKG for a given epoch once the threshold (50%) of key vector submissions is met. We can still consider the FlowDKG complete once this threshold is reached, and emit the EpochCommit event at this point, but we would like to continue allowing key vector submissions after the threshold has been met.
This allows us to have a better sense for the health of the DKG by seeing how many nodes submitted valid key vectors (and therefore can be reasonably expected to participate in consensus in the next epoch).
Definition of Done

EpochLifecycle - end DKG immediately before transitioning to next epoch rather than when the DKG reports being "done"

@jordanschalm Should we do the same with the Quorum Certificate contract? We're currently ending the voting for that at the end of EpochSetup right now also. Seems like it could also be at the same time.

Should we do the same with the Quorum Certificate contract?

Good idea, let's do that 👍


Linking to libraries which implement the design consideration

Learn Build status updates of commit 0416c2f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/best-practices/auto-scaling.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

#sign-off

Learn Build status updates of commit a7a8ac7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/best-practices/auto-scaling.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit be86328:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/best-practices/auto-scaling.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

#Sign-Off

Hi @ckittel, @EdPrice-MSFT
Merging is still blocked due to outstanding requested changes. Can you resolve the issue and #sign-off on the PR again?
Thanks

Thanks everyone :)


Turn and time information in GameState

Codecov Report

Merging #22 into master will decrease coverage by 0.12%.
The diff coverage is 66.66%.

@@             Coverage Diff              @@
##             master      #22      +/-   ##
============================================
- Coverage     69.06%   68.93%   -0.13%
- Complexity       68       69       +1
============================================
  Files            12       13       +1
  Lines           375      396      +21
  Branches         36       38       +2
============================================
+ Hits            259      273      +14
- Misses           95      102       +7
  Partials         21       21

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/chess/model/Side.java
100% <100%> (ø)
1 <1> (?)

src/main/java/chess/model/GameState.java
79.66% <53.84%> (-7.3%)
7 <1> (ø)

src/main/java/chess/connection/LichessAPI.java
74.77% <75%> (+0.24%)
19 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Create the router component

Requires #3
Create a component that uses the request parser from #3 to

When the route is GET /ping returns the response pong
When the route is GET / returns Hello world
When the route is POST / returns the query parameters as a json.

@moein pushed


Use a variable in a .rouge template

Is it possible to use ERB or something else in a .rouge template?

You should be able to, just make sure to name your partial with the additional .erb extension.
For example "_my_code_sample.rouge.erb"

Ha, my suggestion doesn't work. Not even close.
I added support for ERB in version 0.2.1

@jankeesvw would you mind giving this a try and letting me know if it works for your use case?

I just installed version 0.2.1 of this gem, when using a partial that ends in .rouge.erb I get this error:
ActionView::MissingTemplate at /api/documentation
Missing partial api/documentation/_all_clients_json, application/_all_clients_json with {:locale=>[:nl], :formats=>[:html], :variants=>[], :handlers=>[:erb, :builder, :raw, :ruby, :axlsx, :coffee, :arb, :haml, :jbuilder, :rouge]}. Searched in:
  * "/Users/jankeesvw/Documents/timi/timi/app/views"
  * "/Users/jankeesvw/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/activeadmin-1.0.0.pre2/app/views"
  * "/Users/jankeesvw/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/kaminari-0.16.3/app/views"
  * "/Users/jankeesvw/.rbenv/versions/2.1.1/lib/ruby/gems/2.1.0/gems/devise-3.5.6/app/views"

@jenkeesvw, the update doesn't require a change to the file extension to support ERB, you can leave it as just plain .rouge.

:ok_hand: feature confirmed @jacobsimeon, thanks for the work.


[ENG-1368] Add data links feature for Sloan

Purpose
Allows users to add links to off-site data in accordance with the Sloan grant.
Changes

adds model changes to the preprint model
add extra fields and validation for the update preprint serializer with logging and tests.

QA Notes
The user shouldn't be effected by this until we get front end changes.
Documentation
Not user facing, no new docs.
Side Effects
None that I know of.
Ticket
https://openscience.atlassian.net/browse/ENG-1368

merged with https://github.com/CenterForOpenScience/osf.io/pull/9280 and approved


set flag to signal DictionaryCoding is safe for app extensions

Set APPLICATION_EXTENSION_API_ONLY = YES so that DictionaryCoding can
be linked from app extensions without seeing the following warning:
ld: warning: linking against a dylib which is not safe for use in
  application extensions: ...

Under the covers, this toggles some flag on the dynamic library and the
linker checks this flag whenever linking an app extension.
Since DictionaryCoding is not iOS specific, it obviously doesn't use any
iOS specific APIs that are unavailable in app extensions.
Tested that the framework still builds for all platforms and passes
tests.

Looks like this was added in 76d6c65843bcc8d64c65b54cb6a9f2eca205613f.  Thanks!


Added README.md

Hey thanks for the contribution but your PR is same as the one by @akbajwa so can you look at it so i can merge it if any update is given.

@ppap1771 aayush i made pull request forst,you should not do this.He copied everything from my pr.please merge my pr

Hey,
A few things

He was assigned to the issue first and he followed the protocol.
I suggested the changes which were not done apparently so I was obliged to merge the PR of the Assignee.
I know its frustrating but it is what the protocol is.


Find people from their Twitter profile

It'd be cool to add special handling for twitter.com URLs so that if the current user profile has their mastodon handle in their name, handle, or bio somewhere then StreetPass would extract it and provide an easy click to follow experience.
(We could do GitHub profiles as well, but they're already clickable links so maybe not worth the effort)
If you agree with the feature in principle, I'd be up for opening a PR...

Thanks for reaching out I love the show! GitHub links already work because the add the right rel=me tag to them :)
I think the twitter feature kinda starts degrading what’s special about StreetPass, that it uses the simple rel=me web standard and creates a discovery tool around that. There’s already tons of twitter -> mastodon tools out there so I feel like people can still get this value elsewhere!
I have a lot on the roadmap right now, including safari, better federated interop (showing profiles from other federated apps), and adding more profile metadata (avatars, display names etc). If you like the project and are willing to help out on something else, it would be amazing if you take a look at this PR https://github.com/tvler/streetpass/pull/11 . We’re trying to figure out the exact way the official mastodon rails app reconciles links to federated profiles and implement it in typescript for this project.

Ok. Keeping it pure, I get it ✊
I'm happy to help test out the Safari stuff, if you'd find that useful. As for the other work... you lost me at TypeScript 😜

I can send a test app asap! The main problem is that safari is dropping all extension even listeners after you first quit the app. But works perfectly before. Think the problem is because the code I’m transpiling is too modern and uses es modules 🥴


Nox

Replace tox for nox
Remove old and unused methods (federation)
Correct some lint errors

Quite a lot of extra changes on style, comments, dead-code removal and formatting.
Both the cleanup and the nox config LGTM.


Display Snackbar for Bookmark Confirmation in TimetableItemDetailScreen

Idea Description
When a user adds a bookmark in the TimetableItemDetailScreen, a Snackbar should appear with the message "Bookmarked successfully."
This enhancement will provide immediate feedback to the user, confirming that the action was successful.
Reference images and links

🙋

Thanks! Assigned!


init ice/rtp independently

allows initialization of ice/rtp independently. so we can have an rtp server without ice (useful for avp)

LGTM！


Error 500 with some combinations of params and functions

Hi,
I'm using Graphite-api, with cyanite, and Grafana 2.0.1 as dashboard.
But when try to render one metric got an error 500, this be the commands I try to debug.
curl -X POST 'http://graphite-api:8888/render?target=sortByMinima(servers.lnxd704.cpu.total.*)&from=1429710422&until=1429711022&format=json&maxDataPoints=627' => Response 500
The same as previous just without sort:
curl -X POST 'http://graphite-api:8888/render?target=servers.lnxd704.cpu.total.*&from=1429709880&until=1429713380&format=json&maxDataPoints=627' => Response 200
With Sort but with range time:
curl -X POST 'http://graphite-api:8888/render?target=sortByMinima(servers.lnxd704.cpu.total.*)&from=-1hours&until=now&format=json&maxDataPoints=627' => Response 200
Some advice to debug en more details?
Thanks!

Can you update to the latest master version? Full tracebacks are visible in the HTTP response in case of app errors. I'm not able to reproduce the issue with the parameters combination you provided.

I may be running into the same or a similar issue (one difference: I do not get success when using relative time in place of absolute time).  As above, a query for a series succeeds:
curl -X POST 'http://graphite-host:8888/render?target=collectd.myhost.disk-sda.disk_octets.*&from=-1hours&until=now&format=json&maxDataPoints=5'
[{"target": "collectd.myhost.disk-sda.disk_octets.read", "datapoints": [[1348.2675219027778,<PHONE_NUMBER>], [1052.4445949305557,<PHONE_NUMBER>], [5.688876972222221,<PHONE_NUMBER>], [0.0,<PHONE_NUMBER>], [null,<PHONE_NUMBER>]]}, {"target": "collectd.myhostl.disk-sda.disk_octets.write", "datapoints": [[35349.41154551388,<PHONE_NUMBER>], [26339.154876881945,<PHONE_NUMBER>], [7189.422537173612,<PHONE_NUMBER>], [6607.860523791667,<PHONE_NUMBER>], [5954.739903064816,<PHONE_NUMBER>]]}]

but a query for a function fails:
curl -X POST 'http://graphite-host:8888/render?target=sortByMinima(collectd.myhost.disk-sda.disk_octets.*)&from=-1hours&until=now&format=json&maxDataPoints=1304'
Traceback (most recent call last):
  File "/home/pbrannan/.local/lib/python2.7/site-packages/flask/app.py", line 1817, in wsgi_app
    response = self.full_dispatch_request()
  File "/home/pbrannan/.local/lib/python2.7/site-packages/flask/app.py", line 1477, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "/home/pbrannan/.local/lib/python2.7/site-packages/flask/app.py", line 1381, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "/home/pbrannan/.local/lib/python2.7/site-packages/flask/app.py", line 1475, in full_dispatch_request
    rv = self.dispatch_request()
  File "/home/pbrannan/.local/lib/python2.7/site-packages/flask/app.py", line 1461, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/home/pbrannan/graphite-api/graphite_api/app.py", line 401, in render
    series_list = evaluateTarget(context, target, data_store)
  File "/home/pbrannan/graphite-api/graphite_api/app.py", line 496, in evaluateTarget
    result = evaluateTokens(requestContext, tokens, data_store)
  File "/home/pbrannan/graphite-api/graphite_api/app.py", line 506, in evaluateTokens
    return evaluateTokens(requestContext, tokens.expression, data_store)
  File "/home/pbrannan/graphite-api/graphite_api/app.py", line 520, in evaluateTokens
    ret = func(requestContext, *args, **kwargs)
TypeError: sortByMinima() takes exactly 2 arguments (1 given)

As best I can tell, something is going awry with parsing of the function call; pathsFromTarget() is returning an empty list, so no paths are fetched and stored in data_store.  Later, in evaluateTokens(), the call token does not have any arguments.
Curiously, the sumSeries function does not give a failure, but also does not return any data points:
curl -X POST 'http://graphite-host:8888/render?target=sumSeries(collectd.myhost.disk-sda.disk_octets.*)&from=-1hours&until=now&format=json&maxDataPoints=5'
[]%

I'm unable to reproduce this issue with current cyanite (master) and graphite-api 1.1. There was probably an issue in cyanite which has been fixed more or less recently. Please reopen the issue if the problem persists with new versions :)

I believe I have found the cause of the above exception; it was caused by using an old version of pyparsing (1.5.2).  I upgraded by accident when I installed graphite-web (which has 1.5.7 explicitly in its requirements.txt); the exception no longer occurs.  I have confirmed that downgrading to 1.5.2 causes the exception to reappear.
Perhaps graphite-api should also pin pyparsing to 1.5.7?

@cout thank you for the investigation! I've updated the dependency to specify >=1.5.7.


implemented AWS requirements

Hi, everyone) Could someone please take a look at this draft?
How to use it:
Building the backend with TLS support:

go get -u github.com/go-bindata/go-bindata/... - downloading the bindata package
Place your tls certificate and tls key into ./backend/creds folder
cd ./backend && go-bindata -o assets.go ./creds - move credentials files as a .go files
go build -i -ldflags "-X main.CertPath=/creds/cert_file_name -X main.KeyPath=/creds/key_file_name -X main.InsecureSkipVerify=true" -o ./dist/cassandra-plugin_linux_amd64 ./backend - build binary with required variables filled in.
If you'd like to use rootCA, do go build -i -ldflags "-X main.RootCA=/creds/root_ca_file_name" -o ./dist/cassandra-plugin_linux_amd64 ./backend

P.S. as a part of the PR go fmt applied

Hi, thank you for pull request) I'll watch it today. Did you build it locally (without docker)?

Hi, thank you for pull request) I'll watch it today. Did you build it locally (without docker)?

@futuarmo yeah, the last command in the description wasn't right. fixed

@futuarmo yeah, the last command in the description wasn't right. fixed

What's the issue with the tests? We should change the backend dependencies build step, should we?

What's the issue with the tests? We should change the backend dependencies build step, should we?

Looks good, but we must to integrate your changes with Docker and then we'll merge PR 🙂 I'll try it later today

Looks good, but we must to integrate your changes with Docker and then we'll merge PR 🙂 I'll try it later today

I get the same error as github actions - grafana-plugin-model/go/datasource not found, but can not find a way to avoid it yet

I get the same error as github actions - grafana-plugin-model/go/datasource not found, but can not find a way to avoid it yet

@futuarmo I've fixed them) please take a look)

@futuarmo I've fixed them) please take a look)

@IvanProdaiko94 I just tried vendor too and it's worked for me too) Ok, everything is good. Thanks for PR)

@IvanProdaiko94 I just tried vendor too and it's worked for me too) Ok, everything is good. Thanks for PR)

Congrats and thank you so much @IvanProdaiko94 @futuarmo

Congrats and thank you so much @IvanProdaiko94 @futuarmo

@IvanProdaiko94 If you would like to get certified as an Apache Cassandra Developer or an Administrator for free, let me know we sponsor these certifications. You definitely deserve it!

@IvanProdaiko94 If you would like to get certified as an Apache Cassandra Developer or an Administrator for free, let me know we sponsor these certifications. You definitely deserve it!


chore: suggestions

Some suggestions, please create a discussion if you need more info
I also created a quick sample for using tenants, for a customer i developed the generic usage of a base.js (the naming is maybe confusing with the base api).
I make it draft because this is not intended to be merged

What should we do with the PR? Should i create a different PR for the tenants sample that we can merge when your feature is ready or do you want to create your own sample?
We can use this PR only for the documentation

If you can create a different PR with the sample feature i'll just use that as a base for the auto loading of data :)
And we keep this one for docu yes

Readme specific update are covered in https://github.com/SAP/open-ux-odata/pull/888

Thanks @marianfoo i also Included the change to the config syntax in the other change so this one is good to goaway

Thanks!


fix mutation loop range

Hi dear friend,
If the chromosome length is less than the "self.CHROMOSOME_LENGTH", after filling the number of iterations should be equal to "range(2, self.CHROMOSOME_LENGTH)"

Great catch, thanks a lot!


Add polish translations

New features

Add polish translations added (+ tests)
Add optional support for weeks, months and years

Big fixes

Fix days calculations

Will check through the weekend & merge.

phpspec tests failed because of changing interface. Need to fix that before merging.

Fixed, sorry for any inconvenience. That was kind of misspelling


Events not handled

Hi,
I saw that in certain cases, the events are not handled correctly.
The bug is located here :
      BootstrapSwitch.prototype._elementHandlers = function() {
        return this.$label.on({

You can fix this bug by using the following code instead :
      BootstrapSwitch.prototype._elementHandlers = function() {
        return this.$container.on({

Regards

Line 642: insert code below

//mod
var isCurrentChecked = _this.$element.is(':checked');
if (isCurrentChecked === state)
    state = !state;


[cloud_firestore] getDocuments: Invalid argument: Instance of 'DocumentReference'

@amrfarid140 @ditman I think I have found another one of the .valueEncode issues as discussed here. See also: #1986.
The error I get is Invalid argument: Instance of 'DocumentReference'.

Full stack trace
E/flutter (14093): #0      StandardMessageCodec.writeValue (package:flutter/src/services/message_codecs.dart:392:7)
E/flutter (14093): #1      FirestoreMessageCodec.writeValue (package:cloud_firestore_platform_interface/src/method_channel/utils/firestore_message_codec.dart:83:13)
E/flutter (14093): #2      StandardMessageCodec.writeValue.<anonymous closure> (package:flutter/src/services/message_codecs.dart:389:9)
E/flutter (14093): #3      _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:379:8)
E/flutter (14093): #4      StandardMessageCodec.writeValue (package:flutter/src/services/message_codecs.dart:387:13)
E/flutter (14093): #5      FirestoreMessageCodec.writeValue (package:cloud_firestore_platform_interface/src/method_channel/utils/firestore_message_codec.dart:83:13)
E/flutter (14093): #6      StandardMessageCodec.writeValue.<anonymous closure> (package:flutter/src/services/message_codecs.dart:389:9)
E/flutter (14093): #7      _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:379:8)
E/flutter (14093): #8      StandardMessageCodec.writeValue (package:flutter/src/services/message_codecs.dart:387:13)
E/flutter (14093): #9      FirestoreMessageCodec.writeValue (package:cloud_firestore_platform_interface/src/method_channel/utils/firestore_message_codec.dart:83:13)
E/flutter (14093): #10     StandardMessageCodec.writeValue.<anonymous closure> (package:flutter/src/services/message_codecs.dart:389:9)
E/flutter (14093): #11     _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:379:8)
E/flutter (14093): #12     MapView.forEach (dart:collection/maps.dart:337:10)
E/flutter (14093): #13     StandardMessageCodec.writeValue (package:flutter/src/services/message_codecs.dart:387:13)
E/flutter (14093): #14     FirestoreMessageCodec.writeValue (package:cloud_firestore_platform_interface/src/method_channel/utils/firestore_message_codec.dart:83:13)
E/flutter (14093): #15     StandardMessageCodec.writeValue.<anonymous closure> (package:flutter/src/services/message_codecs.dart:389:9)
E/flutter (14093): #16     _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:379:8)
E/flutter (14093): #17     StandardMessageCodec.writeValue (package:flutter/src/services/message_codecs.dart:387:13)
E/flutter (14093): #18     FirestoreMessageCodec.writeValue (package:cloud_firestore_platform_interface/src/method_channel/utils/firestore_message_codec.dart:83:13)
E/flutter (14093): #19     StandardMethodCodec.encodeMethodCall (package:flutter/src/services/message_codecs.dart:524:18)
E/flutter (14093): #20     MethodChannel._invokeMethod (package:flutter/src/services/platform_channel.dart:148:13)
E/flutter (14093): #21     MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:329:12)
E/flutter (14093): #22     MethodChannel.invokeMapMethod (package:flutter/src/services/platform_channel.dart:356:48)
E/flutter (14093): #23     MethodChannelQuery.getDocuments (package:cloud_firestore_platform_interface/src/method_channel/method_channel_query.dart:87:46)
E/flutter (14093): #24     Query.getDocuments (package:cloud_firestore/src/query.dart:37:34)

Setup
The error happens every time a document has a DocumentReference as a value for a field and the snapshot is passed to startAfterDocument with this line (the getDocuments call causes it):
query.startAfterDocument(documentSnapshot).limit(8).getDocuments()

This was recently introduced with 0.13.0. I am currently using cloud_firestore version 0.13.3.

Hey @creativecreatorormaybenot can you share what your query is?

@ditman I have this debug log, which should be the exact same query (apart from the limit, but that value varies). Let me know if I should provide it in a different format.
Regarding the snapshot, I guess the most useful input here would be sharing the data types. The documents that are queried consist of:

Field types
- int
- list (of strings)
- timestamp
- list (of strings)
- float
- document reference
- float
- map (string: int)
- timestamp
- map (string: string)
- int

Yes, this is probably related to the document passed to startAfterDocument containing a DocumentReference. I'm surprised you say this only happens sometimes and not always, though!

@ditman Oh, I know why. Sorry for not thinking carefully.
The reason why it happens only sometimes is that the documents in the query mostly have the document reference field as null. So the error only occurs when a document reference is actually in Cloud Firestore. When the field is null, it does not happen (obviously).

Ah, cool, that makes sense! I'll take a look ASAP, if @amrfarid140 doesn't get to this before!

The issue seems to originate in _PlatformUtils::toPlatformDocumentSnapshot.
It's using the data getter from DocumentSnapshot, which internally converts Platform to Plugin types. This is for convenience for end-users (who only care about Plugin types), but it's a problem when we try to funnel that back into the plugin for further processing.
The fix is to either pass documentSnapshot._delegate.data (skips the getter), or to _CodecUtility.replaceValueWithDelegatesInMap(documentSnapshot.data).
I'm leaning towards the latter, which may waste a few cycles (and on big documents it might be a bunch) converting back and forth the data of the document snapshot, but it doesn't access private fields (which makes it harder to refactor the library as import/export based later).

The "fix" seems to break tests in web, so maybe it's not a good fix though:
Invalid argument (dartObject): Could not convert: Instance of 'Timestamp'
package:dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 196:49      throw_
  package:firebase/src/utils.dart 119:3                                                     jsify
  package:dart-sdk/lib/internal/iterable.dart 417:29                                        elementAt
  package:dart-sdk/lib/internal/iterable.dart 221:19                                        toList
  package:firebase/src/firestore.dart 552:22                                                [_wrapPaginatingFunctionCall]
  package:firebase/src/firestore.dart 523:11                                                startAt
  package:cloud_firestore_web/src/query_web.dart 180:17                                     startAtDocument
  package:cloud_firestore/src/query.dart 130:17                                             startAtDocument
  package:firestore_example/main.dart 325:48                                                <fn>

My new test requires an index to be created. I'm waiting to be added to the Integ test project so I can create said index and continue on this.

@ditman How come that this was not caught in CI?
I realize that this is a Timestamp object and thus not completely related.
I could write tests to catch the error described in this issue if that helps. It is good to see that the tests I helped to write are paying off 😃

same error also with   endBeforeDocument() . I think this error somehow related to FieldValue. if we use fields other than timestamp, working fine!

I'm facing the exact same issue. Downgrading to cloud_firestore: ^0.12.11 works for now.

I'm going to push a fix for most of the issues I've found while investigating this, and fixing the tests today. I'll investigate the Timestamp issue next.

Tagged and published:

https://pub.dev/packages/cloud_firestore/versions/0.13.4+1
https://pub.dev/packages/cloud_firestore_web/versions/0.1.1+1

DocumentReferences with DocumentReferences in startAfterDocument should work as expected now! Please clear your pub caches and grab the latest versions, and let us know how it goes!

@ditman Works :) Thank you so much +1

Sweet, thanks for reporting @creativecreatorormaybenot!

not working, timestamp issue - error-Invalid argument (dartObject): Could not convert: Instance of 'Timestamp'

@kushvatsa can you cut a separate issue for that? Thanks!

@ditman , #2153


Issue with "Getting Started Guide" in @site/docs/concepts/getting-started-guide.md

Describe the problem

Page: Getting Started Guide
Source: https://github.com/demisto/content-docs/tree/master/docs/concepts/getting-started-guide.md

Screenshots

Environment

OS: [e.g. Windows]
Browser: [e.g. chrome, safari, firefox..]
Browser Version:

Suggested fix

@chem12345 Hey :)
What is the issue? you may forgot to explain.

Closing do to not response


Break up readme into separate docs files

Readme is starting to get a bit too long.  Break it up into individual md files in a ./docs folder.

Closed by #133


AL0603 -  Implicit conversion from Enum to Integer

1. Describe the bug
When use subpage part in a page and have Enum in the Subpage Link we receive error:
An implicit conversion is being performed from a value of type 'Integer' to a value of type 'Enum "Default Dimension Parent Type"'. This conversion can lead to unexpected runtime issues. This warning will become an error in a future release.AL(AL0603)
part(defaultDimensions; "APIV1 - Default Dimensions")
{
Caption = 'Default Dimensions';
EntityName = 'defaultDimension';
EntitySetName = 'defaultDimensions';
SubPageLink = ParentId = Field(SystemId), "Parent Type" = const(1);
}
"Parent Type" = Enum "Default Dimension Parent Type"
How can we solve this issue considering we can not use "Parent Type".AsInteger() or use the Enum Value instead of const(1).

You can use #pragma statements for such cases

I used #pragma first but then I thought if it would be better to leave the warning and get it fix without #pragma when you fix it in the base app.
The question is if you have a timeline for fixing this? If it will not be in the next version, then I will use #pragma in our code..

We have a similar behaviour in the CalcFormula of some FlowFields.
Specefically we relate the sales/purchase "Document Type" (Enum) with the "Source Subtype" of the Warehouse Activity documents (Options). The option field must be changed to Enum, can you change it in a future release?

We have no plans to convert Source Type to Enum. This is field is Integer in many places (and this is correct design) and Option on some other places (and this is legacy issue we cannot fix in easy way). We will keep this as is until we have less breaking option to do this kind of changes.

Hi Alexander.
You didn't get it right. I mean to the field "Source Subtype", which is an option to relate to the different document types.
As you said, the "Source Type" is related to the table number and it is correct.

Of course, my comment was about Source Subtype. Corrected above.


Audit Lab components

There are more than 50 lab components right now, with various status. Do an audit and set up following actions accordingly to each status.

Replace by pattern
Replace by new component
New components needs testing / review
Anything else

22 Nov - added all the components to excel, categorized, to do to be written down

24 Nov - mark this as done. The follow up will be setting up each component in their standalone ticket on the actions, this will be happening in the following 2 weeks, as part of addressing stakeholder reporting.

pattern: add deprecation note (JSDoc), link to pattern page when available
replacement: has been / will be replaced component
remove: no longer needed, will be deleted
component: will work towards core promotion

lab
status

app-header
pattern

breadcrumbs
pattern

button-bar
pattern

calendar
component

carousel
remove

cascading-menu
pattern

color-chooser
remove

combo-box
replacement

combo-box-deprecated
replacement

combo-box-next
replacement

contact-details
pattern

content-status
pattern

deck-item
component

deck-layout
component

dialog
component

drawer
component

dropdown
replacement

dropdown-next
replacement

editable-label
remove

file-drop-zone
component

focus-manager
remove

form-field-context-legacy
replacement

form-field-legacy
replacement

form-group
remove

formatted-input
pattern

input-legacy
replacement

layer-layout
component

list
replacement

list-deprecated
replacement

list-next
replacement

logo
remove

menu-button
pattern

metric
pattern

navigation-item
component

overlay
component

pagination
component

parent-child-item
component

parent-child-layout
component

pill
replacement

pill-next
component

portal
remove

progress
component

query-input
pattern

scrim
remove

search-input
pattern

skip-link
pattern

slider
component

stepped-tracker
component

stepper-input
component

tabs
replacement

tabs-next
component

toast-group
component

tokenized-input
component

toolbar
component

tree
component

window
remove


Add ability to add a retries header variable at send options

There isn't a retry mechanism and the only possible solution right now is to recursively make a method with a counter, if the reply times out for example, you would call the same method just like in the following post:
https://groups.google.com/forum/#!topic/vertx/xOQAJeul05k
I wonder if there is a way to automatically have Vert.x retry if a header parameter was set to do so when a message was not replied -only in the case a reply handler is set-, such retries variable could be a message header variable.
Not sure if adding a default retries to be something like 3 would be any wise.

It adds a complexity aspect as now if a message fail you would want to do something like:
message.retryIfRetriesLeft()
which will basically retry only if such message has retries left.

Maybe there is no need to call nothing explicitly because you could easily mark the message as done within the fail block, otherwise retry if you didn't.

@guidomedina can we close this issue ?

Ah, sure though it would be a nice to have in the future.


Update dependencies to their latest version

I've updated dependencies to their latest version. There are a couple of major version upgrades (biggulp, chai, chai-as-promised, sinon and debug).

Seems like the CI task is failing due to a rake error:
...
rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
...


Refactor model EnumTypeGo.

Removed template-specific code from EnumTypeGo.  Most of the code was
for ensuring enum names are unique in a v1-specific way so it was moved
out of the transformer and into the views.
Small refactoring of GetEmptyCheck(), more to do there.
Sorted import statements.

🤖 AutoRest automatic publish job 🤖
> will publish once PR gets merged


Validation issue with +1<PHONE_NUMBER> (US)

Country/region affected (e.g., "US"): US
Example number(s) affected ("+1<PHONE_NUMBER>"): +1<PHONE_NUMBER>
The phone number range(s) to which the issue applies ("+1 555 555-XXXX"):
The type of the number(s) ("fixed-line", "mobile", "short code", etc.): mobile
The cost, if applicable ("toll-free", "premium rate", "shared cost"): premium rate
Supporting evidence (for example, national numbering plan, announcement from mobile carrier, news article): IMPORTANT - anything posted here is made public. Read the guidelines first!

@rossypamdev700
Thank you for taking the time to improve libphonenumber!
As per below official evidence, 607 range is assigned to New York.
https://www.nationalnanpa.com/enas/geoAreaCodeNumberReport.do
We support this range as FIXED_LINE_OR_MOBILE. The type cannot be determined by their prefix, so the best our library can do is say that it's one or the other.
https://libphonenumber.appspot.com/phonenumberparser?number=%2B1+607+323+7509
Below online references says these are normal phone numbers. These can be mobile or fixed-line. https://www.radisson.com/corning-hotel-ny-14830-2786/nycornin
http://www.bizexposed.com/New_York-USA/B/Celtic_Spirit_Inc-Stamford.php
We need more information to consider adding it to premium rate. Please see our contribution
guidelines.

@rossypamdev700
I'm closing as this issue is infeasible for us to fix at this point (we need more information). Please re-open if you respond so we pick up on it.


Prepare for OOB Azure spring bom releases

As title

/azp run java - spring - tests

BOM changes look good to me. Are we still planning to do a spring BOM release to take dependency on 1.0.6, close to the month end(it should be out in a few days, once all the dependent packages release).

BOM changes look good to me. Are we still planning to do a spring BOM release to take dependency on 1.0.6, close to the month end(it should be out in a few days, once all the dependent packages release).

@saragluna FYI. When you do release in this month, please upgrade to azure-sdk-bom:1.0.6 in Spring BOMs.


OAI Special Interest Group (SIG) Overview

Overview
This is an overview of the Special Interest Groups (SIG) that have been emerging within the OpenAPI Initiative (OAI), working to provide a simple overview of what SIGs are, how they operate, and how they can contribute to moving forward the conversation around the OpenAPI Specification (OAS). Providing an evolvable document that can help OAI members establish new SIGs, and evolve the conversation around the existing ones.
Types of SIGs
Currently, there are two types of SiGS that have emerged to move forward some aspect of using OAS, with the first one being about establishing and developing specific extensions to OAS, with some eventually becoming a formal part of the specification, or remaining as an extension or overlay to the spec.

Overlays (Repo) (Slack Channel) - SIG focused on defining the overlays specification for OAS.
Security (Repo) (Slack Channel) - SIG focused on moving forward security portions of the specification.
Workflows (Repo) (Slack Channel) - SIG focused on building workflows with multiple APIs using OAS.
Service Level Agreement (Repo) - SIG focused on the SLA extension being developed.
Codegen (Slack Channel) - A SIG focused on moving forward the code generation conversation.
Formats (Repo) - SIG focused on the formats registry effort.
Lifecycle (Repo) (Slack Channel) - SIG focused on defining the API lifecycle around an API being developed using OAS.

The other type of SIG is more focused on the usage of OAS in service of a specific industry, which may eventually contribute changes, extensions, or overlays to OAS, but will be more likely about coordination across OAS usage withinn specific industry.

Travel (Repo) (Slack Channel) - SIG focused on using OAS within the travel industry.

These are just the first wave of SIGs to be formalized in the last six months, with some of them existing in various forms before the door was opened in May of 2021 for groups to be formed using a less formal review process--encouraging the creation of SIGs with as little friction and allowing them to grow organically over time-based upon activity defined by each group.
SIG Building Blocks
These are some of the commonly recommended building blocks to help move each SIG forward in a standardized way, helping provide a common blueprint that SiGs can employ to move forward each conversation and encourage participation within the OAS community.

Champion - Each SIG should have at least one, but ideally two champions who will help lead each SIG, and act as the owner of each group, and supporting discussions..
Github Repository - It is recommended that each SIG should have its own Github Repository, providing a README, issues, projects, discussions, and other solutions for managing work. - Request Github Repo within Spec Slack channel.
Agenda - It is recommended that SIGs utilize Github Issues to manage the regular agenda in a similar way as done with the TDC meetings to move forward the core specification.
Slack Channel - It is recommended that each SIG have its own Slack Channel, providing an asynchronous place to engage in discussion, with emphasis on the public discussion via public Github discussions - Email @ncaidin with LF for setup.
Recurring Meeting - It is common for SIGs to have a weekly or bi-weekly meeting using Zoom or Google Meet, providing a regular time in which SIGs will convene to move the conversation forward.

That represents what is currently in use to manage SIGs. None of these are required but should provide a set of common practices to consider. If there are other things like calendar, document management, and other building blocks in use, please let us know so that we can add to this list and inform each of the existing SIGS, as well as new ones.
Relationship to Other Existing OAI Groups
SIGs are intended to operate independently of the Technical Steering Committee (TSC), marketing group, and ASC steering committee, moving forward at their own speed, providing regular sync with existing groups, and following the process that is already established.

Technical Steering Committee (TSC) - Each SIG has the option to bring regular updates to the weekly TDC meeting, providing a short and concise recap of what has been happening within the SIG. Establishing changes to the spec as an extension or overlay, and then submitting for formal review using the existing TSC proposal process.
Marketing Group - Each SIG has the option to bring regular updates to the weekly marketing meeting, providing a short and concise recap of what has been happening within the SIG. Stories, social media, and other related activities can be suggested to the marketing group for further consideration.
API Specifications Conference - Each SIG has the option to bring regular updates to the ASC planning meetings when in operation, providing a short and concise recap of what has been happening within the SIG.

Designated SIG leadership are encouraged to bring short updates to existing group gatherings as required but should follow existing group rules and processes when it comes to making contributions or requesting attention or resources from a group.
OAI SIG Structure and Process
It was decided in May of 2021 to go with a less formal approach to starting up and operating SIGs to encourage their formation and evolution. The OAI depends on each group champion and leader to define and manage each SIG and contribute to existing OAI projects, groups, and discussions. There is no formal OAI structure or process for how SIGs should operate, with this document being just one attempt at documenting what is currently happening. Neal has created a pull request in the main specification repository for gathering SIG titles, descriptions, and other information. This issue, as well as the supporting the Kanban board is just working to try to continue formalizing and communicating the structure and process for SIGs but does not claim to be the formal process, or is comprehensive--it is just an attempt to capture what is happening in motion.
Like most aspects of the OAI, SIGs are dependent on champions to move things forward and help define what SIGs are and how they add value to OAS and the community. Please share your feedback, corrections, additions, and concerns below, and feel free to add to the project Kanban board, update your SIG's information, or start up a new SIG to move forward with something that matters to you. SIGs reflect a pretty compelling opportunity to move OAS and the OAI community forward in different ways, beyond the core specification development, and marketing activities that have been going on since the forming of the OAI. We look forward to what your SIG can do, and encourage your participation in helping push forward the SIG discussion within the OAI and OAS community.

Some notes from latest SIG planning meeting:
Nick - Workflows

Statement of Work
How We Run Things
How Do We Start Meetings
Github Barrier
Code of Conduct Slide

Ron - Overlays & Formats

A repeat of Questions Already Asked
Document the Process
Discussions are Better Than Issues
Where Does OAI Stand in Relation to SIGS (Owner, Support)
Can Anyone Create SIG?
How do we market the SIGs?
Code of Conduct Page on Github - Need official statement
How should be things licensed?

Overall

Dedicated Page on Site?
Calendar (OpenID.net)?
Google Docs (Shared OAI Area) - Create a Folder
Cross SIG sharing and communication?
Communication Broadcast to SIGs?

My bad. I planned to attend and got sidetracked. Please keep me on the list for the next meeting.
Stu
Stu Waldron
Open Travel Alliance
www.opentravel.orghttp://www.opentravel.org
e<EMAIL_ADDRESS>From: Kin Lane @.>
Sent: Thursday, October 21, 2021 2:19 PM
To: OAI/Projects @.>
Cc: Stu Waldron @.>; Comment @.>
Subject: Re: [OAI/Projects] OAI Special Interest Group (SIG) Overview (#12)
Some notes from latest SIG planning meeting:
Nick - Workflows

Statement of Work
How We Run Things
How Do We Start Meetings
Github Barrier
Code of Conduct Slide

Ron - Overlays & Formats

A repeat of Questions Already Asked
Document the Process
Discussions are Better Than Issues
Where Does OAI Stand in Relation to SIGS (Owner, Support)
Can Anyone Create SIG?
How do we market the SIGs?
Code of Conduct Page on Github - Need official statement
How should be things licensed?

Overall

Dedicated Page on Site?
Calendar (OpenID.net)?
Google Docs (Shared OAI Area) - Create a Folder
Cross SIG sharing and communication?
Communication Broadcast to SIGs?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/OAI/Projects/issues/12#issuecomment-948885306, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUOKRLHBY3ZK26YSMKS6AM3UIBKRDANCNFSM5FKVKSAA.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Unable to Connect to Hugging Face for Model Download in China Mainland

I encountered the following error message related to the inability to connect to Hugging Face for downloading models in China Mainland: 'HTTPSConnectionPool(host='huggingface.co', port=443)'. I made some modifications to the code to address it:https://github.com/xinbinsun/ControlNet/blob/main/README.md

Hi,i encounter this error also. Unfortunately, the provided link is empty.

thanks, i have sloved this question.

thanks, i have sloved this question.

I'm glad I can help you

thanks, i have sloved this question.

can you tell me how to fix it?

just download the model from mirror wedsite like https://hf-mirror.com/


Multiple uploads: If one description is empty, all pictures in batch will have no desc

Summary:
I uploaded 2 photos via multiple uploads. One had a desc, one did not. I expected the one with the desc to have a desc saved, but both photos were uploaded without a desc.
Steps to reproduce:
Upload 2 photos via 2.9 multiple uploads, 1 with desc and 1 without
Device and Android version:
Samsung Galaxy s7 API 26
Commons app version:
2.9-release prodRelease build
Would you like to work on the issue?
Pref not

@misaochan  I have made some changes here.
#2132
I think this will solve the concerned issue.


Expose UI version number in transcend.version

Related Issues

Blocked by https://github.com/transcend-io/airgap.js-types/pull/130
Unblocks https://github.com/transcend-io/main/pull/28484
Links https://transcend.height.app/T-36217

Security Implications
[none]
System Availability
[none]

The reasoning behind this pr is to improve the debugging flow for UI bugs on customers so that we can immediately pinpoint their UI version.


Add Launch Template capability to Spot Fleets

EC2 Spot Fleets can now launch instances from Launch Templates, not just inline Launch Specifications. This adds that functionality to Troposphere.
I ran into a number of cases where the CF documentation didn't make sense, or when tested, didn't agree with CF's behavior -- I've submitted pull requests to their documentation in those cases, and I've written this PR to agree with CF's behavior, rather than the documentation. I'll point those instances out in the PR comments.

Sorry, going through the PRs and missed this one - another was merged with this in it however.  Please let me know if you see any issues, and thanks for the PR (and sorry once again for missing it).

@phobologic No worries, glad the functionality is in.