CapturePreview

Support capturing preview images from usb-controlled camera models.
Purpose
Capture live preview images from an attached camera
Usage
camera := Camera{}
camera.Init()
cameraFile, errInt := camera.CapturePreview()
if errInt != 0 {
    // problems
}
(*C.CameraFile)(cameraFile.file)

Thanks for the pull request! There's not a lot of activity on this project these days, so rather than wait on us, I've added you as a collaborator. You should be able to push your own updates as necessary.


crash when used in colab

i forked your "77 metaclasses in Python/overloading.py" to use in a project and found that even though it works normally on my local machine but it crashes in a googlecolab when used

It would be difficult to provide any help since you didn't provide any error output or logs, but most errors people report in this repo are just from using an out-of-date version of Python (typically resulting in an ImportError or AttributeError when trying to use a new feature). I believe colab runs Python 3.7 by default, which is now 4ish years old. Try upgrading your colab instance to a more recent version of Python. I don't recall exactly what I used but it would not surprise me if 3.8 or 3.9 was required for that overloading demo. Or, depending on the error, it might be an easy fix in 3.7. Note, however, that if you are using colab for tensorflow, tensorflow may not support any other version of Python and you may run into other issues because of that. Hope this helps and best of luck. Please post if you are able to solve the issue.


Local Development - Cannot find electron v0.24.0 from GitHub

Running "npm start" for development
Cannot find electron v0.24.0 from GitHub
at /Users//Work/git//kitematic/node_modules/gulp-download-electron/index.js:252:13
at /Users//Work/git//kitematic/node_modules/async/lib/async.js:254:17
at /Users//Work/git//kitematic/node_modules/async/lib/async.js:151:21
at /Users//Work/git//kitematic/node_modules/async/lib/async.js:251:21
at /Users//Work/git//kitematic/node_modules/async/lib/async.js:615:34
at /Users//Work/git//kitematic/node_modules/gulp-download-electron/index.js:191:13
at /Users/arunan/Work/git//kitematic/node_modules/gulp-download-electron/node_modules/github-releases/lib/github.js:33:18
at Request._callback (/Users//Work/git//kitematic/node_modules/gulp-download-electron/node_modules/github-releases/lib/github.js:78:16)
at self.callback (/Users//Work/git//kitematic/node_modules/gulp-download-electron/node_modules/github-releases/node_modules/request/request.js:129:22)
at Request.emit (events.js:95:17)
npm ERR! Darwin 14.3.0
npm ERR! argv "node" "/Users//.nvm/v0.10.38/bin/npm" "start"
npm ERR! node v0.10.38
npm ERR! npm  v2.7.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: gulp
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'gulp'.
npm ERR! This is most likely a problem with the Kitematic package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp
npm ERR! You can get their info via:
npm ERR!     npm owner ls Kitematic
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /Users//Work/git//kitematic/npm-debug.log

Does this happen on a fresh clone or only if you pulled before the electron rename?

We need to swap this download-electron package with an npm package

@jeffdm this happened from a fresh clone

@Elesant Just bought a new Mac, and works off a clean env.; tested with 2 other computers - cannot reproduce.
Closing for now.


Issue with CheckboxRenderer when used with generated columns on a grid

Hi,
I am facing issues with CheckboxRenderer in a vaadin 7.7.1 version when used with generated columns on a grid. Source code is as below:
BeanItemContainer bic = new BeanItemContainer<>(CustomClass.class);
GeneratedPropertyContainer container = new GeneratedPropertyContainer(
bic);
setContainerDataSource(container);
container.addGeneratedProperty("isAccepted", new PropertyValueGenerator() {
@Override
public Boolean getValue(Item item, Object itemId, Object propertyId) {
SpinSignal signal = (SpinSignal) itemId;
			return signal.getSignalDescription().getUsed();
		}

		@Override
		public Class<Boolean> getType() {
			return Boolean.class;
		}
	});

Column isAcceptedColumn = getColumn("isAccepted");
isAcceptedColumn.setHeaderCaption("Is Accepted");
isAcceptedColumn.setRenderer(new CheckboxRenderer());
But this column is not getting rendered at all in UI and I dont see any errors also. Can you please check and help? I used 1.2.0 version of the add-on.
Best Regards,
Ramesh

I haven't yet had time to test this myself, but I attempt to do so as soon I can. However I would like to ask couple of questions

Did you remember to recompile the widgetset after you added the add-on to your Project?  Knowing how Grid behaves, and how Renderers are used, missing client renderer would manifest exactly like you see.

Does same issue happen with other Renderers too with generated columns? Renderers should be independent of that column is being generated column. Thus if there is an issue, it should happen with all Renderers and issue being probably somewhere else.

Hi,
Thank you for the reply, adding an add-on first time, didnt know had to compile the widgeset, I did now and tried again but with no luck. Still ther rendering doesn't work. Could you please check?

I see the generated xml has the RenderersCollectionWidgetSet included...
AppWidgetset.gwt.xml.txt

I tried the following test application, and I can't replicate your issue. The application and the Renderer works correctly.
`package com.example.myapplication;
import java.util.Random;
import javax.servlet.annotation.WebServlet;
import org.vaadin.grid.cellrenderers.editoraware.CheckboxRenderer;
import com.vaadin.annotations.Theme;
import com.vaadin.annotations.VaadinServletConfiguration;
import com.vaadin.data.Item;
import com.vaadin.data.util.GeneratedPropertyContainer;
import com.vaadin.data.util.PropertyValueGenerator;
import com.vaadin.server.VaadinRequest;
import com.vaadin.server.VaadinServlet;
import com.vaadin.ui.Button;
import com.vaadin.ui.Grid;
import com.vaadin.ui.Grid.Column;
import com.vaadin.ui.Label;
import com.vaadin.ui.TextField;
import com.vaadin.ui.UI;
import com.vaadin.ui.VerticalLayout;
@Theme("mytheme")
public class MyUI extends UI {
@Override
protected void init(VaadinRequest vaadinRequest) {
    final VerticalLayout layout = new VerticalLayout();

    Grid grid = new Grid();
    grid.addColumn("string");
    for (int i=0;i<100;i++) {
    	grid.addRow("String "+i);
    }

    GeneratedPropertyContainer container = new GeneratedPropertyContainer(grid.getContainerDataSource());
    container.addGeneratedProperty("isAccepted", new PropertyValueGenerator() {
    	@Override
    	public Boolean getValue(Item item, Object itemId, Object propertyId) {
    			Random random = new Random();
    			return random.nextBoolean();
    		}

    		@Override
    		public Class<Boolean> getType() {
    			return Boolean.class;
    		}
    	});
    grid.addColumn("isAccepted",Boolean.class);
    Column isAcceptedColumn = grid.getColumn("isAccepted");
    isAcceptedColumn.setHeaderCaption("Is Accepted");
    isAcceptedColumn.setRenderer(new CheckboxRenderer());
    grid.setEditorBuffered(false);
    grid.setEditorEnabled(true);

    final TextField name = new TextField();
    name.setCaption("Type your name here:");

    Button button = new Button("Click Me");
    button.addClickListener( e -> {
        layout.addComponent(new Label("Thanks " + name.getValue()
                + ", it works!"));
    });

    layout.addComponents(grid, name, button);
    layout.setMargin(true);
    layout.setSpacing(true);

    setContent(layout);
}

@WebServlet(urlPatterns = "/*", name = "MyUIServlet", asyncSupported = true)
@VaadinServletConfiguration(ui = MyUI.class, productionMode = false)
public static class MyUIServlet extends VaadinServlet {
}

}
`


"Honor" column ?

The "Honor" column has disappeared from https://www.codewars.com/users/leaderboard/kata

It did not disappear, it just got shifted out of view by globaldebugs clan name which causes layout issues. Make it disappear and honor column pops back in.

Fixed


Dead code found at line 78

In file bigint.cpp around line 73, I found this code:
Bigint &Bigint::operator+=(Bigint const &b)
{
    if (!b.positive) {
        return *this -= b;
    }
    if (!b.positive && positive) {
        positive = false;
    }

The first if make it returned when !b.positive, then the second if can't be true, right? So it should be dead code

pull #11

pull #11 closed. pull #12 instead

Closed since https://github.com/kasparsklavins/bigint/pull/12 has been merged.


org.openxmlformats.wordprocessingml.document is unrecognized ZTYPEUTI

Two issues here. First, I'd really love #16 to be solved in some better way if possible - I don't like seeing those errors every single time I run.
More relevantly to this issue, I'm getting
org.openxmlformats.wordprocessingml.document is unrecognized ZTYPEUTI

Full output:
Starting Apple Notes Parser at Sat Jul  9 20:09:47 2022
Storing the results in /Users/dmd/Dropbox/bk/AppleNotes/2022_07_09-20_09_47

Created a new AppleBackup from Mac backup: /Users/dmd/Library/Group Containers/group.com.apple.notes/
Guessed Notes Version: 15
Skipping Note ID 19 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 25 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 1231 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 1232 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 1288 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 1311 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 1403 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 1562 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 1621 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 1638 due to a missing folder or account, check the debug log for more details.
Skipping Note ID 1642 due to a missing folder or account, check the debug log for more details.
org.openxmlformats.wordprocessingml.document is unrecognized ZTYPEUTI, please submit a bug report to this project's GitHub repo to report this: https://github.com/threeplanetssoftware/apple_cloud_notes_parser/issues
Updated AppleNoteStore object with 151 AppleNotes in 10 folders belonging to 1 accounts.
Adding the ZICNOTEDATA.ZPLAINTEXT and ZICNOTEDATA.ZDECOMPRESSEDDATA columns, this takes a few seconds

I've had these debug statements running for long enough as I look at my test data that I'm fairly certain nothing is actually being missed in these null notes. I'll rework the error messages and the statement selecting notes to avoid notes with null protobufs. Apologies for the spam!

Ok, commit a072573 should address these issues. It removes the debug spam and cleans up some document handling. It should also handle some other Office file formats now, too.
Please let me know if you see any issues.


Automate and upgrade this gem

This PR is importing a Dockerfile and docker-compose.yml file which helps creating automatically build new version of the gem.
You actually have to update the version.rb with the Dragula version and then run the make_new_release.sh.
This will build the gem Docker image and then start to build the new version.
Finally this gem upgrade the library to the version 3.7.2 which is right now the latest version.

Why are you using docker for this?

In order to not have to install different versions Ruby and all the dependencies (I like to keep things ordered).

Yes but not sure this gem has to come with a docker dependency. I like your solution but without having to have docker to do a simple file update.

Actually it's not really a dependency for that gem, you can work ignoring it, but I do recommend you to use it: It's simple and easy.
How are you upgrading a library within this kind of wrapper gem today?

Here is an example of the output of the make_new_release.sh script:
./make_new_release.sh
Ensuring Docker image zedtux/perfect-scrollbar-rails exists ...
Updating library code to version 0.6.14 ...
Downlading perfect-scrollbar 0.6.14 ...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   597    0   597    0     0   1128      0 --:--:-- --:--:-- --:--:--  1128
100 33042  100 33042    0     0  24565      0  0:00:01  0:00:01 --:--:--  283k
Extracting perfect-scrollbar archive ...
Installating assets files ...
Done!
Committing new version ...
[master d723f55] Import version 0.6.14
 3 files changed, 3 insertions(+), 3 deletions(-)
Releasing gem ...
perfect-scrollbar-rails 0.6.14 built to pkg/perfect-scrollbar-rails-0.6.14.gem.
Tagged v0.6.14.
Pushed git commits and tags.
Pushed perfect-scrollbar-rails 0.6.14 to rubygems.org.

I like the solution, I just don't want to have docker installed every time I want to update the gem, do you know what I mean? This could work for other libraries, but not simple file transfer.

I see what you mean, but for someone like me (and we are more and more) which is using Docker for everything, it's just normal to build an image for that.
Maybe you're not familiar with Docker, and you're not using it. I can then understand, but have a messy system is not for me. I like to be able to delete an image and the cleaning is done.
Putting things in a container, using it as much as I want, and "just" delete when done, or "just" start it in order to perform the task, is the way to go in my opinion.
You didn't answered my question: How are you updating a gem like this one today? Given a new release of dragula is released, what are the steps you're following in order to reach the point where the new gem is published on rugygems.org?

Ok, I will give your workflow a try in the next days and let you know.

@why-el do you have any news? The current version of Dragula is now 3.7.2, maybe it's the good time to test the upgrade 😉

Indeed, I will get back to you in a day or two, sorry for the late
responses. :(
On Tue, Aug 22, 2017 at 2:12 AM, Guillaume Hain<EMAIL_ADDRESS>wrote:

@why-el https://github.com/why-el do you have any news? The current
version of Dragula is now 3.7.2, maybe it's the good time to test the
upgrade 😉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/why-el/dragula-rails/pull/3#issuecomment-323929096,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQ-s4dm9Z18_5uDXjr-ZpepyJw9JK0Lks5sanFKgaJpZM4LJJUW
.

--
Wael Khobalatte


Create new Accordian for Notices

Currently notices are not in accordian and taking too much space in panel.

Done as part of 0.4.0 release.


Create REST API Endpoint for Sections

Create an API endpoint for querying sections in the form /sections/id and /sections/search?property=value making sure to incorporate proper HTTP status codes.

[ ] /sections/id
[ ] /sections/search?property=value
[ ] Write sections API documentation

See https://github.com/UTDNebula/nebula-api/commit/238bb974e12a7212e84ecd9c599613188b64eef7 for /sections/id
See https://github.com/UTDNebula/nebula-api/commit/b124de45944f2ee3579b8945e90df36f88093675 for 'sections/search?property=value`

@heartgg take the code for both sections and middleware and place them into their own directories/files. Have a directory dedicated to middleware as well as having distinct files for each endpoint makes maintaining the codebase far easier as it grows in size. You should them import the code where necessary.
Additionally, please provide documentation for the endpoints in docs.

@CharlieMahana
I have implemented the above. However, I wasn't sure how to have separate files for each endpoint, so I ended up using routers for each umbrella endpoint (i.e. sections has its own router file, and courses will have a separate file as well).


Font sensitive em dimensions

While FeatherGUI has both absolute and relative coordinates in terms of pixels, often times the absolute height of an element is dependent on the line-height of the font being used. A custom layout can't really be used to solve this because in some cases the text may take up more than one line, at which point a layout function cannot determine what the true line-height is. The best way to deal with this would be to allow skins to specify dimensions in "em", where 1em is equal to the line-height of the current font.
How exactly this should be implemented is a bit tricky. Either the "em" calculations would need to be done inside the element itself (which could potentially be complicated or expensive), or "em" would only be tracked inside the skin itself, and would then get "resolved" down to an absolute pixel amount when the skin is applied based on the current font.
This would likely need to be tied in to skin inheritance (See issue #1)

A very simplistic version of this has been implemented, but it does not respond correctly to lineheight specified in the layout because the font information isn't available when the unit is resolved.


Does the Domain Adaptation dataset have 3D semantic labels?

As far as I can tell, the .tfrecord of the domain_adaptation do not have any "segmentation_label_compressed" properties. Is this accurate?

That's correct. The domain adaptation set does not have any segmentation labels.


Handling multiple ADO orgs

[Enter feedback here]
The instructions don't mention that you need to add your public ssh key to each ADO org that you need to git clone from.

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

ID: 7fde585e-edbd-c738-4d34-b1dfca1ef033
Version Independent ID: 974698f8-cb53-24d4-f75f-a88c16f8e51c
Content: Connect to your Git repos with SSH - Azure Repos
Content Source: docs/repos/git/use-ssh-keys-to-authenticate.md
Product: devops
Technology: devops-code-git
GitHub Login: @vijayma
Microsoft Alias: vijayma

Fixed in https://github.com/MicrosoftDocs/azure-devops-docs/pull/12769


cert fails when output_path is different than .

When setting up the output_pathparameter the cert command fails.
From what I could see the .cer file is stored in the root folder instead of chose one, thus the file is not found.
Extract from my Fastfile :
  cert(
    development: options[:development],
    output_path: "./fastlane/profiles"
    #team_id: "yourteamid" # Fails to work with team_id from AppFile https://github.com/KrauseFx/fastlane/issues/700
  )

Logs
[17:41:17]: Starting login with user<EMAIL_ADDRESS>[17:41:57]: Successfully logged in
[17:42:08]: Variable Dump:
[17:42:08]: {:PLATFORM_NAME=>nil, :LANE_NAME=>"dev"}
[17:42:08]: No such file or directory @ rb_sysopen - ./fastlane/profiles/E9X8ZTAN62.cer

On disk :

Hey @nicolasbraun! Are you still running into this issue? Apologies for the long response time, but would you mind updating your tools and trying this again? Please reopen the issue if you're still having trouble. Thanks! :bear:

Hi @ohwutup
From my last test on version 1.63.0 the output_pathparamter is now ignored
Fastfile :
  cert(
      development: development,
      username: ENV["APPLE_ID"],
      team_id: ENV["TEAM_ID"],
      output_path: "./test"
  )

Console :
INFO [2016-02-25 10:25:45.10]: ------------------
INFO [2016-02-25 10:25:45.10]: --- Step: cert ---
INFO [2016-02-25 10:25:45.10]: ------------------

+---------------+------------------------------------------------------+
|                        Summary for cert 1.3.0                        |
+---------------+------------------------------------------------------+
| development   | false                                                |
| force         | false                                                |
| username      |<EMAIL_ADDRESS>                              |
| team_id       | XXX                                           |
| keychain_path | /Users/nicolasbraun/Library/Keychains/login.keychain |
+---------------+------------------------------------------------------+

PS : I cannot reopen the issue (http://stackoverflow.com/questions/21333654/how-to-re-open-an-issue-in-github)

hey @nicolasbraun, apologies that you couldn't reopen the issue... it does look like the output_path option is being used, but it is just not being printed out in the table as you can see here: https://github.com/fastlane/cert/blob/master/lib/cert/runner.rb#L18.
is this not working for you? or were you just expecting to see the line printed in the table?

Oh you are right, my bad.
It is working. I believe this should be printed out :)
Thanks

Awesome! Glad it is working for you! If you would like to submit a PR with the change to keep it printing out, we would be happy to have some discussion about it over there! :rocket: :+1:


Upload directories

Expected Behavior
I have this directory structure:
dist/
  index.html
  img/
      logo.png
      hero.jpg
  css/
      style.css
  js/
      index.js

And I have this config file:
    {
        "name": "myprojcet.com",
        "privateKeyPath": "d:/mypriv.ppk",
        "username": "myuser",
        "protocol": "sftp",
        "remotePath": "/home/myuser/web/myproject.com/skins/",
        "host": "myserver.com",
        "watcher": {
            "files": "dist/*",
            "autoUpload": true
        }
    }

Now the index.html is loading up, but the img, css and js directories aren't.

I tried to use multiple contexts solution, but it didn't helped.
Tried to use in "files" options like this: "dist/|dist//*" with | : ; , and ! spearators.

Version: 1.2.5
Platform: Windows 10

dist/**/*
Balázs Winkler<EMAIL_ADDRESS>于 2018年7月23日周一 22:08写道：

Expected Behavior
I have this directory structure:
dist/
index.html
img/
logo.png
hero.jpg
css/
style.css
js/
index.js
And I have this config file:
{
    "name": "myprojcet.com",
    "privateKeyPath": "d:/mypriv.ppk",
    "username": "myuser",
    "protocol": "sftp",
    "remotePath": "/home/myuser/web/myproject.com/skins/",
    "host": "myserver.com",
    "watcher": {
        "files": "dist/*",
        "autoUpload": true
    }
}

Now the index.html is loading up, but the img, css and js directories
aren't.

I tried to use multiple contexts solution, but it didn't helped.
Tried to use in "files" options like this: "dist/|dist//*" with |
: ; , and ! spearators.

Version: 1.2.5
Platform: Windows 10

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/liximomo/vscode-sftp/issues/252, or mute the thread
https://github.com/notifications/unsubscribe-auth/AJXIoeiT7GiwicQ5NOM80ao1EJ_zARVFks5uJdjUgaJpZM4VbD-d
.

Thanks. This solved the problem.
I suggest to implement this answer to the basic documentation.


[Issue #5] enable user provided schema when reading exasol table

Good morning @3cham,
Thanks for PR! Please keep up the good work!
Overall, everything looks good. However, I have some suggestions. I am going to list them from easier (easy to explain :)) to harder points.

[ExasolRelation] Remove using configSchema in buildScan() here. The user schema will be again automatically selected here.

[ExasolRelation] Keep querySchema function as before. But please rename it to inferSchema, that describes it clearly.

[ExasolRelation] Take configSchema parameter as option, e.g configSchema: Option[StructType]

[ExasolRelation] Change overrided schema function to get configSchema if available and only otherwise inferSchema. Usually, in Scala there are many ways to do this with options. However, let us stick with fold. So in the schema function should be for example:

// This will use inferSchema if configSchema is None
 override def schema: StructType = configSchema.fold(inferSchema){ userSchema =>
    logger.info(s"Using provided schema $userSchema")
    userSchema
  }

You can read about it here, http://blog.originate.com/blog/2014/06/15/idiomatic-scala-your-options-do-not-match/, https://kwangyulseo.com/2014/05/21/scala-option-fold-vs-option-mapgetorelse/

[DefaultSource] Here, let's put query string check and manager creating part into its own private function. E.g,

private def fromParameters(params: Map...): (String, ExasolManager) = {
    val queryString = parameters.get("query") match ..
    ...
    val manager = ExasolConnectionManager(config)
   (queryString, manager)
}

And both createRelation function call this, and return respective ExasolRelation.
 override def createRelation(...): BaseRelation = {
    val (queryString, manager) = fromParameters(parameters)
    new ExasolRelation(sqlContext, queryString, None, manager)
  }

  override def createRelation(
    ....,
    schema: StructType
  ): BaseRelation = {
    val (queryString, manager) = fromParameters(parameters)
    new ExasolRelation(sqlContext, queryString, Option(schema), manager)
  }

Hope these are clear. Please let me know if you have questions!

Hi @morazow, please check the following up commits. If you don't mind, allow me to change the author info in the last PR ;)

Hey @3cham ,
PR looks good! Going to merge soon!
Yes, sure. I was also confused to seeing you in contributors list. Just for your information, I am also going to add authors list from my fork, https://github.com/morazow/spark-exasol-connector/blob/task/authors/AUTHORS.md.
Best

@morazow: many thanks, I used my lap from work with a different email config. That's why I need to change the info from the last PR.


Docs example: Use Object.assign also for updating state.todos

The current example throws a syntax error (unexpected token). Not sure if we can even use "...-syntax" in object literals? Maybe this example just got never checked. But please let me know if I'm wrong.

Spread syntax is possible with ES7 extension.
That doc page already mentioned that you can use Object.assign instead, but generally spread looks more readable.

Good call. We shouldn't use ES7 proposals in docs.

@gaearon that's weird, because rest of the examples in this file still uses it.
Does that mean, that I can send a PR with replacement for them too?

The rest of the examples use ES6 array spread operator, not ES7 object spread operator proposal.

Ok, got it, that makes sense


Export not found project

Hello, I am using the library to interact with Gitlab but when I go to download the repository files it gives me this error, if someone could help me
Thanks

When I run this method it returns this to me
https://gitlab.com/api/v4/projects/26975042/export
{"id":26975042,"description":"","name":"template-technique-java-springboot","name_with_namespace":"cli-project / template-technique-java-springboot","path":"template-technique-java-springboot","path_with_namespace":"proyectos/template-technique-java-springboot","created_at":"2021-05-27T18:28:38.369Z","export_status":"none"}

Are your credentials correct for that project? I.e. does it have the correct permissions?

¿Son correctas sus credenciales para ese proyecto? Es decir, ¿tiene los permisos correctos?

Where you can verify these permissions, however that same user is the creator of that repository

Hey... Did you manage to solve this, or it this still an issue?

I'm going to close this due to no response and no way to reproduce.


Parametric DMD for heat conduction example

Parametric DMD for heat conduction example

Example command (at examples/dmd directory):

rm -rf parameters.txt
python3 parametric_heat_conduction.py -r 0.1 -cx 0.1 -cy 0.1 -o 4 -visit -offline -rdim 16
python3 parametric_heat_conduction.py -r 0.1 -cx 0.1 -cy 0.5 -o 4 -visit -offline -rdim 16
python3 parametric_heat_conduction.py -r 0.1 -cx 0.5 -cy 0.1 -o 4 -visit -offline -rdim 16
python3 parametric_heat_conduction.py -r 0.1 -cx 0.5 -cy 0.5 -o 4 -visit -offline -rdim 16
python3 parametric_heat_conduction.py -r 0.5 -cx 0.1 -cy 0.1 -o 4 -visit -offline -rdim 16
python3 parametric_heat_conduction.py -r 0.25 -cx 0.2 -cy 0.4 -o 4 -visit -online -predict
python3 parametric_heat_conduction.py -r 0.4 -cx 0.2 -cy 0.3 -o 4 -visit -online -predict

Offline phase output:

step 50, t = 0.500000
Creating DMD with rdim: 16
Elapsed time for training DMD: 9.828897e-01 second
Elapsed time for solving FOM: 1.608722e+01 second

Online phase output ( -r 0.25 -cx 0.2 -cy 0.4 -o 4 case):

Predicting temperature using DMD at: 0.500000
Relative error of DMD temperature (u) at t_final: 0.500000 is 0.002553
Elapsed time for predicting DMD: 3.375082e+00 second
Elapsed time for training DMD: 1.508939e+00 second
Elapsed time for solving FOM: 1.735957e+01 second

Online phase output (-r 0.4 -cx 0.2 -cy 0.3 -o 4 case):

Predicting temperature using DMD at: 0.500000
Relative error of DMD temperature (u) at t_final: 0.500000 is 0.069653
Elapsed time for predicting DMD: 3.164990e+00 second
Elapsed time for training DMD: 1.443344e+00 second
Elapsed time for solving FOM: 1.554798e+01 second

new pylibROM bindings

Bindings for CSVDatabase and HDFDatabase. Only minimal member functions are binded now.
Binding for getParametricDMD:

c++ getParametricDMD passes a pointer reference as output parameter, which format cannot be supported in python.
In python, a newly created pointer is returned from the function.
In c++, the pointer reference determines the derived class type of DMD. In python, we pass the class method itself instead. For example, note the first argument in the following snippet:

import pylibROM.algo as algo
dmd_u = algo.getParametricDMD(algo.DMD, param_vectors, dmd_paths, desired_param)

python_utils.StopWatch module added in place of mfem::StopWatch class, which is not supported by PyMFEM.
Re-wrote PointwiseSnapshot class in python. However, this is currently not supported:

PointwiseSnapshot class requires FindPointsGSLIB::GetCode() function which is supposed to return mfem::Array<unsigned int>. However, this is currently not working properly on PyMFEM side. See the issue.

Miscellaneous PyMFEM issue:
The latest version (v<IP_ADDRESS>) of PyMFEM has an installation issue with gslib. To install PyMFEM with gslib, PyMFEM must be v.<IP_ADDRESS>. The following command will install PyMFEM with parallel mfem and gslib:
python3 setup.py install --with-parallel --with-gslib

Add --user flag if this is installed on LC quartz.

@ebchin Please check out this parametric DMD examples in pylibROM. Will this be helpful?


Floralchemy Values

Looks like we need to specify which fluids generate mana.

Hm. So, the conversion rate of fuel to mana is 2:1 for solid fuel in the endoflame. So, a piece of charcoal which has a burn time of 1600 ticks would produce 800 mana.
Diesel produces 4096 rf/t for 125 ticks, or 1 bucket produces 512,000 rf. A stirling generator from EIO with an octadic capacitor produces 128,000 rf at 80rf/t with one charcoal. Not sure we'd want to use octadic stirling generator as the base, as most other mods are less efficient than this. I think double-layer generates 32,000rf at 40rf/t.  If we use a similar conversion ratio, a bucket of diesel fuel would produce 3,200 mana, which is half as much as an entropinnyum would produce from a single explosion. If we go closer to the double-layer capacitor for the base, a bucket of diesel fuel would produce 12,800, which would make the petropetunia pretty damn effective.
Anyway, I'll continue to think about this later.


CRITICAL:ZODB.FileStorage:/.../worm.fs Database records<PHONE_NUMBER>9 seconds in the future

This message prints when a ZODB store is reopened. Doesn't seem to affect data integrity.

Unable to reproduce this one.


[FEATURE] View RWX Volumes on Dashboard.

I use https://longhorn.io/docs/1.0.2/advanced-resources/rwx-workloads/#enabling-rwx-support for RWX volumes. But i cant see the Volumes in Longhorn Dashboard. I guess the problem is that the nfs.longhorn.io driver dosnt do it.

Currently the RWX volume is not shown directly in the UI, since they're using the same volume across the board.
In the upcoming v1.1.0, we will provide an enhanced experience that can create volumes as RWX and manage it through the Longhorn UI.

related longhorn/longhorn#1470

leaving a note here.
For we added an accessMode field to the volume api object
https://github.com/longhorn/longhorn/issues/2048
which can be used by the frontend to differentiate between rwo/rwx volumes

@Trackhe This feature has been released as part of Longhorn v1.1.0. You can refer https://longhorn.io/docs/1.1.0/advanced-resources/rwx-workloads/ to try it out and you should be able to view RWX volumes on Longhorn UI.

i saw this. thank you all.


Postgres vs Debian Commands

In the FIT script, use Debian commands instead of the Postgres general functions presently in the script.  Examples to use are pg_dropcluster and pg_createcluster.  Desired completion date of 3/21/16

@rsial2 The latest delivery of FIT addresses this issue and concur with closing this issue.


Android export: Add setting for custom source ZIP for custom builds

Godot version:
3.2-stable, master (e2b66ca)
OS/device including version:
Exporting to Android from any device.
Issue description:
The Android export preset has settings for "Custom Templates", both Release and Debug, like other platforms:

But since 3.2, there's also an android_source.zip source ZIP that is used when "Custom Build" is enabled. There's no way to specify a path to a custom source ZIP currently to used with the custom debug and release templates.
Steps to reproduce:

Build custom Android template
Try to use it with the Custom Build workflow. You are forced to copy release, debug and source custom templates to ~/.local/share/godot/templates/<version>/ or equivalent.

CC @godotengine/android

Hello,
My friend and I want to try to take care of this, if no one is already on it.
If anyone has an idea for where to start, don't hesitate!

@TheMagnat feel free to take a crack at it. The menu in the screenshot is populated from the export.cpp file so that would be a good place to get started.

Hello,
I'm a beginner and I wanted to try my shot at this for my first contribution since I saw there was still no pull request for this.
But, after i managed to add an entry for specifying the path and checking that path besides the default one, I found out that it isn't used anywhere, because for custom build it already asks to install that build in the project and as I see it the check for the custom template path should be removed as it isn't used (as apposed to adding a way to specify that path as specified in the issue).
I worked on commit b383484e445 (Merge pull request #37421 from akien-mga/python-format-black )
Is this right? if so, can I delete that check and make a pull request for it?

@akien-mga Just to make sure, you want it to be possible to specify the location of an android_source.zip?
Then when we click "Install Android Build Template..." in the Project menu, the specified source ZIP will be used to set up the project for custom Android builds ( by installing the source ZIP to res://android/build )

Yeah that's the idea. It would likely be custom_template/source after custom_template/release.

@akien-mga
I think it might be better to specify the location of the custom source ZIP when we click "Install Android Build Template..." instead of specifying it in an Android export preset.
If we specify it in an Android export preset, there can be multiple Android export presets, each specifying a different custom source ZIP. "Install Android Build Template..." will not know which custom source ZIP to use then. We could use the first occurence, but it gets very messy. Eventually all Android export presets will use the custom build template in "res://android/build" ( after we install it ), so no need to have a custom source ZIP for each.

Hi, my collegue @TheMagnat and myself are working on this issue, what label should we display for the Android Build Template file picker ?

@edoblette "Custom Android Build Template"?

We've edited the export.cpp file to now have a field to specify a path to the android_souce.zip file.
If the path is empty it will use the default android_source.zip template file.
This is for export.cpp but now we have to deal with the installation of the template in ress/android/build. I figured out that this is done in the export_template_manager.cpp file,
but in this file, it uses the default template path.
First I would like to know if you think that we are on the right path and if so, if there is a way to access the path filled in one of the parameters of the EditorExportPreset (in the export.cpp file, a new option we added to specify the android_source.zip path).
Here is our fork of the project with the edits we've done for the moment.

Fixed by #50481.


Robots.txt from theme

Related issues
https://github.com/DivanteLtd/vue-storefront/issues/2110
Short description and why it's useful
It is more flexible to have robots.txt in the theme instead of src/server/robots.js
Which environment this relates to

[x] Test version (https://test.storefrontcloud.io) - this is a new feature or improvement for Vue Storefront. I've created branch from develop branch and want to merge it back to develop

Upgrade Notes and Changelog

[x] No upgrade steps required (100% backward compatibility and no breaking changes)

Could you please tell motivation why it's better to have it theme? From my PoV it adds unnecessary complexity

@filrak
Hello!
Because the theme is safe place to put everything specific to project. When we have robots.txt in src/server/robots.js it is hard to have different robots.txt for different themes, hard to update it, also a possibility to override the file during upgrade.

@shkodasv I'm not convinced. can you please give a real-world example when such thing is needed?
It's something that could potentially break others stores in a future if refactored/changed so new api should be included only if absolutely necessary.

Closing becuase there are better ways to handle this issue (static file hosting via proxy or just assets + alias)


regex matching not supported

(This is used to request new product features, please visit https://github.com/istio/istio/discussions for questions on using Istio)
i have 2 virtualservices defining below
VS1:
spec:
  gateways:
  - istio-system/istio-ingressgateway
  hosts:
  - '*'
  http:
  - match:
    - uri:
        prefix: /demo/api
    route:
    - destination:
        host: api.demo.svc.cluster.local
        port:
          number: 80
    timeout: 30s
  - match:
    - uri:
        prefix: /demo/swagger
    route:
    - destination:
        host: api.demo.svc.cluster.local
        port:
          number: 80
    timeout: 30s

VS2:
spec:
  gateways:
  - istio-system/istio-ingressgateway
  hosts:
  - '*'
  http:
  - match:
    - uri:
        prefix: /demo/
    route:
    - destination:
        host: web.demo.svc.cluster.local
        port:
          number: 80
    timeout: 30s

They are deployed in the same order in which they are defined above. But after deployment, what I am finding is: all traffic with /demo/api* is getting directed to web service than the api service.
I think it is due to the Istio routing order and I am not sure how it maintains the order.
I tried to use regex in web virtualservice to drop all traffic /demo/api/* and /demo/swagger*. But again those complex regex is not supported in envoy.
is there a way to do so? I understand by putting all virtualservices in a single file will solve the issue. Problem is, we have near about 20 application teams following the multiple virtualservice.yml file method to create virtualservice services from different helm releases. it would be good, if someone can put some light on to this.
Describe alternatives you've considered
Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ X ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Affected features (please put an X in all that apply)
[X  ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane
Additional context

The regex use https://github.com/google/re2/wiki/Syntax
The above behavior is determined by which VS is created ealier

Thanks @hzxuzhonghu this explains
web:
creationTimestamp: "2024-03-18T18:02:09Z"
api:
creationTimestamp: "2024-03-18T18:43:53Z"

Hmm, i was wrong. After reading the code, i found the VS is not sorted by creationtimestamp.

but this somehow worked!! this is so so confusing to be very honest with you

Sorry i missed: it does sort https://github.com/istio/istio/blob/edb10b016dbc30749de2e4362c18116f6a31f5fd/pilot/pkg/model/virtualservice.go#L288

that explains.... it does sort by time.. perfect.. this solved my problem

But in your comment https://github.com/istio/istio/issues/53564#issuecomment-2421888576, the order doesnot align with the create order
I am confused

Yeah, this is the right output

Thanks @hzxuzhonghu for jumping in to it. I must say Istio's documentation is vast and sometime's unclear on these things. Istio is complex and on top of that it is confusing sometimes going through the documentation and trying to catch it.
But super happy now as the issue is sorted now.


Isn't it enough that dd stayed as deprecated?

When will it be removed? It has been years... ^.^

refer to https://github.com/raveren/kint/issues/170


Mandate group ID only if unique ID for groups is enabled for the userstore

Resolves https://github.com/wso2/product-is/issues/13306
Purpose
ReadOnly LDAP supports uniqueID feature. Other user stores does not have that support. So when we plug a ReadWrite secondary user store, it fails since it does not have a uniqueID.
So IS should mandate uniqueID for groups only if the feature is enabled.
Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email<EMAIL_ADDRESS>to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to<EMAIL_ADDRESS>and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

Unit tests

Code coverage information

Integration tests

Details about the test cases and coverage

Security checks

Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
Ran FindSecurityBugs plugin and verified report? yes/no
Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/2094530479

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/2094530479
Status: success


fix(typeahead): removed incorrect behavior to do ENTER behavior on TAB

... TAB should simply skip to next field as expected.
fixes #686, fixes  #490, closes #689

squash and merge replaces commit author! not cool at all!


wfm card list update

update card list directives to support multi selecting

hi~
the chevron icon seems rotating incorrectly when open a card. is it merging issue or..
could you please have a look at that. :)

it is fixed and pushed, for some reason it was set to 180 deg rotation. I will update the version in the project aswell


update predicted events in test tracker with policy and confidence

Proposed changes:

fix #6899

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

Debug logs (and non-included log of latest action) before:
2020-10-05 14:47:45 DEBUG    rasa.core.policies.memoization  - There is no memorised next action
2020-10-05 14:47:45 DEBUG    rasa.core.policies.mapping_policy  - The predicted intent 'bot_challenge' is mapped to  action 'utter_iamabot' in the domain.
2020-10-05 14:47:45 DEBUG    rasa.core.policies.ensemble  - Predicted next action using policy_2_MappingPolicy
2020-10-05 14:47:45 DEBUG    rasa.core.processor  - Predicted next action 'utter_iamabot' with confidence 1.00.
2020-10-05 14:47:45 WARNING  rasa.core.test  - latest action: ActionExecuted(action: utter_iamabot, policy: None, confidence: None)
2020-10-05 14:47:45 DEBUG    rasa.core.policies.memoization  - Current tracker state [{'intent_mood_unhappy': 1.0, 'prev_action_listen': 1.0}, {'prev_utter_cheer_up': 1.0, 'intent_mood_unhappy': 1.0}, {'prev_utter_did_that_help': 1.0, 'intent_mood_unhappy': 1.0}, {'prev_action_listen': 1.0, 'intent_bot_challenge': 1.0}, {'prev_utter_iamabot': 1.0, 'intent_bot_challenge': 1.0}]
2020-10-05 14:47:45 DEBUG    rasa.core.policies.memoization  - There is no memorised next action
2020-10-05 14:47:45 DEBUG    rasa.core.policies.mapping_policy  - The mapped action, 'utter_iamabot', for the intent, 'bot_challenge', was executed last, but it was predicted by another policy, 'None', so MappingPolicy is not predicting any action.
2020-10-05 14:47:45 DEBUG    rasa.core.policies.ensemble  - Predicted next action using policy_0_TEDPolicy
2020-10-05 14:47:45 DEBUG    rasa.core.processor  - Predicted next action 'action_listen' with confidence 0.87.
2020-10-05 14:47:45 WARNING  rasa.core.test  - latest action: ActionExecuted(action: action_listen, policy: None, confidence: None)
2020-10-05 14:47:45 DEBUG    rasa.core.policies.memoization  - Current tracker state [{'prev_utter_cheer_up': 1.0, 'intent_mood_unhappy': 1.0}, {'prev_utter_did_that_help': 1.0, 'intent_mood_unhappy': 1.0}, {'prev_action_listen': 1.0, 'intent_bot_challenge': 1.0}, {'prev_utter_iamabot': 1.0, 'intent_bot_challenge': 1.0}, {'intent_deny': 1.0, 'prev_action_listen': 1.0}]

After:
2020-10-05 14:45:24 DEBUG    rasa.core.policies.memoization  - There is no memorised next action
2020-10-05 14:45:24 DEBUG    rasa.core.policies.mapping_policy  - The predicted intent 'bot_challenge' is mapped to  action 'utter_iamabot' in the domain.
2020-10-05 14:45:24 DEBUG    rasa.core.policies.ensemble  - Predicted next action using policy_2_MappingPolicy
2020-10-05 14:45:24 DEBUG    rasa.core.processor  - Predicted next action 'utter_iamabot' with confidence 1.00.
2020-10-05 14:45:24 WARNING  rasa.core.test  - latest action: ActionExecuted(action: utter_iamabot, policy: policy_2_MappingPolicy, confidence: 1)
2020-10-05 14:45:24 DEBUG    rasa.core.policies.memoization  - Current tracker state [{'prev_action_listen': 1.0, 'intent_mood_unhappy': 1.0}, {'prev_utter_cheer_up': 1.0, 'intent_mood_unhappy': 1.0}, {'prev_utter_did_that_help': 1.0, 'intent_mood_unhappy': 1.0}, {'prev_action_listen': 1.0, 'intent_bot_challenge': 1.0}, {'prev_utter_iamabot': 1.0, 'intent_bot_challenge': 1.0}]
2020-10-05 14:45:24 DEBUG    rasa.core.policies.memoization  - There is no memorised next action
2020-10-05 14:45:24 DEBUG    rasa.core.policies.mapping_policy  - The mapped action, 'utter_iamabot', for this intent, 'bot_challenge', was executed last so MappingPolicy is returning to action_listen.
2020-10-05 14:45:24 DEBUG    rasa.core.policies.ensemble  - Predicted next action using policy_2_MappingPolicy
2020-10-05 14:45:24 DEBUG    rasa.core.processor  - Predicted next action 'action_listen' with confidence 1.00.
2020-10-05 14:45:24 WARNING  rasa.core.test  - latest action: ActionExecuted(action: action_listen, policy: policy_2_MappingPolicy, confidence: 1)
2020-10-05 14:45:24 DEBUG    rasa.core.policies.memoization  - Current tracker state [{'prev_utter_cheer_up': 1.0, 'intent_mood_unhappy': 1.0}, {'prev_utter_did_that_help': 1.0, 'intent_mood_unhappy': 1.0}, {'prev_action_listen': 1.0, 'intent_bot_challenge': 1.0}, {'prev_utter_iamabot': 1.0, 'intent_bot_challenge': 1.0}, {'intent_deny': 1.0, 'prev_action_listen': 1.0}]

I really don't think this is a good idea and the code doesn't look like it is part of the mapping policy, is there any other way we can fix this?

is there any other way we can fix this?
yes, there outer loop that calls this method can be overwritten to use partial_tracker that contains WronglyPredictedAction event instead of original event, then it will contain the policy that was used to predict it

We should rather feed new WronglyPredictedAction into the next prediction.

What about the correctly predicted actions though? Those are the ones that are relevant here.
I'm pretty sure that currently the arguments we pass here: https://github.com/RasaHQ/rasa/pull/6907/files#diff-af205c540e3d6ceb3627cf630700148eR349 will always be None for policy, confidence, etc

Oops, wrong account 🌝

What about the correctly predicted actions as well?

true, then we need to create a new ActionExecuted event for correct prediction and feed it into next step

However, I'd say the policy should be updated only if predicted action corresponds to gold action

Wouldn't this affect the further actions if you don't have --fail-on-prediction-errors though? In production, the fact that mappingpolicy predicted x action (incorrectly) could then further affect the next predictions -- if we don't update the wrongly predicted one with the policy that predicted it, that changes future predictions


Improve layering of collections confirmation modal

Just another layering issue that needs to be fixed as soon as possible.
Confirmation modal for collections was behind the options modal (z-10 confirmation on z-50 collections modal). Now it should be on top again (both z-50).

Merging because it's priority and seems to work after self-review!


About conf files and an error

Hi Sungnyun,
Thanks for sharing the code. I found the conf files are not provided, do you use the same conf file as in AV-HuBERT?
I tried using the avhubert conf file and changed the model name to xmodal_av_hubert_seq2seq. It showed this error:

File "avsr-temporal-dynamics/avhubert/hubert.py", line 769, in extract_finetune_features
assert 'clean_audio' in source
AssertionError

Many thanks,
Zhaofeng

Hi Zhaofeng,
Sorry for inconvenience. I just uploaded the missing config file here.
Please use this one.
Thanks,
Sungnyun Kim

Thank you for your quick response!
The model name in the config file didn't work initially, but I was able to resolve the issue by changing it to xmodal_av_hubert_seq2seq. I appreciate your help!
Many thanks,
Zhaofeng

My bad, you are right. I appreciate it!


Navigation between search results and detail pages is flaky

I should be able to use the back/forward buttons to navigate between the result list and detail pages. Sometimes the URL query parameters get erased, and sometimes the URL updates but the page doesn't change


[as2_platform_dji_osdk] Add gimbal support

Feature Description
Add gimbal support to control it
Implementation Considerations
No response

@RPS98, we should check if this is already implemented

It works well


Add PrivacyInfo.xcprivacy

We should change the base branch to master since we made the changes to use that for Tinder iOS


fix: Remove deprecated ::shadow selector

Replaced deprecated ::shadow pseudo-element with .editor

@YouKnowBagu Thanks


fix(button): update button disabled style

Checklist

[x] Fix linting errors
[x] Tests have been added / updated (or snapshots)

Change information

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


pointerevents-extension is missing

Defined here:
https://w3c.github.io/pointerevents/extension.html
I noticed pointerevents-extension.idl and its tests while authoring https://github.com/web-platform-tests/wpt/pull/11922

Now added to the report in pointerevents-extension.idl


Sub socket stops after message handler throws an exception

I've come across an issue similar to #442 still present in v2.5.13. This time happens with a sub socket.
Here's a script that demonstrates the issue:
var zmq = require('zmq');

s_pub = zmq.socket('pub');
s_pub.bindSync('tcp://*:45000');

s_sub = zmq.socket('sub');
s_sub.connect('tcp://localhost:45000');
s_sub.subscribe("");

s_sub.on('error', function(x) {
    console.log("error handler: ", x);
});

s_sub.once('message', function(x) {
    console.log("sub recv:", x.toString(), " throwing now");
    throw "sorry";
});

console.log("-- msg1");
s_pub.send("msg1");

setTimeout(function() {
    s_sub.once('message', function(x) {
        console.log("sub recv:", x.toString(), " 1st after throw");
    });
    console.log("-- msg2");
    s_pub.send("msg2");
}, 500);

setTimeout(function() {
    s_sub.once('message', function(x) {
        console.log("sub recv:", x.toString(), " 2nd after throw");
    });
    console.log("-- msg3");
    s_pub.send("msg3");
}, 1000);

The output I get using zmq v2.5.13 is:
-- msg1
sub recv: msg1  throwing now
error handler:  sorry
-- msg2
-- msg3

What I'd expect is:
-- msg1
sub recv: msg1  throwing now
error handler:  sorry
-- msg2
sub recv: msg2  1st after throw
-- msg3
sub recv: msg3  2nd after throw

I can also confirm that this happens on zmq v4.1.5 using node v6.3.1
I think that expected behavior would be that the program would crash after the error is thrown, like it does when an error is thrown in an event handler for a vanilla EventEmitter:
ee = new (require('events'))
ee.on('test', ()=>{
  throw "sorry"
})
ee.emit('test')

yeilds:
/home/hurricane/projects/scratch/scratch.js:5
    throw "sorry"
    ^
sorry

Instead, the error is never logged, and message events stop getting emitted, like @n-riesco described.
@JustinTulloss would you accept a PR?

@ronkorving is the primary maintainer. Go for the PR @hhamilto!

@rgbkrk Thanks for the info!
Regarding my assumption that errors thrown from the message event handler should bubble up normally and halt execution: It looks like we intentionally prevent this from happening inside the Socket.prototype._flushReads method:
try {
    received = this._flushRead();
} catch (error) {
    this._isFlushingReads = false;
    this.emit('error', error); // can throw
    return;
}

Instead, as you can see in the above excerpt, we catch the errors, and emit them as error events on the socket. While this seems odd to me, it also seems like we should not break this existing behavior. We should however, still fix the underlying issue.
The underlying issue is that after the error is handled, we never call _flushRead again, like we normally would. For some reason, calling _flushRead (and it in turn calling Readv in the binding) resets the UV_READABLE event on the socket, and allows libuv to notify us of new messages. currently, the UV_READBALE event is never unset and messages simply queue up without the _flushReads method ever being called again. _flushReads is normally called when the libuv detects the underlying socket is readable and calls our UV_PollCallback callback. I should have a PR to fix this issue up in a day or two, which might make the issue clearer.

@rgbkrk Thanks for the info!
Regarding my assumption that errors thrown from the message event handler should bubble up normally and halt execution: It looks like we intentionally prevent this from happening inside the Socket.prototype._flushReads method:
try {
    received = this._flushRead();
} catch (error) {
    this._isFlushingReads = false;
    this.emit('error', error); // can throw
    return;
}

Instead, as you can see in the above excerpt, we catch the errors, and emit them as error events on the socket. While this seems odd to me, it also seems like we should not break this existing behavior. We should however, still fix the underlying issue.
The underlying issue is that after the error is handled, we never call _flushRead again, like we normally would. For some reason, calling _flushRead (and it in turn calling Readv in the binding) resets the UV_READABLE event on the socket, and allows libuv to notify us of new messages. currently, the UV_READBALE event is never unset and messages simply queue up without the _flushReads method ever being called again. _flushReads is normally called when the libuv detects the underlying socket is readable and calls our UV_PollCallback callback.
PR here: https://github.com/JustinTulloss/zeromq.node/pull/575

PR here: #575


Can not change postgres password

Hi,
First thank you so much for your work and for sharing it !
I'm new in Docker, so I need help for a problem.
All is working on my project except that I cannot change the postgres password.
It tried to changed it on my env file and next directly on the file, the password is ever "changeme".
Of course, I stop and restart docker after each change :
docker-compose -f "docker-compose.yml" down
docker-compose -f "docker-compose.yml" up -d --build
whereas the change of the identifiers of PGADMIN worked well. I changed it by adding values in my .env file.
Thanks,
Ben.

Is someone reproduce it ?

@picbenoit https://github.com/docker-library/postgres/issues/203#issuecomment-255200501


Determine if it's possible to update proxies to run on JDK11

JDK 11 and proxies in a world past sun.misc.Unsafe
This blog post explains the challenges of implementing dynamic proxies on newer versions of Java. Selenium Foundation uses Byte Buddy in three contexts:

Creation of "enhanced" versions of ComponentContainer classes to install method hooks
Creation of "robust" versions of driver-specific WebElement classes to handle stale references
Creation of RevisedCapabilityMatcher to replace the SafariSpecificValidator class

Resolved by #147


Proposal: provide a way to more easily test test utility

For larger Go projects, it's common to write some utility functions or types for use in it's test suite.  Ideally, those utilities should themselves be tested.  However, there are certain types of behaviour that are difficult to test at present:

Check that a function causes a test to fail.
Check that a function logs a particular message.
Check that a function spawns an expected set of subtests.

With most testing frameworks, the usual method to handle this would be to invoke the test runner with a custom set of tests, and then inspect the results.  That's not really possible with Go's testing framework, since the method of constructing a test suite and invoking the runner is all private API (either inaccessible like testing/internal/testdeps, or documented to be unstable like testing.TestMain).  Also, the runner depends on global state through flags that would be shared with the real test suite.

A proposal is generally a very specific idea. This seems more like a vague problem statement, and I'm not understanding what solution you're proposing.

I guess I tagged it wrong.  I was trying to describe what features I wanted without locking down an implementation.
I guess a more concrete proposal would be something like:

Add a publicly supported version of testing.MainStart that doesn't depend on the undocumented testDeps interface, and takes some kind of config argument to use in lieu of the command line flags (i.e. we don't want the -run command line argument to restrict what tests are run in this independent test runner).

Add a method to testing.M to set where to send test output instead of stdout.  This could be a simple io.Writer accepting the default test output format, or more usefully something accepting the -json style TestEvent structures.

@jhenstridge would a better title for this issue be “provide a way to test Testmain functions” ?

Perhaps related to #40984.

@davecheney: the scope is a bit more than what a TestMain function currently does.  It's the stuff that happens before TestMain is called, and the result reporting within M.Run() that I'd like access to.
The concrete use case I have for this is https://github.com/go-check/check/pull/122.  I was trying to port go-check to use the stdlib test runner.  While I was easily able to port the code over to using stdlib subtests, porting the tests has proved more difficult.    These tests took the form of tests that create a new test runner that runs a collection of tests not part of the main test suite, and then inspecting the results.  That kind of thing is all private in the stdlib testing framework.
@ianlancetaylor: the suggestion in that bug report of using cleanup functions gets close to the first use case from my original post, with something like:
func TestUtility(t *testing.T) {
    t.Cleanup(func() {
        if (!t.Faled()) {
            t.Error("utility function did not fail the test")
            return
        }
        // XXX: mark test as successful somehow?
    })
    failTheTest(t)
}

This would be enough to make the test fail if failTheTest doesn't set the failed state, but it also reports a failure if things work correctly.  Perhaps some function doing the opposite of T.Fail could help in this specific case.
I'm not sure it would help out with the other two use cases I mentioned, where it is not clear how you'd check they worked directly from a test calling them.

@jhenstridge, note that a test can invoke its own executable as a subprocess using the os/exec package. In many cases that suffices for testing test helpers.
(See also https://github.com/golang/go/issues/41980#issuecomment-709318155, https://github.com/golang/go/issues/39903#issuecomment-662113961.)

@bcmills: Thanks for the suggestion.  I'll see if I can use that to adapt the tests I'm working on.  Presumably something like this:

Define a test that contains the logic under test that calls t.SkipNow() unless a particular environment variable is set.
Run os.Args[0] as a subprocess with the environment variable set and -run to select just the test in question.  Maybe also -json if the I need the structured output.

Hopefully the tests I actually want to keep can fit into environment variables + log inspection as the only communication needed.
It would still be nice to have a more direct method of testing functionality like this.

This is not a concrete proposal, and we just spent a lot of time discussing the topic on #40984. In the absence of a concrete proposal and to avoid duplicated effort, closing.

@jhenstridge I've had success testing test helpers in https://github.com/gotestyourself/gotest.tools so I thought I would share in case it helps you.
For the first two cases in the description I think the common practice is to have test helpers use a smaller interface instead of using testing.T. Once they accept their own interface in place of testing.T a fakeT can pretty easily confirm that Fatal, Error, or Log are called correctly.
"Check that a function spawns an expected set of subtests" is still difficult because T.Run always passes a *testing.T to the subtest. I believe that problem was discussed in #39903.
As long as go-check doesn't expose t.Run directly, it seems like it would be possible to swap it out and call the subtest with a fakeT that records the hierarchy.


docker compose up failed on respberrypi

Device: Respberrypi 4B
lsb_release -a

prints
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye

Run mainflux
git clone git@github.com:mainflux/mainflux.git
cd mainflux/docker
docker compose up

the container fails to restart times, some loop errors:
mainflux-users-db      |
mainflux-users-db      | PostgreSQL Database directory appears to contain a database; Skipping initialization
mainflux-users-db      |
mainflux-users-db      | 2022-08-11 09:04:10.454 UTC [1] LOG:  starting PostgreSQL 13.3 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit
mainflux-users-db      | 2022-08-11 09:04:10.455 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
mainflux-users-db      | 2022-08-11 09:04:10.455 UTC [1] LOG:  listening on IPv6 address "::", port 5432
mainflux-users-db      | 2022-08-11 09:04:10.466 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
mainflux-users-db      | 2022-08-11 09:04:10.484 UTC [22] LOG:  database system was shut down at 2022-08-11 09:03:36 UTC
mainflux-users-db      | 2022-08-11 09:04:10.493 UTC [1] LOG:  database system is ready to accept connections
mainflux-auth-redis    | 1:C 11 Aug 2022 09:04:11.350 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
mainflux-auth-redis    | 1:C 11 Aug 2022 09:04:11.351 # Redis version=6.2.2, bits=64, commit=00000000, modified=0, pid=1, just started
mainflux-auth-redis    | 1:C 11 Aug 2022 09:04:11.351 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
mainflux-auth-redis    | 1:M 11 Aug 2022 09:04:11.356 * monotonic clock: POSIX clock_gettime
mainflux-auth-redis    | 1:M 11 Aug 2022 09:04:11.359 * Running mode=standalone, port=6379.
mainflux-auth-redis    | 1:M 11 Aug 2022 09:04:11.359 # Server initialized
mainflux-auth-redis    | 1:M 11 Aug 2022 09:04:11.359 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
mainflux-auth-redis    | 1:M 11 Aug 2022 09:04:11.373 * Loading RDB produced by version 6.2.2
mainflux-auth-redis    | 1:M 11 Aug 2022 09:04:11.373 * RDB age 35 seconds
mainflux-auth-redis    | 1:M 11 Aug 2022 09:04:11.373 * RDB memory usage when created 0.80 Mb
mainflux-auth-redis    | 1:M 11 Aug 2022 09:04:11.373 * DB loaded from disk: 0.000 seconds
mainflux-auth-redis    | 1:M 11 Aug 2022 09:04:11.373 * Ready to accept connections
mainflux-vernemq       | exec /usr/sbin/start_vernemq: exec format error
mainflux-keto-db       |
mainflux-keto-db       | PostgreSQL Database directory appears to contain a database; Skipping initialization
mainflux-keto-db       |
mainflux-auth-db       |
mainflux-auth-db       | PostgreSQL Database directory appears to contain a database; Skipping initialization
mainflux-auth-db       |
mainflux-broker        | [1] 2022/08/11 09:04:11.725531 [INF] Starting nats-server
mainflux-broker        | [1] 2022/08/11 09:04:11.725699 [INF]   Version:  2.2.4
mainflux-broker        | [1] 2022/08/11 09:04:11.725710 [INF]   Git:      [924b314]
mainflux-broker        | [1] 2022/08/11 09:04:11.725725 [INF]   Name:     NAHUKHAAARARUIPUX5A6BFVYBE7VK44DFQBFNIRP6TGYRG34PBUH376I
mainflux-broker        | [1] 2022/08/11 09:04:11.725747 [INF]   ID:       NAHUKHAAARARUIPUX5A6BFVYBE7VK44DFQBFNIRP6TGYRG34PBUH376I
mainflux-broker        | [1] 2022/08/11 09:04:11.725769 [INF] Using configuration file: /etc/nats/nats.conf
mainflux-broker        | [1] 2022/08/11 09:04:11.728665 [INF] Listening for client connections on <IP_ADDRESS>:4222
mainflux-broker        | [1] 2022/08/11 09:04:11.735054 [INF] Server is ready
mainflux-keto-db       | 2022-08-11 09:04:11.841 UTC [1] LOG:  starting PostgreSQL 13.3 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit
mainflux-keto-db       | 2022-08-11 09:04:11.841 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
mainflux-keto-db       | 2022-08-11 09:04:11.841 UTC [1] LOG:  listening on IPv6 address "::", port 5432
mainflux-auth-db       | 2022-08-11 09:04:11.854 UTC [1] LOG:  starting PostgreSQL 13.3 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit
mainflux-auth-db       | 2022-08-11 09:04:11.854 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
mainflux-auth-db       | 2022-08-11 09:04:11.854 UTC [1] LOG:  listening on IPv6 address "::", port 5432
mainflux-es-redis      | 1:C 11 Aug 2022 09:04:11.861 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
mainflux-es-redis      | 1:C 11 Aug 2022 09:04:11.861 # Redis version=6.2.2, bits=64, commit=00000000, modified=0, pid=1, just started
mainflux-es-redis      | 1:C 11 Aug 2022 09:04:11.861 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
mainflux-es-redis      | 1:M 11 Aug 2022 09:04:11.865 * monotonic clock: POSIX clock_gettime
mainflux-es-redis      | 1:M 11 Aug 2022 09:04:11.868 * Running mode=standalone, port=6379.
mainflux-es-redis      | 1:M 11 Aug 2022 09:04:11.868 # Server initialized
mainflux-es-redis      | 1:M 11 Aug 2022 09:04:11.868 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
mainflux-keto-db       | 2022-08-11 09:04:11.867 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
mainflux-es-redis      | 1:M 11 Aug 2022 09:04:11.878 * Loading RDB produced by version 6.2.2
mainflux-es-redis      | 1:M 11 Aug 2022 09:04:11.878 * RDB age 35 seconds
mainflux-es-redis      | 1:M 11 Aug 2022 09:04:11.878 * RDB memory usage when created 0.80 Mb
mainflux-es-redis      | 1:M 11 Aug 2022 09:04:11.878 * DB loaded from disk: 0.000 seconds
mainflux-es-redis      | 1:M 11 Aug 2022 09:04:11.878 * Ready to accept connections
mainflux-auth-db       | 2022-08-11 09:04:11.880 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
mainflux-keto-db       | 2022-08-11 09:04:11.896 UTC [20] LOG:  database system was shut down at 2022-08-11 09:03:42 UTC
mainflux-auth-db       | 2022-08-11 09:04:11.898 UTC [21] LOG:  database system was shut down at 2022-08-11 09:03:40 UTC
mainflux-auth-db       | 2022-08-11 09:04:11.919 UTC [1] LOG:  database system is ready to accept connections
mainflux-keto-db       | 2022-08-11 09:04:11.911 UTC [1] LOG:  database system is ready to accept connections
mainflux-jaeger        | exec /go/bin/all-in-one-linux: exec format error
mainflux-things-db     |
mainflux-things-db     | PostgreSQL Database directory appears to contain a database; Skipping initialization
mainflux-things-db     |
mainflux-things-db     | 2022-08-11 09:04:12.968 UTC [1] LOG:  starting PostgreSQL 13.3 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 10.3.1_git20210424) 10.3.1 20210424, 64-bit
mainflux-things-db     | 2022-08-11 09:04:12.968 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
mainflux-things-db     | 2022-08-11 09:04:12.968 UTC [1] LOG:  listening on IPv6 address "::", port 5432
mainflux-things-db     | 2022-08-11 09:04:13.000 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
mainflux-things-db     | 2022-08-11 09:04:13.040 UTC [21] LOG:  database system was shut down at 2022-08-11 09:03:37 UTC
mainflux-things-db     | 2022-08-11 09:04:13.056 UTC [1] LOG:  database system is ready to accept connections
mainflux-keto-migrate  | exec /usr/bin/keto: exec format error
mainflux-keto          | exec /usr/bin/keto: exec format error
mainflux-vernemq exited with code 0
mainflux-jaeger exited with code 1
mainflux-auth          | exec /exe: exec format error
mainflux-keto-migrate exited with code 1
mainflux-things        | exec /exe: exec format error
mainflux-users         | exec /exe: exec format error
mainflux-keto exited with code 1
mainflux-mqtt          | exec /exe: exec format error
mainflux-http          | exec /exe: exec format error
mainflux-coap          | exec /exe: exec format error
mainflux-nginx         | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
mainflux-nginx         | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
mainflux-nginx         | /docker-entrypoint.sh: Launching /docker-entrypoint.d/entrypoint.sh
mainflux-vernemq exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-auth exited with code 1
mainflux-vernemq exited with code 1
mainflux-keto exited with code 1
mainflux-users exited with code 0
mainflux-things exited with code 0
mainflux-keto-migrate exited with code 1
mainflux-auth exited with code 1
mainflux-mqtt exited with code 1
mainflux-http exited with code 1
mainflux-vernemq exited with code 1
mainflux-keto exited with code 1
mainflux-coap exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-users exited with code 1
mainflux-mqtt exited with code 1
mainflux-things exited with code 1
mainflux-auth exited with code 1
mainflux-http exited with code 1
mainflux-vernemq exited with code 1
mainflux-keto exited with code 1
mainflux-coap exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-users exited with code 1
mainflux-mqtt exited with code 1
mainflux-things exited with code 1
mainflux-auth exited with code 1
mainflux-vernemq exited with code 1
mainflux-http exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-coap exited with code 1
mainflux-keto exited with code 1
mainflux-users exited with code 1
mainflux-mqtt exited with code 1
mainflux-things exited with code 1
mainflux-http exited with code 1
mainflux-auth exited with code 1
mainflux-vernemq exited with code 1
mainflux-coap exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-keto exited with code 1
mainflux-mqtt exited with code 1
mainflux-users exited with code 1
mainflux-things exited with code 1
mainflux-http exited with code 1
mainflux-auth exited with code 1
mainflux-coap exited with code 1
mainflux-mqtt exited with code 1
mainflux-users exited with code 1
mainflux-keto exited with code 1
mainflux-vernemq exited with code 1
mainflux-things exited with code 1
mainflux-coap exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-http exited with code 1
mainflux-auth exited with code 1
mainflux-mqtt exited with code 1
mainflux-users exited with code 1
mainflux-http exited with code 1
mainflux-things exited with code 1
mainflux-coap exited with code 1
mainflux-keto exited with code 1
mainflux-mqtt exited with code 1
mainflux-auth exited with code 1
mainflux-users exited with code 1
mainflux-http exited with code 1
mainflux-things exited with code 1
mainflux-coap exited with code 1
mainflux-vernemq exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-keto exited with code 1
mainflux-mqtt exited with code 1
mainflux-auth exited with code 1
mainflux-users exited with code 1
mainflux-http exited with code 1
mainflux-things exited with code 1
mainflux-coap exited with code 1
mainflux-vernemq exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-keto exited with code 1
mainflux-mqtt exited with code 1
mainflux-auth exited with code 1
mainflux-users exited with code 1
mainflux-http exited with code 1
mainflux-coap exited with code 1
mainflux-things exited with code 1
mainflux-vernemq exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-keto exited with code 1
mainflux-mqtt exited with code 1
mainflux-auth exited with code 1
mainflux-users exited with code 1
mainflux-http exited with code 1
mainflux-coap exited with code 1
mainflux-things exited with code 1
mainflux-vernemq exited with code 1
mainflux-keto-migrate exited with code 1
mainflux-keto exited with code 1
mainflux-mqtt exited with code 1
mainflux-auth exited with code 1
mainflux-users exited with code 1
mainflux-http exited with code 1
mainflux-coap exited with code 1
mainflux-things exited with code 1
mainflux-vernemq exited with code 1

Change the Makefile https://github.com/mainflux/mainflux/blob/d9c47045cd9844c8a1119d0981140747147c49b2/Makefile#L12
GOARCH ?= $(shell dpkg --print-architecture)

No need to change the Makefile, just pass the env var:
GOARCH=arm64 make dockers

@drasko yes, that's a method, and I comment on my reply. But some addons and dependences should update the version which docker image support arm

@muei Unfortunately, I think that ARM support for Compose is not something we support out of the box. Compose is dev env, and we assume that development will be on x86. Please let us know if you have an idea of how to simplify and run composition on ARM. Ofc, there is always an option of a separate compose file (which brings the complexity of maintenance).


Working with rows

I can't iterate through rows using koala, is there any method that I don't know off? row[idx] only gives List<Object?>
I suggest implementing a row index to map of column name to value method, and using this method to iterate through the dataframe. Unless I am missing something, and there is a better way.
I can make a PR, but I think you'd probably make a better design decision than I will. I can review nonetheless!

There already is the List<RecordRowMap> rowMaps() function, which should provide what you're looking for.


Game Disc dumping not working

I'm using the newest release where you've said you fixed disc dumping, but it still hangs on the screen saying "Looking for a game disc...". I already have a disc inserted and I copied over the new dumpling files to my SD card, but no dice. The digital game dumped perfectly though.

Nevermind, reinserting the disc while running dumpling fixed the issue with the newest release.


Uncaught TypeError: Cannot read property 'getIndentLevel' of null

Issue Id: 7f31e4e5-3ae9-f29e-a9b8-bc1e4e83ea88Versions - 1.17.0-  5316a2d916b504cc627eb68e119e6b99ea7ad5e5-  f6ef4bef42fa2948426c99fefa340235e67a0c5e-  81fc22ec957de26d2bf6aada3f16f04e0164741cStack TypeError: Cannot read property 'getIndentLevel' of null/vs/editor/contrib/quickFix/browser/lightBulbWidget.ts#L139:23 (getIndentLevel)/vs/editor/contrib/quickFix/browser/lightBulbWidget.ts#L111:9 (_show)/vs/base/common/winjs.base.raw.js#L1524:0 (onComplete)/vs/base/common/winjs.base.raw.js#L1180:0 (call)/vs/base/common/winjs.base.raw.js#L852:0 (_notify)/vs/base/common/winjs.base.raw.js#L1068:0 (enter)/vs/base/common/winjs.base.raw.js#L1036:0 (_run)/vs/base/common/winjs.base.raw.js#L1813:0 (complete)/vs/base/common/winjs.base.raw.js#L1838:0 (argDone)/vs/base/common/winjs.base.raw.js#L1170:0 (onComplete)

Still seeing this...

Code has changed in the meantime. Wait for this to occur again in a different way...


Update no_update_context, fix upsert docs

Why are these changes needed?

Address #24
Add a parameter to force recreate collections
Fix a bug in upsert docs (will not insert docs  when number of chunks is less than 40000, copied from #50)

Related issue number
Closes #24
Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report

Merging #52 (420c0fc) into main (d802b7a) will decrease coverage by 2.66%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
- Coverage   35.36%   32.70%   -2.66%
==========================================
  Files          17       17
  Lines        1971     1972       +1
  Branches      434      433       -1
==========================================
- Hits          697      645      -52
- Misses       1222     1273      +51
- Partials       52       54       +2

Flag
Coverage Δ

unittests
32.70% <0.00%> (-2.56%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Files
Coverage Δ

autogen/retrieve_utils.py
14.78% <0.00%> (ø)

...gen/agentchat/contrib/retrieve_user_proxy_agent.py
4.44% <0.00%> (-0.03%)
:arrow_down:

... and 2 files with indirect coverage changes


Easy, Medium, Hard Puzzles

Hi,
Just a quick question, if i wanted to generate a pack of easy, medium and hard puzzles, what would be the best parameters for each one?
Everything I've tried so far has resulted in some fairly tough puzzles.
Thanks!

An attempt was made to grade the difficulty of various move types in the Methodology section of the original paper from which this algorithm was taken. That should give you some indication of what is considered 'difficult' by the algorithm (difficultyFactors are numbered in order of the move types in that section). Even so, the algorithm is quite noisy due to the size of the search space and the subjectivity of difficulty. For example, a puzzle of generally less difficult move types where the next move is not readily apparent might be judged more difficult by someone who has to search longer even if the move itself is not logically complicated.
In general, you should get some easier puzzles by moving minMoves closer to 35, difficultyFactor closer to 4, and minOfDifficulty closer to 8. The constants are set to the thresholds of what I personally consider reasonable minimum and maximum acceptable levels of challenge; move levels which I personally consider trivial are 1 > difficultyFactor > 4. So you should also be able to generate some extremely easy puzzles by adjusting the parameters and constants to that range.


[2.x] OpenApi Generator examples

Fixes #5669
[2.x] backport for OpenApi Generator examples

I can be wrong, but there are many wrong copyrights in this PR.

@Captain1653 This is the PR was created in 2022 and merged in 2023.


make PydanticProgramExtractor importable from extractors

Description
The example code here https://gpt-index.readthedocs.io/en/latest/examples/metadata_extraction/PydanticExtractor.html
does not work because the module is not importable from extractors.
Fixes # (issue)
no issue
Type of Change
Please delete options that are not relevant.

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[ ] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I ran make format; make lint to appease the lint gods

Thanks for the fix!

done

hmm, now there's no change in the PR

checks are now finished, should be fine now

lol sorry my bad, should be good to go now

Thanks!


fix extension and spec handling; closes #3808

Also fixes some issues in the options unit tests and adds coverage around spec handling.
This needs some manual testing, as I had to monkey with watch a bit.
cc @dedene

Rebase

I think there is a standard yargs way to achieve this, using the "default" option. I just did some short testing, nevertheless it seems to work.
// line 109
const result = yargsParser.detailed(args, {
    default: {extension: ["js"]},      // set default values with "mocharc"
    configuration,
    configObjects,
    coerce: coerceOpts,
    narg: nargOpts,
    alias: aliases,
    string: types.string,
    array: types.array,
    number: types.number,
    boolean: types.boolean.concat(nodeArgs.map(pair => pair[0]))
  });

// line 326
args = parse(
    args._,
    args,
    rcConfig || {},
    pkgConfig || {},
    optsConfig || {},
    //mocharc                           don't set default values here
  );

@juergba Hmm, you're right.
I think instead of this strategy, I'll change it so that we can still keep the default config in our lib/mocharc.json, but use its values as defaults instead of just another config object which is merged in.

Also in "lib/cli/run-helpers.js" the default extension of "js" is set hardcoded several times.
i.e. watchRun() or runMocha().

@boneskull is it ok for you, if I work on this one?

Coverage increased (+0.08%) to 91.851% when pulling 847a331eac3e538b853a7acde9cbb4398662a919 on boneskull/issue/3808 into 57a97386109be02e6d665b01bfd5f2aa75b16ab6 on master.

@juergba yes, go ahead

@juergba second time now you merged without any review (despite prior request to do otherwise) and this time you introduced bug...

Corrected code...
"lib/utils.js"
/**
 * Lookup file names at the given `path`.
 *
 * @description
 * Filenames are returned in _traversal_ order by the OS/filesystem.
 * **Make no assumption that the names will be sorted in any fashion.**
 *
 * @public
 * @memberof Mocha.utils
 * @param {string} filepath - Base path to start searching from.
 * @param {string[]} [extensions=[]] - File extensions to look for.
 * @param {boolean} [recursive=false] - Whether to recurse into subdirectories.
 * @return {string[]} An array of file pathnames.
 * @throws {Error} if no files match pattern.
 * @throws {TypeError} if `filepath` is directory and `extensions` not provided or empty.
 */
exports.lookupFiles = function lookupFiles(filepath, extensions, recursive) {
  var files = [];
  var stat;

  if (extensions === undefined) {
    extensions = [];
  }
  if (recursive === undefined) {
    recursive = false;
  }

  if (!fs.existsSync(filepath)) {
    // Check all extensions, using first match found (if any)
    if (
      !(extensions.some(function(ext) {
        var filepathWithExtname = filepath + '.' + ext;
        if (fs.existsSync(filepathWithExtname)) {
          filepath = filepathWithExtname;
          return true;
        }
      })
    ) {
      // Handle glob
      files = glob.sync(filepath);
      if (!files.length) {
        throw createNoFilesMatchPatternError(
          'Cannot find any files matching pattern ' + exports.dQuote(filepath),
          filepath
        );
      }
      return files;
    }
  }

  // ...no further changes to merged code...
}

@plroebuck
Yes, without @boneskull contributions to "needs-review"-PRs have been close to null during the last few weeks. There is no one stepping into his gap, that's worrying.
you introduced bug...  can you be more ... specific?
corrected code: this is the solution @boneskull already proposed, so nothing new. It only uses the first match of filepath + '.' + ext and ignores the rest of matches. I wonder why this should be correct.

As I commented originally in his PR [...]

You are right, a directory named "test.js" will fail. I will open a PR and use your proposition. I don't agree completely, though. With two files (eg. "unit.ts" and "unit.js") a call "unit" plus extension: ['ts', 'js'] should return both files, not just some/the first one.
I will also have to check wether the glob always returns files.

True, but almost no PRs here [...]

I can live with that procedure.

You are right, a directory named "test.js" will fail. I will open a PR and use your proposition. I don't agree completely, though. With two files (eg. "unit.ts" and "unit.js") a call "unit" plus extension: ['ts', 'js'] should return both files, not just some/the first one.

The filepath + '.js' hack was never intended to handle what you're trying to do with it. Its purpose was to allow small packages that only exported a couple functions (typically from "index.js") to use "test.js" to test them.
If a package is exporting functions in more than one language, its specifications should live in the "test" directory -- the simplistic specification scheme above shouldn't apply.


[opencascade] update to 7.7.2

Library name
opencascade
New version number
7.7.2
Other information that may be useful (release notes, etc...)
Blog announcement: https://dev.opencascade.org/content/open-cascade-technology-772-maintenance-release
Release tag: https://git.dev.opencascade.org/gitweb/?p=occt.git;a=shortlog;h=refs/heads/OCCT-772

@FrankXie05 Can be closed in favour of: https://github.com/microsoft/vcpkg/pull/33498


Update Task 5 - Ping localization, channel navigation and obstacle avoidance

This task is adapted from the gymkhana task from VORC: https://github.com/osrf/vorc

Load Sydney Regatta instead of Marina in La Spezia.
Load WAMV instead of CoRa
Update the starting pose of the WAM-V
Update to use RobotX 2022 course elements.
Create a tutorial here: https://github.com/osrf/vrx/wiki/vrx_2022-gymkhana_task

Copy from vorc:

gymkhana.launch
gymkhana.world.xacro

Update:

gymkhana.launch
gymkhana.world.xacro
pinger.yaml

Getting warnings about non-unique names in the models:
Warning [Model.cc:212] Non-unique names detected in XML children of model with name[short_navigation_course_0].
Warning [Model.cc:212] Non-unique names detected in XML children of model with name[buoys].

Notes about updating short_navigation_course0:

We no longer have a blue marker, so the exit gate is black on the port side instead.
Instead of port and starboard, the model names the gates "red" on the port side and "green" on the right. Is it a nautical convention to call the port gates "green"? If not, this is a little confusing because not all of our green gates are green. The names of these gates are referenced external to the model when they are passed in to the navigation scoring plugin so it might be worth renaming.

Notes about updating obstacle_course to use new course elements:

Previously this used 3 different sizes of round buoys:

polyform_a3: smallest
polyform_a5: medium size
polyform_a7: largest

The new course elements have only two types of round buoys and they are both the same size:

mb_round_buoy_black
mb_round_buoy_orange

I've updated to replace all the polyform_a3 and polyform_a5 with mb_round_buoy_black and polyform_a7 with mb_round_buoy_orange.

Problems encountered while running through tutorial:

The high level task/info topic does not appear in the list.

The wamv::base_link errors are resolved by changing the lock joint in wamv_gazebo.urdf.xacro to wamv::wamv/base_link. It looks like the prefix wamv/ was added to all links except wamv_external_link, but a few places were missed.
A similar change to the wind object link_name in the gymkhana.world.xacro makes the debug message complaint disappear. This is probably also why we weren't seeing any wind in the default tutorial.

TODO:

Polish tutorial language.
Create PR

Resolved with PR #307


Dialyzer errors

Hi,
slug.ex is causing Dialyzer errors for me:
lib/ecto_autoslug_field/slug.ex:2: Function get_sources/2 has no local return
lib/ecto_autoslug_field/slug.ex:168: The pattern 'nil' can never match the type 'name'

Thanks!

Thanks! I would try to fix it.
I have actually never used Dialyzer myself. Any specific steps to reproduce this error?
You may send a PR if you want to.

Thanks for your prompt response.
Just add https://github.com/jeremyjh/dialyxir to a Phoenix project that uses an ecto_autoslug_field, and run:
mix dialyzer
Will have a look at it myself later too... 😃

Please have a look at #11, any ideas?

@suhrawardi any feedback on this one? does it work?

I'm afraid that it does not fix it.... :-(
Added the errors to my .dialyzer/ignore-warnings file...

I hope I have fix it at last:

» mix dialyzer
Compiling 4 files (.ex)
Generated ecto_autoslug_field app
Checking PLT...
[:ecto, :elixir, :ex_doc, :kernel, :logger, :slugger, :stdlib]
PLT is up to date!
Starting Dialyzer
dialyzer args: [check_plt: false,
init_plt: '/Users/sobolev/Documents/github/ecto_autoslug_field/_build/dev/dialyxir_erlang-19.3_elixir-1.4.4_deps-dev.plt',
files_rec: ['/Users/sobolev/Documents/github/ecto_autoslug_field/_build/dev/lib/ecto_autoslug_field/ebin'],
warnings: [:unknown]]
done in 0m1.77s
done (passed successfully)

New version is coming.


Issue with the loop

var count = prompt("Enter number of messages");
var message = prompt("MESSAGE YOU WANT TO SPAM : ", "Hello ");
console.clear();
for (let i = 0; i < count; i++) {
    console.log(`"${message}" sent -> ${i + 1} times`);

      // Get the input box
      var box = document.querySelectorAll("[role=textbox]")[1];

      // create event of type 'input' so that the whatsapp UI will update to sending text message instead of voice message
      InputEvent = Event || InputEvent;
      var evt = new InputEvent("input", {
        bubbles: true,
        composer: true,
      });
      box.innerHTML = message; // set the message as input box value
      box.dispatchEvent(evt); // trigger the event

      // This is bit of stratch to select the send button and click it
      // You need to climb up the DOM tree three levels and then to second child and then the first child is the send button
      box.parentElement.parentElement.parentElement.children[1].children[0].click();
    }

This runs well and selects the send button and clicks it( typed a random input while executing and it sends) but it doesnt send the text we enter or the number of times to the chat.
Thanks

I think it could be the issue with the loop

Hi @amalsebastian7, Thanks for pointing this out.  Although I was not able to reproduce this so I will need some more info from your side.
Can you provide the following information?

Browser Name
Browser version
which chat were you using?(group/personal)?
whatsapp version

Thank you

i have the same problem,
i'm using Chrome (version 105.0.5195.102) with a personal chat
whass version (0.4.930)

Hi, I am sorry for late response but I have been busy in other projects.
I checked with the latest version of whatsapp web and I found that they have changed the implementation from their end. So this script will not work in there.
Technical details:

I don't remember if they were using react using or not back in the days  built this script. But they are using it now.
Whatsapp web changed their code to start using the react hot keys and authentic event filtering.
This allows it to block almost all scripts running from the console.
So it is very tricky to get it work through console.

Workarounds:

There are none to use directly from the developer console.
You can use automation tools such as selenium with python or java to automate this process. [Not recommended, As it has higher chances of getting caught by whatsapp]

I am leaving this issue open for other coming to this repo.

Hi @amalsebastian7, Sorry for late response. I have updated the script to be working again on Edge and Chrome. Although firefox is still having issues. Closing this issue as it is fixed. Feel free to reopen it if issue persists or create a new issue.


Disable breakpoint command

I don't think its possible to disable just one breakpoint using key bindings.
I would like to see it implemented.

This is correct, for that a "Disable Breakpoint Command" would have to be registered in the quick open menu.
Code pointer where to add that command https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/parts/debug/browser/debugCommands.ts#L29
We accept PRs that fix this


Working CNI & Network policy

Depends on merging https://github.com/UKHomeOffice/keto-k8/pull/27 and new tag

@Joseph-Irving not intentional but works either way - amended for consistency.

@vaijab spelling fixed.

Let's leave this PR open. I am not sure what the goal of this is at the moment.

I'll leave it with you @vaijab @jon-shanks  - It's ready for people to easily prototype with canal (which I think is probably where we want to go) It's kernel level routing only (iptables), uses flannel for overlay and Calico enables a superset of the kubernetes network policy all using the kubernetes cluster API with calicoctl. We can even control egress! See ticket for updates: https://github.com/UKHomeOffice/application-container-platform-board/issues/328