KeyError: 'feat_static_cat' with

I get a bug when trying to run the deepar estimator with the (as i understand new) system of specifying static categorical features in pd dataframe with one row per time series.
I configure the data set as:
gluonts_val_pre_covid = PandasDataset(
    validation_pre_covid,
    timestamp = "timestamp",
    target=data_parameters['target'],
    static_features = pre_covid_static_cols,
    freq= data_parameters['frequency']
)

with validation_pre_covid a dictionary of pd dataframes, and pre_covid_static_cols a pd dataframe with the same number of rows as the number of keys in the validation_pre_covid dictionary.
The DeepAr estimator is configured as:
estimator_with_features = DeepAREstimator(
    freq=data_parameters['frequency'],
    prediction_length=data_parameters['forecast_length'],
    use_feat_static_cat=True,
    cardinality=[values for key, values in cardinalities_dict.items()],
    trainer=Trainer(epochs=10),
)

but running:
predictor = estimator_with_features.train(gluonts_val_pre_covid)

yields:
KeyError: 'feat_static_cat'.

I'm just trying to follow the framework in the tutorial https://ts.gluon.ai/stable/tutorials/data_manipulation/pandasdataframes.html, but it doesn't seem to work :(

@runesuhr could you try running
print(gluonts_val_pre_covid)

and post the output?

PandasDataset<size=3289, freq=M, num_feat_dynamic_real=0, num_past_feat_dynamic_real=0, num_feat_static_real=5, num_feat_static_cat=0, static_cardinalities=[]>
i smell that there's an issue here, but i'm not quite sure how.

You're getting 5 static real features. Probably all columns of pre_covid_static_cols are numeric. You can check it with
pre_covid_static_cols.dtypes

If you check out the example at https://ts.gluon.ai/stable/tutorials/data_manipulation/pandasdataframes.html#Include-static-and-dynamic-features, some of the columns of the static features data frame are constructed with pd.Categorical. You can also set a column to be categorical with
pre_covid_static_cols[name] = pre_covid_static_cols[name].astype("category")

Ah, thanks a lot! I will try this. (It's late evening here, so I don't have time to run it today, I posted the question at this time as I didn't really expect such a quick answer. MUCH appreciated!)

@runesuhr any news? Feel free to close the issue if the above suggestion does the trick, otherwise we can look into it further

Yes, it worked, thank you very much for the help!


Support IMDSv2 in launch template

This PR adds support for IMDSv2 to the compute EC2 launch template. See the doc for metadata options for more info.

@oavdeev tagging you for visibility : )

can we make it off by default so its backwards compatible? it seems like right now if someone upgrades their deployment using this template, they'll have instance metadata disabled and their metaflow tasks will stop working

For some reason I thought the TF default for http_endpoint was disabled but it's actually enabled - just fixed it. All three variables now default to the TF default so upgrading without overriding them should have no impact.

Hi @oavdeev, is there anything I can do to help release this? We're currently running Metaflow off my fork and that's not nice

Sorry for the delay! I'll cut a release next week

@oavdeev bumping this again :)
Would it make sense to add something like https://github.com/cycjimmy/semantic-release-action to the repo so that releases are cut automatically after merging?

Hey @olivermeyer sorry for the delay, @ob-uk just cut a new release 0.8.0! As for the github action, I think its a good idea eventually but for now we don't have enough automated testing to be cutting releases completely on auto-pilot. Today we do at least some manual testing for each release to make sure it works as expected.

Hey @olivermeyer sorry for the delay, @ob-uk just cut a new release 0.8.0! As for the github action, I think its a good idea eventually but for now we don't have enough automated testing to be cutting releases completely on auto-pilot. Today we do at least some manual testing for each release to make sure it works as expected.

Awesome thanks! And makes sense about testing.


Fixes issue #4

Just fixing the exercise 3 documentation to make it clear that the advertisements() method should return AdvertisementList instead of Iterable<Advertisement>.

Thanks a lot for the pull request.
But please let me state here a disclaimer:

For simplicity reasons not everything that is implemented in our sample solution is documented in the step-by-step exercise description.

The sample solution is only offered to you, in case you get stuck with your own one.


Query results grid resets to row one on switch to another tab/switch back

Execute a query then navigate to/select a row far down results in query grid. Switch to another tab then come back to original window and query results grid is reset to row one and prior selection is lost. Expected behavior would be that the query results stay on row that was previously selected rather than losing selection and going back to top of results.
Version is 0.23.6

Sort of related to #114.

Yes, sounds like they are the same, I'll close mine. Thank you.

I wasn't implying that you should close it, more to state that they can probably be solved in similar ways. :)

Yeah but I'm pretty sure it's the same problem. It sure sounds like it, though #114 doesn't mention the query results grid explicitly. I'll ask about that on #114 and reopen if it's not. Thank you!

I will keep this opened so that we can track the progress of the reset of query editor and the results of query separately.

I'll close as a duplicate to keep the number of active issues more manageable.  https://github.com/Microsoft/sqlopsstudio/issues/114


making NSCompoundPredicate tests compatible with reference platform

It seems as on reference platform predicate classes are not concrete instance, thus doing an alloc/init will not return a copy-able object.
Since our backing implementation is different, it gives us the freedom to do the that.
Changing the test to be compatible with the reference platform.
fix #747 #704

:shipit:

:shipit:

:shipit:

In CI Build

CI Build passed.


Fix the main crate failing to build on Windows

Hello.
Attempting to cargo build the main rust-rosetta crate on Windows currently fails due to several solutions that use Unix-specific constructs. These changes should resolve this.

Gosh darnit! It looks like this also didn't work. :( I'm comfortable merging this if you'd like though!

@Hoverbear, I wasn't expecting the changes to fail, but I had a look at the build error.
Unable to update https://github.com/gtk-rs/glib#bc965ac4

Caused by:
  failed to clone into: C:\Users\appveyor\.cargo\git\db\glib-1ddee14a5a05b311

Given that the other 32-bit build configuration succeeded on the same commit, I think this might be a spurious case of Cargo giving up due to some network error out of our immediate control.
I've also updated the AppVeyor configuration to use shallow cloning, which doesn't directly affect Cargo updates, but should help cloning the main rust-rosetta crate source once as it grows in size. There shouldn't be a problem with merging. However, I'll keep my eye on any future AppVeyor builds failing along the same lines (i.e. via Cargo updates).

@miqid Awesome!!!! :) This is so exciting that we support Windows now! I might need update the readme...


Update Git Submodules On Refresh

When using a Git repo as a backend and that Git repo contains a submodule you can clone the submodules but they are never refreshed.
See https://github.com/spring-cloud/spring-cloud-config/issues/1917#issuecomment-873216819
I think we can use SubmoduleWalk to walk the submodules and update them
https://download.eclipse.org/jgit/site/<IP_ADDRESS>106070339-r/apidocs/index.html

@spencergibb let me know if you think there is a way to make this work today

Not that I'm aware of


FR: Add option to set own interface names

Hi,
we ran into problem with interface name length.
There're some interfaces which reach length over 80 characters, so they are displayed cutted:
(due to limitation of 64 Char in field)
"vNIC 1 (tn-xyz|xy-XYZ-business-intelligence|epg-XYZ-XXX-xyXYZq_b"
Is there any switch to set own interface names, like "vNIC 'interface_number'".
Sync should set automatically (increase) 'interface_number'.
David

Hi Ricardo,
during sync, interfaces are discovered by their real names.
We use ACI, so interface names are long due to name conventions.
examples:
"vNIC 1 (tn-xyz|xy-XYZ-business-intelligence|epg-XYZ-XXX-xyXYZq_b"
"vNIC 2 (tn-xyz|xy-XYZ-business-intelligence|epg-XYZ-XXX-xyXYZq_b"
We need an switch:
use_custom_interface_prefix: true
custom_interface_prefix: 'VM_INT'
So discovery should create following interfaces for discovered VMs:
"VM_INT 1"
"VM_INT 2"
"VM_INT ..."
David

Cisco supports aliases for interface names, so renaming isn't needed anymore.


Issue with the pause menu

Describe your bug here.
You see, if you go into the song pause menu and go into change difficulties, and you press Back, it just searches for "songname-null.json" when it's not supposed to do that and its frustrating when you accidentally go into it and are not meant to change difficulties
Command Prompt/Terminal logs (if existing)
none

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no

Yet another duplicate, already fixed in source


mimic is null

Building Gadgets Version
buildinggadgets-3.16.2-build.22+mc1.19.2
Describe the bug
Viewing a certain item from the building gadgets mod in creative menu or in jei immediately crashes the game.
To Reproduce
Steps to reproduce the behavior: Searching building gadgets in jei or going to building gadgets category in creative menu.
Expected behavior
Not to crash
Screenshots
If applicable, add screenshots to help explain your problem.
Log Files
https://pastebin.com/yE3df5cF
NOTE ON RUBIDIUM
Disabled Embeddium gave the same result.

Sorry that versions no longer supported


Bump version for hotfix

Bump ADS version

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 41.66%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
1
52.04%

extensions/notebook/src/jupyter/serverInstance.ts
4
75.5%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
27863

Relevant Lines:
62305

💛  - Coveralls


[VS Code for Web] Extension readme & changelog aren't displayed after installation

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.86.0
OS Version: Not available, this only happens on VS Code for Web

Steps to Reproduce:

Open https://vscode.dev to use VS Code for Web
Search for extension dragon-archer.paradox-highlight
You may find that the Details and Changelog sections all have content
Install the extension
Switch to any other extension page to refresh the page
Switch back to dragon-archer.paradox-highlight. You will find the Details and Changelog sections are all empty with No xxx avaliable

Note: Since this problem exists even if I disabled the extension, I think perhaps it might be a VS Code issue other than an extension one. However, I tried the same with ms-python.python, it works correctly! Perhaps there's some special rules to write package.json that cause this problem? Here's my package.json for the extension https://github.com/dragon-archer/paradox-highlight/blob/main/package.json

I cannot reproduce it with vscode.dev
Can you please let me know if there are any specific steps I am missing?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


ENH: Add "value" parameter to Stairs.mask and Stairs.where

Describe the solution you'd like
Currently, using Stairs.mask and Stairs.where means making certain values of the step function NaN.
Add "value" parameter to Stairs.mask and Stairs.where which defaults to numpy.nan and masks with this value.
Compare this to
https://pandas.pydata.org/docs/reference/api/pandas.Series.mask.html
https://pandas.pydata.org/docs/reference/api/pandas.Series.where.html
which have an "other" parameter, which defaults to NaN.  We can provide a similar parameter (which takes a number).

closed in #137


Workbox 6: ReferenceError: swDest is not defined

Getting ReferenceError: swDest is not defined when trying to run Workbox 6...
https://stackoverflow.com/questions/67274743/workbox-6-referenceerror-swdest-is-not-defined

(This was answered at https://stackoverflow.com/a/67275374/385997)


Orphan artifact : change the artifactId create a new artifact without delete the old.

Hi All,
I detected a new issue on the apicurio's operator inside openshift.
Inside a CRD of an apicurio artifact, when I change the value of the artifactId field, the operator create a new artifact inside apicurio registry. This behavior of creation is correct. But the old artefact has not been deleted, and It is no longer managed by the operator. The old artefact become an orphan.
So I have a CRD named kafka-sample-kafka-sample-pet-mpusg-1 which contain its spec like this :
spec:
  modifiedBy: ''
  modifiedOn: '2022-09-23T13:08:36+0000'
  name: kafka-sample-kafka-sample-pet-mpusg
  artifactId: com.company.mpusg.test.Pet
  state: ENABLED
  properties: {}
  contentId: 66
  version: '1'
  content: >-
    {"type":"record","name":"Pet","namespace":"com.company.mpusg.test","fields":[{"name":"name","type":"string"},{"name":"age","type":["int","null"]}]}
  type: AVRO
  description: MPUSG pet test
  globalId: 205
  labels:
    - avro
    - kafka
status:
  artifactId: com.company.mpusg.test.Pet
  globalId: 205
  status: ready
  version: '1'

I see it by registry/v2 rest api :
curl https://myregistry.company.com/apis/registry/v2/groups/default/artifacts | jq '.artifacts[].id'
"com.company.mpusg.test.Pet"

I change only the value of the artifactId field.
spec:
  modifiedBy: ''
  modifiedOn: '2022-09-23T13:48:17+0000'
  name: kafka-sample-kafka-sample-pet-mpusg
  artifactId: com.company.mpusg.test.Pet.new
  state: ENABLED
  properties: {}
  contentId: 66
  version: '1'
  content: >-
    {"type":"record","name":"Pet","namespace":"com.company.mpusg.test","fields":[{"name":"name","type":"string"},{"name":"age","type":["int","null"]}]}
  type: AVRO
  description: MPUSG pet test
  globalId: 206
  labels:
    - avro
    - kafka
status:
  artifactId: com.company.mpusg.test.Pet.new
  globalId: 206
  status: ready
  version: '1'

curl https://myregistry.company.com/apis/registry/v2/groups/default/artifacts | jq '.artifacts[].id'
"com.company.mpusg.test.Pet"
"com.company.mpusg.test.Pet.new"

A new artifact is created with the name "com.company.mpusg.test.Pet.new" but the old is always up. When I push a new schema, the new version is applicate only on "com.company.mpusg.test.Pet.new". From the change on the artifactId, the operator loses control over the old one.
Can you analyze ? Thanks for your investigations.

Hi @jsenko
Any news ?
cc @vsevel

any news on this?


Modified tutorial 01 console introduction string

Trac ticket number

There is no ticket assigned to this pr. This modification came from django con workshop in a separated excel file
Branch description
There was a line reffering to unix console. It has been modified by adding a comment extended that other consoles may exists.
Checklist

[x] This PR targets the main branch.
[x] The commit message is written in past tense, mentions the ticket number, and ends with a period.
[ ] I have checked the "Has patch" ticket flag in the Trac system.
[ ] I have added or updated relevant tests.
[ ] I have added or updated relevant docs, including release notes if applicable.
[ ] I have attached screenshots in both light and dark modes for any UI changes.

Since there is no activity and it's not a big change I'm closing the pr.

Hey @Kurara! The lack of activity was due to the Fellows handling other tasks with higher priority (fixing of release blocker issues, security reports, Django 5.1 releases).
With the Django 5.1 final release just issued, I was planning on restarting work on these DjangoCon Europe PRs. If you want, you can re-open and I'll review. But it's also OK if you wish to keep it closed.
Thanks!


[Doom - Downgrade] Ops email change of copy

Only internal email text => merging directly

:pray:


use XDG_DATA_DIRS to locate mime database

I ran into issue https://github.com/mimemagicrb/mimemagic/issues/160. Not all operating systems are using /usr or /opt and XDG_DATA_DIRS was made to avoid hard-coding paths like /usr and /opt. This PR makes use of XDG_DATA_DIRS while still maintaining compatibility with systems that do not have XDG_DATA_DIRS.
On my system XDG_DATA_DIRS looks like:
$ echo $XDG_DATA_DIRS
/nix/store/mcxhdbhz0wqi3icx6lvc33iaggd02v6v-patchelf-0.12/share:/nix/store/wrkla3l0c3hg9m9bp5mvjj7z4xqv54wz-terminator-2.1.1/share:/nix/store/2bqip8j6v2hxpafpsaahfdq851i01nan-gsettings-desktop-schemas-40.0/share/gsettings-schemas/gsettings-desktop-schemas-40.0:/nix/store/fdjrhdgvhic14jg6llvm6vz2jvgnhfl6-gtk+3-3.24.27/share/gsettings-schemas/gtk+3-3.24.27:/nix/store/k75hslc3jrcb8y5rd92saxbxxkg2hb03-desktops/share:/home/bob.vanderlinden/.nix-profile/share:/etc/profiles/per-user/bob.vanderlinden/share:/nix/var/nix/profiles/default/share:/run/current-system/sw/share

Fixes https://github.com/mimemagicrb/mimemagic/issues/160
Possible replacement for https://github.com/mimemagicrb/mimemagic/pull/125

@jellybob could you have a look?

@janko @minad could you have a look? Not sure if you're also maintainers of the project?


[3.1.8-prepare] Use adhoc connection in sql/procedure task

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

(or)
If your pull request contain incompatible change, you should also add it to docs/docs/en/guide/upgrede/incompatible.md

The Related PR: #14631


Cors bug when using Link

Qwik Version
0.12.1
Operating System (or Browser)
Any
Node Version (if applicable)
No response
Which component is affected?
Qwik City
Expected Behaviour
useResource is able to handle cors exactly the same when directly accessing a page or from a Link
Actual Behaviour
On access a page following a Link the useResource shows a cors problem
Additional Information
This is strange because on access directly a page the fetch request is working perfect but when the same function is executed as a result of a page visit from a Link is not working

const reposResource = useResource$<string[]>(({ track }) => {
    track(() => user.auth)

    return getRepositories(user.auth)
  })

export async function getRepositories(token: string): Promise<string[]> {
  const response = await fetch(`http://localhost:3000/repositories`, {
    headers: {
      Authorization:  'Bearer whatever,
      'Content-Type': 'application/json',
       'Access-Control-Allow-Origin': '*',
    },
  })
    .then((res) => res.json())
    .catch((err) => console.log(err))

  return response
}

This always give an error from Link
The most interesting part is if I ignore the error and just return response without catch data is correctly appearing on the app but I st get the cors issue on the console.

you need to add the right CORS headers to the server response, not the request! This is not a problem of Link


Add Vuejs example

I can do that. What do you want inside? The same as the other examples?

Feel free to do something similar or slightly different. I think it should:

Work as a codesandbox link (like the others)
Have a global theme (not sure what the context equivalent is for Vuejs, but can even be imported if needed)
Have a component that is using margin/padding/color from the theme

That said, anything is better than nothing and this would be super helpful IMO

This is an attempt but kinda sucks.
You need a utility to map propTypes (for example, space.propTypes) to Vue props in order to be useful.
Also, I'm not experienced with Vue, today I checked it. It may not be a good solution.

@MarkosKon Thanks for this example, it was pretty much the only one I found on the internet!!! :)
Anyways, I'm not sure if here's the right place to ask my question, but if it is not I will remove it.
I basically reproduced your example in my project, and it works pretty much. The only difference, and I don't understand why, is that all my prop types have a value of undefined in the CSS, yours don't.
I can defined them all to overwrite them and at the same time declare the default values, but in my example you'll see that I have close to 30 properties since I import 4 style-system utilities (layout, space, width, color). Do you see any reason why?

![Screen Shot 2019-10-25 at 8 47 42 AM](https://user-images.githubusercontent.com/3512326/67572428-2c7f9780-f704-11e9-9f68-175996846a9a.png)
![Screen Shot 2019-10-25 at 8 47 26 AM](https://user-images.githubusercontent.com/3512326/67572429-2c7f9780-f704-11e9-8731-0b7a54a0080b.png)
![Screen Shot 2019-10-25 at 8 47 12 AM](https://user-images.githubusercontent.com/3512326/67572430-2c7f9780-f704-11e9-99aa-84c6de0a63b5.png)

@MarkosKon I think I found the issue. The issue happens in all versions of major 5 of styled-system and testing with the latest major 4 (4.2.4) version, the issue disappears.
@jxnblk Do you mind if I open an issue for this?

Closing this due to inactivity. If anyone would like to add an example using Vuejs, feel free to open a PR

thanks for this, ive added an example here on how to do the Box component as a vue single file component. It is annoying having to map the propTypes. But one benefit is the code IntelliSense and completion works, at least in WebStorm it does.
https://github.com/fatlinesofcode/vue-with-styled-system/blob/main/src/components/layout/Box.vue
https://codesandbox.io/s/quirky-boyd-3tmc8?file=/src/components/layout/Box.vue
@carldufourm could you share your proptypes.js file ?

@fatlinesofcode Sure, here it is
https://codesandbox.io/s/affectionate-ganguly-i9ozr?file=/proptypes.js

thanks @carldufourm here's my Box component solution now as a functional component. Looks quite elegant now i think
<template functional>
  <component :is="$options.components.StyledBox" v-bind="props">
    <slot />
  </component>
</template>

<script>
import styled from 'vue-styled-components'
import { space, fontSize, color } from 'styled-system'
import { colorProps, spaceProps, typographyProps } from './propTypes'

const props = {
  ...spaceProps,
  ...typographyProps,
  ...colorProps
}

const StyledBox = styled('div', props)`
  ${space}
  ${fontSize}
  ${color}
`

export default {
  name: 'Box',
  components: {
    StyledBox
  },
  props
}
</script>


Lazy loading on filetype happens before syntax is set?

Hey @Shougo, excellent plugin. There's been a long-standing issue with one of my plugins which I've just been able to reproduce when using neobundle's lazy loading.
My question: given the lazy loading shown below, based on filetype, what do you know of neobundle's ordering when it comes to setting up syntax? The error is happening here and only happens when lazy loading is enabled.
Example config:
  NeoBundleLazy 'jeaye/color_coded', {
      \ 'build': {
      \   'unix': 'cmake . && make && make install',
      \ },
      \ 'autoload' : { 'filetypes' : ['c', 'cpp', 'objc', 'objcpp'] },
      \ 'build_commands' : ['cmake', 'make']
  \}

Here is a trivial (26 line) vimrc which replicates the issue. Note that color_coded can take a while to install, since it downloads libclang. Upon opening a C++ file, one sees [neobundle] Uncaught error while sourcing "color_coded": Vim(execute):E121: Undefined variable: b:current_syntax in function color_coded#enter, line 7

OK.  I will test it.

I cannot test it.
Because, ..
$gvim -u test.vimrc6 test.cpp
 Vim: Caught deadly signal SEGV
Vim: Finished.

It is too bad...

I think it is fixed.

I think color_coded plugin should check the syntax file is already sourced.
Same problem is available in Vundle and other plugin managers.

On Sun, Oct 11, 2015 at 10:43:08PM -0700, Shougo wrote:

I think color_coded plugin should check the syntax file is already
sourced.
Same problem is available in Vundle and other plugin managers.

The issue isn't that syntax has already been sourced, since that would result in b:current_syntax existing. color_coded does rely on the syntax existing, yes, since it needs to invoke ownsyntax on each buffer. I don't see a way around that.

@Shougo If color_coded is crashing for you, please take the time to work with me (or look at the README) so that we can resolve this issue. I can say that, even with the latest neobundle master, lazy loading color_coded still shows that b:current_syntax is set.

A simple test on your end would be to print b:current_syntax here
My guess, based on your crash is that you're using luajit, which doesn't support being embedded in a native shared object (thus is incompatible with color_coded)

If you're not interested in giving color_coded a proper shot, please give 1) a look on your end so you can also verify that b:current_syntax is not yet set.

My guess, based on your crash, is that you're using luajit, which doesn't support being embedded in a native shared object (thus is incompatible with color_coded)

OH, it is bad.  I use luajit based if_lua.

@jeaye OK.  I get it.
You must specify augroup attribute.
						*neobundle-options-augroup*
		augroup		(String)
		Specify an augroup name that the plugin uses for |VimEnter| or
		|GUIEnter| autocmd events.
		Neobundle will call their |VimEnter| or |GUIEnter| autocmds
		automatically when |:NeoBundleSource| is executed.
		Note: You'll want to set this option because some plugins
		rely on autocmds defined for |VimEnter| or |GUIEnter|, but by
		using |:NeoBundleSource| after loading .vimrc, those autocmds
		may get skipped
skipped. Some examples are, "fugitive", "NERDTree",
		and "session.vim".

Because, color_coded uses VimEnter autocmd to load
after/syntax/color_coded.vim.
NeoBundleLazy 'jeaye/color_coded', {
      \ 'build': {
      \   'unix': 'cmake . && make && make install',
      \ },
      \ 'augroup' : 'color_coded',
      \ 'autoload' : { 'filetypes' : ['c', 'cpp', 'objc', 'objcpp'] },
      \ 'build_commands' : ['cmake', 'make']
  \}

Closing.

Thanks for looking into it!


Rename repo to something like "azure-sql-db-django"

So that it will be better for the SEO and also more in line with all the other existing samples

yeah...will do

Done


[WIP] endpoint: Defer 1st labels update until 1st policy realization

Start a controller to delay the update of the labels until we have at
least generated completely one policy for the endpoint.
This allows configuring the init policy for the endpoint completely, in
order to allow enough connectivity for a sidecar proxy to get
configured, which can be required to enforce L7 policy rules as a result
of the labels update.
Signed-off-by: Romain Lenglet<EMAIL_ADDRESS>

This change is

test-me-please

Hand-tested that it works as intented.

test-me-please

In manual testing, I'm hitting a bug in the controller package:
Jun 22 01:05:38 runtime1 cilium-agent[13876]: panic: close of closed channel
Jun 22 01:05:38 runtime1 cilium-agent[13876]: goroutine 1502 [running]:
Jun 22 01:05:38 runtime1 cilium-agent[13876]: github.com/cilium/cilium/pkg/controller.(*Controller).stopController(...)
Jun 22 01:05:38 runtime1 cilium-agent[13876]:         /home/vagrant/go/src/github.com/cilium/cilium/pkg/controller/controller.go:251
Jun 22 01:05:38 runtime1 cilium-agent[13876]: github.com/cilium/cilium/pkg/controller.(*Manager).removeController(0xc4201bdd90, 0xc423040f70, 0xc4231f2201)
Jun 22 01:05:38 runtime1 cilium-agent[13876]:         /home/vagrant/go/src/github.com/cilium/cilium/pkg/controller/manager.go:90 +0x43
Jun 22 01:05:38 runtime1 cilium-agent[13876]: github.com/cilium/cilium/pkg/controller.(*Manager).UpdateController(0xc4201bdd90, 0xc4231f22a0, 0x13, 0xc4231495f0, 0x0, 0x0, 0x0, 0x0, 0x0)
Jun 22 01:05:38 runtime1 cilium-agent[13876]:         /home/vagrant/go/src/github.com/cilium/cilium/pkg/controller/manager.go:65 +0x47f
Jun 22 01:05:38 runtime1 cilium-agent[13876]: github.com/cilium/cilium/pkg/endpoint.(*Endpoint).UpdateLabels(0xc4201bdb80, 0x3c36440, 0xc4202667e0, 0xc423149530, 0xc423149560)
Jun 22 01:05:38 runtime1 cilium-agent[13876]:         /home/vagrant/go/src/github.com/cilium/cilium/pkg/endpoint/endpoint.go:2214 +0x1dc
Jun 22 01:05:38 runtime1 cilium-agent[13876]: github.com/cilium/cilium/pkg/workloads.(*dockerClient).handleCreateWorkload(0xc42000e4a8, 0xc421b0f740, 0x40, 0x126b300)
Jun 22 01:05:38 runtime1 cilium-agent[13876]:         /home/vagrant/go/src/github.com/cilium/cilium/pkg/workloads/docker.go:477 +0x876
Jun 22 01:05:38 runtime1 cilium-agent[13876]: created by github.com/cilium/cilium/pkg/workloads.(*watcherState).syncWithRuntime.func1
Jun 22 01:05:38 runtime1 cilium-agent[13876]:         /home/vagrant/go/src/github.com/cilium/cilium/pkg/workloads/watcher_state.go:133 +0xb5

test-me-please

@aanm no, still working on it.

Start a controller to delay the update of the labels until we have at least generated completely one policy for the endpoint.

What's wrong on updating the labels before generated the first policy?

@aanm The problem can occur when an L7/HTTP policy is imported, then a pod with sidecar proxy is created.
If the labels are updated before the init policy is compiled, the init policy is never in effect. Here’s what happens in this case:

No BPF program is currently installed (no policy has been generated yet), so all traffic is dropped.
We try to generate the pod’s actual policy. Since it has L7/HTTP rules, and the pod is in sidecar proxy mode, we wait for the sidecar proxy to ACK the policy, before we compile and install the BPF program.
Since all traffic is still dropped, the sidecar Envoy proxy can’t connect to Istio Pilot. Therefore, it can’t get configured, so it can’t install the Cilium filters, so it can’t query and ACK the policy configuration from the Cilium agent.
Since the agent never receives an ACK from Envoy, the policy generation fails.
This situation can’t be fixed. We never install any BPF program. All traffic keeps getting dropped.

By waiting until we at least compile the policy for the init policy, before we update the labels, we will at least allow Envoy to connect to Istio Pilot and get configured, so subsequent policy generations can happen.

test-me-please

I nailed the controller bug. I significantly cleaned up the design in the process.

test-me-please

test-me-please

Successful CI build:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/4405/

@rlenglet How is this problem specific to the init phase? Isn't this a generic problem that we can't install an L7 problem one the policy does not allow communication with the Istio control plane? The same will apply if a user loads a regular L3/L4 only policy which does not allow communication to pilot and then loads an L7 policy.

@tgraf Yes, it's specific to the init phase. In your case, it's a user error. The problem I'm solving is quite different. Even if the policies given by users (init policy and actual policy) correctly allow traffic to Istio services (i.e. no user error in this case), we might still prevent the proxy from getting configured, because we drop all traffic until the first policy is completely generated.

@ianvernon I addressed your comments.

test-me-please

CI build failed because of infra:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/4428/execution/node/69/log/
05:18:53 Timed out while waiting for the machine to boot. This means that
05:18:53 Vagrant was unable to communicate with the guest machine within
05:18:53 the configured ("config.vm.boot_timeout" value) time period.
05:18:53
05:18:53 If you look above, you should be able to see the error(s) that
05:18:53 Vagrant had when attempting to connect to the machine. These errors
05:18:53 are usually good hints as to what may be wrong.
05:18:53
05:18:53 If you're using a custom box, make sure that networking is properly
05:18:53 working and you're able to connect to the machine. It is a common
05:18:53 problem that networking isn't setup properly in these boxes.
05:18:53 Verify that authentication configurations are also setup properly,
05:18:53 as well.
05:18:53
05:18:53 If the box appears to be booting properly, you may want to increase
05:18:53 the timeout ("config.vm.boot_timeout") value.

test-me-please

test-me-please

@rlenglet I still don't understand the difference between init and non-init.

Istio is deployed
Pods are started with injection enabled
L3 only policy is loaded
L3-L7 policy is loaded which also includes access granted to istio-system
Deadlock

@tgraf Your case can be fixed by modifying the policy. The case I'm fixing here can only be fixed by either disabling policy enforcement, or restarting the pod.

@tgraf In your case, the policy loaded in step 3. is incorrect (assuming that you meant that it doesn't allow egress to istio-system). In my case, all the policies (the init policy as well as the actual pod's policy) are correct. They all allow egress to istio-system.

@tgraf And in your case, we would typically NOT deadlock. Assuming that egress to istio-system is allowed before step 3., i.e. we have a chance to install a policy that allows egress to istio-system, the proxy can get initialized and get at least one Cilium filter installed. As long as at least one Cilium filter has been installed, for ingress or egress traffic, Envoy will ACK policies from Cilium, and we wouldn't deadlock.
The problem I'm fixing here, is that in some cases we don't even have a chance to install even one Cilium filter, because Envoy can't get configured at all.

Reviewed 3 of 5 files at r2, 1 of 4 files at r4, 3 of 3 files at r5.
Review status: all files reviewed, 3 unresolved discussions (waiting on @aanm and @ianvernon)

Comments from Reviewable

How can a policy be "incorrect"? The user loads a number of policy yamls, one of them is the L3 egress to allow to istio-system, another policy might be loaded first and will be generated on the endpoint. The user might also remove and re-add the policy and we will re-generate endpoints in between. Are you assuming that the policy allowing to istio-system is always preloaded before any pod with injection and is never removed?

If the user wants to use Cilium with Istio sidecars, there should be a policy allowing egress DNS and egress TCP to istio-system. We can't synthesize those policies for the user.

If the user wants to use Cilium with Istio sidecars, the user must import policies that allow egress DNS and egress TCP to istio-system. We can't synthesize those policies for the user.

I understand and agree but you make further assumptions. You assume that the no L7 policy is ever loaded before access to the istio-system has been implemented. I'm not sure how we can expect this if we allow deletion and re-addition of policies.
We can safely apply and commit all L3/L4 policies which do not contain L7 rules in a initial phase before applying all other policies to solve the deadlock. It will fix the problem throughout the lifecycle of policies.

I understand and agree but you make further assumptions. You assume that the no L7 policy is ever loaded before access to the istio-system has been implemented. I'm not sure how we can expect this if we allow deletion and re-addition of policies.

That is not true. I only assume that the init policy doesn't contain L7 HTTP rules.

That is not true. I only assume that the init policy doesn't contain L7 HTTP rules.

@rlenglet OK, then please walk me through the following two use cases. It is still unclear to me:

User runs Istio and Cilium in sidecar mode without any Cilium policies loaded at first and then loads L3-L7 policies which includes a policy to enable egress to DNS and istio-system as well as L7 policies.
User deletes and re-adds the policy allowing egress to istio-system while an L7 policy is in place.

Successful CI build: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/4466/

test-me-please

CI build failure due to provisioning:
https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/4757/
00:32:53 K8sValidatedPolicyTest [BeforeEach]
00:32:53 /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:344
00:32:53   Basic Test
00:32:53   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:344
00:32:53     checks all kind of Kubernetes policies
00:32:53     /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:376
00:32:53
00:32:53
00:32:53             ===================== ERROR - VM PROVISION FAILED =====================
00:32:53
00:32:53             Unable to provision and start VM "k8s1-1.10": exit status 1", vm, err
00:32:53
00:32:53             =======================================================================
00:32:53
00:32:53
00:32:53     /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:460

test-me-please

Build link: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/4761/
Build failure is due to an error provisioning the VM:
==> k8s1-1.10: Running provisioner: ipv6-config (shell)...
    k8s1-1.10: Running: inline script
==> k8s1-1.10: Running provisioner: shell...
    k8s1-1.10: Running: inline script
==> k8s1-1.10: Running provisioner: file...
==> k8s1-1.10: Running provisioner: shell...
    k8s1-1.10: Running: /tmp/vagrant-shell20180707-2293-1zdusb.sh
    k8s1-1.10: updating /etc/resolv.conf
    k8s1-1.10: beginning trying up to 10 times function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
    k8s1-1.10: ***************************************
    k8s1-1.10: *
    k8s1-1.10: *
    k8s1-1.10: * on attempt 0 of function "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg"
    k8s1-1.10: *
    k8s1-1.10: *
    k8s1-1.10: ***************************************
    k8s1-1.10: --2018-07-07 03:33:07--  https://packages.cloud.google.com/apt/doc/apt-key.gpg
    k8s1-1.10: Resolving packages.cloud.google.com (packages.cloud.google.com)...
    k8s1-1.10: <IP_ADDRESS>, 2607:f8b0:4006:811::200e
    k8s1-1.10: Connecting to packages.cloud.google.com (packages.cloud.google.com)|<IP_ADDRESS>|:443...
    k8s1-1.10: connected.
    k8s1-1.10: HTTP request sent, awaiting response...
    k8s1-1.10: 200 OK
    k8s1-1.10: Length: 1326 (1.3K) [application/octet-stream]
    k8s1-1.10: Saving to: 'apt-key.gpg'
    k8s1-1.10:
    k8s1-1.10:      0K .
    k8s1-1.10:
    k8s1-1.10: 100%  617K=0.002s
    k8s1-1.10: 2018-07-07 03:33:07 (617 KB/s) - 'apt-key.gpg' saved [1326/1326]
    k8s1-1.10: running of "wget https://packages.cloud.google.com/apt/doc/apt-key.gpg" successful
    k8s1-1.10: Warning: apt-key output should not be parsed (stdout is not a terminal)
    k8s1-1.10: OK
    k8s1-1.10: Disabling crio CNI bridge
    k8s1-1.10: removed '/etc/cni/net.d/100-crio-bridge.conf'
    k8s1-1.10: removed '/etc/cni/net.d/200-loopback.conf'
    k8s1-1.10: Reading package lists...
    k8s1-1.10: E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
    k8s1-1.10: E: Unable to lock directory /var/lib/apt/lists/
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Trying again.

test-me-please

Successful CI build: https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/4763/


User Authentication Prompt button says "restart now" when prompted after scheduling restart for later date/time

I noticed after I scheduled a restart for a later date/time, the user authentication prompt that displayed to enter a password read "restart now" for the button text. I thought it may cause some confusion and  since it won't be restarting until later at the scheduled date/time. Perhaps in that scenario the button could just say "OK" or "Schedule"

This was resolved in the latest build... thanks!
https://github.com/Macjutsu/super/releases/tag/v5.0.0-beta3


A proposal on monad which prohibits exceptions

Exceptions are evil, right? However yet there is no standard way of protecting from them when dealing with IO. The "errors" library proclaims the EitherT e IO r idiom as an alternative to exception-based control-flow, however it does not protect the user from still getting the exceptions thrown by the wrapped IO computation. I propose defining a new monad, which will serve as a general replacement of IO, to solve that problem. Following is a sketch of my idea:
module EIO (EIO, liftIO, liftIO') where

-- |
-- A monad for 'IO' computations,
-- which prohibits exceptions in favour of a cleaner 'EitherT'-based approach.
--
-- When executed it returns a computation,
-- which has all the exceptions wrapped by the 'EitherT' monad.
-- It however rethrows the async exceptions of the @base@ package
-- for the reasons of general compatibility with the platform.
--
-- Note that it intentionally does not derive 'MonadIO'.
-- Instead it provides specialized 'liftIO' and 'liftIO'' functions.
newtype EIO e r = EIO { run :: EitherT e IO r } deriving (Functor, Applicative, Monad)

-- |
-- A specialized version of @MonadIO.'Control.Monad.IO.Class.liftIO'@,
-- which catches exceptions and forces to adapt them to the @EIO@ monad.
-- It catches all exceptions, except for asynchronous ones of the @base@ package.
liftIO :: (SomeException -> e) -> IO r -> EIO e r
liftIO f = EIO . fmapLT f . syncIO

-- |
-- A version of 'liftIO' for cases
-- when any exception thrown from the computation to be lifted
-- is considered a bug.
liftIO' :: IO r -> EIO e r
liftIO' = liftIO $ error "An IO action lifted to EIO throws an exception"

Now, of course, it is implied that this API should be extended with adaptations of many functions of the errors library or be otherwise provided with support for them.
I am not sure whether this proposal is fit for the purposes of the "errors" library. Possibly it should be developed as a separate project. However I want to discuss it with you and get you involved.

But, either way, same or different, would be nice to see something make it into 2.0 which I gather is coming soon?

I will add this after the transition to 2.0

Ok

Happy new year!  Wondering if there's still interest in this :)

Yes!  I will try to get to this soon.  Thanks for the reminder

BTW, @singpolyma please release the update, which we've discussed on your tracker.

So I was doing a first pass at implementing this and realized that the use of UnexceptionalIO does cause one issue, which is that there is no mtl-style type class for the UnexceptionalIO monad.  I ran into this issue when attempting to generalize tryIO, whose current type signature looks like this:
tryIO :: MonadIO m => IO a -> ExceptT Ex.IOException m a

@singpolyma Would you consider adding such a class?  If you do, I might suggest naming the class Unexceptional, so then the type of tryIO would be:
tryIO :: Unexceptional m => IO a -> ExceptT IOException m a

so, it would be:
class Unexceptional m where
    liftUIO :: UIO a -> m a

instance Unexceptional IO where
    liftUIO = runUnexceptionalIO

and similar?  I'll do that, as well as the default-name-to-UIO discussed previously

please check that my current master works for you and then I will release it

Alright, this worked great!  I'll upload this to Hackage tomorrow if nobody has any remaining objections

Looks good!  I've put 0.3.0 for unexceptionalio on hackage

Cool! :)

Alright, this is on Hackage as errors-2.1.0


rocAL - Prefetch queue depth python example

Reintroduce the python example
Update the python script to use latest rocal python API
Update README

@fiona-gladwin can you check the codacy errors?

@fiona-gladwin can you check the codacy errors?

@kiritigowda can be merged after this


getPoolByCoins Fetch failed

async function getPoolByCoins() {
const coinA = '0x5d4b302506645c37ff133b98c4b50a5ae14841659738d6d733d59d0d217a93bf::coin::COIN'
const coinB = '0xc060006111016b8a020ad5b33834984a437aaa7d3c74c18e09a95d48aceab08c::coin::COIN'
const pools = await testnetSDK.Pool.getPoolByCoins([coinA, coinB])
console.log('find pools by cointypes', pools)

}
getPoolByCoins()
can not get the PoolInfo by Coins i don't know what reason casued this problem
and my node js is follow the docs , my network is well
please tell me the true reason

 const url = this._sdk.sdkOptions.swapCountUrl!
    const response = await fetch(url)
    let json
    try {
      json = await response.json()
    } catch (e) {
      throw new ClmmpoolsError(`Failed tp [arse response from ${url}].`, RouterErrorCode.InvalidSwapCountUrl)
    }
    const pools = json.data.pools
    if (!pools || pools.length === 0) {
      throw new ClmmpoolsError(`Failed tp [arse response from ${url}].`, PoolErrorCode.PoolsNotFound)
    }

   const poolAddresses = []
    for (const pool of pools) {
      if (coins.includes(pool.coin_a_address) && coins.includes(pool.coin_b_address)) {
        if (feeRate != null) {
          if (pool.object.feeRate === feeRate) {
            poolAddresses.push(pool.address)
          }
        } else {
          poolAddresses.push(pool.address)
        }
      }
    }

pool.address is missing in pool object


Add GeoJsonReader.readToGeometryRDD example to the docs

Expected behavior
Example how to read geojson RDD as described here just like the shapefileReader
Actual behavior
Steps to reproduce the problem
Settings
GeoSpark version = 1.2.0
Apache Spark version = ?
JRE version = 1.8?
API type = Scala or Java?

Thank you for the effort of writing such a great framework. There is really a big demand in the Spark community.
I have tried to set up a small example using the stable release based on the tutorial but there are several false information in it.

GeoJsonReader does not exist in Maven central (org.datasyslab.geospark.formatMapper) under version 1.1.3
GeoSparkSQL does not have the version 1.1.3 in Maven, only 1.1.1
There is no JavaDoc for version 1.1.3 under http://www.public.asu.edu/~jiayu2/geospark/javadoc/ and version 1.1.2 does not conform with the Maven Repo.

It would be important to mention that the Tutorial is for the SNAPSHOT and not for the stable release. I wasted so much time, trying to figure out, what the problem is.

@ps-spark

All GeoSpark stable releases are hosted on Maven Central including GeoSparkSQL 1.1.3.
https://mvnrepository.com/search?q=geospark
Please make sure you use the correct Maven coordinate.

SNAPSHOT version can also be used directly in POM.xml or build.sbt
http://datasystemslab.github.io/GeoSpark/download/GeoSpark-All-Modules-Maven-Central-Coordinates/#snapshot-versions

GeoSpark-core 1.1.3 has the same API with 1.1.2. But thanks for reminding me.

I would suggest you use GeoJSONReader provided in 1.2.0-SNAPSHOT. Its API won't change and it is easier for you to use. BTW, thanks for your suggestion. I will figure out a way to include docs for different versions.


Create BasicStructure

Adding a basic structure for beginners in HTML

that's to simple try different one!


No templates matched the input template name: blazorwasm.

Describe the bug
No blazorwasm template. I have tried to create new project blazorwasm but via Visual Studio I have only one option - Blazor Server App. Via console I have the same situation.

No templates matched the input template name: blazorwasm

.NET Core SDK (reflecting any global.json):
Version:   3.0.100-preview8-013656
Commit:    8bf06ffc8d
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.17134
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\3.0.100-preview8-013656\
Host (useful for support):
Version: 3.0.0-preview8-28405-07
Commit:  d01b2fb7bc
.NET Core SDKs installed:
2.1.700 [C:\Program Files\dotnet\sdk]
2.1.801 [C:\Program Files\dotnet\sdk]
2.2.301 [C:\Program Files\dotnet\sdk]
3.0.100-preview8-013656 [C:\Program Files\dotnet\sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.0.0-preview8.19405.7 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.0.0-preview8-28405-07 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.0.0-preview8-28405-07 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Expected behavior
Create new project
Screenshots

You need to run the following command on the command line to get the blazorwasm template:
dotnet new -i Microsoft.AspNetCore.Blazor.Templates::3.0.0-preview8.19405.7

After that you should see it when you run
dotnet new --help

From the command-line, use the --hosted param to create a WebAssembly project with Server project and Shared-Project like this
dotnet new blazorwasm -o MyFirstWasmApp --hosted

Closing as answered by @thomasclaudiushuber

When I attempt to do dotnet new -i part, I get bash: $'\302\226dotnet': command not found
Running Windows 10 , preview8 and latest VS preview on git-bash

Latest template version can be checked here:
https://docs.microsoft.com/en-gb/aspnet/core/blazor/get-started?view=aspnetcore-3.0&tabs=visual-studio
Still in preview for now:
dotnet new -i Microsoft.AspNetCore.Blazor.Templates::3.0.0-preview9.19465.2

When will formal release published?


Grouping (libGDX) related gradle tasks together sensibly

As seen in https://github.com/libgdx/libgdx/issues/7418, there can be some light confusion on which Gradle tasks are actually relevant to run in the context of a libGDX project. Thinking back many years when I didn't understand big words like Gradle myself, I can vaguely remember similar confusion, especially from the perspective of an out-of-the-box expectation.
It might make sense to ensure some sort of structure for tasks on the implementation level (i.e. beyond the documentation), so that tooling like an IDE can integrate more easily and beginners can just get started, i.e. improve the onboarding experience.
From a quick sample over platforms/Lwjgl3.kt and platforms/Android.kt I couldn't see that the tasks defined in there have configured a group or definition.

A structure I could see work is something like

libgdx
libgdx-html
libgdx-desktop
...
for the 'public' API, and then
libgdx-internal
libgdx-html-internal
libgdx-desktop-internal
...
for the 'private' API (if needed).

I am currently not really familiar with the whole task grouping details of Gradle and only argue from the point of view of the consumer.

If groups turn out to only 1-2 items each, a better structure might be:

libgdx

desktop:dist
html:dist
...

i.e. only have one libGDX group with all relevant base tasks.

So the task grouping now (which only applies in IDEs, and Android Studio makes the task list harder to see) mostly uses the defaults. run is under lwjgl3/application. jar is under lwjgl3/build (it should be what dist calls on LWJGL3). The HTML tasks have superDev under html/gwt if I remember correctly, but dist is under html/other. I don't know if there's a way to group tasks from different projects in one parent group. I'm not sure if we can move important tasks like run from out of application, since that's created by the application plugin. We could create a synonymous task with a different name and group, like how jar and dist work.
I barely know how much of Gradle works myself, so I haven't actually put a task into a group yet. I figure it shouldn't be too hard... I am reluctant to move existing tasks where people are used to them, so new aliases in groups may make more sense.


Crash in the SSLSessionData::usePrivateKeyBuffer

http://sentry.adguard.com/adg/adguard-android-rs/issues/5909/
Might be related:
http://sentry.adguard.com/adg/adguard-android-rs/issues/5854/

Corrupted heap?

Might be related as well:
http://sentry.adguard.com/adg/adguard-android-rs/issues/5916/


Encoding issue

Dbeaver <IP_ADDRESS>112271055 (Portable version) on Windows Server 2016 Standard connecting to Teradata 17.05
I don't know how to fix this codification issue in the table view. I tried changing the connection charset.

Hello @ClodoaldoPinto
Could you please check the newest DBeaver version? You can download it here: https://dbeaver.io/download/

Hello @ClodoaldoPinto
Could you please check the newest DBeaver version? You can download it here: https://dbeaver.io/download/

Same problem with 23.0.1 which is the last in portable

Hello @ClodoaldoPinto,
Can you please send a screenshot of this page?

Hello @ClodoaldoPinto,
Can you please send a screenshot of this page?

Hello @ClodoaldoPinto,
Can you please send a screenshot of this page?

Thank you. That fixes it.


Titration calculator

Description
A Titration Calculator is a valuable tool in chemistry that helps determine the concentration of an unknown solution by using a solution of known concentration (the titrant). The process of titration involves adding the titrant to the analyte (the solution with unknown concentration) until a reaction is complete, which is usually indicated by a color change (if an indicator is used) or reaching an endpoint measured by a pH meter or other means.
Key Components of a Titration Calculator
Titrant Concentration (C₁): The concentration of the solution of known concentration, usually expressed in moles per liter (M).
Volume of Titrant (V₁): The volume of the titrant added to reach the endpoint of the titration, measured in liters (L) or milliliters (mL).
Analyte Volume (V₂): The volume of the solution with the unknown concentration being titrated, also measured in liters (L) or milliliters (mL).
Reaction Stoichiometry: The balanced chemical equation of the reaction between the titrant and the analyte. It provides the mole ratio between the reactants.
Endpoint: The point in the titration process where the reaction is complete, often indicated by a color change or pH change.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a GSSOC'24 contributor.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

@Rakesh9100 sir, can you please assign this to me

Go ahead @mahek0620


SPIKE: UI Guide for Freemium user

Child of #994
As a Product Owner I want a user guide on Tempus, which would prompt a new user to take actions in Tempus, so that the user can navigate and use through Tempus.
Some of the standard practices to consider while implementing the UI guide:
-> Hierarchy. Set a clear hierarchy on the screen. One thing should clearly be the most important (i.e. larger, more colorful). If other things are on the screen, then they should clearly be less important (i.e. less contrast, less space around them). A lot of design mistakes can be cleared up by answering "What is the most important thing here? What is second and third?"
-> Colors. Start with one color plus light and dark grey. Add another color if you want to. You could add a third, but more than three colors is usually unnecessary. Two-to-six shades of light and dark grey will usually be enough. Avoid shades of grey in the middle range.
-> Typography. Establish a clear size hierarchy. As a rule of thumb, have three basic sizes: headline, title, and body (regular) size. The font-size menus in word processors show certain numbers (18, 36, 64 etc.) because their ratios go well together, so that is a good place to pick from.
Iconography. Icons should generally be a muted single-color (gray, faded colors) and not be too eye-catching unless they are actions or meant to draw attention.
-> Spacing. Make sure you to tighten up spacing of elements. Spacing on the top and bottom should be consistent. Pay attention to proper spacing between elements as well.
-> Alignment. Make sure elements are aligned to a grid. In other words, each view should be aligned to surrounding elements (i.e text to the middle or edge of an image). Here is a useful exercise: Pick the left edge of any object in a design. Now draw a vertical line from the top to the bottom of the screen, aligned with that edge. Now do that for every element on screen, unless it already rests on a line. How many lines do you end up with? Try to reduce that number by aligning elements to the same vertical lines.
-> Information. Present only the information that is necessary in a given moment. Having multiple pieces of text that are all near each other, or several items that are exactly the same size color and style, is usually not a good practice.
Tabs. Tabs should be a consistent with the background color of the Toolbar above them.

Shepherd Tool For user guide is an extensive library for creating a tour guide for  the applications.
Dependency needed :- Tippy.JS for animations.
Installation Command:- npm install shepherd.js --save
Import the library into your code and create a tour by adding an array of steps .
Following is the Documentation link which gives the API resource:-
https://shipshapecode.github.io/shepherd/
Shepherd also provide wrapper code for angular named angular-shepherd, you can find the github repo here:-
https://github.com/shipshapecode/angular-shepherd ( Compatible to Angular 6 and 7), apart from that they also provide wrappers for ember,recat and vuejs.
Additional Link for steps describing the usage:-
https://code.tutsplus.com/tutorials/how-to-build-a-user-tour-with-shepherd-in-javascript--cms-28509


migrate Mongoose to Prisma

remove (currently comment out) all usage of mongoose(MongoDB) and replace it with Prisma(PostgreSQL)

it is vary nice, prisma >>> mongoose

@amitojsingh366 there ya go 🙃

@amitojsingh366 there ya go 🙃

nice 🙃


Enhance loading bars component with additional (optional) text

Types of changes

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

Checklist:

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING and other relevant documents.

Description
fix(course): implement "Is loading..." - Message and place loading-icon in centre
Screenshots (if appropriate):

is changed

V3: changed (again)


Get rid of code under BUSL license

Description
Fixes #3078.

TODOs
Read the Gruntwork contribution guidelines.

[ ] Update the docs.
[ ] Run the relevant tests successfully, including pre-commit checks.
[ ] Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.
[ ] Include release notes. If this PR is backward incompatible, include a migration guide.

Release Notes (draft)

Added / Removed / Updated [X].
Migration Guide

@yhakbar, thanks for the review!

Resolved in v0.57.6 release.


Avoid static state based on current classloader

I could be wrong, but when doing things like ClassReaders.reader = Some(new DefaultJaxrsApiReader) we rely on defining some static state, actually based on the classloader that loaded the ClassReaders class.
This become cumbersome when using swagger into exotic scenarios, like preparing a plugin for a build system like gradle. Now the swagger plugin is loaded by the build system classloader, but the built application defines some custom code overriding default swagger behavior (like adding ModelConverters for specific classes and so on): since the customization code MUST be loaded through a dedicated classloader (in order to load the classes that have just been compiled) gaining access to all the needed libraries, it needs to be in a classloader hierarchy separated from the build system one.
So every override of swagger behavior performed by the custom code is done on the class copies loaded by the separate classloader, but this way - as soon as the execution returns to the plugin - every customization is lost (as it is doesn't share the same copy of classes as the customization code).
Wouldn't it be better having a configurable swagger context that can be passed as needed? i.e. a SwaggerContext populated with all the needed objects. This way you could have more that a swagger configuration per JVM/classloader and avoid duplicate static state issues

@fehguy - isn't this part of 1.5 already?

I believe this is fixed now.


Fix worker metrics in 2.x

Metrics were broken in a couple ways - the identifier for the service port was incorrect due to an incomplete identifier change, and workers were not actually incrementing any of the metric counters.  Fixed by incrementing counters in datum.go.  Also changed the worker metrics to use promauto to remove a little boilerplate.
Fixed #6809 and #6811

can we get this pulled into the next RC?

@tybritten - this has been cherry-picked into 2.0.x, it should be in the next RC


Add Amplify deployment to NextJs example [reopened]

Reopen PR #363

Great work @guiyom-e 🎉
Let me know if everything is working as expected, and if it is we can merge 😃

Hi @adriencaccia !
I have just tested to deploy swarmion-with-next project with Amplify, it is working properly!


Newer versions do not have an ARM build

Hello, I tried using docker-lirc-watcher on a Raspberry Pi 3 running latest Raspbian (buster). I used docker-compose with your example, however every attempt to run it gave me several errors:
lirc    | standard_init_linux.go:219: exec user process caused: exec format error
After some googling, it looks like it might be because the later versions of docker-lirc-watcher are only being built with the amd64 architecture. I looked at https://hub.docker.com/r/pilotak/lirc-watcher/tags?page=1&ordering=last_updated to see what was available.
After I changed the tag from :latest to :1.0.6 the container seemed to work although it is using 100% CPU, an issue I think you fixed on later versions so maybe I'll try building the current version myself.. Just thought I would let you know. Otherwise, thanks for the hard work!

For those interested, I was able to build the latest:
docker build https://github.com/pilotak/docker-lirc-watcher.git -t lirc-watcher
And then I modified my docker-compose.yml to: image: lirc-watcher

For those interested, I was able to build the latest:
docker build https://github.com/pilotak/docker-lirc-watcher.git -t lirc-watcher
And then I modified my docker-compose.yml to: image: lirc-watcher

It's being cross compiled for raspberry pi. But I will double check that

It's being cross compiled for raspberry pi. But I will double check that

@brainrecall Fixed
Thanks for spotting it, this kind of error was in all of my docker images you can try tag latest or 1.0.10

@brainrecall Fixed
Thanks for spotting it, this kind of error was in all of my docker images you can try tag latest or 1.0.10

Thanks, new images look good!

Thanks, new images look good!


Disable validation-webhook daemonset for managed clusters

When running the node density workloads on managed clusters, starting
with 4.10.5 on ROSA, we are seeing an error like "admission webhook
"regular-user-validation.managed.openshift.io" denied the request" when trying add a label to a
node directly by using oc label node. The recommended way to add labels
to nodes on managed ROSA clusters is by editing the machinepool.
However, the Default machinepool cannot be edited to add labels and we
see an error like "Labels cannot be updated on the Default machine pool".
The only way to add a label is by disabling the
validation-webhook daemonset and thereby admission cotnrol in the
openshift-validation-webhook project that only exists on managed services
clusters. We disable the daemonset by adding a fake nodeSelector before
labeling the nodes and remove thenodeSelector after unlabeling the nodes.
Adding a nodeSelector on top of the existing nodeAffinity means that both
the conditions needs to be met for a pod to be scheduled. Also by adding
the nodeSelector, the spec is not overwritten during reconcillation whereas
changes to nodeAffinity are being overwritten.
Signed-off-by: Sai Sindhur Malleni<EMAIL_ADDRESS>Description
Fixes

When running the node density workloads on managed clusters, starting with 4.10.5 on ROSA, we are seeing an error like "admission webhook "regular-user-validation.managed.openshift.io" denied the request" when trying add a label to a node directly by using oc label node. The recommended way to add labels to nodes on managed ROSA clusters is by editing the machinepool. However, the Default machinepool cannot be edited to add labels and we see an error like "Labels cannot be updated on the Default machine pool". The only way to add a label is by disabling the validation-webhook daemonset and thereby admission cotnrol in the openshift-validation-webhook project that only exists on managed services clusters. We disable the daemonset by adding a fake nodeSelector before labeling the nodes and remove thenodeSelector after unlabeling the nodes. Adding a nodeSelector on top of the existing nodeAffinity means that both the conditions needs to be met for a pod to be scheduled. Also by adding the nodeSelector, the spec is not overwritten during reconcillation whereas changes to nodeAffinity are being overwritten.
Signed-off-by: Sai Sindhur Malleni<EMAIL_ADDRESS>Description
Fixes

curious, why do we need to label a node?

When running the node density workloads on managed clusters, starting with 4.10.5 on ROSA, we are seeing an error like "admission webhook "regular-user-validation.managed.openshift.io" denied the request" when trying add a label to a node directly by using oc label node. The recommended way to add labels to nodes on managed ROSA clusters is by editing the machinepool. However, the Default machinepool cannot be edited to add labels and we see an error like "Labels cannot be updated on the Default machine pool". The only way to add a label is by disabling the validation-webhook daemonset and thereby admission cotnrol in the openshift-validation-webhook project that only exists on managed services clusters. We disable the daemonset by adding a fake nodeSelector before labeling the nodes and remove thenodeSelector after unlabeling the nodes. Adding a nodeSelector on top of the existing nodeAffinity means that both the conditions needs to be met for a pod to be scheduled. Also by adding the nodeSelector, the spec is not overwritten during reconcillation whereas changes to nodeAffinity are being overwritten.
Signed-off-by: Sai Sindhur Malleni<EMAIL_ADDRESS>Description
Fixes

curious, why do we need to label nodes?
I assume this is used for the old node-density implementation available in e2e-benchmarking, the implementation based on the kube-burner's OCP wrapper doesn't need to label nodes anymore.
Rather than keep fixing and updating the old implementation we should encourage users to use the new implementation

Oh, I didn't realize that was the case, thanks for surfacing that.


How can I override Model and ModelSchema to appear in snake case instead of simple Java property Names?

@dilipkrish I got a problem with CAMEL_CASE_TO_LOWER_CASE_WITH_UNDERSCORES, swagger core serialize all its properties too, Ex:

"basePath" in Swagger Object --> "base_path"
"operationId" in Operation Object --> "operation_id"
This issue lead to my swagger UI could not render the whole documentation Api
spec-converter.js:362 Uncaught TypeError: Cannot read property '$ref' of undefined

And also the error message from Swagger UI make me confusing
thanks

@mrkingdom75 that should not be the case. what version of springfox are you using and could you please create a new issue as this ☝ one is really old

thanks @dilipkrish, I will file a new issue


Imbued rings don't count for boost

For example Berserker Ring gives a boost for Giant Mole but Berserker Ring (i) doesn't.

solved with similar items


egui_glow:  egui_glow.paint(gl_window.window()); painting the UI causes everything to be brighter

Problem
Using the egui_glow.paint(...); function to render the UI causes absolutely everything to be brighter in the gl context.
To Reproduce
This bug is present in the only egui_glow example - https://github.com/emilk/egui/blob/master/crates/egui_glow/examples/pure_glow.rs.
Screenshots

OS: Windows 10

It seems to me gamma isuue.


[BUG]:

Describe the bug
After starting translation with LibreTranslate plugin  I'm continiously getting error:
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
    at Client_PG.acquireConnection (/srv/app/node_modules/knex/lib/client.js:312:26)
    at runNextTicks (node:internal/process/task_queues:61:5)
    at listOnTimeout (node:internal/timers:528:9)
    at processTimers (node:internal/timers:502:7)
    at async Runner.ensureConnection (/srv/app/node_modules/knex/lib/execution/runner.js:287:28)
    at async Runner.run (/srv/app/node_modules/knex/lib/execution/runner.js:30:19)
    at async Object.execute (/srv/app/node_modules/@strapi/database/lib/query/query-builder.js:481:22)
    at async Object.count (/srv/app/node_modules/@strapi/database/lib/entity-manager/index.js:199:19)

To Reproduce
Steps to reproduce the behavior:

Go to '/admin/plugins/translate'
Click on 'Translate' in the row 'Company' and column 'ru'

Expected behavior
Translation should be done of all set of untranslated records without errors.
System:

OS: macos
Browser firefox
Versions:

strapi: 4.7.1
strapi-plugin-translate: 1.1.1
provider<EMAIL_ADDRESS>Other Strapi plugins:

<EMAIL_ADDRESS>
Plugin.js config
  // ...
  translate: {
    enabled: true,
    config: {
      // Choose one of the available providers
      provider: 'libretranslate',
      // Pass credentials and other options to the provider
      providerOptions: {
        // your API key - required and wil cause errors if not provided
        apiKey: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx',
        // api url - required
        apiUrl: 'https://translate.somesite.com/',
        // maximum number of requests per minute - optional, default is `undefined` => no limit
        apiMaxRPM: 40,
        // maximum number of chars per request - optional, default is `undefined` => no limit
        apiMaxChars: 1234,
        // maximum number of texts per request
        apiMaxTexts: 55,
        // manually overwrite the Strapi Locale to LibreTranslate Locale mapping.
        // default is the string before the `-` character for every locale
        localeMap:{ }
      },
      // other options ...
    },
  },
  // ...

Database.js config:
module.exports = ({ env }) => ({
  connection: {
    client: 'postgres',
    connection: {
      host: env('DATABASE_HOST', 'IP'),
      port: env.int('DATABASE_PORT', 5432),
      database: env('DATABASE_NAME', 'database'),
      user: env('DATABASE_USERNAME', 'postgres'),
      password: env('DATABASE_PASSWORD', 'SomePassword'),
//      ssl: env.bool('DATABASE_SSL', false),
      ssl: {
        rejectUnauthorized: env.bool('DATABASE_SSL_SELF', false), // For self-signed certificates
      },
    },
    // https://github.com/strapi/strapi/issues/11860
    debug: false,
    acquireConnectionTimeout: 600000,
    pool: {
      min: 0,
      max: 40,
      acquireTimeoutMillis: 300000,
      createTimeoutMillis: 300000,
      destroyTimeoutMillis: 50000,
      idleTimeoutMillis: 300000,
      reapIntervalMillis: 10000,
      createRetryIntervalMillis: 2000,
      propagateCreateError: false,
    },
  },
});

Removing packages strapi-plugin-rest-cache and strapi-provider-rest-cache-memory doen't help.

Hi @SVronskiy,
I'm trying to reproduce this at the moment.
I noticed the apiMaxChars: 1234 in your config. I know this is the value from the providers README, but that was just supposed to be an example of a random number. Unless your LibreTranslate server really does have a limit of 1234 characters per request, can you try increasing this value or omitting it if your server does not have a limit?
Also, could you possibly share more information about the texts you are trying to batch translate, i.e. how many entities, how many fields per entity, how many characters per field (on average)? I am currently having trouble reproducing/pinpointing the issue.

Hello, @layaxx !
It happens on tables with 30M+ of records with 10+ languages. Slow queries are reason of errors. I think query optimization will resolve the issue. I'm closing it for a moment.


Real lines of code fails with new grammar for java when using multi-line string literals

Code like the following does fail with the new Java grammar:
String multiLine = """
    Multi
    Line
   String
""";

Let's mark this as a bug and move it to the backlog. I think this has a high priority. Would a downgrade to the old grammar makes sense?

Would you please provide the error message/description? I am not sure what is failing exactly.


"Tweets did not appear!"

Code
scrap_keyword(keyword="nft", browser="chrome",               tweets_count=999999, until="2022-06-30", since="2022-06-29",output_format="csv",filename="nft")
Error Message
[WDM] - Current google-chrome version is 103.0.5060
[WDM] - Get LATEST driver version for 103.0.5060
[WDM] - Driver [./.wdm/drivers/chromedriver/mac64/103.0.5060.53/chromedriver] found in cache
Tweets did not appear!
Tweets did not appear!
Tweets did not appear!
Tweets did not appear!
Tweets did not appear!
Tweets did not appear!
Tweets did not appear!
Tweets did not appear!
Tweets did not appear!
Tweets did not appear!
Other Infomation
requirement.txt has already been installed

Okay, I will look into this issue

The number of tweets you're scraping might be the issue. I'm unable to recreate the same scenario but it is evident when you scroll too many tweets, Twitter redirects you to the login page. I assume after scrolling for around 100-200 tweets Twitter is redirecting you to the login page which leads to this error that the crawler couldn't find the tweets.

i occasionally have this issue with scrape_profile. im only looking at the 2 most recent tweets, and checking in every 5 minutes


Fixtures Library not supported with @slack/bolt: "^3.3.0"

I want to know if you will support the dependency of fixtures library to use the latest version of slack/bolt ?

Has anything important broken? I expect not much from a fixture perspective. I believe all that needs to be done is update the dev dependency and check the test cases.
Have you tried it and seen breakages?


Open TSC Meeting, Thursday April 23rd 2020

NOTE: This meeting is on Thursday at 9am - 10am PT
Zoom Meeting link: https://zoom.us/j/975841675
In order to give some more visibility into the topics we cover in the TSC meetings here is the planned agenda for the next meeting.  Hopefully this will allow people to plan to attend meetings for topics that they have an interest in.  And for folks who cannot attend they can comment on this issue prior to the meeting.  Feel free to suggest other potential agenda topics.
*Please submit comments below for topics or proposals that you wish to present in the TSC meeting

Topic
Owner
Decision/NextStep

Motion to remove OpenAPI.next branch. Local and GitHub backups exist
@MikeRalphson
@webron to clean up stale branches

3.1, fake 3.1 or 4.0

/cc @OAI/tsc Please suggest items for inclusion

3.1 respecting semantic versioning - Explicitly call out that OAS has certain different behavior than JSON Schema.

3.1 (ignore this edge case) - Align with JSON Schema

3.1  Pre-process the JSON schema based on context

3.5 Pseudo not breaking

4.0 Align with JSON Schema

I struggle to see that we get a benefit from semver that outweighs the cost of semver. I'd consider dropping semver from 3.1 (I don't see that 4.0 is required to drop).

I can't see why we would bump to 4.0 and remove semver. 3.5, or OAS Vista, yes.

I think there are several choices involved here and it might be helpful to split them.  Right now I feel like the people who want to let the Schema Object remain incompatible with JSON Schema are having one conversation, and the people who just want to figure out the best way to communicate the changes around JSON Schema are having a different one.  So:

Does OAS want the next version to be fully compatible with JSON Schema, in the sense that schema objects can be passed directly to JSON Schema validators, and the validation result is consistent with what an OAS documentation or code generation tool would document or produce?

IF NO:

a) Which incompatibility with JSON Schema is desired?

Treating Schema Objects as templates even though they look identical to JSON Schemas (e.g. preprocess to remove required and maybe adjust exclusive* based on where the object is attached)?
Simply accepting and documenting the remaining incompatibilities, and requiring specialized implementations (not just vocabulary extensions, as that won't work) to handle OAS Schema Objects that use those incompatible features

IF YES:

b) How is the OAS incompatibility between the new version and 3.0.x expressed?

Preserve SemVer: 4.0

by restricting incompatibilities to the Schema Object
by throwing open the floodgates to some degree or another

Discard SemVer entirely: 3.1
Split the difference between proper SemVer (which has psychological / cognitive load problems relative to the actual breakage) and abandoning all meaning of numbering, by declaring that skipping a few minor numbers means that there are limited breaking changes that will probably not impact many people, and/or are trivial for migration (e.g. exclusive*): 3.5

If we can answer the first question, then we shrink the set of answers we're debating for the 2nd question.


Enhancement Request

When processing a report for multiple campaigns we get the "warning" that this may take some time; however it looked like it was processing very fast until about half way then it looked like it hung for a while and then continued fast again. When it paused it looked like the whole program hung/crashed but after a few minutes it continued on. - It would be nice to have more on-screen reporting so we know it isn't crashed.

Was there a particular campaign that stood out? Like, is there one campaign that's much bigger than the rest of them?

On Sep 11, 2017, at 7:32 PM, Raytri3<EMAIL_ADDRESS>wrote:
When processing a report for multiple campaigns we get the "warning" that this may take some time; however it looked like it was processing very fast until about half way then it looked like it hung for a while and then continued fast again. When it paused it looked like the whole program hung/crashed but after a few minutes it continued on. - It would be nice to have more on-screen reporting so we know it isn't crashed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

No not really (4 campaigns of 17,22,22,22 for a total of 83 folks). I did
some digging and think I know why it slowed down (really just sat at one
for about 10 minutes) - one user had some weird results. They "clicked" 77
times with 77 different browsers - this of course isn't right so I suspect
they reported the phishing site to Google/Windows and they in turn visited
the link (and if it had the users identifier it would appear to have
originated from that user). I think it was this user that slowed down the
results. It would have been nice to see something like .....  or something
across the screen as we waited just so we know the program isn't hung.
Again a simple nice to have - doesn't really matter as far as functionality
goes.
Ray
On Mon, Sep 11, 2017 at 9:01 PM, Jordan Wright<EMAIL_ADDRESS>wrote:

Was there a particular campaign that stood out? Like, is there one
campaign that's much bigger than the rest of them?

On Sep 11, 2017, at 7:32 PM, Raytri3<EMAIL_ADDRESS>wrote:
When processing a report for multiple campaigns we get the "warning"
that this may take some time; however it looked like it was processing very
fast until about half way then it looked like it hung for a while and then
continued fast again. When it paused it looked like the whole program
hung/crashed but after a few minutes it continued on. - It would be nice to
have more on-screen reporting so we know it isn't crashed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/chrismaddalena/GoReport/issues/10#issuecomment-328700484,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABt4L6GsRlHMxZrfCdHSaldazommIr16ks5shdftgaJpZM4PT8UX
.

Thanks for the suggestion, Ray. I can look into this and see what I might be able to do for these cases. This sort of thing is why I have GoReport provide a progress report of sorts ("working on x/1209"), but you're right, it doesn't keep updating or providing feedback until it finishes that piece. I think I have something in another tool of mine I may be able to repurpose for a sort of progress bar.
You are right, though. GoReport can move very quickly through report composition when its just assembling tables, but you'll see the results slow down when GoReport has to parse a large number of results for a single recipient. I have seen cases like you described. When I have seen those sorts of results, it was as you suggested. The recipient submitted the GoPhish link to urlquery or VirusTotal, which triggers "clicks" from either several Mountain View, CA servers owned by Google or some servers in Norway.
Then you can start seeing all kinds of wild results, like clicks from Russia, China, the UK, and elsewhere, presumably from people reviewing the latest submissions to these services. Each new IP means another geo IP lookup, another row in a table, etc. GoReport has to give some of the APIs and web services a second between requests, so time start to add up quickly.

Closing this out because these issues have been addressed in the latest release. Geolocate requests are far more efficient now. There's also much, much more included in v3.0 just pushed to master.


Circular references stoped working after #2305

Context

After the release of version 7.7.8 my document freezes when opening an schema containing circular references.
Current Behavior

Freezes when opening schemas containing circular references.
Expected Behavior

Should not freeze when opening schemas containing circular references.
Possible Workaround/Solution

Revert to version 7.7.7 until it's fixed.
Steps to Reproduce

Open an schema containing circular references.

Environment

Version used: 7.7.8
Environment name and version (e.g. Chrome 39, node.js 5.4): Any browser
Operating System and version (desktop or mobile): Any OS
Link to your environment/workspace/project:

@P0lip Would you mind looking into this?

Here you go:
openapi: 3.1.0
info:
  title: Tic Tac Toe
  description: |
    This API allows writing down marks on a Tic Tac Toe board
    and requesting the state of the board or of individual squares.
  version: 1.0.0
tags:
  - name: Gameplay
paths:
  # Whole board operations
  /board:
    get:
      summary: Get the whole board
      description: Retrieves the current state of the board and the winner.
      tags:
        - Gameplay
      operationId: get-board
      responses:
        '200':
          description: 'OK'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/status'

  # Single square operations
  /board/{row}/{column}:
    parameters:
      - $ref: '#/components/parameters/rowParam'
      - $ref: '#/components/parameters/columnParam'
    get:
      summary: Get a single board square
      description: Retrieves the requested square.
      tags:
        - Gameplay
      operationId: get-square
      responses:
        '200':
          description: 'OK'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/mark'
        '400':
          description: The provided parameters are incorrect
          content:
            text/html:
              schema:
                $ref: '#/components/schemas/errorMessage'
              example: 'Illegal coordinates'
    put:
      summary: Set a single board square
      description: Places a mark on the board and retrieves the whole board and the winner (if any).
      tags:
        - Gameplay
      operationId: put-square
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/mark'
      responses:
        '200':
          description: 'OK'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/status'
        '400':
          description: The provided parameters are incorrect
          content:
            text/html:
              schema:
                $ref: '#/components/schemas/errorMessage'
              examples:
                illegalCoordinates:
                  value: 'Illegal coordinates.'
                notEmpty:
                  value: 'Square is not empty.'
                invalidMark:
                  value: 'Invalid Mark (X or O).'

components:
  parameters:
    rowParam:
      description: Board row (vertical coordinate)
      name: row
      in: path
      required: true
      schema:
        $ref: '#/components/schemas/coordinate'
    columnParam:
      description: Board column (horizontal coordinate)
      name: column
      in: path
      required: true
      schema:
        $ref: '#/components/schemas/coordinate'
  schemas:
    errorMessage:
      type: string
      maxLength: 256
      description: A text message describing an error
    coordinate:
      type: integer
      minimum: 1
      maximum: 3
      example: 1
    mark:
      type: string
      enum: ['.', 'X', 'O']
      description: Possible values for a board square. `.` means empty square.
      example: '.'
    board:
      type: array
      maxItems: 3
      minItems: 3
      items:
        type: array
        maxItems: 3
        minItems: 3
        items:
          $ref: '#/components/schemas/mark'
    winner:
      type: string
      enum: ['.', 'X', 'O']
      description: Winner of the game. `.` means nobody has won yet.
      example: '.'
    status:
      type: object
      properties:
        winner:
          $ref: '#/components/schemas/winner'
        board:
          $ref: '#/components/schemas/board'
        meta:
          $ref: '#/components/schemas/status'

Try opening the status schema.

Hello is it possible to revert that #2305 PR until this bug is fixed?

I'll try to fix it ASAP

Still running into this problem. Tried reverting to the 7.7.7 version, but I still see the problem where the document freezes when opening a schema containing circular references. Is anyone else running into this?

Still running into this problem. Tried reverting to the 7.7.7 version, but I still see the problem where the document freezes when opening a schema containing circular references. Is anyone else running into this?

We're also seeing this.


[EventRequest] Codeunit 22 “Item Jnl. – Post Line”, UpdateUnitCost [Local] missing parameter

We have requested this before on #3845 but we are missing one parameter itemJournalLine : Record "Item Journal Line".

from a newly pulled base app the publisher looks like the following

is it possible to request a parameter extension to this publisher as mentioned in #3845

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Specify the output directory to run tests

Hi @andrewchaa, this pr are to fix travis CI ?

Hi @mbdavid
it was my intention, but after pushing the pr, I learned it was appveyor that was failing, not travis.
if you don't mind, I can create appveyoor.yml to fix the CI

Hi @andrewchaa, will be fantastic. I'm not expert in CI and aways get "red" alert... i spend long time to fix, but back again...

No problem. I'll work on it.