Error with Notebook #2

In the second notebook, step 2 of step 5 tells you to do something to a file, but not how to do it.

The whole of the second notebook cannot be run. When the second step is run, it immediately comes back with:
“Directory '.' is not installable. File 'setup.py' not found.
Requirement 'retrieve_and_rank_scorer-1.0-py2-none-any.whl' looks like a filename, but the file does not exist
Processing ./retrieve_and_rank_scorer-1.0-py2-none-any.whl
Exception:
Traceback (most recent call last):
File "/Users/mwassel/miniconda2/lib/python2.7/site-packages/pip/basecommand.py", line 215, in main
status = self.run(options, args)
File "/Users/mwassel/miniconda2/lib/python2.7/site-packages/pip/commands/install.py", line 310, in run
wb.build(autobuilding=True)
File "/Users/mwassel/miniconda2/lib/python2.7/site-packages/pip/wheel.py", line 750, in build
self.requirement_set.prepare_files(self.finder)
File "/Users/mwassel/miniconda2/lib/python2.7/site-packages/pip/req/req_set.py", line 370, in prepare_files
ignore_dependencies=self.ignore_dependencies))
File "/Users/mwassel/miniconda2/lib/python2.7/site-packages/pip/req/req_set.py", line 587, in _prepare_file
session=self.session, hashes=hashes)
File "/Users/mwassel/miniconda2/lib/python2.7/site-packages/pip/download.py", line 798, in unpack_url
unpack_file_url(link, location, download_dir, hashes=hashes)
File "/Users/mwassel/miniconda2/lib/python2.7/site-packages/pip/download.py", line 705, in unpack_file_url
unpack_file(from_path, location, content_type, link)
File "/Users/mwassel/miniconda2/lib/python2.7/site-packages/pip/utils/init.py", line 599, in unpack_file
flatten=not filename.endswith('.whl')
File "/Users/mwassel/miniconda2/lib/python2.7/site-packages/pip/utils/init.py", line 482, in unzip_file
zipfp = open(filename, 'rb')
IOError: [Errno 2] No such file or directory: '/Users/mwassel/Downloads/answer-retrieval-master/notebooks/retrieve_and_rank_scorer-1.0-py2-none-any.whl’”
in the output terminal that is running the notebook. After that step, all other steps come back with similar responses.

Unable to re-create locally. Also, the developers I contacted didn't seem to have this issue.

Fixed. The error was due to the snippet pointing to the wrong directory. Modified and verified the same to be working.


Add dialogue based creation of work items (#352)

Add dialogue based creation of work items (#352)
User story - https://github.com/almighty/almighty-core/issues/501
UX - https://redhat.invisionapp.com/share/Y39KFTAE7

Current coverage is 67.10% (diff: 37.93%)

Merging #508 into master will decrease coverage by 0.90%

@@             master       #508   diff @@
==========================================
  Files            27         27
  Lines          1266       1286    +20
  Methods         269        271     +2
  Messages          0          0
  Branches        250        252     +2
==========================================
+ Hits            861        863     +2
- Misses          405        423    +18
  Partials          0          0

Powered by Codecov. Last update 05fab26...e0a2916

@nimishamukherjee @joshuawilson Don't we need common dialog/modal layout across the project rather than creating modal again and again.
I have already used ng2-modal for other dialog. Even If we want to create our own dialog we need something like that

[test]


thuang-837-process-status

#837
MAKE THIS THE FEATURE BRANCH!
Reviewers
Functional:
@Bento007
Readability:
@seve
Changes

add

PROCESSING_STATUS enum
Use such enum as a new failure scenario

modify

useCheckCollection() should check for isFailed to prevent permanent fetching

When we get processing_status === PROCESSING_STATUS.FAILURE we show the following message:

Thanks @seve ! We just need @Bento007 's help to fix the unit test in this PR, then we can merge his branch into this feature branch, and merge all into main :fire!

rerunning a failed unit test! I think it's a flaky one 👌


Support for .gql files (mergeTypes)

Thank you for this super useful module.
Let me suggest a single line change to add support for .gql files when mergin types:
src/file_loader.js line 40
      case '.gql':
      case '.graphqls':

Since everything is pretty new when it comes to GraphQL, I have no idea if ".gqls" extension would also be used, but ".gql" is already pretty common!
Once again, thank you!

Hey @euthiago,
I've added gql extension to the fileLoader as you've suggested. PR #81. I'll let you know when it's published.
Cheers!

@RodMachado
I appreciate!
(Vlw Rodrigo! hehe)

@euthiago
Your changes were deployed!
Cheers!


use nexus schema with nextjs

hi all,
I'm trying with nextjs example but for this code
registerModule(
  gql`
    type Query {
      users: String!
    }
  `,
  {
    resolvers: {
      Query: {
        users(_root, _args, _ctx) {
          return "hello";
        },
      },
    },
  }
);

Can i use schema from nexus created as following
import { makeSchema } from "nexus";
import * as types from "../types";

export const schema = makeSchema({
  types,
});

thanks

You can use the "schema" property
import { CreateApp } from '@graphql-ez/nextjs';
import { schema } from '../schema';

export const { buildApp } = CreateApp({
  schema,
});

https://www.graphql-ez.com/docs/integrations/nextjs


(frontend) replace grommet text input with cunningham text input

Purpose
Replace grommet text input with cunningham text input.
It is more critical than we thought I guess, we often need to refactor the code to make it work with the new input:

the grommet Form  component is not working with the new input
the way the errors are managed change as well (not from the Form component anymore)

Proposal

[x] replace every grommet TextInput by cunningham Input
[x] improve fetch error
[x] tests

the font weight is not the same with master branch. 400 on the master branch, 300 on this one.

The font weight is not the same but visually it should be the same, the weight change visually from 600.
On the top is the grommet input and the bottom the cunningham, the only visual diff on  the label is that cunningham add a small opacity on the label, so the color become slightly lighter on the cunningham one.

Oh and I just notice that the font family used is not the same

Oh and I just notice that the font family used is not the same

You're right, incredible eyes.
https://github.com/openfun/marsha/pull/2374/commits/f383dc0a3cea6f2475cd75b062c70a53ff68457e

I added this commit (♻(frontend) update way to load correct front), before to have a bold Roboto, we had to change the font-family (example). With the new way, we don't have to change the font-family anymore, just changing the weight will load the correct font (works only with the exact font name Roboto, so only with cunningham for the moment).


Shift lock_until if a task is still running

The documentation says:
You have to set lockAtMostFor to a value which is much longer than normal execution time
but normally it's hard to predict the execution time of a task. I'd suggest to add an optional feature to shit the time in case of a task is still running:

Before a task will start create a scheduler that runs every n time
If a task is still running and lock_until is about to expire then update the field (lock_until + n time)

Hi, thanks for feedback. It's possible but you have to create the lock manually. See this https://github.com/lukas-krecan/ShedLock/issues/443

You can try this (just released) https://github.com/lukas-krecan/ShedLock#extending-the-lock

Hi Lukas, as I understood, to use it I have to manually check for a task completion and call the new static method to extend a lock, right? I'm expecting to hide it under library and just use @SchedulerLock for scheduled method.
I created my own class ExtendableLockingTaskExecutor that extends DefaultLockingTaskExecutor and put logic to track a task completion and add some time if it's still running. It's working but I didn't have time to test it carefully. If you are interested I can share my solution.

Hi @lukas-krecan, I made the simple change and we are gonna test it. Please take a look https://github.com/lukas-krecan/ShedLock/pull/668/files


[SPARK-19426][SQL] Custom coalescer for Dataset

What changes were proposed in this pull request?
This pr adds a new API for coalesce in Dataset; users can specify the custom coalescer which reduces an input Dataset into fewer partitions. This coalescer implementation is the same with the one in RDD#coalesce added in https://github.com/apache/spark/pull/11865 (SPARK-14042).
This is the rework of https://github.com/apache/spark/pull/18861.
How was this patch tested?
Added tests in DatasetSuite.

@hvanhovell Coalesce does not enforce uniform data distribution across partitions. We would like to pass custom size based coalescer to have more uniform data distribution. This would avoid using shuffle at places.

@hvanhovell will you be able to add review here or tag relevant folks here?


sett cacert.pem file in secure connections

connecting to remote host in ssl using HTTPClient
I can not set cacert.pem file path so I have this error
Cause: unable to get local issuer certificate
CERT STR: **********************************
VALID: 0
CONNECTION RESULT: -1
139946413610840:error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed:s3_clnt.c:1258:
ERROR: _print_error: Some I/O error occurred. The OpenSSL error queue may contain more information on the error.
At: drivers/openssl/stream_peer_openssl.cpp:406.

found this tutorial: https://github.com/godotengine/godot/wiki/tutorial_ssl
Sorry for this issue


feat: add workspace initialization command

Summary
Added a command that allows you to initalize biome settings in the workspace based on this tweet:
https://x.com/colinhacks/status/1841219884287737886
and this dicussion:
https://github.com/biomejs/biome-vscode/discussions/230
Description
when you right click on either setttings.json in .vscode or biome.json you can click on the biome: initalize workspace command to add all the required fields into settings.json for biome to work properly, also check this tweet for the merging of the config files:
https://x.com/andhaveaniceday/status/1841226098706956625
Feel free to edit and add whatever you deem is needed here
Checklist

[ ] I have tested my changes on the following platforms:

[x] Windows
[ ] Linux
[ ] macOS

@nhedger seems to get added to test.code-workspace instead of settings.json in the individual ones, what would be the right behaviour here?

@nhedger seems to get added to test.code-workspace instead of settings.json in the individual ones, what would be the right behaviour here?

I think we'd want the config to be added to the .vscode/settings.json file if the action was triggered from the context menu on that file. Maybe we could also add a context menu for the .code-workspace file, WDYT?

@nhedger when you click on the .code-workspace it will generate it on the root of that workspace into a separate .vscode folder, and if you click on the workspaces inside it will generate it there, would that be the expected behavior?

I would expect it to add the config inside the .code-workspace file in the settings section.

@nhedger I can't get it to output it to the .code-workspace file at all, seems that vscode isn't happy with that, when i scope it to the .code-workspace file it's still output to the .vscode folder and whatever I do it's the same result, the only way to allow it on .code-workspace is to manually parse the file and rewrite it with fs it seems, unless I'm missing something.

my findings:
workspace1/.vscode/settings => if you set output to Workspace it's output to the .code-workspace
workspace1/.vscode/settings => if you set output to WorkspaceFolder AND scope it to the current path its output properly (what this PR does)
.code-workspace => no scope / scoped to workspace path with Workspace is output to .vscode folder neighbouring it.
.code-workspace => no scope / scoped to workspace path with WorkspaceFolder nothing happens
.code-workspace => no scope / scoped to workspace path with Global it's output to global settings above the workspace

you can easily check if it's a .code-workspace by checking if the args.path ends with that extension and feel free to try it out yourself and see if i've missed something obvious. From my perspective the PR is ready as is, but that feature can be added on top of course!

Thanks Alem, I love this!
I do have a question for the maintainers. Why are the per-language settings necessary in the first place? If Biome is set as the top-level default formatter in a workspace, it seems surprising that is isn't used by default for all file types that Biome is capable of formatting. I'm sure this was an intentional decision, but I'd love to see it revisited, especially as Biome matures (and with a new major of the extension on the horizon).
Should Biome add support for additional file types down the line, those will need to be added. This is likely to cause confusion for users who have run the "Biome: Initialize" and don't understand why it doesn't work for certain files.

I do have a question for the maintainers. Why are the per-language settings necessary in the first place? If Biome is set as the top-level default formatter in a workspace, it seems surprising that is isn't used by default for all file types that Biome is capable of formattin

It isn't necessary, actually.  For example, I use the following setting on my VSCode:
{
	"editor.defaultFormatter": "biomejs.biome",
	"editor.formatOnSave": true,
}

These settings work as expected. If they don't, there's probably a bug lurking somewhere (either the extension or the editor).
I suppose the docs are outdated, and at that time, we suggested an opt-in approach not to disrupt the user's settings and default formatter. We are happy to revisit them if you think it's more valuable. There's an open PR for the upcoming v3 of the extension if you're interested: https://github.com/biomejs/website/pull/974

@ematipico I also believe there is a bug somewhere, we have been extensively using biome in our company and we had to play around with the settings.json a lot to get it working properly with biome.
I've added the suggested changes by @colinhacks to the PR

Hey guys, any updates on this, anything on my side I need to do? Really interested if it will be merged or not!

Hey @AlemTuzlak, haven't had a chance to test it out yet. I've been taking a break. I'll try to review and test it this week.

@nhedger no worries, just wanted to confirm I'm not the cause of it. Great to hear, take your time


Bug: multiple choice not working in textbook

Where does the issue happen?
https://learn.qiskit.org/course/ch-states/representing-qubit-states#rules-measurement
What is the content issue?
The option to select "0 or 1" does not work.  I am able to select "1" or "0" or "-1 and 1" but the correct option cannot be clicked.

Screenshots
No response
Additional information
No response

@vandieren I could n't reproduce the issue. It is working correctly for me (see below).

This repository is no longer maintained. It has been superseded by IBM Quantum Learning


Erase annotations on top-level script blocks

Fixes

https://github.com/gradle/gradle/issues/20131

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test APT

I've triggered the following builds for you:

AllPerformanceTestsReadyForRelease build

@bot-gradle test this

I've triggered the following builds for you:

PullRequestFeedback build

Your PR is queued. See the queue page for details.

@bamboo I will address your comments in a follow-up PR.

I've triggered a build for you. Click here to see all failures if there's any.

@bamboo please see https://github.com/gradle/gradle/pull/25688


Issue with Theme Persistence When Navigating Back Between Components

Description
Description:
I am encountering an issue in a scenario where navigation occurs among three components, each assigned with a unique theme. The components and their respective themes are as follows:
Component A: Theme A
Component B: Theme B
For each component, upon its initial load, I utilize the UnistylesRuntime.setTheme method to set the corresponding theme. This approach is functioning correctly for the initial load of each component. However, a problem arises when using the router.back method for backward navigation. For example, if I navigate back from Component B to Component A, the theme does not update accordingly and remains set to Theme C, despite the expectation that it should switch to Theme B.
This issue seems occur with backward navigation since previous page is currently loaded. Any insights or solutions to ensure the correct theme is applied when navigating back would be appreciated.
Steps to reproduce

Component A.

const ComponentA = () => {
  // I also tried this
  // React.useLayoutEffect(() => {
  //   UnistylesRuntime.setTheme(("themeA")
  // }, [])

  // or this
  // React.useEffect(() => {
  //   UnistylesRuntime.setTheme(("themeA")
  // }, [])

  UnistylesRuntime.setTheme(("themeA")

  return (
    <View>
      <Link href={'componentB'}/>
      <Text>Component A Theme A</Text>
    </View>
  );
};

Component B.

const ComponentB = () => {
  UnistylesRuntime.setTheme(("themeB")

  // expo-router
  const router = useRouter()

  return (
    <View>
      <Text>Component B Theme B</Text>
      <Button onPress={() =>router.back()}>Go back</Button>
    </View>
  );
};

Snack or a link to a repository (optional)
No response
Unistyles version
2.0.0-alpha.11
React Native version
^0.72.6
Platforms
iOS

Thanks for the report. I think it's because your component A is mounted and going back from component B doesn't re-trigger the useEffect. When it comes to the react-navigation, I was using this hook: https://reactnavigation.org/docs/5.x/use-focus-effect/
As far as I know expo router is built on top of react navigation, so you can use the same approach.
Other approach is to call Unistyles runtime when you go back. Nevertheless you need to call it somewhere.
I hope it will help 🙏


Validate: Rules are optional unless declared required

Before this PR the logic was like this:
validate( '', 'Generic'); // message about format being wrong
validate( '', 'required,Generic'); // message about being required
validate( '', 'optional,Generic'); // success

Both the code and users could infer that something is optional if it's not explicitly required.
The change in this PR ensures that no validators run if the fields are empty and not required. We should also consider marking optional as a deprecated "rule".
The behavior becomes:
validate( '', 'Generic'); // success
validate( '', 'required,Generic'); // message about being required
validate( '', 'optional,Generic'); // success

On a sidenote we may want to implement a dataprovider (random example being https://github.com/jphpsf/jasmine-data-provider). That way when one of the loops fail, it is clear what data was passed in. Even the for () it( 'verifies' + key is a bit weak because one doesn't know which regex failed.

jphpsf? I refuse to have more php in my javascript.

I'm not sure what you mean. It is clear that data is passed in from the fact that you call validate() with data as its first parameter. Failures will set message. In no case should actual access to the rule object be allowed.

:+1:


Proposed Recipes for ROMS Data from UW Coastal Modeling Group

I just had a great chat with @parkermac about their model data and am opening this issue to track the idea of ingesting some of their regional ocean model data into OSN via Pangeo Forge.
I'm not sure about many of the details; hopefully Parker can chime in with some clarifications.
Source Dataset

ROMS simulation output from UW Coastal Modeling Group

Link to the website / online documentation for the data: http://faculty.washington.edu/pmacc/LO/LiveOcean.html
The file format (e.g. netCDF, csv): netCDF
How are the source files organized? Time snapshots output by the model with a certain output frequency (daily? hourly?). All variables in a single file.
How are the source files accessed (e.g. FTP): This is the hard part. The data are not available over the public internet. They are stored on a group server at UW. To move forward, we would need to work with Parker and his IT department to get access. The easiest thing (for us) would be to just open up HTTP access to the files so we could ingest them. Globus or SCP could be options as well.

Transformation / Alignment / Merging

Straightforward concatenation in time.
Output Dataset

Zarr

Ryan,
Thanks for the succinct summary of a really helpful conversation.
My first question getting started is to ask for advice on converting ROMS
history files (one tile per hour) to zarr.  Is this:
https://raphaeldussin.medium.com/modern-python-tools-for-the-roms-ocean-model-bfca8642db01
the state of the art right now?
Thanks,
Parker
On Tue, Mar 8, 2022 at 9:17 AM Ryan Abernathey @.***>
wrote:

I just had a great chat with @parkermac https://github.com/parkermac
about their model data and am opening this issue to track the idea of
ingesting some of their regional ocean model
http://faculty.washington.edu/pmacc/LO/LiveOcean.html data into OSN via
Pangeo Forge.
I'm not sure about many of the details; hopefully Parker can chime in with
some clarifications.
Source Dataset
ROMS simulation output from UW Coastal Modeling Group

Link to the website / online documentation for the data:
http://faculty.washington.edu/pmacc/LO/LiveOcean.html
The file format (e.g. netCDF, csv): netCDF
How are the source files organized? Time snapshots output by the
model with a certain output frequency (daily? hourly?). All variables in a
single file.
How are the source files accessed (e.g. FTP): This is the hard part.
The data are not available over the public internet. They are stored on a
group server at UW. To move forward, we would need to work with Parker and
his IT department to get access. The easiest thing (for us) would be to
just open up HTTP access to the files so we could ingest them. Globus or
SCP could be options as well.

Transformation / Alignment / Merging
Straightforward concatenation in time.
Output Dataset
Zarr
—
Reply to this email directly, view it on GitHub
https://github.com/pangeo-forge/staged-recipes/issues/123, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5WRX6S7OCEXFRKOZAELDLU66DT5ANCNFSM5QG7BWKA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Parker MacCready - Leo Maddox Endowed Professor
University of Washington, School of Oceanography
** I acknowledge that I live and work on the land and waters of the Squaxin
Island Tribe. **
Email: @.***
URL: faculty.washington.edu/pmacc
LiveOcean Daily Forecasts
http://faculty.washington.edu/pmacc/LO/LiveOcean.html
Cell:<PHONE_NUMBER>, Office:<PHONE_NUMBER>
pronouns: he/him

I would say two main things have changed since @raphaeldussin's excellent blog post is

the development of Pangeo Forge, which aims to automate many of the time-consuming and confusing steps of making Zarr data from many netCDF files.
the development of kerchunk which makes it possible to build an "index" of the netCDF files and expose the collection as a virtual Zarr store. (Pangeo Forge can generate kerchunk indexes via the HDFReferenceRecipe class)

I think a good roadmap here would be to take some of the preprocessing functions from Raphael's gist  and use then in an XarrayZarrRecipe.
Parker, what are the chances of getting your netCDF files accessible over the internet (HTTP or FTP)?

Ryan, picking up on this conversation after my vacation...
I put a day of NetCDF files on this server:
https://liveocean.apl.uw.edu/output/history_files/f2022.03.18/
Each ocean_his_00##.nc file is an hourly snapshot of many model fields.
They are compressed NetCDF4 made by ROMS.  Each history file is 613 MB, and
on that server I get download speeds of 30 MB/sec.
I will try converting things to zarr and let you know how it goes.  Maybe I
will even contribute my own Pangeo Forge Recipe!
Cheers,
Parker
On Tue, Mar 8, 2022 at 11:10 AM Ryan Abernathey @.***>
wrote:

I would say two main things have changed since @raphaeldussin
https://github.com/raphaeldussin's excellent blog post:

the development of Pangeo Forge
https://pangeo-forge.readthedocs.io/, which aims to automate many of
the time-consuming and confusing steps of making Zarr data from many netCDF
files.
the development of kerchunk https://fsspec.github.io/kerchunk/
which makes it possible to build an "index" of the netCDF files and expose
the collection as a virtual Zarr store. (Pangeo Forge can generate kerchunk
indexes via the HDFReferenceRecipe
https://pangeo-forge.readthedocs.io/en/latest/recipe_user_guide/recipes.html#hdf-reference-recipe
class)

I think a good roadmap here would be to take some of the preprocessing
functions from Raphael's gist
https://gist.github.com/raphaeldussin/f40621068b6b5fc48e14d38ec50fb094#file-main_roms2zarr-py
and use then in an XarrayZarrRecipe
https://pangeo-forge.readthedocs.io/en/latest/recipe_user_guide/recipes.html#xarrayzarr-recipe
.
Parker, what are the chances of getting your netCDF files accessible over
the internet (HTTP or FTP)?
—
Reply to this email directly, view it on GitHub
https://github.com/pangeo-forge/staged-recipes/issues/123#issuecomment-1062111200,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5WRXZYY23IW2GQSQDECYLU66Q23ANCNFSM5QG7BWKA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Parker MacCready - Leo Maddox Endowed Professor
University of Washington, School of Oceanography
** I acknowledge that I live and work on the land and waters of the Squaxin
Island Tribe. **
Email: @.***
URL: faculty.washington.edu/pmacc
LiveOcean Daily Forecasts
http://faculty.washington.edu/pmacc/LO/LiveOcean.html
Cell:<PHONE_NUMBER>, Office:<PHONE_NUMBER>
pronouns: he/him


Incremental Loading of Dimensions

The purpose is to replace flush and load of dimensions and fact tables with incremental loading.
The scripts aren't expected to change in logic (what is currently there).

@DennisGibz could you kindly format the scripts  to make them more readable ? the long ones loke DimPatient are hard to read.
We can use this online formatter: https://www.atatus.com/tools/sql-beautify

@DennisGibz could you kindly format the scripts to make them more readable ? the long ones loke DimPatient are hard to read. We can use this online formatter: https://www.atatus.com/tools/sql-beautify

@DennisGibz kindly re format the scripts to enable easier revewing.

@DennisGibz could you kindly format the scripts to make them more readable ? the long ones loke DimPatient are hard to read. We can use this online formatter: https://www.atatus.com/tools/sql-beautify

Well noted @nobert-mumo

Closing this as there is a new PR on this.


do not  support 4.4？

   Caused by: java.lang.NoClassDefFoundError: de.hdodenhof.circleimageview.R$styleable
                                                                   at de.hdodenhof.circleimageview.CircleImageView.<init>(CircleImageView.java:91)
                                                                   at de.hdodenhof.circleimageview.CircleImageView.<init>(CircleImageView.java:85)

4.4 is supported. This is likely an issue with your multidex setup, make sure to properly include the multidex support library.

you right 。 I  resolved。 tks

I too had the same problem. Thanks @hdodenhof for the solution


Feat: Support default config print logic by @summingyu

Support default config print logic

[x] "jenkins"
[x] "jira-github-integ"
[x] "kube-prometheus":
[x] "openldap":
[x] "trello-github-integ":
[x] "trello":

Sorting the output of the list command

Related Issues
#383

close #383


Fix Virtual Wan Point to site feature resources property names from swagger.

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

This is to get bug fix from August branch:- https://github.com/Azure/azure-rest-api-specs/pull/7498

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@Nilambari  please fix the code check errors in NetworkValidation and modelValidation.

@Nilambari  please fix the code check errors in NetworkValidation and modelValidation.

Done.

Can you Please help approve PR?

@lirenhe please take a look


Add SimpleCache implementation

I think it would be helpful to add a PSR SimpleCache implementation.
This Implementation should work like ArrayCache, but keeping and providing the history of operations

Is there currently a use-case for it?

Why not?

tested service requires a CacheInterface implementation. Pull ArrayCache? Create a mock (which may not match expected behavior)? Write custom stub?
you need to test actions with the CacheInterface

tested service requires a CacheInterface implementation

Which one? Is there any existing package that requires it?

https://github.com/yiisoft/yii-cycle/blob/master/src/Schema/Provider/SimpleCacheSchemaProvider.php

OK.


Setup CI

We should automatically verify that the new installer can install known Istio versions. As the current CI of the Istio community is CircleCI, we should deliver this as CircleCI config.
Things to verify:

The installation is indeed modular:

Install Istio Citadel + Control plane and verify a service A can reach a service B via Envoy data plane
Add an Istio Ingress Gateway and verify we can reach service A from outside the cluster
Add Istio telemetry and verify we get metrics from the service mesh
Add Istio Policy and verify that it works
Add Istio Egress Gateway and verify that it works

The installation can be updated without service degradation:

Update all Istio components and verify that the service mesh stays functional

I propose we verify the installation of Istio 1.1.0 and the update to the branch release-1.1.

@costinm I'd like to add job that verifies modular installation. Is there an e2e test that would work with Citadel and istio-control alone? Just looked into the simple e2e test, but that already needs a Gateway.

There is a way to deploy Pilot + Gateway alone (in different NS) - this should work for simple.

The PR #21 has added a Circle CI job that tested the installation. It seemed to work from https://circleci.com/gh/istio-ecosystem/istio-installer/73 to https://circleci.com/gh/istio-ecosystem/istio-installer/122 (5 days ago), but is broken at the moment.
I think we should have some circle CI label in the readme, so that we have a visual clue for the CI job failing. What do you say, @costinm ?

Hi @costinm, we now have an installation/upgrade pipeline running on concourse https://concourse.istio.sapcloud.io/ where we could imagine to also run a PR validation. I think we need to grant members of the istio org viewer access to the build logs there before we can do that.
Concourse can understand github.com oauth and organisation membership, but one Istio org administrator would need to permit that workflow. Do you think that is feasible?

@costinm ?

@sdake @linsun @howardjohn ?

Hi - sorry for the delay, had a few other fires.
Yes, I think it is great - we want to verify the installer works with multiple CI/CD systems.
@linsun  is admin on istio org, /lgtm

Is there a link we can add to the README ?

Also - I don't seem to have permission to the jobs (401)

I can't view either of these 2 links you posted earlier @holgero
We are open to integrate with other CIs, it will be optional first till it is proved to stable then we can move to required.
A little tight on time before kubecon, but please specify exactly what admin support you need.

The earlier posted links in https://github.com/istio/installer/issues/5#issuecomment-484031906 no longer work for me too. They worked while the istio installer was in istio-ecosystem.
Here is the new location: https://circleci.com/gh/istio/istio-installer
The newer link  https://concourse.istio.sapcloud.io/ is the more interesting one. If you follow it, you will see a concourse UI with public pipelines displayed. In the top-right corner there is a login button which brings you to a page where you have the choice to login with Github. We configured the concourse to allow all github users that are members of the Istio org to be granted viewer role on the concourse. But to check if someone is a member of the Istio org, that org has to allow the oauth workflow. And that workflow needs someone with admin permission to allow it.
I just wanted to check if it is okay to ask for that permission. I can also make a screen shot if that helps.

But I just tried it myself and it didn't seem to work any more at the moment. And the developer who did the setup isn't here today. Perhaps we can give it a try next week, if your time permits? Otherwise we postpone this after the kubecon.

It is great to have this, and login with github seems good idea ( but the redirect is broken indeed).
We can wait - if we get it ready before the freeze on 21 it would be great.
If I understand the script correctly, they run install and test on a k8s cluster ? Do you support using
Kind ? I suppose when logs become visible I can answer my own q.

@costinm I added your github user explicitly. You should now be able login to our concourse and view the logs.

I got the redirect page working for me again (had to remove the application from my github settings page to see it again). Now I got the chance to let it send a request to Istio org owners to access organization data. Org owners should see now that request.

Thanks to @geeknoid it works now. Members of the Istio org can now view the build logs on our concourse instance.


about msls

hello, i succeeded formatting every datasets except mapillary.
i downloaded via the link you provided and unzip those things.
in VPR-datasets-downloader/datasets/mapillary_sls
when  i typed tree -L 2 , it output is like :

it is the right file directory structure to run the code?
i can't  make it although i read the code
thankyou

Hey, you can check the issue i opened, where i clearly explain what the problem is: https://github.com/gmberton/VPR-datasets-downloader/issues/18 . I shall share code to fix it soon, keep an eye out on that issue.

Hey, you can check the issue i opened, where i clearly explain what the problem is: #18 . I shall share code to fix it soon, keep an eye out on that issue.

thankyou!

Hello @GyoungTaeChae
I have not pushed a PR on current repo yet but have released 2 data cleaning scripts in my repo which will give MSLS dataset in a manner required for VPR. It was very difficult to work with this dataset and was taking a lot of time everytime I set it up, hence I created these. You can take a look and let me know if that's helpful.
https://github.com/AnyLoc/Revisit-Anything/tree/main/dataloaders/msls_data_clean

Hello
I want to know how to use your code to process the msls dataset. After processing with your code, aren't the msls-test dataset and the msls-val dataset the same? Also, what is the msls-challenge dataset mentioned in the literature?
I am looking forward to your answer，thank you.

The dataset before formatting should look like this, by just unzipping the files provided by Mapillary


Allow to use with Arrays and non-associations

This PR allows to use cocoon with custom methods and doesn't bind it to AR only.
So ActiveAttr or just transient methods can be used.

Fix the issue when error is raised when an association doesn't exist (#85).
Allow to build the form for Non-AR associations, plural and singular. The only requirement is a method build_<association>.
Raise a descriptive error when it isn't association and no build_<association> method is defined.
Minor refactoring of create_object

May deal with the related issues: #79, #85, #86

I know this is a little old but... thank you @dnagir! You save my life 👍

Can we have the same feature for link_to_remove_association?


Fix update script to work with all v9 versions

fixes #1286
Copies layout-unbranded.html - this is needed for the new password page to work and was changed during v9.
Also updated the grep test so it works for v9
Note that Step by step pattern is still broken if updating from v9 - this PR does not fix that

thanks for reviewing, just to note the style issues are because there's a step in the update guide where you copy the latest application.scss, that would fix this


Ext overrides3 fix auth import s3 add

Description of changes

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #8704 (31d56b2) into extOverrides3 (b8576b4) will decrease coverage by 0.00%.
The diff coverage is 65.00%.

@@                Coverage Diff                @@
##           extOverrides3    #8704      +/-   ##
=================================================
- Coverage          56.31%   56.30%   -0.01%
=================================================
  Files                834      834
  Lines              47145    47167      +22
  Branches            9442     9449       +7
=================================================
+ Hits               26550    26558       +8
- Misses             19777    19791      +14
  Partials             818      818

Impacted Files
Coverage Δ

...cloudformation/service-walkthroughs/s3-auth-api.ts
17.64% <12.50%> (-4.58%)
:arrow_down:

...wscloudformation/utils/check-for-auth-migration.ts
100.00% <100.00%> (ø)

...udformation/service-walkthroughs/s3-walkthrough.ts
74.75% <100.00%> (+0.33%)
:arrow_up:

Continue to review full report at Codecov.

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


diagnosticsRelatedInformation: false

Scenario
int x = 2; // 1
//...
int x = 3; // 2

This shows error on 2, but nothing on 1.
Feature
To my knowledge coc does not have support for diagnostic related information. Hence when one uses ccls as a language server in coc, one can add
        "client": {
          "diagnosticsRelatedInformation": false
        }

which than serves the related information as warnings, which in the above case show up on 1, and the error on 2.
Is there such a possibility within the config of the coc-clang?

To my knowledge coc does not have support for diagnostic related information

No, coc does support this, set "diagnostic.separateRelatedInformationAsDiagnostics": true in your coc-settings.json.

@fannheyward Thank you for clearing that up for me. It works as expected, using this setting.


[2<IP_ADDRESS>] Backport patch to avoid corrupted osx_arm64 builds

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

For context see:

https://github.com/man-group/ArcticDB/issues/1322
https://github.com/facebook/folly/commit/e3dc03f5621935bf9caabadb9f46712f561747e9
https://github.com/llvm/llvm-project/issues/73313

@conda-forge-admin, please rerender

I more or less have been responsible for this branch for ArcticDB's needs.
I propose to merge this PR when the workflows complete and that I take care of any failures this might cause in the ecosystem (unlikely there will exist, IMO).


[Doc] Move Connector Admin CLI to Connector Guide

Fix https://github.com/apache/pulsar/issues/5015

LGTM

run java8 tests


[Typescript] beta.8 withTheme compile error

Hello! Thank you for your great job! 👍  It is amazing lib!
Problem description
withTheme is defined as interface not a function.
Steps to reproduce
import { withTheme } from 'material-ui/styles';
const Comp = withTheme(props => null);
// [ts] 'withTheme' only refers to a type, but is being used as a value here.

Versions

Material-UI: 1.0.0-beta.8

@sebald I didn't want to open up a new issue for this but, many of the Checkbox types are missing, checkedIcon, disabledRipple, disabledClassName, icon, indeterminate, inputProps, inputRef, checkedClassName. Most importantly though checked is missing.


[dtd] Add a 'getProjectRoots' method on the DTD file system API

This should return the value set by the 'setProjectRoots' method (which requires a secret). The 'getProjectRoots' should not require a secret.
@CoderDake @bkonyi

Why is this a 'area-vm' issue, can this be handled purely in DTD code ?

chatted with @bkonyi and updated the labels.

getProjectRoots

Out of interest, do we really want the project roots here, or will the workspace roots do?
If the goal is to restrict where the clients can read from, I think the workspace (eg. the folders the user opened in their IDE) might make more sense. However these are not necessarily project roots (because they may have opened a monorepo).
Currently, in Dart-Code we have to walk the tree to find projects (where there are pubspec.yamls) to send for PubRootDirectories, but maybe we should just report workspace folders to DTD and it could find the projects (to avoid each IDE/tool doing the same walking, and maybe doing it slightly differently)?

What is the difference between "project roots" and "workspace roots"? I have been using those terms interchangeably. Is a "project root" considered to be a directory that contains a pubspec.yaml file and a "workspace root" is a top level directory in the IDE?
If so, then I'm referring to workspace roots in this issue.

CC @CoderDake @bkonyi @helin24 - maybe we should come to agreement on terminology here. Should we change setProjectRoots and getProjectRoots to be setWorkspaceRoots and getWorkspaceRoots?

What is the difference between "project roots" and "workspace roots"? I have been using those terms interchangeably. Is a "project root" considered to be a directory that contains a pubspec.yaml file and a "workspace root" is a top level directory in the IDE?

Yeah, that's how I'd describe them. VS Code and LSP call the top-level folders you open (which can be one - a single-root workspace, or multiple - a multi-root workspace) "WorkspaceFolders". I use "project" to mean something with a pubspec (maybe "package" would be better for Dart, but in other languages they'd be Projects).
We also often refer to "analysis roots" in the analyzer, but for VS Code/LSP these are just the same as "Workspace Folders"/"Workspace roots" (with some uninteresting exceptions).

SGTM :)

This came up earlier and @jacob314 informed me that setPubRootDirectories doesn't actually need the individual project folders, and it would be better to send the IDE workspace roots.
He also pointed out that Pub has a concept of "Workspaces" and the term is a little overloaded.
So, it might be better to label these roots discussed above consistently as "IDE Workspace Roots" to avoid any confusion with "Pub Workspace Roots" that might exist in future. Although those might end up being the same on most cases, it's not guaranteed so it may bet best to avoid the ambiguous "Workspace Roots" without a qualifier.

And this should work fine for IntelliJ also.


Ability to Specify Listen IP Address

Hello,
It'd be really nice to be able to specify an specific IP address when starting xTeVe. Although xTeVe listens & serves on all interfaces, if you use xTeVe to generate your XEPG file then the XML file created will use whatever IP address xTeVe picked as the primary interface to populate the URL for images within the XML file. For me, xTeVe picks my VPN interface, So when I try to configure a new DVR in my local network, the XML file has the VPN interface IP address and no images will download for the guide as it's not reachable.  My work around for now is to use sed to replace the IP address in the XEPG file with one that is reachable and then serve that file via Apache instead.
<programme channel="1060" start="20191219203000 -0500" stop="20191219210000 -0500">
          <title lang="">TV Show</title>
          <desc lang="">My Favorite TV Show.</desc>
          <icon height="" src="http://<IP_ADDRESS>:34400/images/ab5bd084ca0825c7467d0c79bf4fb8cf.png" width=""></icon>
          <video></video>
          <date></date>
      </programme>

This will lead to many issues with DHCP or IPv6.
When starting xTeVe uses the last IP address of your OS, in your case that of your VPN interface.
With any HTTP request, xTeVe recognizes via which IP or domain the request was made. Except for downloading the xteve.xml, the URLs are generated immediately. (M3U, DVR lineup). The XML file can take several seconds to create, so the URLs in the XML are not changed immediately. The next time the xteve.xml file is created, the new URL will be taken into account
But that works with the xTeVe API
With the API function update.xepg you can create the xteve.xml and xteve.m3u file with with a specific IP address or domain.
Example with curl (IP <IP_ADDRESS>):
curl -X POST -H "Content-Type: application/json" -d '{"cmd":"update.xepg"}' http://<IP_ADDRESS>:34400/api/
xteve.xml:
  <tv generator-info-name="xTeVe" source-info-name="xTeVe - 2.1.1">
      <channel id="1105">
          <display-name>Bunny HD 1</display-name>
          <icon src="http://<IP_ADDRESS>:34400/images/0485a5651a59142f0a0d6edfe8069f54.png"></icon>
      </channel>
  </tv>

Example with curl (domain mbp.local):
curl -X POST -H "Content-Type: application/json" -d '{"cmd":"update.xepg"}' http://mbp.local:34400/api/
xteve.xml:
  <tv generator-info-name="xTeVe" source-info-name="xTeVe - 2.1.1">
      <channel id="1105">
          <display-name>Bunny HD 1</display-name>
          <icon src="http://mbp.local:34400/images/0485a5651a59142f0a0d6edfe8069f54.png"></icon>
      </channel>
  </tv>

While I appreciate the reply, I'm not sure how being able to specify a specific IP address to listen on could possibly lead to issues with DHCP or IPv6. The default behavior would still be to listen on all interfaces, but add a configuration option to allow you to specify just a single interface. I'm honestly hard pressed to think of any other software that won't let you do this and was a bit surprised when I discovered you couldn't. I'll look into patching it myself, wish me luck :)

this issue really blocks me from using it. on windows it takes always a random IP from those available. with 7 IPs on this machine it is almost impossible to get the right one. most of the time it takes the docker IPs and so it won't work. binding it to a fixed IP would come a long way.

xTeVe uses a Docker IP when it's ran outside of Docker? I find this behavior very strange.

An API (update.xepg) call after starting xTeVe solves the issue.
No idea if this works with Docker, my FreeBSD server also has several IP addresses, but the jail (similar to Docker) in which xTeVe runs has only one IP address from the server.
ifcofig server:
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
	ether d0:50:99:xx:xx:11
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	inet <IP_ADDRESS> netmask 0xffffffff broadcast <IP_ADDRESS>
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>

ifconfig xTeVe Jail:
igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6>
	ether d0:50:99:xx:xx:11
	inet <IP_ADDRESS> netmask 0xffffff00 broadcast <IP_ADDRESS>
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active

xTeVe uses a Docker IP when it's ran outside of Docker? I find this behavior very strange.

not a container IP. it's binding to the host IP of the docker NAT interface.

may i ask where the issue is ?
u call xteve via <IP_ADDRESS> as sample and the ip in the m3u will be <IP_ADDRESS> ...
u call xteve via domain behind reverse proxy and m3u will be generated via the domain.
so i wonder where there could be any issue ?
native on host, u use the host ip to connect to xteve
in docker in host/bridge mode, u map the port from host to docker, u use the ip from docker host
behind reverse proxy, upper steps, then map reverse to xteve, u se the domain from reverse
all checked and 100 % working here ... so may please leave a real life scenario where it aint work ?

i have this issue here: https://github.com/xteve-project/xTeVe/issues/84 and it only works again when xteve starts up with the same interface again. not sure what's going on.

https://raw.githubusercontent.com/xteve-repo/images/master/xteve-plex-device-not-found.png

I will really enjoy if its possible restrict the listening to a single IP address. I don't really want to listen on ipv6 address and make xTeVe available from the internet.
In may case plex and xTeVe are on the same machine, so listening on <IP_ADDRESS> address will be enough for me.
as we can specify a listening port we can specify an ip don't you think so ?

just dont open the port, then its not available outside your LAN.
in the end there is no benefit to bind the ip to one specific ... next step would be if you run xteve through a VPN and still want to be able to connect locally ...
so may describe what is really the point to bind to a specific ip ?

You totally right, but I just want to have the choice. most of users will use default that will be listening on all IP (<IP_ADDRESS> or ::), but some other users will want to change it, and will be be happy if they can :)
for example, "binding to the host IP of the docker NAT interface" and broadcasting on this interface do not make sense for me.
sometimes when you troubleshooting, you need to make the things clear by disabling unnecessary workload, traffic flows, etc.


🔭 Force exclude a dependency from a plan

Is your feature request related to a problem? Please describe.
I would like to have the ability to force exclude a specific dependency even though it is included in the plan by
- build
  - command: cache
    include: [Alamofire, SnapKit]

Describe the solution you'd like
§ rugby --plan build --exclude Alamofire SnapKit
§ rugby --plan build -e Alamofire SnapKit

@nonameplum Hello!
Now you can add exclude to the plan. Like this:
- build
  - command: cache
    include: [Alamofire, SnapKit]
    exclude: [SomePod]

In this solution, there is a problem. Your plan can contain many different commands and also, some of them can be duplicated (like drop command). So, it's not easy to add a common interface for different user plans. And it's not clear how to manage additional flags if command duplicates.
rugby --plan build --exclude Alamofire SnapKit
rugby --plan build -e Alamofire SnapKit

But anyway, thank you for your request, and feel free to add some more info or implement a draft.

Feel free to reopen the issue if you have more information

Yeah, I see. Thank you for your answer.
But we can't limit the plan with only one drop command. Someone already can use several drop commands in one plan. So we need a more general solution. The same with other different fields of each command of Rugby. There can be corner cases. But I think I understand your idea.
Right now It looks like a complex feature request for me.
So, let's reopen it, but sorry I don't have enough free time to implement any request for now.
Also, maybe you can find these features useful for your needs:

You can read all code with such option: https://github.com/swiftyfinch/Rugby/blob/main/Docs/Cache.md#keep-pods-group-in-project
Here you can create a base plan and reuse it in your other plans: https://github.com/swiftyfinch/Rugby/blob/main/Docs/Plans.md#-generate-example

Hello! I've decided to close the issue, because there is not enough demand.
Feel free to reopen it if it's still important to you.
And let's collect more votes for this feature request.


Fix format in maintainer guide

While reading the maintainer guide, I noticed an error in the Markdown format that makes it really difficult to read in the GitHub user interface:

This PR fixes that.

Thanks for the assistance!


Block JSEcoin

Someone Tweeted at me that there's another coin mining service named JSEcoin. Should have a look into adding that one to the blacklist too
Link: https://jsecoin.com

#17

#17 Added jsecoin to blacklist

I just downloaded this extension thanks you @arthurgeron for your great work!!!

This has been added to the blacklist. Closing.


graphite metrics not being emitted

Using the out of the box configuration, and this configuration file, I can't see graphite metrics being emitted on TCP or UDP port 9109 to localhost (the configured port).
## Allow anonymous users to connect, default is 'off'
##
## Default: off
##
## Acceptable values:
##   - on or off
allow_anonymous = on

## Allow operation even when a VerneMQ cluster is inconsistent,
## by removing consistency checks while registering new
## clients or subscribing/unsubscribing from topics
##
## Default: off
##
## Acceptable values:
##   - on or off
trade_consistency = off

## Allows a client to logon multiple times using the same client id
## (non-standard behaviour!).
##
## Default: off
##
## Acceptable values:
##   - on or off
allow_multiple_sessions = off

## Set the time in seconds VerneMQ waits before a retry, in case a (QoS=1 or QoS=2) message
## delivery gets no answer.
##
## Default: 20
##
## Acceptable values:
##   - an integer
## retry_interval = 20

## Set the maximum size for client IDs. MQTT v3.1 specifies a
## limit of 23 characters
##
## Default: 23
##
## Acceptable values:
##   - an integer
## max_client_id_size = 23

## This option allows persistent clients ( = clean session set to
## false) to be removed if they do not reconnect within 'persistent_client_expiration'.
## This is a non-standard option. As far as the MQTT specification is concerned,
## persistent clients persist forever.
## The expiration period should be an integer followed by one of 'd', 'w', 'm', 'y' for
## day, week, month, and year.
##
## Default: never
##
## Acceptable values:
##   - text
## persistent_client_expiration = 1w

## The maximum number of QoS 1 or 2 messages that can be in the process of being
## transmitted simultaneously. This includes messages currently going through handshakes
## and messages that are being retried. Defaults to 20. Set to 0 for no maximum. If set
## to 1, this will guarantee in-order delivery of messages.
##
## Default: 20
##
## Acceptable values:
##   - an integer
max_inflight_messages = 20

## The maximum number of messages to hold in the queue above
## those messages that are currently in flight. Defaults to 1000. Set to 0 for
## no maximum (not recommended). This option allows to control how a specific
## client session can deal with message bursts. As a general rule of thumb set
## this number a bit higher than the expected message rate a single consumer is
## required to process.
##
## Default: 1000
##
## Acceptable values:
##   - an integer
max_online_messages = 1000

## The maximum number of QoS 1 or 2 messages to hold in the offline queue.
## Defaults to 1000. Set to -1 for no maximum (not recommended). Set to 0
## if no messages should be stored offline.
##
## Default: 1000
##
## Acceptable values:
##   - an integer
max_offline_messages = 1000

## This option sets the maximum payload size that VerneMQ will allow for publishers.
## Messages that exceed this size will not be accepted by VerneMQ. The
## default value is 0, which means that all valid MQTT messages are accepted. MQTT
## imposes a maximum payload size of 268435455 bytes.
##
## Default: 0
##
## Acceptable values:
##   - an integer
message_size_limit = 0

## If a message is published with a QoS lower than the QoS of the subscription it is
## delivered to, VerneMQ can upgrade the outgoing QoS. This is a non-standard option.
##
## Default: off
##
## Acceptable values:
##   - on or off
upgrade_outgoing_qos = off

## listener.max_connections is an integer or 'infinity' defining
## the maximum number of concurrent connections. This option can be overridden
## on the protocol level by:
## - listener.tcp.max_connections
## - listener.ssl.max_connections
## - listener.ws.max_connections
## - listener.wss.max_connections
## or on the listener level by:
## - listener.tcp.my_tcp_listener.max_connections
## - listener.ssl.my_ssl_listener.max_connections
## - listener.ws.my_ws_listener.max_connections
## - listener.wss.my_wss_listener.max_connections
##
## Default: 10000
##
## Acceptable values:
##   - an integer
##   - the text "infinity"
listener.max_connections = 10000

## Set the nr of acceptors waiting to concurrently accept new connections.
## This can be specified either on the protocol level:
## - listener.tcp.nr_of_acceptors
## - listener.ssl.nr_of_acceptors
## - listener.ws.nr_of_acceptors
## - listener.wss.nr_of_acceptors
## or on the listener level:
## - listener.tcp.my_tcp_listener.nr_of_acceptors
## - listener.ssl.my_ssl_listener.nr_of_acceptors
## - listener.ws.my_ws_listener.nr_of_acceptors
## - listener.wss.my_wss_listener.nr_of_acceptors
##
## Default: 10
##
## Acceptable values:
##   - an integer
listener.nr_of_acceptors = 10

## listener.tcp.<name> is an IP address and TCP port that
## the broker will bind to. You can define multiple listeners e.g:
## - listener.tcp.default = <IP_ADDRESS>:1883
## - listener.tcp.internal = <IP_ADDRESS>:10883
## - listener.tcp.my_other_listener = <IP_ADDRESS>:10884
## This also works for SSL listeners and WebSocket handlers:
## - listener.ssl.default = <IP_ADDRESS>:8883
## - listener.ws.default = <IP_ADDRESS>:800
## - listener.wss.default = <IP_ADDRESS>:880
##
## Default: <IP_ADDRESS>:1883
##
## Acceptable values:
##   - an IP/port pair, e.g. <IP_ADDRESS>:10011
listener.tcp.default = <IP_ADDRESS>:1883

## listener.vmq.clustering is the IP address and TCP port that
## the broker will bind to accept connections from other cluster
## nodes e.g:
## - listener.vmq.clustering = <IP_ADDRESS>:18883
## This also works for SSL listeners:
## - listener.vmqs.clustering = <IP_ADDRESS>:18884
##
## Default: <IP_ADDRESS>:44053
##
## Acceptable values:
##   - an IP/port pair, e.g. <IP_ADDRESS>:10011
listener.vmq.clustering = <IP_ADDRESS>:44053

## Set the mountpoint on the protocol level or on the listener level
## - listener.tcp.mountpoint
## - listener.ssl.mountpoint
## - listener.ws.mountpoint
## - listener.wss.mountpoint
## listener level:
## - listener.tcp.my_tcp_listener.mountpoint
## - listener.ssl.my_ssl_listener.mountpoint
## - listener.ws.my_ws_listener.mountpoint
## - listener.wss.my_wss_listener.mountpoint
##
## Default: off
##
## Acceptable values:
##   - text
listener.mountpoint = off

## The cafile is used to define the path to a file containing
## the PEM encoded CA certificates that are trusted. Set the cafile
## on the protocol level or on the listener level:
## - listener.ssl.cafile
## - listener.wss.cafile
## or on the listener level:
## - listener.ssl.my_ssl_listener.cafile
## - listener.wss.my_wss_listener.cafile
##
## Default:
##
## Acceptable values:
##   - the path to a file
## listener.ssl.cafile = ./etc/cacerts.pem

## Set the path to the PEM encoded server certificate
## on the protocol level or on the listener level:
## - listener.ssl.certfile
## - listener.wss.certfile
## or on the listener level:
## - listener.ssl.my_ssl_listener.certfile
## - listener.wss.my_wss_listener.certfile
##
## Default:
##
## Acceptable values:
##   - the path to a file
## listener.ssl.certfile = ./etc/cert.pem

## Set the path to the PEM encoded key file on the protocol
## level or on the listener level:
## - listener.ssl.keyfile
## - listener.wss.keyfile
## or on the listener level:
## - listener.ssl.my_ssl_listener.keyfile
## - listener.wss.my_wss_listener.keyfile
##
## Default:
##
## Acceptable values:
##   - the path to a file
## listener.ssl.keyfile = ./etc/key.pem

## Set the list of allowed ciphers (each separated with a colon),
## on the protocol level or on the listener level. Reasonable defaults
## are used if nothing is specified:
## - listener.ssl.ciphers
## - listener.wss.ciphers
## or on the listener level:
## - listener.ssl.my_ssl_listener.ciphers
## - listener.wss.my_wss_listener.ciphers
##
## Default:
##
## Acceptable values:
##   - text
## listener.ssl.ciphers =

## If you have 'listener.ssl.require_certificate' set to true,
## you can create a certificate revocation list file to revoke access
## to particular client certificates. If you have done this, use crlfile
## to point to the PEM encoded revocation file. This can be done on the
## protocol level or on the listener level.
## - listener.ssl.crlfile
## - listener.wss.crlfile
## or on the listener level:
## - listener.ssl.my_ssl_listener.crlfile
## - listener.wss.my_wss_listener.crlfile
##
## Default:
##
## Acceptable values:
##   - text
## listener.ssl.crlfile =

## Enable this option if you want to use SSL client certificates
## to authenticate your clients. This can be done on the protocol level
## or on the listener level.
## - listener.ssl.require_certificate
## - listener.wss.require_certificate
## or on the listener level:
## - listener.ssl.my_ssl_listener.require_certificate
## - listener.wss.my_wss_listener.require_certificate
##
## Default: off
##
## Acceptable values:
##   - on or off
## listener.ssl.require_certificate = off

## Configure the TLS protocol version (tlsv1, tlsv1.1, or tlsv1.2) to be
## used for either all configured SSL listeners or for a specific listener:
## - listener.ssl.tls_version
## - listener.wss.tls_version
## or on the listener level:
## - listener.ssl.my_ssl_listener.tls_version
## - listener.wss.my_wss_listener.tls_version
##
## Default: tlsv1.2
##
## Acceptable values:
##   - text
## listener.ssl.tls_version = tlsv1.2

## If 'listener.ssl.require_certificate' is enabled, you may enable
## 'listener.ssl.use_identity_as_username' to use the CN value from the client
## certificate as a username. If enabled other authentication plugins are not
## considered. The option can be specified either for all SSL listeners or for
## a specific listener:
## - listener.ssl.use_identity_as_username
## - listener.wss.use_identity_as_username
## or on the listener level:
## - listener.ssl.my_ssl_listener.use_identity_as_username
## - listener.wss.my_wss_listener.use_identity_as_username
##
## Default: off
##
## Acceptable values:
##   - on or off
## listener.ssl.use_identity_as_username = off

## Set the path to an access control list file.
##
## Default: ./etc/vmq.acl
##
## Acceptable values:
##   - the path to a file
acl_file = ./etc/vmq.acl

## set the acl reload interval in seconds, the value 0 disables the
## automatic reloading of the acl file.
##
## Default: 10
##
## Acceptable values:
##   - an integer
acl_reload_interval = 10

## Set the path to a password file.
##
## Default: ./etc/vmq.passwd
##
## Acceptable values:
##   - the path to a file
password_file = ./etc/vmq.passwd

## set the password reload interval in seconds, the value 0 disables the
## automatic reloading of the password file.
##
## Default: 10
##
## Acceptable values:
##   - an integer
password_reload_interval = 10

## Specify the address and port of the bridge to connect to. Several
## bridges can configured by using different bridge names (e.g. br0). If the
## connection supports SSL encryption bridge.ssl.<name> can be used.
##
## Default: <IP_ADDRESS>:1889
##
## Acceptable values:
##   - an IP/port pair, e.g. <IP_ADDRESS>:10011
## bridge.tcp.br0 = <IP_ADDRESS>:1889

## Set the clean session option for the bridge. By default this is disabled,
## which means that all subscriptions on the remote broker are kept in case of
## the network connection dropping. If enabled, all subscriptions and messages
## on the remote broker will be cleaned up if the connection drops.
##
## Default: off
##
## Acceptable values:
##   - on or off
## bridge.tcp.br0.cleansession = off

## Set the client id for this bridge connection. If not defined, this
## defaults to 'name.hostname', where name is the connection name and hostname
## is the hostname of this computer.
##
## Default: auto
##
## Acceptable values:
##   - text
## bridge.tcp.br0.client_id = auto

## Set the number of seconds after which the bridge should send a ping if
## no other traffic has occurred.
##
## Default: 60
##
## Acceptable values:
##   - an integer
## bridge.tcp.br0.keepalive_interval = 60

## Configure a username for the bridge. This is used for authentication
## purposes when connecting to a broker that support MQTT v3.1 and requires a
## username and/or password to connect. See also the password option.
##
## Acceptable values:
##   - text
## bridge.tcp.br0.username = my_remote_user

## Configure a password for the bridge. This is used for authentication
## purposes when connecting to a broker that support MQTT v3.1 and requires a
## username and/or password to connect. This option is only valid if a username
## is also supplied.
##
## Acceptable values:
##   - text
## bridge.tcp.br0.password = my_remote_password

## Set the amount of time a bridge using the automatic start type will wait
## until attempting to reconnect. Defaults to 30 seconds.
##
## Default: 10
##
## Acceptable values:
##   - an integer
## bridge.tcp.br0.restart_timeout = 10

## If try_private is enabled, the bridge will attempt to indicate to the
## remote broker that it is a bridge not an ordinary client.
## Note that loop detection for bridges is not yet implemented.
##
## Default: on
##
## Acceptable values:
##   - on or off
## bridge.tcp.br0.try_private = on

## The cafile is used to define the path to a file containing
## the PEM encoded CA certificates that are trusted.
##
## Default:
##
## Acceptable values:
##   - the path to a file
## bridge.ssl.sbr0.cafile = ./etc/cacerts.pem

## Define the path to a folder containing
## the PEM encoded CA certificates that are trusted.
##
## Default:
##
## Acceptable values:
##   - the path to a file
## bridge.ssl.sbr0.capath = ./etc/cacerts

## Set the path to the PEM encoded server certificate.
##
## Default:
##
## Acceptable values:
##   - the path to a file
## bridge.ssl.sbr0.certfile = ./etc/cert.pem

## Set the path to the PEM encoded key file.
##
## Default:
##
## Acceptable values:
##   - the path to a file
## bridge.ssl.sbr0.keyfile = ./etc/key.pem

## When using certificate based TLS, the bridge will attempt to verify the
## hostname provided in the remote certificate matches the host/address being
## connected to. This may cause problems in testing scenarios, so this option
## may be enabled to disable the hostname verification.
## Setting this option to true means that a malicious third party could
## potentially inpersonate your server, so it should always be disabled in
## production environments.
##
## Default: off
##
## Acceptable values:
##   - on or off
## bridge.ssl.sbr0.insecure = off

## Configure the TLS protocol version (tlsv1, tlsv1.1, or tlsv1.2) to be
## used for this bridge.
##
## Default: tlsv1.2
##
## Acceptable values:
##   - text
## bridge.ssl.sbr0.tls_version = tlsv1.2

## Pre-shared-key encryption provides an alternative to certificate based
## encryption. This option specifies the identity used.
##
## Default:
##
## Acceptable values:
##   - text
## bridge.ssl.sbr0.identity =

## Pre-shared-key encryption provides an alternative to certificate based
## encryption. This option specifies the shared secret used in hexadecimal
## format without leading '0x'.
##
## Default:
##
## Acceptable values:
##   - text
## bridge.ssl.sbr0.psk =

## The integer number of seconds between updates of the $SYS subscription hierarchy,
## which provides status information about the broker. If unset, defaults to 10 seconds.
## Set to 0 to disable publishing the $SYS hierarchy completely.
##
## Default: 10
##
## Acceptable values:
##   - an integer
sys_interval = 10

## the interval we push metrics to the graphite server in ms
##
## Default: 15000
##
## Acceptable values:
##   - an integer
graphite.interval = 10000

## set the prefix that is applied to all metrics reported to graphite
##
## Default: vernemq
##
## Acceptable values:
##   - text
graphite.prefix = vernemq

## the tcp port of the graphite server
##
## Default: 2003
##
## Acceptable values:
##   - an integer
graphite.port = 9109

## the graphite server host name
##
## Default: carbon.hostedgraphite.com
##
## Acceptable values:
##   - text
graphite.host = localhost

## the graphite server api key
##
## Default: UNDEFINED
##
## Acceptable values:
##   - text
graphite.api_key = UNDEFINED

## Where to emit the default log messages (typically at 'info'
## severity):
## off: disabled
## file: the file specified by log.console.file
## console: to standard output (seen when using `vmq attach-direct`)
## both: log.console.file and standard out.
##
## Default: file
##
## Acceptable values:
##   - one of: off, file, console, both
log.console = file

## The severity level of the console log, default is 'info'.
##
## Default: info
##
## Acceptable values:
##   - one of: debug, info, warning, error
log.console.level = info

## When 'log.console' is set to 'file' or 'both', the file where
## console messages will be logged.
##
## Default: ./log/console.log
##
## Acceptable values:
##   - the path to a file
log.console.file = ./log/console.log

## The file where error messages will be logged.
##
## Default: ./log/error.log
##
## Acceptable values:
##   - the path to a file
log.error.file = ./log/error.log

## When set to 'on', enables log output to syslog.
##
## Default: off
##
## Acceptable values:
##   - on or off
log.syslog = off

## Whether to enable the crash log.
##
## Default: on
##
## Acceptable values:
##   - on or off
log.crash = on

## If the crash log is enabled, the file where its messages will
## be written.
##
## Default: ./log/crash.log
##
## Acceptable values:
##   - the path to a file
log.crash.file = ./log/crash.log

## Maximum size in bytes of individual messages in the crash log
##
## Default: 64KB
##
## Acceptable values:
##   - a byte size with units, e.g. 10GB
log.crash.maximum_message_size = 64KB

## Maximum size of the crash log in bytes, before it is rotated
##
## Default: 10MB
##
## Acceptable values:
##   - a byte size with units, e.g. 10GB
log.crash.size = 10MB

## The schedule on which to rotate the crash log. For more
## information see:
## https://github.com/basho/lager/blob/master/README.md#internal-log-rotation
##
## Default: $D0
##
## Acceptable values:
##   - text
log.crash.rotation = $D0

## The number of rotated crash logs to keep. When set to
## 'current', only the current open log file is kept.
##
## Default: 5
##
## Acceptable values:
##   - an integer
##   - the text "current"
log.crash.rotation.keep = current

## Name of the Erlang node
##
## Default<EMAIL_ADDRESS>##
## Acceptable values:
##   - text
nodename =<EMAIL_ADDRESS>
## Cookie for distributed node communication. All nodes in the
## same cluster should use the same cookie or they will not be able to
## communicate.
##
## Default: vmq
##
## Acceptable values:
##   - text
distributed_cookie = vmq

## Sets the number of threads in async thread pool, valid range
## is 0-1024. If thread support is available, the default is 64.
## More information at: http://erlang.org/doc/man/erl.html
##
## Default: 64
##
## Acceptable values:
##   - an integer
erlang.async_threads = 64

## The number of concurrent ports/sockets
## Valid range is 1024-134217727
##
## Default: 65536
##
## Acceptable values:
##   - an integer
erlang.max_ports = 65536

## Set scheduler forced wakeup interval. All run queues will be
## scanned each Interval milliseconds. While there are sleeping
## schedulers in the system, one scheduler will be woken for each
## non-empty run queue found. An Interval of zero disables this
## feature, which also is the default.
## This feature is a workaround for lengthy executing native code, and
## native code that do not bump reductions properly.
## More information: http://www.erlang.org/doc/man/erl.html#+sfwi
##
## Acceptable values:
##   - an integer
## erlang.schedulers.force_wakeup_interval = 500

## Enable or disable scheduler compaction of load. By default
## scheduler compaction of load is enabled. When enabled, load
## balancing will strive for a load distribution which causes as many
## scheduler threads as possible to be fully loaded (i.e., not run out
## of work). This is accomplished by migrating load (e.g. runnable
## processes) into a smaller set of schedulers when schedulers
## frequently run out of work. When disabled, the frequency with which
## schedulers run out of work will not be taken into account by the
## load balancing logic.
## More information: http://www.erlang.org/doc/man/erl.html#+scl
##
## Acceptable values:
##   - one of: true, false
## erlang.schedulers.compaction_of_load = false

## Enable or disable scheduler utilization balancing of load. By
## default scheduler utilization balancing is disabled and instead
## scheduler compaction of load is enabled which will strive for a
## load distribution which causes as many scheduler threads as
## possible to be fully loaded (i.e., not run out of work). When
## scheduler utilization balancing is enabled the system will instead
## try to balance scheduler utilization between schedulers. That is,
## strive for equal scheduler utilization on all schedulers.
## More information: http://www.erlang.org/doc/man/erl.html#+sub
##
## Acceptable values:
##   - one of: true, false
## erlang.schedulers.utilization_balancing = true

have you enabled the vmq_graphite plugin via vmq_admin plugin enable -n vmq_graphite ?

No, I'll give it a shot (this is all inside my docker environment, but I presume the one time command should stick).

was just playing with the graphite plugin... and figured that we're having a problem with it... will push a fix soon.

So can the plugin be enabled before server startup? vmq-admin I just noticed wants to talk to a running server, which doesn't work in docker and would still be awkward when starting up on a normal machine.

the plugin stuff is actually easier, you don't need -eval for that ;)
The plugins are initialized from lib/vmq_plugin.conf, you can edit this file directly:
{plugins,[
      {application,vmq_systree,[]},   %% delete this line if you don't need the $SYStree
      {application,vmq_passwd,[]},
      {application,vmq_acl,[]},
      {application,vmq_graphite,[]},  %% add this line for graphite
      {module,vmq_config,[{hooks,[{change_config,change_config,1}]}]},
      {module,vmq_lvldb_store,
              [{hooks,[{msg_store_write,msg_store_write,2}]}]},
      {module,vmq_lvldb_store,
              [{hooks,[{msg_store_delete,msg_store_delete,2}]}]},
      {module,vmq_lvldb_store,
              [{hooks,[{msg_store_find,msg_store_find,1}]}]},
      {module,vmq_lvldb_store,
              [{hooks,[{msg_store_read,msg_store_read,2}]}]}
]}.

That does drastically simply things from a dockerizing perspective so I'll modify my files now and look for the updated git commit.

sure.. btw. can you recommend a graphite docker image, if possible with grafana integration?

I'm actually using it with https://github.com/prometheus/graphite_exporter which is a bridge to the prometheus metrics system. That includes a docker build (how I'm deploying) though doesn't link to grafana without more work.

have to check prometheus out, looks very interesting. Btw.. are you interested in contributing to a vernemq_docker repo?

I've pushed the fix for the graphite plugin...
a git pull && make rel should do it.. revisit the config file.

@wrouesnel how did it go for you?

I close this for now. Feel free to reopen it if required.


tf.nn.softmax fails with dim > 0

If I do this:
import tensorflow as tf
import numpy as np

session = tf.InteractiveSession()
logits = np.array([[1.0,2.0,4.0],[1.0, 1.0, 1.0]])

tf.nn.softmax(logits,dim=1).eval()

I get:
InvalidArgumentError (see above for traceback): Requires start <= limit when delta > 0: 2/1 	 [[Node: range_9 = Range[Tidx=DT_INT32, _device="/job:localhost/replica:0/task:0/cpu:0"](range_9/start, Sub_6, range_9/delta)]]
But both of these work:
tf.nn.softmax(logits.T, dim=0).eval().T
tf.nn.softmax(logits, dim=-1).eval()

Those are what I would expect to get from the first one with dim=1.
I am using '0.12.0-rc1'

Thick to what works.

Documentation is confusing. It says the default is the last dimension, which I would expect to be dim=1 for a tensor with shape=(2,), @yuefengz can you comment?

came across with exactly the same problem. tf.version = 1.0.1

This is already fixed.


Changed save method to work

Updated to use io.file to write a bytestream instead of out-file, tested, worked great.

Type of Change

[x] Bug fix (non-breaking change, fixes #)

Purpose

Update files to show data instead of a series of numbers
Approach

Change t io.write because I forget how to do that in out-file

thank youuuu!


Added delete-empty.sh

{PR Description goes here}

I have checked the following requirements before making this PR.

[y] The script is marked as executable (chmod +x).
[y] I have added/updated the README entry for the script (if applicable).
[y] I have mentioned any outstanding dependencies and OS requirements for the script in the README.

Hi @VrajGohil, I closed your old PR #22. Please add the script file in patch-1 branch in your fork so that it can be included in this PR.

File added


exporter_exporter windows service functionality

Currently, exporter_exporter does not have means to run as a windows service. Running it as a service on windows without a service wrapper a la nssm/winsw would be ideal.
I also investigated the possibility of building it as an MSI package with INSTALL_OPTIONS a la wmi_exporter.
Is this worth investigating?

I don't have access to a Windows system to test on, but if you can get something working I'd definitely consider the patches.
Ideally it would fit with the existing release process.

I'd be interested in this too. We are currently using an in-house chocolatey package which basically wraps it in nssm to have a service.

The golang 'svc' package provides means to build Windows services. wmi_exporter and telegraf make use of it.
Examples can be found here:
https://github.com/golang/sys/tree/master/windows/svc/example
The bosun project has a very good example on how this works:
https://github.com/bosun-monitor/bosun/blob/master/cmd/scollector/service_windows.go
Perhaps we could implement similar functionality and then use smth like
exporter_exporter.exe -winsvc install

@frunzales I had a look at the bosun example, it looks reasonable enough. If the flag can be hidden on non-winodws OSes, that would be ideal. I'll happily accept a PR, but I can't work on this myself (just don't have access to something to test on, sorry).


View Data Button Missing in Jupyter Variable Tab

Environment data

VS Code version: 1.84.1
Jupyter Extension version (available under the Extensions sidebar): v2023.10.1100000000
Python Extension version (available under the Extensions sidebar): v2024.2.1
OS (Windows | Mac | Linux distro) and version: Windows 10 Enterprise
Python and/or Anaconda version: Python 3.11.5
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Jupyter server running: Local

Expected behaviour:
After running a notebook the listed variables of the type (list, data_frame, ndarray, ...) should have the show data button to open the data viewer.
Actual behaviour:
Button is missing and the data viewer cant be opened:
Steps to reproduce:

create a simple dataset like:
import pandas as pd
test = pd.DataFrame(data = [[0,1,2],[1,2,3]])

go to the jupyter tab in the terminal, to see that the "view data" button is 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!


youtube rag error

Bug Report
Description
Bug Summary:
youtube rag error
video url
https://www.youtube.com/watch?v=frcird_ffyc
Steps to Reproduce:
error information
ERROR:apps.rag.main:The content provided is empty. Please ensure that there is text or data present before proceeding.
Traceback (most recent call last):
  File "/app/backend/apps/rag/main.py", line 532, in store_youtube_video
    store_data_in_vector_db(data, collection_name, overwrite=True)
  File "/app/backend/apps/rag/main.py", line 618, in store_data_in_vector_db
    raise ValueError(ERROR_MESSAGES.EMPTY_CONTENT)
ValueError: The content provided is empty. Please ensure that there is text or data present before proceeding.

INFO:     <IP_ADDRESS>:0 - "POST /rag/api/v1/youtube HTTP/1.1" 400 Bad Request
Environment
ghcr.io/open-webui/open-webui:0.1.124

This feature relies on the presence of embedding closed captions or transcription to function. Your provided video hasn't got any:


IO-Events may get processed out of order

Due how the Thread-Model is implemented in Netty 4 you can get out-of order events, this is most likely noticed when writing to a Channel.
This order of method calls will produce an out-of-order write:

write1 (from within the eventloop)
write2 (from outside the eventloop but the eventloop is still processing stuff)
write3(from within the eventloop)

This will produce:

write1
write3
write2

I think the is incorrect as as long as you call for example write from another thread and the call is done after the first returns and before the third is done the order should be correct. It should have the same semantic as a concurrent queue. In fact this was the case in netty 3.
I think we need a fundamental fix here, maybe by have a queue per ChannelHandlerContext.
@trustin wdyt ?

Agree with @trustin , Application developer should guarantee the order, not the framework.Write from different thread should have "happen before".


[FS] Fix for NullReferenceException for MempoolSignaled async loop

Code to handle peers that may not have mempool behavior registered

How does this happen? The mempool behaviour should be in the list of template behaviours that get attached to every peer on connection?

This is the line where nullreferenceexception happens, so I guess if node is not using UseMempool it can happen. The logs a very limited

Hmm, actually, I think this probably happens when a peer is being disconnected.
Probably a race condition something like the following:

this.connection.ConnectedPeers; gets assigned to peers
A peer gets disconnected elsewhere & behaviour detachment starts. The mempool behaviour for that peer gets disposed
peers gets enumerated, causing the exception

That would definitely explain it. The code change should handle it though


_ebpf_program_program_information_provider_changed updates trampoline with older helper functions

_ebpf_program_program_information_provider_changed(..., const ebpf_extension_dispatch_table_t* provider_dispatch_table)

This function updates the trampoline with existing provider dispatch table, before updating it later.
        return_value = ebpf_update_trampoline_table(
            program->trampoline_table, program->program_information_provider_dispatch_table);

    program->program_information_provider_dispatch_table = provider_dispatch_table;

The provider dispatch table on program object is not updated until ebpf_extension_load returns.

    return_value = ebpf_extension_load(
        ...
        &program->program_information_provider_dispatch_table,
        _ebpf_program_program_information_provider_changed);

ebpf_extension_load sets the output dispatch table parameter only after NmrRegisterClient call returns.

ebpf_extension_load

status = NmrRegisterClient(client_characteristics, local_client_context, ...);

    *provider_dispatch_table = local_client_context->provider_dispatch_table;

The register client will cause attach_provider callback. This calls NmrClientAttachProvider which gets the provider dispatch table. The notify_change (_ebpf_program_program_information_provider_changed) callback happens right after this. But the program object's provider dispatch table is not updated at this point.
_ebpf_extension_client_attach_provider

    status = NmrClientAttachProvider(
        ...,
        &local_client_context->provider_dispatch_table);

    _ebpf_extension_client_notify_change(local_client_context);

Also it looks like in provider detach case _ebpf_program_program_information_provider_changed  will only mark the program as invalidated but not set the provider dispatch table to NULL.
        if (provider_dispatch_table == NULL) {
            program->program_invalidated = true;
            return;
        }

A secondary issue is that we currently don't test this code. https://github.com/microsoft/ebpf-for-windows/issues/300


Python 3.10 SSL Error

Looks like due to SSL deprecations and/or changes to default ciphers this no longer works on Python 3.10
Attempts to connect are met with
>>> client.connect()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\tehps\AppData\Local\Programs\Python\Python310\lib\site-packages\deluge_client\client.py", line 84, in connect
    self._connect()
  File "C:\Users\tehps\AppData\Local\Programs\Python\Python310\lib\site-packages\deluge_client\client.py", line 98, in _connect
    self._socket.connect((self.host, self.port))
  File "C:\Users\tehps\AppData\Local\Programs\Python\Python310\lib\ssl.py", line 1374, in connect
    self._real_connect(addr, False)
  File "C:\Users\tehps\AppData\Local\Programs\Python\Python310\lib\ssl.py", line 1365, in _real_connect
    self.do_handshake()
  File "C:\Users\tehps\AppData\Local\Programs\Python\Python310\lib\ssl.py", line 1341, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_HANDSHAKE_FAILURE] sslv3 alert handshake failure (_ssl.c:997)

If I set a cipher in client.py in the _create_socket method this seems to fix things
    def _create_socket(self, ssl_version=None, ciphers="AES256-SHA"):
        if ssl_version is not None:
            self._socket = ssl.wrap_socket(socket.socket(socket.AF_INET, socket.SOCK_STREAM), ssl_version=ssl_version, ciphers=ciphers)
        else:
            self._socket = ssl.wrap_socket(socket.socket(socket.AF_INET, socket.SOCK_STREAM), ciphers=ciphers)
        self._socket.settimeout(self.timeout)

Same problem here on fedora and python 3.10.3

Not sure how active development is on this project but I was able to get things working temporarily by subclassing and fixing this one method, sample below
# Fix for python 3.10 SSL issues
class SMADelugeRPCClient(DelugeRPCClient):
    def _create_socket(self, ssl_version=None):
        if ssl_version is not None:
            self._socket = ssl.wrap_socket(socket.socket(socket.AF_INET, socket.SOCK_STREAM), ssl_version=ssl_version, ciphers="AES256-SHA")
        else:
            self._socket = ssl.wrap_socket(socket.socket(socket.AF_INET, socket.SOCK_STREAM), ciphers="AES256-SHA")
        self._socket.settimeout(self.timeout)

...
client = SMADelugeRPCClient(host=settings.deluge['host'], port=int(settings.deluge['port']), username=settings.deluge['user'], password=settings.deluge['pass'])

@mdhiggins this worked for me, thank you!

I've tried to do a fallback fix but SSL is hard.


Set Require Only App-Extension-Safe API to Yes under build settings

Enables the framework to be included in App Extensions. Everything still builds just fine.

Thanks for opening the issue and the detailed description.
This issue has been fixed in a recently merged PR. The commit is this: https://github.com/cybertk/FLAnimatedImage/commit/3dfeba5cd295086608171613c6ecd7fc226d3e59
It's already on master and will be included in the shortly upcoming version 1.0.9.


Change blob to byte array in WebSocket

Purpose

Related issue: https://github.com/ballerina-platform/ballerina-lang/issues/8962

:white_check_mark: Build ballerina-lang 174 completed (commit https://github.com/ballerina-platform/ballerina-lang/commit/9d9edba3f2 by @riyafa)

:white_check_mark: Build ballerina-lang 202 completed (commit https://github.com/ballerina-platform/ballerina-lang/commit/fecbbd40e3 by @riyafa)


Using a generic like Omit on a @deprecated field in TS removes its strikethrough

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

VS Code Version: I'm using the last version of TS (4.4) and the last version of VSCode
OS Version: Same on macOS and in the web version of VSCode so I don't think that it's relevant here

In this code snippet, we can see that world is deprecated. But in the interface B, as we are using Omit, we are loosing the strike trough afterwards:

The weird thing is that @deprecated is still in the description when we hover on the variable:

Here is the snippet to reproduce: TypeScript Play
I don't know if that's a bug in TypeScript or in VSCode, but as @deprecated is present in the description, I think that it might be a VSCode error

Omit uses Pick which is mapped type.
/duplicate of https://github.com/microsoft/TypeScript/issues/42609
You should add your use case in that issue but with more real world examples.

Thanks @IllusionMH!
I looked for a similar issue but I didn't find it. Sorry for the noise


Please release asap

django-two-factor-auth has been incompatible with a lot of other projects for quite a long time now, specifically due to its ancient dependency on django-phonenumberfield. This seems to be fixed in master. Please make at least a patch release that fixes the dependency as soon as possible.

I am unaware of any incompatibilities with other projects, so I don't see any great urgency in doing a release.
Are you unable to install from git directly?

Hi,

I am unaware of any incompatibilities with other projects, so I don't see any great urgency in doing a release.

Any other project that keeps its dependencies up to date is affected.

Are you unable to install from git directly?

Yes, like anyone else doing serious software development. Dependencies from some git remote are not an option.
Please release your software so others can depend on it!

Any other project that keeps its dependencies up to date is affected.

That's an incompatibility with policy, not another package on PyPI.

Are you unable to install from git directly?
Yes, like anyone else doing serious software development. Dependencies from some git remote are not an option.

There's no need for snide remarks. If you really can't install from git, then I would suggest you vendor this package until we do a release.
I'm closing this issue. We will release when we're ready and there are other issues I would like to be fixed before making another release.

I'm closing this issue. We will release when we're ready and there are other issues I would like to be fixed before making another release.

You can actually make more than one release within any period of time. Making a release nornally is as simple as git tag - s.
But ok, I will fork and upload to PyPI under a different name if you prefer that. I do not think it makes the situation better for anyone, but maybe better than having everyone wait until you have collected enough changes to release.


bug failed to claimTask: failed to ListPendingTasks

FATA[2024-04-30T00:32:02.918-07:00] could not run ingestion                       error="failed to claimTask: failed to ListPendingTasks: Post "/#listPendingTasks": context deadline exceeded" pid=18903
exit status 1

thanks for reporting! the timeout is now fixed


ProgressBar doesn't exit cleanly on error

When call to get terminates abruptly due to an error in one of the tasks the progressbar continues counting off time.  Presumably we should call the finalize callback when we encounter an error.

Hmm, that is a problem. Calling finish on error seems wrong to me though, as there's no way to distinguish between an error and the actual end of task. I see three solutions to this:

Add yet another callback to get called on errors. Could potentially call it cleanup or something, and have it called at the end as well. I imagine this taking no parameters.
Handle this in the __exit__ method of Profiler. Unfortunately this will fail if the callbacks are set globally instead of contextually.
Modify finish to take a third parameter that's either None or the traceback. This would work, but destroys the symmetry between start and finish.

I'd prefer either the 1st or 3rd option.

In current code is there anything that would break by calling finish on error?

None at all. I would want to add a parameter though to note whether it was a clean finish or not. Could be boolean, or include the traceback (thinking about it's uses, I think I'd actual prefer the parameter to be clean_finish or errored, and boolean).

I trust your judgement here more than my own.


Adds block production time in logs

This provides useful information to measure block production time (specially for parachain) without having to enable detailed logs for millisecond resolution.

bot merge


Color.New() overload for accepting hex string

Color.FromHex() works but is less discoverable

resolved in #4170


Extremely large programs may exhaust memory due to COPY-INSTANCE on gate objects

Specifically the file urf3_155.qasm in the QASM benchmarks repo.

@notmgsk Where is the source of the copying now?

In ast.lisp -- copy-instance on gate-applications.

If you mean where is that invoked: I think in the various cost-functions.

 The question is: Why is it all being held in memory to exhaust it?


List of magic comments supported with dynamic imports

System Info
N/A
Details
I do not think all the magic comments used with dynamic imports in webpack are supported in rspack yet.
Can we please include in the documentation what all magic comments are supported and if there is any future plan for the ones that are not ?
thanks
Reproduce link
No response
Reproduce Steps
N/A

yes, of course we should do this


something's funky with limit

Using the testLimit code in olapscript-tests-and-utils:
.limit(5, 1) returned:
blank row
row 5
row 6
row 2
row 8
.limit (5, 5) returned:
row 8
row 10
row 9
row 11
row 12
.limit (5) returned:
blank row
row 5
row 6
row 2
row 8

This is probably a duplicate of #60 .

Tested and verified.


Parsing Markdown Lists

I'm trying to parse markdown lists, where you create a list using * like so:
This is my test case:
* List Item 1
* List Item 2
* List Item 3
Match lists and random text

Here's my grammar, where I'd like to have those list lines grouped together unambiguously into one object:

@{%
const appendItem = (a, b) => { return (d) => { return d[a].concat([d[b]]); } };
const emptyStr = (d) => { return ""; };
%}

page     -> block
          | page block         {% appendItem(0, 1) %}

block    -> list
          | line

list     -> listItem
          | list listItem      {% appendItem(0, 1) %}

listItem -> "\n*" string

line     -> "\n" string

string   -> null               {% emptyStr %}
          | string [^\n*]      {% appendItem(0, 1) %}

My problem is that this grammar is ambiguous because you can group the list lines * List Item a couple of different ways.  I want all the list items grouped together, but I'm not sure how to force this and make my grammar unambiguous.  Or maybe I'm just solving this problem completely wrong ;)
Slight side note, I assume the example text starts with a "\n" to make the grammar easier to parse.
Any help would be greatly appreciated, thanks!

Duplicate of #89. The problem is the same: prefer [a, a] to [a], [a].
Possible solutions are also the same:

Reject [a], [a] later in post-processor of the parent (page in this case).
Define the grammar in a way that doesn't allow two consecutive lists:

page     -> (list line | line):+ list:?
list     -> listItem:+
listItem -> "\n*" string
line     -> "\n" string
string   -> null | [^\n*]:+

In this example, each list must be followed by a line, so it can't be followed by another list.
Solution 1 is potentially slower but easier to implement. In solution 2, you get an array of pairs of blocks (list line) which you need to flatten.

@deltaidea Thanks for the reply, your example code is not only correct but also really informative!
Using reject seems like the most robust solution, since my actual problem is more complicated and has potentially many more types of blocks.
Also, you linked to #89 but @introrse said "I modified nearley.js" to get his example working, so maybe others should look here for how to solve (unless there is a difference between the two problems that I'm not getting)

Thanks for helping out with this, @deltaidea. And glad we could solve your problem, @techpines!


Create Base AVL Tree skeleton

Create class AVLTree with following methods:
__init__: Does not take in any input]
Initializes a bridges instance
insert: Take in key and value as the input
Automatically balance the tree upon insertion
Create an AVL tree element, put in balance factor, balance tree
visualize: Does not take in any input
Just call bridges.visualize()

Working on the testing of the tree