Christina delligatta

In your controller, for the endpoint that retrieves dog by id, you should include some error handling.
Something like
    public ResponseEntity<?> getDogDetail(@PathVariable long id)
    {
        Dog rtnDog;
        if (DogsexceptionApplication.ourDogList.findDog(d -> (d.getId() == id)) == null)
        {
            throw new ResourceNotFoundException("Dog with id " + id + " not found!");
        } else
        {
            rtnDog = DogsexceptionApplication.ourDogList.findDog(d -> (d.getId() == id));
        }
        return new ResponseEntity<>(rtnDog, HttpStatus.OK);
    }```

You would also need classes for those exceptions.


[tfgan] Remove outdated estimator TODO

Training discriminator and generator with different ratios can already be done using get_hooks_fn.
This was resolved in #14723

Assign to @joel-shor to ensure the TODO has been addressed.

Nagging Reviewer @joel-shor: You have been added as a reviewer to this pull request. Please add your review or reassign. It has been 14 days with no activity and the awaiting review label has been applied.


Does it work?

You have rather many different adapters here.
Do they work? Can I take it to repository?
iobroker.wm-bus
iobroker.cec
iobroker.lightify
ioBroker.koubachi
iobroker.hid
iobroker.tr-064
Thank you,
Bluefox

Hi, most of this adapters are in an early development state. Koubachi is bought by the Husqvarna Group and will retire. Existing devices will work with this Adapter. All Adapters worked for me, but they are not realy ready for production. I will try to get them ready for public use.
By the way, can you have a look at the pullrequst of the sonos Adapter? Can I do anything to get that changes to the release Version?
Thank you,
soef


usermod: -o flag is only allowed with the -u flag

On ubuntu 14.04 chef improperly forms arguments for useradd when trying to modify "user" with non-unique uid.
[2015-01-23T16:49:08+05:00] INFO: Processing user[root] action create (accounts::root-test line 1)
[2015-01-23T16:49:08+05:00] INFO: Running queued delayed notifications before re-raising exception
[2015-01-23T16:49:08+05:00] ERROR: Running exception handlers
[2015-01-23T16:49:08+05:00] ERROR: Exception handlers complete
[2015-01-23T16:49:08+05:00] FATAL: Stacktrace dumped to /var/cache/chef/chef-stacktrace.out
[2015-01-23T16:49:08+05:00] ERROR: user[root] (accounts::root-test line 1) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '2'
---- Begin output of ["usermod", "-p", "$pw", "-o", "root"] ----
STDOUT:
STDERR: usermod: -o flag is only allowed with the -u flag
Usage: usermod [options] LOGIN
Options:
-c, --comment COMMENT         new value of the GECOS field
-d, --home HOME_DIR           new home directory for the user account
-e, --expiredate EXPIRE_DATE  set account expiration date to EXPIRE_DATE
-f, --inactive INACTIVE       set password inactive after expiration
to INACTIVE
-g, --gid GROUP               force use GROUP as new primary group
-G, --groups GROUPS           new list of supplementary GROUPS
-a, --append                  append the user to the supplemental GROUPS
mentioned by the -G option without removing
him/her from other groups
-h, --help                    display this help message and exit
-l, --login NEW_LOGIN         new value of the login name
-L, --lock                    lock the user account
-m, --move-home               move contents of the home directory to the
new location (use only with -d)
-o, --non-unique              allow using duplicate (non-unique) UID
-p, --password PASSWORD       use encrypted password for the new password
-R, --root CHROOT_DIR         directory to chroot into
-s, --shell SHELL             new login shell for the user account
-u, --uid UID                 new UID for the user account
-U, --unlock                  unlock the user account
-v, --add-subuids FIRST-LAST  add range of subordinate uids
-V, --del-subuids FIRST-LAST  remvoe range of subordinate uids
-w, --add-subgids FIRST-LAST  add range of subordinate gids
-W, --del-subgids FIRST-LAST  remvoe range of subordinate gids
-Z, --selinux-user SEUSER     new SELinux user mapping for the user account
---- End output of ["usermod", "-p", "$pw", "-o", "root"] ----
Ran ["usermod", "-p", "$pw", "-o", "root"] returned 2
[2015-01-23T16:49:08+05:00] ERROR: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
[2015-01-23T16:49:08+05:00] ERROR: Sleeping for 1800 seconds before trying again
Here is the example recipe:
user "root" do
comment "Bastard Operator From Hell"
password "$pw"
shell "/bin/bash"
uid "0"
gid 0
supports :non_unique => true
home "/root"
end
This is old bug reported to https://tickets.opscode.com/browse/CHEF-3344 but still not fixed.

Quick fix which solves the problem:
diff --git a/lib/chef/provider/user/useradd.rb b/lib/chef/provider/user/useradd.rb
index cc770c0..570e307 100644
--- a/lib/chef/provider/user/useradd.rb
+++ b/lib/chef/provider/user/useradd.rb
@@ -135,6 +135,7 @@ class Chef
               opts << option << new_resource.send(field).to_s
             end
           end
+         opts << option << new_resource.send("uid")
         end

         def useradd_options

More correct quick fix:
diff --git a/lib/chef/provider/user/useradd.rb b/lib/chef/provider/user/useradd.rb
index cc770c0..aca235f 100644
--- a/lib/chef/provider/user/useradd.rb
+++ b/lib/chef/provider/user/useradd.rb
@@ -135,6 +135,7 @@ class Chef
               opts << option << new_resource.send(field).to_s
             end
           end
+          opts << "-u" << new_resource.uid
         end

         def useradd_options

need that in a PR, plus tests so as not to regress, plus needs to be shown as correct on all the platforms that the useradd provider runs on.  looks like it applies to all linux based distros so rhel/ubuntu/suse should be checked at least.

Probably better:
diff --git a/lib/chef/provider/user/useradd.rb b/lib/chef/provider/user/useradd.rb
index cc770c0..5de3328 100644
--- a/lib/chef/provider/user/useradd.rb
+++ b/lib/chef/provider/user/useradd.rb
@@ -135,6 +135,7 @@ class Chef
               opts << option << new_resource.send(field).to_s
             end
           end
+          opts << "-u" if new_resource.uid
         end

         def useradd_options

Finally:
diff --git a/lib/chef/provider/user/useradd.rb b/lib/chef/provider/user/useradd.rb
index cc770c0..33b4e75 100644
--- a/lib/chef/provider/user/useradd.rb
+++ b/lib/chef/provider/user/useradd.rb
@@ -135,6 +135,9 @@ class Chef
               opts << option << new_resource.send(field).to_s
             end
           end
+          if new_resource.uid
+            opts << "-u" << new_resource.uid
+          end
         end

         def useradd_options

We'll need to write some tests for this, as Lamont says.

@thommay where should the tests go, would this be a test-kitchen style approach, to show that useradd -o needs -u UID across all supported platforms?

https://tickets.opscode.com/browse/CHEF-3344
Created:	02/Aug/12 8:21 AM
I've run across this any time I'm on ubuntu and want to update a user password, and the users need -o due to overlapping uids. (which happens more often than I care to admit)

I've run into this issue on CentOS 7 as well:
Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '2'
---- Begin output of ["usermod", "-p", "$password", "-o", "$username"] ----
STDOUT:
STDERR: usermod: -o flag is only allowed with the -u flag

The resource roughly reads:
user '$username' do
  uid 9001
  shell '/sbin/nologin'
  home '$home'
  group '$group'
  password '$password'
  non_unique true
  action [:create, :modify]
end

The issue is raised when the password changes from a nil value to an actual hash (i.e on :modify action).

note that all the linux code has now been moved here:
https://github.com/chef/chef/blob/master/lib/chef/provider/user/linux.rb
the best place for a spec is here:
https://github.com/chef/chef/blob/master/spec/functional/resource/user/useradd_spec.rb
that can be used to validate that we get the behavior correct on debian/ubuntu/rhel/suse since we run that spec file on all of those distros before release.


bclib 1.2.5 impact Terralith yellowstone generate

with bclib 1.2.5

no bclib 1.2.5

only bclib1.2.5 and Terralith 2.0.12 datapack

but bclib1.2.4 no this generate error

Could you please try with the just released update. It should fix this issue.

no
bclib1.3.0 no fix this issue

I am sorry to ask, but just to make sure: You tested this with new worlds, right?

yes
generate new world with bclib1.3.0


CompletionItem can't replace text left and right of the cursor

While trying to clarify https://github.com/Microsoft/language-server-protocol/issues/264 I discovered that a completion item can't repace text left and right of the cursor
Extension code:
'use strict';
// The module 'vscode' contains the VS Code extensibility API
// Import the module and reference it with the alias vscode in your code below
import * as vscode from 'vscode';

// this method is called when your extension is activated
// your extension is activated the very first time the command is executed
export function activate(context: vscode.ExtensionContext) {

    vscode.languages.registerCompletionItemProvider('plaintext', {
        provideCompletionItems: (textDocument, position) => {
            if (position.line !== 0 || position.character !== 1) {
                return undefined;
            }
            const result: vscode.CompletionItem[] = [];
            let item: vscode.CompletionItem = new vscode.CompletionItem('wxyz');
            item.insertText = 'wxyz';
            item.range = new vscode.Range(0, 0, 0, 4);
            result.push(item)
            return result;
        }
    })

}

// this method is called when your extension is deactivated
export function deactivate() {
}

text file with content

a<cursor>bcd

Open code complete. No entry is listed.

I played a little and the problem is that the text start with a and the replacement text starts with w (which is !== a). If the text is w<cursor>bcd.

I understand why it is filtered (it doesn't score I guess) but I am not sure that this is intentional.

As someone writing an LSP extension, I think this is the proper behavior.
If I wanted to insert 'wxyz' between 'a' and 'bcd' I would send a TextEdit with range (0,1,0,5), not (0,0,0,4).
If sending a range that overlaps a string, the string should match the relevant part of the replacement text, or be filtered out (or way down), IMO.

Yes, nothing is shown because the suggestion select a to replace but it doesn't set a filter text. That means we'll compare a with w which isn't a match. Either set a filter text or use this sample w<cursor>bcd.


How to apply inner join for four tables?

@pranay2210 Can you describe your scenario some more? Like what kind of tables you have and what query you need. If I know more about your use case I can write a fitting example.

I'm closing question issues that are older than a year.
This is one of them.


CAMEL-11209: Removed the additional dependency to caffeine

Please find a proposal concerning CAMEL-11209.
My understanding is that camel-core has its own private copy of caffeine packages.
Would another component/starter depends upon caffeine, I think it should explicitly state this on its own.
On my machine, mvn clean install succeeded in platforms/spring-boot. Please, let me know if more checks are needed.

Thanks for the PR it has been merged. Do you mind closing this?

The itests was using a bit older SB 1.5.3 release. I upgraded to 1.5.6 and ran the tests and there is a few known issues. But the caffeine change should not have caused those as we have seen those before.


Add labels file example, https file usage

This PR adds to documentation with:

Add example of fetching labels over HTTP
Add example of labels file yml structure

Thanks a lot @rpsu for your PR!


Games?

Any games to feature + screenshots?
Snake game ... tetris... minesweeper. Anything, just to see how it looks like. So, simple
games, nothing fancy or taking too much of your time away.

Ah, I forgot to check the date. Still, it would be nice to have a widget set that could be used for something and is much simpler than gtk and qt. :P


Provide a webhook-style callback on nuget.org

Just like github (https://help.github.com/articles/post-receive-hooks), it would be awesome to have a similar mechanism built in nuget.org. This could open the door to interesting services on top of the gallery, such as smart indexing of packages content.
We talked about this idea during the OuterConf 2013, in particular how such a feature would enable building a smart intellisense service in VS that automatically installs packages from smart-tags in the text editor :).
This is something a user should be able to configure alongside his API key and other settings...

This is one old issue, however I don't see it anywhere though you mentioned it copied to NuGet/NuGetApi#5. Anyone know what happened to it?

@Stephanvs , re-opening this issue, seems this proposal is not tracked.

Push notification would be very valuable for me, and perhaps more consistent with the current state of development processes (particularly in the .Net Core world).
Since packages are being updated more frequently with smaller changes I would like to be continuously updating my projects' references, building and testing them.  This is particularly important in a security context where deploying patched libraries quickly (sic. automatically) is prudent.
To achieve the above goal I currently have to poll Nuget for the latest package versions and compare that to the last response to identify changes.  This is effective, but wasteful on both ends -- needless code executing in my systems to initiate the check, and code running in Nuget to respond the queries.  Moreover, there is a trade-off between timeliness and cost that works against us.
The ideal solution from my perspective would be to have nuget store a distinct (account, package, webhook) triplet and asynchronously POST to the hooks associated with a package when a new version is published (listed, release or pre-release).  The payload could be as simple as the package name (requires more API calls by clients) but the more metadata the better since it obviates the need to hit the API in downstream event processing.  Looking at the code (as a newbie), it seems this would not be a substantial modification to the package upload pipeline.
A less ideal solution, but one I would support and be happy to process for downstream users, would be a full stream of updates ala Twitter's Firehose.

I would like to use a web hook to update a github repo and trigger another project to be built based on the new dependency now on nuget.

I could've used a webhook like that, a simple setting of a URL to which nuget.org will send notifications regarding activities in an account packages, like uploaded, published, and deleted (or unlisted). The arriving payload should include the package name, version, and relevant action.

Related issue: https://github.com/NuGet/NuGetGallery/issues/7392

if everyone who needs this upvotes the original message we'll have a better chance of having it.

As a workaround one can create a mail client receiving the notifications and handling them, although this is error prone and requires larger code base (unless you find a way to integrate such special casing per email message with an existing email client, still an overkill in my opinion).


1.0.5

Could you please release new git and npm versions?

oops, thought it's an issue, not pr, already pushed package.json and tag
npm publish
+<EMAIL_ADDRESS>


Snow can be bypassed by creating a Blob URI inside a worker

In order to prevent Blob URIs from being created within workers, snow overrides the Worker constructor using the following code:
const native = win.Worker;
win.Worker = function Worker(aURL, options) {
  const url = typeof aURL === 'string' ? aURL : toString(aURL);
  if (stringStartsWith(url, 'blob')) {
    return new native(swap(url), options);
  }
  return new native(url, options);
};
// [...]
function swap(url) {
  if (!blobs.has(url)) {
    const content = syncGet(url);
    const prefix = `(function() { Object.defineProperty(URL, 'createObjectURL', { value: () => { throw new Error(\`${BLOCKED_BLOB_MSG}\`) }}) }())`;
    const js = prefix + '\n\n' + content;
    blobs.set(url, createObjectURL(new Blob([js], {
      type: 'text/javascript'
    })));
  }
  return blobs.get(url);
}

This code overrides the URL.createObjectURL function in every worker that is created from a URL that begins with 'blob'. Because URI schemes are case-insensitive, this can be bypassed simply by creating a worker with a URL that begins with 'Blob'. Here is a little demo for that:
blob = new Blob([`
    console.log(URL.createObjectURL(new Blob(["test"])))
`], {type: "text/javascript"})
u = URL.createObjectURL(blob)
u = "B" + u.substring(1)
const w = new Worker(u)

Building on top of arxenix's brilliant bypass in issue #43, this can be used to bypass Snow using the following PoC:
blob = new Blob([`
    js_url = URL.createObjectURL(new Blob([\`
        alert(origin)
    \`], {type: "text/javascript"}))
    postMessage(URL.createObjectURL(new Blob(['<script src="'+js_url+'"></script>'], {type: "text/html"})))
`], {type: "text/javascript"})
u = URL.createObjectURL(blob)
u = "B" + u.substring(1)
w = new Worker(u)
w.onmessage = (msg) => {
    console.log(msg);
    f = document.createElement("iframe");
    document.body.appendChild(f)
    f.src = msg.data;
}

And as for this bypass specifically - awesome work. Truly.

function swap2(aURL) {
    const url = typeof aURL === 'string' ? aURL : toString(aURL);
    if (stringStartsWith(url, 'blob')) {
        if (!blobs.has(url)) {
            const content = syncGet(url);
            const preloadURL = createObjectURL(new Blob([`window.parent.SNOW_WINDOW(window);`], {
                type: 'text/javascript'
            }));
            const prefix = `<script src=${preloadURL}></script>`;
            const js = prefix + '\n\n' + content;
            blobs.set(url, createObjectURL(new Blob([js], {
                type: 'text/html'
            })));
        }
        return blobs.get(url);
    }
    return url;
}
Object.defineProperty(win.HTMLIFrameElement.prototype, 'src', {
    configurable: true,
    enumerable: true,
    set: function(url) {
        return setSrc(this, "IFRAME", swap2(url));
    }
});
Object.defineProperty(win.HTMLFrameElement.prototype, 'src', {
    configurable: true,
    enumerable: true,
    set: function(url) {
        return setSrc(this, "FRAME", swap2(url));
    }
});

function setSrc(element, tag, url) {
    switch (tag) {
        case 'IFRAME':
            return bag.iframeSrc.call(element, url);
        case 'FRAME':
            return bag.frameSrc.call(element, url);
        default:
            return null;
    }
}

The code above is a solution to the problem,, but I only tested the code in the issue. However, I have a few questions. First, why didn't you use MutationObserver? Second, why did you use the iframe onload event? When I examined the code, I couldn't see any benefits of using 'onload'.

MutationObserver isn't a synchronous API, so by the time it tells you a new iframe is introduced to the page, it's too late because the attacker probably gained access to it before you.
The onload event on the other hand acts synchronously against iframes loading local resources (e.g. about:blank or blob:), so it answers that need that the MutationObserver approach doesn't.
Hope this helps.

I got confused because MutationObserver was used in that project, which caused me to be misled. Your explanation helped me understand, thank you.

It's all a matter of what you're trying to defend 😉

It is possible to provide some protections against this bypass without Realm Initialization Control, although RIC would make it much easier to solve.


documentation - to complete

make a minimal documentation - can be completed more after
use also that to write the methods

[ ] important : start with how to run and the description of the ouput files
[ ] make some example also of scripts for analyses / reports at the same time


fix: The pinned array and shortcut array can be implented as one and would make the code cleaner and more efficient

@prajjwalkapoor can i close this?


Accessing context in fetch

Is your feature request related to a problem? Please describe.
I want to make a base resource that causes the user to log out when a 401 is encountered. The authorization state is currently implemented as a top-level context provider, and there is currently no way to adjust it and trigger a rerender inside rest-hooks (unless I write a wrapper hook for all the exported hooks).
Describe the solution you'd like
I actually don't know how to cleanly make this work with the current API.
Describe alternatives you've considered
Wrapping all the use* hooks with a useEffect that accesses the context.

Going to close this issue, just realized I can make this work with a custom error boundary :)

Alternatively you can hook directly into the dispatches via Manager:
import { Manager } from 'rest-hooks';

class AuthManager implements Manager {
  cleanup() {}
  getMiddleware = memoize(function<T extends NetworkManager>(this: T) {
    return <R extends React.Reducer<any, any>>({
      dispatch,
    }: MiddlewareAPI<R>) => {
      return (next: React.Dispatch<React.ReducerAction<R>>) => (
        action: React.ReducerAction<R>,
      ) => {
        switch (action.type) {
          case 'rest-hooks/purge':
          case 'rest-hooks/rpc':
          case 'rest-hooks/receive':
            if (action.error && action.payload.status === 401) {
              // TODO: dispatch auth system
            }
          default:
            next(action);
            return;
        }
      };
    };
  });
}

This has the advantage of not causing double renders if your reaction to 401 would cause a render. This is because the hook throwing the network error can only do so after the commit stage (when DOM is updated). Manager middleware is run during render (before commit) so it can trigger other render updates to be in the same commit batch.

@ntucker Good to know, thanks!

@ntucker I can't import a MiddlewareAPI type to a file (TS2305: Module "../node_modules/rest-hooks/lib" has no exported member "MiddlewareAPI"). I have the latest version of rest-hooks.

https://github.com/coinbase/rest-hooks/pull/139/files#diff-f41e9d04a45c83f3b6f6e630f10117feR107 coming soon. You can just copy the type from the code for now


After upgrading from ver. 0.37.2 to ver. 1.2.0 I get error: Unexpected error: SupersetApiError: Not authorized

Hi
I hope someone can help me to get my Apache Superset running again.
I have upgraded to Superset ver. 1.2.0
First I get the error that the field dashboards.uuid was missing.
I created manually the field with phpMyAdmin with field type binary and length =16
I then created values with this command
UPDATE dashboards SET uuid=uuid()
But now I get this error when I log in to superset and opens a dashboard
Unexpected error: SupersetApiError: Not authorized
The dashboard is public, so everyone should be authorized to see it.
See error on screenshoots:

Can anyone help to solve this issue?
Thank you
Environment

superset version: 1.2.0
python version: 3.7.2
node.js version: 10.16.3

I have searched a long time for a solution, but haven't found any similar problem.

have you run all the commands required after upgrading?
superset db upgrade
superset init

Are there any errors and stack trances from the backend logs?

Hi
Thank you for your reply.
Yes I have run these commands several times.
pip install apache-superset --upgrade
superset db upgrade
superset init

When I start apache I get this info  on the server. Is there another way to see logs?
: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
  "Flask-Caching: CACHE_TYPE is set to null, "
Loaded your LOCAL configuration at [/root/.superset/superset_config.py]
logging was configured successfully
2021-07-10 12:20:33,802:INFO:superset.utils.logging_configurator:logging was configured successfully
2021-07-10 12:20:33,819:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
/superset/lib/python3.7/site-packages/flask_caching/__init__.py:202: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
  "Flask-Caching: CACHE_TYPE is set to null, "
Loaded your LOCAL configuration at [/root/.superset/superset_config.py]
logging was configured successfully
2021-07-10 12:20:33,908:INFO:superset.utils.logging_configurator:logging was configured successfully
2021-07-10 12:20:33,924:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
/superset/lib/python3.7/site-packages/flask_caching/__init__.py:202: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
  "Flask-Caching: CACHE_TYPE is set to null, "
Loaded your LOCAL configuration at [/root/.superset/superset_config.py]
logging was configured successfully
2021-07-10 12:20:34,115:INFO:superset.utils.logging_configurator:logging was configured successfully
2021-07-10 12:20:34,132:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
/superset/lib/python3.7/site-packages/flask_caching/__init__.py:202: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
  "Flask-Caching: CACHE_TYPE is set to null, "
[2021-07-10 12:20:39 +0200] [23370] [INFO] Handling signal: winch

I think maybe it has to to with how I have created uuid-fields. I also found out that I missed the field in table dbs
Can I find a code how to create these fields?
Thanks
Best regards,
Bjarne

Hi again
I can add that when I try to open a dashboard which gives this error
Unexpected error: SupersetApiError: Not authorized
I get this information in the backend log:
  File "/superset/lib/python3.7/site-packages/gunicorn/instrument/statsd.py", line 127, in _sock_send
    self.sock.send(msg)
ConnectionRefusedError: [Errno 111] Connection refused

So I have not access to any of my dashboards
Any ideas to solve this?

Hi
I have searched a lot more for a solution and I guess the issue has something to do with the missing uuid fields.
I don't think that I have created it correctly
According to this fix: https://github.com/apache/superset/pull/13216
I should be able to downgrade db with this command:
Superset db downgrade 070c043f2fdb
It should delete uuid fields. It doesn't for me. I deleted the field manually.
I then upgraded the db again
Superset db upgrade
Superset init
Unfortunately it did not create uuid-fields in my MySQL-tables.
According to this issue https://github.com/apache/superset/issues/13033 I should have uuid-fields created in several other tables than dbs and dashboards
Adding uuids for dbs...
Adding uuids for dashboards...
Adding uuids for slices...
Adding uuids for tables...
Adding uuids for table_columns...
Adding uuids for sql_metrics...
Adding uuids for dashboard_email_schedules...
Adding uuids for slice_email_schedules...
How do I get this?
I hope somebody can help me
Thank you

The statsd error log doesn't seem related this this. I'm not sure what the missing uuid fields would result in not authorized error, it may be caused by something else. Do you have any logs related to the db upgrade command? It seems that with changes in https://github.com/apache/superset/pull/13216 the upgrade command should fail loudly if the uuid columns were not added by the migration.
As a last resort you could try bringing up 1.2 against a new database and then import your datasets/dashboards/charts/etc into the newly installed version.

As a last resort you could try bringing up 1.2 against a new database and then import your datasets/dashboards/charts/etc into the newly installed version.

How could I do this ?

Hi
I bought a new VPS and installed Superset ver. 1.2.0 from scratch. I also connected to a mysql-database.  It is now working but empty from data. How do I import my datasets/dashboards from my existing server?
Best regards,
Bjarne

Superset has an export feature for each of the objects, otherwise you could do a sql dump for each of the tables.

Version 0.38 might be missing exports on some of the objects (database and datasets I think), so the sql dump might be necessary

Hi nytai
Thank you for your reply.
I can easily get all data imported with a SQLdump, but how do I solve that some tables don't have uuids fields.
Is there SQL-job which can add them?  Is it possible to find in the upgrade files?
Best regards,
Bjarne

Hi
I have now imported all data to my new VPS.
I have created all uid fields and changed the values with this job
UPDATE dbs SET uuid = UNHEX(REPLACE(uuid(), "-", ""));
UPDATE slices SET uuid = UNHEX(REPLACE(uuid(), "-", ""));
UPDATE tables SET uuid = UNHEX(REPLACE(uuid(), "-", ""));
UPDATE table_columns SET uuid = UNHEX(REPLACE(uuid(), "-", ""));
UPDATE sql_metrics SET uuid = UNHEX(REPLACE(uuid(), "-", ""));
UPDATE dashboard_email_schedules SET uuid = UNHEX(REPLACE(uuid(), "-", ""));
UPDATE slice_email_schedules SET uuid = UNHEX(REPLACE(uuid(), "-", ""));

I get the exact same error, so it must be in my data
Unexpected error: SupersetApiError: Not authorized
An error occurred while fetching query info: Not authorized
An error occurred while fetching dashboard info: Not authorized
There was an issues fetching your dashboards: [object Response]
There was an issues fetching your chart: [object Response]
There was an issues fetching your saved queries: [object Response]
How can I solve this?
Thanks

Hi,
I solved the issue.
It was the tables below which was completely wrong after update. I found out by comparing a new Superset installation
ab_permission_view
ab_permission
ab_view_menu
ab_permission_view_role
By copying this tables from the new installation to my old installation I got it to work again.
I also found a lot of tables which missed fields  - mostly uuid but also other fields and some tables.
I anyone are interested in the exact changes I can write them here
Best regards,
Bjarne

Yea normally these db schema changes are applied via superset db upgrade, I'm glad you figured it out and were able to apply these schema changes manually -- you clearly know your SQL!

Thank you, nytai. Yes it is strange that my database it not updated with this command and that I don't get error messages. I have experienced this before.
After many hours of searching and trying I feel like an expert on this issue :-)


feat: custom path labels

resolves: #193
related: #192

Hey @goibon
I added the option to customize the current regex and/or add more path labels.
You can try this version by using bundlemon 2.1.0-rc.0
Let me know what you think about the PR
Thanks (:

Hey @goibon
I added the option to customize the current regex and/or add more path labels. You can try this version by using bundlemon 2.1.0-rc.0 Let me know what you think about the PR
Thanks (:

I just tried out 2.1.0-rc.0 for my project and it worked like a charm plus I really like the approach of being able to configure it 👏


How do I build the binary?

Feature Description
I'm always frustrated when there are 0 build instructions.
I want to build this app on an ARM device, but can't find any instructions.
I am not a Go developer, but I can use Dockerfiles. Usually, they build the binaries from source. Otherwise, what's the point? I can download the binary myself, no need for a Docker image.
Solution you would like
Shell instructions that build the binary would be nice. An official Dockerfile that runs these instructions would be even better.
Both would be perfect.
Alternatives you have considered
I see a Makefile, but don't really know how to use these. Do I build the binary by executing make?
Additional context
Typically, the basics of a Dockerfile are to put shell instructions into lines e.g.
RUN mkdir /aaa
RUN echo 123

and to execute the binary in the end with CMD or ENTRYPOINT or both.

Hi!
Sure, I can make instruction more clear.
If you run make It will show available options.

To build: make build
To install (build and add to path): make install

Hope it helps!

@metafates Thanks for making clear instructions!
I am not sure how one would run the binary from a Docker image because it seems to require manual configuration.
Here is a working Dockerfile that builds the binary from source and creates a small image, if it helps :)
FROM golang:latest AS builder

ENV MANGAL_DOWNLOADER_PATH=/downloads
ENV MANGAL_UID=1000
ENV MANGAL_GID=1000

COPY . /mangal-build
WORKDIR /mangal-build
RUN GOOS=linux GOARCH=arm64 make build

FROM alpine:latest

COPY --from=builder --chown=${MANGAL_UID}:${MANGAL_GID} /mangal-build/mangal /mangal
COPY --from=builder --chown=${MANGAL_UID}:${MANGAL_GID} /mangal-build/config /config
COPY --from=builder --chown=${MANGAL_UID}:${MANGAL_GID} /mangal-build/downloads ${MANGAL_DOWNLOADER_PATH}

USER ${MANGAL_UID}:${MANGAL_GID}

WORKDIR /

RUN apk add coreutils

# ENTRYPOINT ["/mangal"]


Restack, add various fixes branch

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #324

PR #314

PR #310

PR #311

PR #312

PR #313

PR #315

PR #316


Updates PR messages

Jenkins istio-testing/pr-master job started

Jenkins istio-testing/pr-master job passed

Jenkins job istio-testing/pr-master started

Jenkins job istio-testing/pr-master passed


ome-training-2: Replacement for current outreach

Main changes:

OMERO.server runs from a virtualenv
OMERO 5.5.1
PostgreSQL 10.8

Requires:

https://github.com/ome/ansible-role-omero-server/pull/36
https://github.com/ome/ansible-role-omero-web/pull/21

OMERO was restored as follows:
systemctl stop omero-server
sudo -u postgres pg_restore --clean -d omero omero-database-omero-20190710-154903-139204.pgdump
cd /
sudo tar -xf ~/outreach-omero-20190710/outreach-OMERO-20190710-1550.tar
systemctl start omero-server

The wrapper may need to overwrite the original location due to hard-coded scripts using /opt/omero/server/OMERO.server/bin/omero

Interesting drop of the fqdn hostname. Deployed to a different infrastructure?

I'd assume it's just a group that's in a different PR.

Conflicting PR. Removed from build TRAINING-merge#333. See the console output for more details.
Possible conflicts:

Upstream changes

requirements.yml
omero/training-server/playbook.yml

--conflicts

Conflicting PR. Removed from build TRAINING-merge#334. See the console output for more details.
Possible conflicts:

Upstream changes

requirements.yml
omero/training-server/playbook.yml

--conflicts

This has been deployed to ome-training-2.openmicroscopy.org (also known as workshop.openmicroscopy.org), but will need rebasing after https://github.com/ome/prod-playbooks/pull/206

Note updated description

Rebased following merging of https://github.com/ome/prod-playbooks/pull/206
diff -Nur omero/training-server/playbook.yml omero/training-server-2/playbook.yml
--- omero/training-server/playbook.yml	2019-09-26 10:11:33.000000000 +0100
+++ omero/training-server-2/playbook.yml	2019-09-26 10:38:19.000000000 +0100
@@ -1,6 +1,9 @@
-# Install OMERO.server and OMERO.web on localhost
+---
+# The OME training server(s)
+# Set https_letsencrypt_enabled to True in production to ensure certbot
+# handles the letsencrypt certificate setup

-- hosts: outreach.openmicroscopy.org
+- hosts: ome-outreach
   pre_tasks:

     - name: Install Make Movie script Prerequisite | MEncoder - Repo
@@ -41,13 +44,18 @@
       - user: omero
         password: omero
         databases: [omero]
-      postgresql_version: "9.6"
+      postgresql_version: "10"

     - role: ome.versioncontrol_utils

     - role: ome.nfs_mount

     - role: ome.omero_server
+      omero_server_virtualenv: yes
+      omero_server_python_addons:
+        - "omero-cli-duplicate=={{ omero_cli_duplicate_release }}"
+        - "omero-cli-render=={{ omero_cli_render_release }}"
+        - "omero-metadata=={{ omero_metadata_release }}"

     - role: ome.omero_web
       # omero_web_config_set:
@@ -70,7 +78,7 @@
         state: directory

     # Inspired by
-    # https://github.com/openmicroscopy/prod-playbooks/blob/7695bf8b1c4f0ae4314524366b91c300c1fdb30b/nightshade-webclients.yml#L119
+    # https://github.com/ome/prod-playbooks/blob/7695bf8b1c4f0ae4314524366b91c300c1fdb30b/nightshade-webclients.yml#L119
     - name: omero-web nginx nested include
       become: yes
       lineinfile:
@@ -105,15 +113,6 @@
         name: docker-python
         state: present

-    - name: Omero.cli plugins | plugin install via pip & pypi
-      become: yes
-      pip:
-        name:
-        - "omero-cli-duplicate=={{ omero_cli_duplicate_release }}"
-        - "omero-cli-render=={{ omero_cli_render_release }}"
-        - "omero-metadata=={{ omero_metadata_release }}"
-        state: present
-
     - name: Create a figure scripts directory
       become: yes
       file:
@@ -251,6 +250,15 @@
         insertbefore: BOF
         line: "+:{{ omero_server_system_managedrepo_group }}:ALL"

+    - name: bin/omero wrapper
+      become: yes
+      copy:
+        src: files/bin-omero
+        dest: /usr/local/bin/omero
+        owner: "root"
+        group: "root"
+        mode: 0755
+
     - name: Run docker for ldap
       become: yes
       docker_container:
@@ -338,4 +346,3 @@
     external_nic: "{{ ansible_default_ipv4.interface }}"

 - include: letsencrypt.yml
-  when: not (molecule_test | default(False))

From now until 27 October 2019 outreach and workshop will be treated as independent servers.

This explains the cut-n-paste?  If so, is there likely to be so much divergence between the two?

The plan now is to re-image outreach so it will be identical to workshop as defined by this PR

Rebased to include https://github.com/ome/prod-playbooks/pull/211

Which playbook should I run, the one under training-server or the one under training-server-2 ?

At the moment neither, I'm in the middle of updating outreach. Once that's done they'll only be one playbook.

@sbesson it seems that my testing is finished for now here, see https://openmicroscopy.slack.com/archives/C0K5ME1EW/p1572522697009600

I am afraid this is too unclear for me to try to run something against the training servers - these are production. Happy to be told otherwise, as well as please tell me what playbook to run and how to point it to which servers (like outreach, workshop, or both) or is that taken care of already ? @sbesson @manics

Thinking about it further, I guess  it would be good to merge this. I will not be running the original playbook here against workshop server. I need to upgrade the apps - hence, need to open a PR for that - only then run the playbook. I guess outreach server could serve as.a testing server, and then, if all is good, we can re-run the playbook against both (outreach and workshop).
cc @manics @sbesson ?

I think the strategy proposed in https://github.com/ome/prod-playbooks/pull/186#issuecomment-548748004 looks sane. As far as I can tell, the playbook has successfully been run against the production training server so there is no reason to keep the old playbook.
Leaving @pwalczysko to perform follow-up tests upgrading the deployment as necessary in preparation of the upcoming workshop.


Keycloakify Account Theme Calling AccountFormService

Summary
I am using the account theme with Keycloakify. The react code is displaying as expected, but when I try to create an SPI to pass other server-side variables to the frontend (by setting a new AccountResourceProvider), there's no effect. I'm looking at the logs (running locally from docker) and I'm seeing log statements like:
INFO  [org.keycloak.services.resources.account.AccountFormService] (executor-thread-1) accountPage

Looking at the Keycloak source code, the AccountFormService hasn't existed since version 21.1. I'm using Keycloak version 23.0.3. How is Keycloakify calling this old code?
Keycloak Version
23.0.3
Keycloakify Version
9.3.1
Steps to reproduce

run yarn run build-keycloak-theme
copy the *.jar file to the Keycloak root and build
select 'mytheme' as the account theme for the realm
login/impersonate a user
view logs and see the message from an old build of Keycloak

package.json
"scripts": {
    "postinstall": "copy-keycloak-resources-to-public",
    "start": "react-scripts start",
    "build": "react-scripts build",
    "build-keycloak-theme": "yarn build && keycloakify",
    "storybook": "start-storybook -p 6006",
    "test": "jest"
  },
  "keycloakify": {
    "themeName": "mytheme",
    "doBuildRetrocompatAccountTheme": false
  },
"dependencies": {
    ...
    "keycloak-js": "23.0.3",
    "keycloakify": "9.3.1",
    ...
  },

Looks like I just needed to use the mytheme_retrocompat theme

Ohhhhh! Damn I understand!!! I left "doBuildRetrocompatAccountTheme" to false in the starter!
That must be why we're losing stars!

Thanks for reporting!


python311Packages.axis: 54 -> 55

Diff: https://github.com/Kane610/axis/compare/refs/tags/v54...v55
Changelog: https://github.com/Kane610/axis/releases/tag/v55
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 296358 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.axis
python311Packages.axis
python311Packages.axis.dist
python312Packages.axis
python312Packages.axis.dist


[Integration Tests] Additional stratisX tests

What it says on the tin.

@zeptin can you merge latest from master so that we can see how the build runs?

@fassadlr done. Note that this may require #2611 to be merged before the tests will pass, but let's see.


Visual "glass" effect after window close

Environment
Windows build number: Microsoft Windows [Versione 10.0.18363.778]
Windows Terminal version (if applicable): 0.11.1191.0

Any other software? No

Steps to reproduce

Open new terminal window
Move your mouse on Windows Taskbar, on terminal icon

Close the terminal with middle mouse (scroll wheel) click

Expected behavior

No visual glitches
Actual behavior

Visual "glass" effect glitch

Notes
Visual glitch persists with stock settings

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #4774 for more discussion.
/dup #4774


Remove usage of fmt.Errorf

The patchset uses the errors pkg to follow the guideline at
https://hyperledger-fabric.readthedocs.io/en/latest/error-handling.html
Change-Id: I36eaac1b429c69195e4af1bb5bb25fc1a2578168
Type of change

Improvement (improvement to code, performance, etc)

Description
Remove the usage of fmt.Errorf. Follow the official guideline to change
to the errors package.
Additional details
N/A
Related issues
N/A
Release Note
N/A

I'm not sure these guidelines are still up-to-date, since github.com/pkg/errors has been archived 2 years ago and is effectively a dead project. @denyeart wdyt?

@ale-linux I made an initial comment over at https://github.com/hyperledger/fabric/pull/4461#issuecomment-1747668231.
I've also opened issue #4468 with more background so that we can discuss a plan in more detail.


Fix issue 32

Fix dummy content:

Skip routes with less than two stops
Remove caching from a generator function (which was producing wrong output)

Fix stop extraction:

Many stops were being missed due to a mistake

Close #32

Hey @mehdisadeghi thanks for the quick fix :)
As a quick remark. Since you are sole developer of osmtogtfs I can understand that you know all the little details of it so there is not real need for explaining the fixes. However  I just thought about myself in those cases where I came to work on a project 6 month laters and found myself completely ignorant on why I did things in a certain way :D
I think it would be better for your future sanity to have a more clear description of the errors that were fixed, otherwise in the future you would be left wondering why was that changed at all. (I am assuming that you know of the Blame feature of git and github which lets you know exactly which commit changed which line of code; that is pretty handy if you are tracing back errors or design decisions ;))
To make it more clear

Remove caching from a generator function (which was producing wrong output)

From what I saw, the output contained lots of duplicates which is I guess what you mean here ...

Many stops were being missed due to a mistake

What is that mistake? I saw an if statement change in conditions but couldnt quickly grasp what was the intention there.

Thanks for your remarks @carocad!

I came to work on a project 6 month laters and found myself completely ignorant on why I did things in a certain way :D

Yes, very true!

I think it would be better for your future sanity to have a more clear description of the errors that were fixed

Please see the commit messages, here and here. I have tried to put important fixes in separate commits and instead of writing in the PR, I have written more information in the commit log (the body, not the first line).
However, I totally agree that it's a good practice to explain everything in more detail :) (and perhaps not mixing cleanups and important fixes).

From what I saw, the output contained lots of duplicates which is I guess what you mean here ...

It was causing many routes with single stops, not sure about duplicates. The problem was like this: I have a simple function which returns a list of stops for the given route. This function is a generator, (like lazy sequences in Clojure). So, once cache, after first consumption, the later calls were getting the consumed cached generator, which was obviously yielding no stops, hence so many routes with no stops.

What is that mistake? I saw an if statement change in conditions but couldnt quickly grasp what was the intention there.

I try my best to explain this problem correctly! While processing OSM relations I call a function to extract stops. While iterating over relation members, I find stops and add them to a list. At the same time, I add them to a map of route->stops. The mistake was putting this line in the wrong place, so it was missing many stops. I mean, a stop could be shared by many different routes, so the if there, was correctly avoiding creating those stops for a second time, however, those stops should have been added to their corresponding routes, and there was the mistake!
Hope it helps!

Please see the commit messages, here and here. I have tried to put important fixes in separate commits and instead of writing in the PR, I have written more information in the commit log (the body, not the first line).

Thanks for letting me know. My mistake ... I will check those more throughly in the future  😄


feibit zigbee-smoke-co-detector

Hi Mariano, can you add to Edge-Drivers-Beta/zigbee-smoke-co-detector/fingerprints.yml the device below?
Manufacturer Code: feibit
Model: FNB56-GAS05FB1.4
Thank you,

Hi,
Added to this driver version
You need uninstall device
Install this driver version in your Hub
Pair device with with this driver version, you do not perform a driver change from zigbee thing
I don't know if it will work well
───────────────────────────────────────────────────
 Driver Id    a2f7ec78-14c8-492d-9965-7544b0fc3b68
 Name         Zigbee Smoke/CO Detector Mc
 Version      2024-08-19T20:54:02.425672381
───────────────────────────────────────────────────
- id: "FNB56-GAS05FB1.4/feibit"
    deviceLabel: feibit Gas Sensor
    manufacturer: feibit
    model: FNB56-GAS05FB1.4
    deviceProfileName: gas-detector

Thank you sir!


add security linter bandit to nox

closes #74

Today I had the opportunity together with @Nicoretti to take a look at your PR.
Nico and I are aware of some changes described in issue #181.
And we propose to wait until #181 is implemented before finalizing the current PR.


Multiselected objects: Enum values are not applied!

Hi Jacob, this one is much more serious:

Select multiple game objects with the same BaseBehavior script.
Change an ENUM property
Select a single one of these objects
The enum value was not applied

This really fu**s up our workflow and brings a lot of mistakes. Please fix it asap. Thanks allot.

FYI, multi-edit is still very buggy and not yet complete. I'm probably going to put it behind a flag.

I've put it behind the fiSettings.EnableMultiEdit flag.

This should be fixed in the next build.


Activity tab should be optional

I create a team with only issues tab, but he still could see Activity tab

I think in such case you can see activities only for issues or not?

@lafriks you are right.


Issue #2658: cache StorageClient to avoid create it each time.

Motivation
cache StorageClient to avoid create it each time.
Modifications
add storageClient in FunctionsImpl
Result
original UT pass.

rerun java8 tests


Allow non root users to interact with wpa_supplicant over dbus

Describe the bug
We have the option networking.wireless.userControlled.enable = true; which allows users to interact with wpa_supplicant via wpa_cli and wpa_gui. This option however does not enable users to interact with wpa_supplicant directly via its dbus interface. It would be nice if this boolean also gave us permission to communicate with wpa_supplicant directly over dbus. I am not an expert, but I can't see any reason why this would be unsafe, considering that we can already interact with it as non root users indirectly using other tools.
I think this could be easily done by changing <policy user="root"> to <policy group="wheel"> in the first policy and deleting the second policy in the following config:
cat  $out/share/dbus-1/system.d/dbus-wpa_supplicant.conf

<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
        <policy user="root">
                <allow own="fi.w1.wpa_supplicant1"/>

                <allow send_destination="fi.w1.wpa_supplicant1"/>
                <allow send_interface="fi.w1.wpa_supplicant1"/>
                <allow receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
        </policy>
        <policy context="default">
                <deny own="fi.w1.wpa_supplicant1"/>
                <deny send_destination="fi.w1.wpa_supplicant1"/>
                <deny receive_sender="fi.w1.wpa_supplicant1" receive_type="signal"/>
        </policy>
</busconfig>

If I am understanding correctly, this config gets used when we have
services.dbus = {
  enable = true;
  packages = [ pkgs.wpa_supplicant ];
};

Steps To Reproduce
Steps to reproduce the behavior:

Try and talk to wpa_supplicant over dbus as a non root user.

PR implementing above: https://github.com/NixOS/nixpkgs/pull/173318


Error Connecting DB

2017-11-05T17:16:09.897Z - error: Error connecting to database
{ SequelizeConnectionRefusedError: connect ECONNREFUSED <IP_ADDRESS>:3306

Hello!
Probably you haven't enter database information correctly, and you receive this error.
You can try to delete "config" file , copy it again and try to connect to the database you have created in MySQL. When you enter database information in "database host" we would recommend enter : localhost as value

Hi,
The main problem is that the installation script \backoffice-administration-master\config\env\db.connection.js tries to install the portal in mysql but mysql is not known to the installation. I tried to install mysql locally on the server but with no luck. I tried also to "npm install mysql" but no luck.
I changed the above file to point to "sqlite" before the installation starts. It worked and then I logged on the server but half of the things does not work with in portal (useless). This is quite buggy installation + procedure which does not work out of the box.  Please try on a clean box to reproduce the errors. I have tried the installation on Redhat + ubuntu but the result is the same.
I think may there are some major part missing in the installation guide or some prequisite for the installation. For example: if you look the the db.connection.js file it points to mysql servver by default but there is no information about the mysql server installation through npm, if it is install then server.js doesnot checks that or try to connect to the server.

I got the solution. (I am installing on Redhat and also valid for Centos/Fedora)
Mariadb/Mysql server must be installed before you continue.
git clone https://github.com/MAGOWARE/backoffice-administration.git
cd backoffice-administration/
npm install
mysql
MariaDB [(none)]> create database magoware;
Query OK, 1 row affected (0.00 sec).
node server.js
entering first function
sync =  undefined
force =  undefined
Please enter database information below :
Enter database username:  root
Enter database password:
Enter database host address:  localhost
Enter database name:  magoware
Configuration file saved !
Logon to http://server-ip
username: admin
Password:admin
Now you can start using/testing Magoware
I hope this will help anyone trying to install MAGOWARE.
Regards
Armaghan


fix nav button 404 bug on nginx

Simply adds a .html to each URL to fix the 404 bug with nginx, reported in #276. I wasn't sure which branch to open this in but I believe next is the testing branch and I should push this there? Not sure. Anyway, hope this helps! ^.^

I discovered that I missed some other instances of the problem. Creating a new pull request.


Zero Scraches not working on Hugging Face

Also, can you tell if this project can be run on Google Colab and how?

for now, try from the backend Zero Scratches

Also, can you make it runnable on Google Colab? I tried it doesn't work there.


Readme typo fix

I agree with this statement about Python package installation so strongly I felt it was important to fix the typo :)

Greeeeeat


GPUGridLayer PART-2: Add support for multiple weights

For #2084

Background

Update gpu aggregation utility methods  to support multiple weights.
Update Contour and GPUGridLayers to use these updated methods.
Update GPUGridCellLayer (private to GPUGridLayer) JS and Shaders to support color and elevation, based on aggregation results.
Add unit test for GPUGridCell layer's vertex shader.

NEXT: RFC and PR to integrate GPUGridLayer with GridLayer.

Change List

GPU Grid Aggregation PART-2: Add support for multiple weights

Coverage decreased (-0.2%) to 60.183% when pulling 75974dd72c3ac1350d7577347d09c18cec6b741b on GPUGridLayer2 into fb6d14e574126b3305f35a1c95cb8f46279c670d on GPUGridLayer1.


Tensorflow error when calling to fd.LogLikelihood bestfit() function

I am currently fitting a source to data, and while it worked fine yesterday, as of today I get an error when running the LogLikelihood.bestfit function. Below is the code I am running (more or less) and the output error. Here's the main summary line: OperatorNotAllowedInGraphError: using a tf.Tensor as a Python bool is not allowed: AutoGraph did convert this function. This might indicate you are trying to use an unsupported feature.
I have tried changing the optimizer, the dataset and the use_hessian arguments, but this seems to be a tensorfzlow issue? I am on flamedisx v1.3.0 and tensorfzlow v2.4.1, again no changes to any of this code since I ran yesterday.
I'm happy to provide other information to help sort this out!
Code:
fdll = fd.LogLikelihood(sources=dict(er=fd.SR1ERSource),
                                batch_size = 100,
                                free_rates = 'er',
                                data = rn_data_cut,
                                log_constraint = None,
                        **kwargs # these are my fit variables, e.g. g1, gamma_er, omega_er., based on arxiv:1902.11297v2
                             )
fdll_guess = fdll.guess()
fdll_bestfit = fdll.bestfit(guess=fdll_guess, optimizer='scipy', use_hessian=True) #this is the breaking line

Output:
---------------------------------------------------------------------------
OperatorNotAllowedInGraphError            Traceback (most recent call last)
<ipython-input-49-dafbd7a2e4bf> in <module>
      1 fdll_guess = fdll.guess()
----> 2 fdll_bestfit = fdll.bestfit(guess=fdll_guess, optimizer='scipy', use_hessian=True)

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/likelihood.py in bestfit(self, guess, fix, bounds, optimizer, get_lowlevel_result, get_history, use_hessian, return_errors, nan_val, optimizer_kwargs, allow_failure)
    513         # Check the likelihood has a finite value and gradient before starting
    514         val, grad, hess = self.log_likelihood(**guess,
--> 515                                               second_order=use_hessian)
    516         if not np.isfinite(val):
    517             raise ValueError("The likelihood is - infinity at your guess, "

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/likelihood.py in log_likelihood(self, second_order, omit_grads, **kwargs)
    321                     omit_grads=omit_grads,
    322                     second_order=second_order,
--> 323                     **params)
    324                 ll += results[0].numpy().astype(np.float64)
    325

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py in __call__(self, *args, **kwds)
    826     tracing_count = self.experimental_get_tracing_count()
    827     with trace.Trace(self._name) as tm:
--> 828       result = self._call(*args, **kwds)
    829       compiler = "xla" if self._experimental_compile else "nonXla"
    830       new_tracing_count = self.experimental_get_tracing_count()

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py in _call(self, *args, **kwds)
    860       # In this case we have not created variables on the first call. So we can
    861       # run the first trace but we should fail if variables are created.
--> 862       results = self._stateful_fn(*args, **kwds)
    863       if self._created_variables:
    864         raise ValueError("Creating variables on a non-first call to a function"

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/eager/function.py in __call__(self, *args, **kwargs)
   2939     with self._lock:
   2940       (graph_function,
-> 2941        filtered_flat_args) = self._maybe_define_function(args, kwargs)
   2942     return graph_function._call_flat(
   2943         filtered_flat_args, captured_inputs=graph_function.captured_inputs)  # pylint: disable=protected-access

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/eager/function.py in _maybe_define_function(self, args, kwargs)
   3359
   3360           self._function_cache.missed.add(call_context_key)
-> 3361           graph_function = self._create_graph_function(args, kwargs)
   3362           self._function_cache.primary[cache_key] = graph_function
   3363

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/eager/function.py in _create_graph_function(self, args, kwargs, override_flat_arg_shapes)
   3204             arg_names=arg_names,
   3205             override_flat_arg_shapes=override_flat_arg_shapes,
-> 3206             capture_by_value=self._capture_by_value),
   3207         self._function_attributes,
   3208         function_spec=self.function_spec,

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/framework/func_graph.py in func_graph_from_py_func(name, python_func, args, kwargs, signature, func_graph, autograph, autograph_options, add_control_dependencies, arg_names, op_return_value, collections, capture_by_value, override_flat_arg_shapes)
    988         _, original_func = tf_decorator.unwrap(python_func)
    989
--> 990       func_outputs = python_func(*func_args, **func_kwargs)
    991
    992       # invariant: `func_outputs` contains only Tensors, CompositeTensors,

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/eager/def_function.py in wrapped_fn(*args, **kwds)
    632             xla_context.Exit()
    633         else:
--> 634           out = weak_wrapped_fn().__wrapped__(*args, **kwds)
    635         return out
    636

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/eager/function.py in bound_method_wrapper(*args, **kwargs)
   3885     # However, the replacer is still responsible for attaching self properly.
   3886     # TODO(mdan): Is it possible to do it here instead?
-> 3887     return wrapped_fn(*args, **kwargs)
   3888   weak_bound_method_wrapper = weakref.ref(bound_method_wrapper)
   3889

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/framework/func_graph.py in wrapper(*args, **kwargs)
    971                     recursive=True,
    972                     optional_features=autograph_options,
--> 973                     user_requested=True,
    974                 ))
    975           except Exception as e:  # pylint:disable=broad-except

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/autograph/impl/api.py in converted_call(f, args, kwargs, caller_fn_scope, options)
    348   if conversion.is_in_allowlist_cache(f, options):
    349     logging.log(2, 'Allowlisted %s: from cache', f)
--> 350     return _call_unconverted(f, args, kwargs, options, False)
    351
    352   if ag_ctx.control_status_ctx().status == ag_ctx.Status.DISABLED:

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/autograph/impl/api.py in _call_unconverted(f, args, kwargs, options, update_cache)
    473
    474   if inspect.ismethod(f) and isinstance(f.__self__, function.TfMethodTarget):
--> 475     return f.__self__.call(args, kwargs)
    476
    477   if kwargs is not None:

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/eager/function.py in call(self, args, kwargs)
   3847     if tf_inspect.ismethod(wrapped_fn):
   3848       wrapped_fn = six.get_unbound_function(wrapped_fn)
-> 3849     return wrapped_fn(self.weakrefself_target__(), *args, **kwargs)
   3850
   3851

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/likelihood.py in _log_likelihood(self, i_batch, dsetname, data_tensor, batch_info, omit_grads, second_order, **params)
    411         # Forward computation
    412         ll = self._log_likelihood_inner(
--> 413             i_batch, params_unstacked, dsetname, data_tensor, batch_info)
    414
    415         # Autodifferentiation. This is why we use tensorflow:

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/likelihood.py in _log_likelihood_inner(self, i_batch, params, dsetname, data_tensor, batch_info)
    446                 # it breaks the Hessian (it will give NaNs)
    447                 autograph=False,
--> 448                 **self._filter_source_kwargs(params, sname))
    449             drs += dr * rate_mult
    450

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/source.py in differential_rate(self, data_tensor, autograph, **kwargs)
    409         else:
    410             return self._differential_rate(
--> 411                 data_tensor=data_tensor, ptensor=ptensor)
    412
    413     def ptensor_from_kwargs(self, **kwargs):

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/block_source.py in _differential_rate(self, data_tensor, ptensor)
    260
    261             # Compute the block
--> 262             results[b_dims] = r = b.compute(data_tensor, ptensor, **kwargs)
    263
    264             # Try to matrix multiply with earlier blocks, until we cannot

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/block_source.py in compute(self, data_tensor, ptensor, **kwargs)
     49     def compute(self, data_tensor, ptensor, **kwargs):
     50         kwargs.update(self.source._domain_dict(self.dimensions, data_tensor))
---> 51         result = self._compute(data_tensor, ptensor, **kwargs)
     52         assert result.dtype == fd.float_type(), \
     53             f"{self}._compute returned tensor of wrong dtype!"

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/lxe_blocks/detection.py in _compute(self, data_tensor, ptensor, photons_produced, photons_detected)
    118         return super()._compute(quanta_produced=photons_produced,
    119                                 quanta_detected=photons_detected,
--> 120                                 data_tensor=data_tensor, ptensor=ptensor)
    121
    122

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/lxe_blocks/detection.py in _compute(self, data_tensor, ptensor, quanta_produced, quanta_detected)
     45         acceptance = self.gimme(self.quanta_name + '_acceptance',
     46                                 bonus_arg=quanta_detected,
---> 47                                 data_tensor=data_tensor, ptensor=ptensor)
     48         return result * acceptance
     49

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/block_source.py in gimme(self, *args, **kwargs)
     41     def gimme(self, *args, **kwargs):
     42         """Shorthand for self.source.gimme, see docs there"""
---> 43         return self.source.gimme(*args, **kwargs)
     44
     45     def gimme_numpy(self, *args, **kwargs):

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/source.py in gimme(self, fname, data_tensor, ptensor, bonus_arg, numpy_out)
    350             kwargs = {pname: self._fetch_param(pname, ptensor)
    351                       for pname in self.f_params[fname]}
--> 352             res = f(*args, **kwargs)
    353
    354         else:

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/xenon/x1t_sr1.py in photon_acceptance(self, photons_detected, scalar)
    252                                         self.recon_eff_map_s1,
    253                                         self.domain_def_ph,
--> 254                                         scalar)
    255         return acceptance
    256

~/.conda/envs/sophia/lib/python3.7/site-packages/flamedisx-1.3.0-py3.7.egg/flamedisx/xenon/x1t_sr1.py in cal_rec_efficiency_tf(sig, fmap, domain_def, pivot_pt)
    136     bias_median = interpolate_tf(sig_tf, fmap[1], domain_def)
    137
--> 138     if pivot_pt<0:
    139         bias_other = interpolate_tf(sig_tf, fmap[0], domain_def)
    140         bias_out = pivot_pt*(bias_median-bias_other)+bias_median

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/framework/ops.py in __bool__(self)
    883       `TypeError`.
    884     """
--> 885     self._disallow_bool_casting()
    886
    887   def __nonzero__(self):

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/framework/ops.py in _disallow_bool_casting(self)
    487     elif ag_ctx.control_status_ctx().status == ag_ctx.Status.ENABLED:
    488       self._disallow_when_autograph_enabled(
--> 489           "using a `tf.Tensor` as a Python `bool`")
    490     else:
    491       # Default: V1-style Graph execution.

~/.conda/envs/sophia/lib/python3.7/site-packages/tensorflow/python/framework/ops.py in _disallow_when_autograph_enabled(self, task)
    474     raise errors.OperatorNotAllowedInGraphError(
    475         "{} is not allowed: AutoGraph did convert this function. This might"
--> 476         " indicate you are trying to use an unsupported feature.".format(task))
    477
    478   def _disallow_in_graph_mode(self, task):

OperatorNotAllowedInGraphError: using a `tf.Tensor` as a Python `bool` is not allowed: AutoGraph did convert this function. This might indicate you are trying to use an unsupported feature.

Interesting: it looks like somehow the pivot_pt argument to cal_rec_efficiency_tf has become a tensor, but it should be a python float. Perhaps the values in kwargs have become tensors?
(The parameter controlling the S1 reconstruction efficiency pivot seems to currently have the unhelpful name scalar; we should change this. I missed this during the review of #97.)
Flamedisx's bestfit should return a dict of python values; if it's giving tensors instead something strange is happening. Maybe a package was upgraded in your environment yesterday, and you've hit on some compatibility problem?
@plt109, since you wrote the reconstruction efficiency interpolation code, maybe you have seen things like this before?

Hey! Thanks for the fast reply.
Yes indeed, the fdll.guess() function is yielding results like (numbers made up by me since based on data ;) ):
'er_rate_multiplier': <tf.Tensor: shape=(), dtype=float32, numpy=0.16739142>
etc. for the other parameters.
So, potentially if I just change this to a dict, that would solve the trouble? I agree this must be an incompatibility issue, what's weird is I'm working in a private conda environment that hasn't changed in the past ~18 hours to warrant this, at least to my knowledge.
What's even STRANGER (and more interesting to me as a new learner of fd), is that if I change to call fd.xenon.x1t_sr1.SR1ERSource, rather than fd.SR1ERSource, it works okay with the tensor guesses... so this is strange to me! I think the issue is still important, but this seems to fix it for now.

I should also note that I was getting this error while working with fd.SR1ERSource, which disappeared when I switched to fd.xeon.x1t_sr1.SR1ERSource in the fdll = LogLikelihood call as above:
ValueError: Found event with non-positive s2 acceptance: did you apply and configure your cuts correctly?

Not a pressing issue anymore, but seems inconsistent, unless the cuts are somehow different between the two calls.

Your last observation sounds like bad news, fd.SR1ERSource is fd.xenon.x1t_sr1.SR1ERSource should be True. Otherwise you may have two different flamedisx installations that are somehow fighting one another.
For me ll.guess() also outputs a dict of tensorflow constants. This isn't very nice, but even if we fixed that, Likelihood.prepare_params will still converts every parameter the user or the optimizer specifies to a tensorflow constant. (It has to: if autographed functions get a different python-valued argument they retrace themselves). So converting to a dict of python values shouldn't solve your problem -- flamedisx will convert them right back.
Maybe tensorflow 2.4 has become stricter about some things, causing the interpolation function to break? I have 2.3.0, since 2.4.1 isn't out on conda yet (https://anaconda.org/anaconda/tensorflow). Unfortunately continuous integration is not of much help, our Travis builds have been down for a while (something about expired credits?), and they don't test the SR1 sources anyway.

Hey Jelle! Moving to tf v2.2.0 solved the issue but I cannot be confident that that was the solution alone, or if I had frantically changed another line of code here or there.
One thing I can confirm is that the fd.SR1ERSource does == fd.xenon.x1t_sr1.SR1ERSource once I reinstalled in a clean environment, so perhaps I was simply working with some added incompatibilities this whole time. The good news is that it works now, with tf v2.2.0!

So this issue is resolved when you moved back to tf v2.2.0?
Just for documentation's sake, I am currently using
tensorboard==2.4.0
tensorboard-plugin-wit==1.6.0
tensorflow==2.3.1
tensorflow-estimator==2.3.0
tensorflow-probability==0.11.1
I usually do not upgrade unless something breaks. Might be a bad habit.

Hey! Yes I think it was a versioning issue. Given that we can probably close this issue? I will reopen if I find the same problem again with the working versions!

Sounds good. It will be nice to keep track of the version of the tf-related packages to see when things start to break.

Haha yep! This is usually what Travis CI could solve, but they've recently gone to requiring payment for checks, so unfortunately we'll have to think of something else (or find a generous PI ;) ) That way you can check with multiple versions of packages in isolated environments, and then set up requirements to ensure users are not going to have incompatibilities. With tensor flow, I think there's a lot of development ongoing always so things can break often (just requiring little fixes and calls.)


CASSANDRA-18715 Add support for a vector search index in SAI

Adds a HNSW index for floating point vectors
Add ORDER BY ANN OF capability to do ANN search of the HNSW index and order the results by score

patch by Mike Adamson; reviewed by  for CASSANDRA-18715
Co-authored-by Jonathon Ellis<EMAIL_ADDRESS>More to follow

@adelapena I have addressed (I believe) the remaining review comments and rebased the branch against the latest cassandra-5.0

@adelapena @jbellis I believe I have now addressed the current review comments. I will carry on with CI getting the tests work reliably. I am nearly there with that.
If you could please have another look, I would be grateful.

Committed with https://github.com/apache/cassandra/commit/949b760f5516c139591473038917247b1fd7f500


bot.AnswerCallbackQueryAsync(e.QueryId).Wait();

System.AggregateException
HResult=0x80131500
Сообщение = One or more errors occurred. (Object reference not set to an instance of an object.)
NullReferenceException: Object reference not set to an instance of an object.

Thank you for reporting this. Version 1.3.1 has a fix for the issue.

Version 1.4 has a fix for this. Thanks.


Jasmine specs

All your test titles read a little weirdly given the it method. Maybe tweak them (in a rebase and force push?) so they read like a sentence?
For example:
it('original placeholder text is used when summary is blank'

might become:
it('uses original placeholder text when summary is blank'

:shipit:


Create hello.py

Thanks @thisiscoding1234 we can create a hello.py.

Also @thisiscoding1234 the workflow is down so don't worry about that.

As you can see, I have mentioned this pull request in an issue and we will be working on an actual hello.py . Thanks @thisiscoding1234


Why safety matters

I found this article quite relevant to the extendr project:
https://developer.r-project.org/Blog/public/2019/03/28/use-of-c-in-packages/index.html
It would be great if someone could explain how the extendr project can solve the problems of interfacing R with C++ mentioned in this article.

Considering that both resource and error management in Rust is entirely different from C++, I don't see how it's useful to go through the specific problems that C++ creates. I believe we're aware of all the issues the blog post raises and we're working through them in developing the extendr api.
You're welcome to review the extendr code and point out specific issues that you see. Though honestly, apart from #27, I think we're in pretty good shape.

Considering that both resource and error management in Rust is entirely different from C++, I don't see how it's useful to go through the specific problems that C++ creates. I believe we're aware of all the issues the blog post raises and we're working through them in developing the extendr api.
You're welcome to review the extendr code and point out specific issues that you see. Though honestly, apart from #27, I think we're in pretty good shape.


feat: add axone chain

Add Axone chain to build heighliner images.
Thx 🙏

Hi, any chance you were able to test it locally?
Did it need a Dockerfile change.
At the moment I see this while testing.
~ $ axoned version
/bin/sh: axoned: not found
~ $
~ $ which axoned
/bin/axoned
~ $ ls -la /bin/axoned
-rwxr-xr-x    1 root     0        150505944 Dec 17 06:04 /bin/axoned
~ $ echo $PATH
/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

@vimystic you’re  right. I had checked that the binary was produced but didn’t actually run it. Turns out it was incorrect. My bad.
I’ve fixed this in version v11.0.1, and it should be working fine now.
$ heighliner build --chain axone --git-ref v11.0.1
...
Step 14/58 : RUN git clone ...
Cloning into 'axoned'...
...
+ sh -c 'make install'
 🚚 Installing project axoned
...
(a few moments later)
...
Successfully tagged axone:v11.0.1

$ docker run -it --rm --entrypoint sh axone:v11.0.1
~ $ axoned version
11.0.1

Thx 🙏

Thank you @ccamel.
I can confirm too.
merging now.
Excited to see what Axone chain does :)
Good luck!

@vimystic done.


avoid second execution of parseSQLToPhysicalPlan in executeStatement

by adding a private executeQueryStatement(String statement, PhysicalPlan plan)

This idea is borrowed from executeUpdateStatement:
public TSExecuteStatementResp executeUpdateStatement(TSExecuteStatementReq req)
private TSExecuteStatementResp executeUpdateStatement(String statement)
private TSExecuteStatementResp executeUpdateStatement(PhysicalPlan plan)

I need rebase and merge. Thx.


Update to allow for new entry not to be added to the data source

Change:
New setting 'confirm.resolve.skipAdd'=true will skip adding the new entry to the data source. Added to allow for better integration with rxjs and ngrx.
Short summary of issue:
The function event.confirm.resolve() does two separate things at the moment:

disable UI controls
add the new entry to the table.

This pull request allows the event.confirm.resolve() to only (1) modify the UI controls, and not (2) add the new entry to the data source by setting the new parameter 'skipAdd' to true.
The problem this new feature solves is further described in Issue #273.

duplicate of https://github.com/akveo/ng2-smart-table/pull/280


chore: RCTConvert - allocate array with capacity

Summary
this is a trivial change that allocates the NSMutableArray with the correct capacity before it is filled
Changelog

[Internal] [Changed] - RCTConvertVecToArray - allocate array with capacity
Test Plan
tested locally: the code builds and runs as expected

tested locally: the code builds and runs as expected

Doesn't look like its building :) - double check your syntax. I believe you have an extra [ in there.

lol, since it was just a one-liner I didn't bother to create a branch and push from it locally, and just copy-pasted in the GH ui... well, now it's fixed. Thanks 👍


Review positions: precipitation

positions: precipitation indicates the precipitation with an integer code:
https://github.com/ices-tools-dev/esas/blob/0d294b4ea678e34f52409a16602f9133ac179dcf/_data/table-schemas/positions.yaml#L223-L228

[x] @ices-tools-dev/data-and-information Does ICES already have a controlled vocabulary for this? no
[x] @nicolasvanermen Wouldn't human readable values like rain, fog be better, or are the integer codes well established?

Yes, OK to use human-readable values here.
Nicolas Vanermen
Wetenschappelijk medewerker
Instituut voor Natuur- en Bosonderzoek
Havenlaan 88, bus 73, 1000 Brussel
0486/361.582
On Wed, Jan 6, 2021 at 12:52 PM Peter Desmet<EMAIL_ADDRESS>wrote:

position: precipitation indicates the precipitation with an integer code:
https://github.com/ices-tools-dev/esas/blob/0d294b4ea678e34f52409a16602f9133ac179dcf/_data/table-schemas/positions.yaml#L223-L228

@ices-tools-dev/data-and-information
https://github.com/orgs/ices-tools-dev/teams/data-and-information
Does ICES already have a controlled vocabulary for this?
@nicolasvanermen https://github.com/nicolasvanermen Wouldn't human
readable values like rain, fog be better, or are the integer codes
well established?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ices-tools-dev/esas/issues/29, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYKGXOVZCR3Y2EGUGJF3NTSYRFHJANCNFSM4VXNXB3A
.

Yes, OK to use human-readable values here.
Nicolas Vanermen
Wetenschappelijk medewerker
Instituut voor Natuur- en Bosonderzoek
Havenlaan 88, bus 73, 1000 Brussel
0486/361.582
On Wed, Jan 6, 2021 at 12:52 PM Peter Desmet<EMAIL_ADDRESS>wrote:

position: precipitation indicates the precipitation with an integer code:
https://github.com/ices-tools-dev/esas/blob/0d294b4ea678e34f52409a16602f9133ac179dcf/_data/table-schemas/positions.yaml#L223-L228

@ices-tools-dev/data-and-information
https://github.com/orgs/ices-tools-dev/teams/data-and-information
Does ICES already have a controlled vocabulary for this?
@nicolasvanermen https://github.com/nicolasvanermen Wouldn't human
readable values like rain, fog be better, or are the integer codes
well established?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ices-tools-dev/esas/issues/29, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYKGXOVZCR3Y2EGUGJF3NTSYRFHJANCNFSM4VXNXB3A
.

need new vocab
Personally, i have doubts about usefulness of this field and the 'glare' in any future assessments/estimates.
It seems like 'visibility' alone would have been more useful

need new vocab
Personally, i have doubts about usefulness of this field and the 'glare' in any future assessments/estimates.
It seems like 'visibility' alone would have been more useful

Update in db80fc2 to use human-readable values.

Implemented: positions have a Precipitation field.


Not able to perform browser action on input field using proximity selectors

Expected behavior
Should be focused on the text field which is below the label "First name:"
Actual behavior
✘ Error: Input Field Below First name: not found, run .trace for more info.
Steps to reproduce

openBrowser()
goto("https://www.w3schools.com/html/tryit.asp?filename=tryhtml_form_submit")
focus(inputField(below('First name:')))
Note:
The above steps works fine with the below html code snippet
html snippet:

<!DOCTYPE html>

HTML Forms

<form action="/action_page.php">
  First name:

  <input type="text" name="firstname" value="Mickey">

  Last name:

  <input type="text" name="lastname" value="Mouse">

  <input type="submit" value="Submit">
</form>

If you click the "Submit" button, the form-data will be sent to a page called "/action_page.php".

Versions
commit: d9e89e2
Version: 0.8.0 (Chromium: 74.0.3723.0)

Fix available in f6e741f

This issue has been verified and found fixed with the commit version a622aa5c84bc8544ef3e3028ae73afcb55a96b1b


chore(ci): changes for oclif-v2

Proposed changes

Fixed deployment config (not having a Snyk Code section is making it angry, and we ditched Veracode)
Shifted from an exclusive to an inclusive listing for packages, macos builds were being painful by copying a whole npm arborescence somewhere in the project during its build process, creating duplicates among the packages.
Tweaked the release scripts for 'normal operation with Oclif v2'. That doesn't replace the funkeries that need to be manually done for the smooth transition from Oclif v1 to Oclif v2.

Testing
https://github.com/coveo/cli-v2-temp.
I did 2 releases on the dev environment:

1.25.5 which is the 'transition' one, so Oclif v2 but compat Oclif v1.
1.25.6, a vanilla Oclif v2

I ensured that 1.25.4 and 1.25.5 were able to reach 1.25.6 when running coveo update once or twice.

Snyk will fail because we don't run a scan on every branches, but is ok, will run on the CDX-746


Showing position null after match update

As u can see in round 2 , semi 1 infront of Team 2 there is #null why ?

I think it's because in the viewer, I show the position when the position is different than undefined. I don't check for null value, so it showed it.
I need to check why there is a null value in this opponent's position...
Can you show the different updates you did?

Well I modified some things.Actually  I want to put  object in seeding. Like
seeding: [{
      id: 'some id',
      name: 'some name'
   }]

And also idk typescript .
Please can u tell me how brackets works in 'single_elimination' ?

Well I modified some things. Actually I want to put object in seeding.

Do you really need to set ids? There are automatically added in the storage when you add them (kind of if you were using AUTO_INCREMENT in SQL).

Please can you tell me how brackets works in 'single_elimination' ?

It's the easiest for of bracket elimination.
Basically, you have a seeding at start, in round 1. Teams are ordered in inner_outer way by default. Which means: 1v16, 8v9, etc. (you can see the tests if you want).
After that, each loser of a match is disqualified, whereas the winners are moved into the next match, etc.
And you reach the final like this.
You optionally have a consolation final, which matches the semi final losers.
Was it your question?

Bit of code would help me

The current code doesn't updates the next match .😬

And I was using mongoose.
The only way to convert it to that was modifying node-json-db xD.

Do you want to contact me on discord? I could help you here

Yea sure

Here is my discord account: Drarig29#6746

Sent u a friend request

Result of the exchange: I will add more documentation on how the library works later.


extend lua by register extensions

advoid old lua register pullute the global environment

thanks, looks good to me, once ci check passed, I  will merge this excellent pr

with this pr, wen can use lua extension as follow:
local yasio = require 'yasio'
local cjson = require 'cjson'


Update for MSAL 3.x

Unfortunately, this sample is outdated and cannot be easily built after upgrading the referenced nuget packages. Are there any plans on updating this to the new version?

MSAL 3.x introduces breaking changes, so for this sample as-is you need to stay at 2.7.x. It is in our backlog to update this to 3.x.

Thanks for the clarification. Any timeline to share?

Nothing concrete. I'd like to get all of our "training" samples updated to 3.x soon though, so hopefully in the next 2-3 weeks.

@sebfrie I'm investigating this now and considering upgrading the project to a clean project created with VS 2019. What version of Visual Studio are you using?

I'm using VS 2019 (updated today to 16.1.0). I really appreciate your work and am looking forward to the updated tutorial.

Let me know if you have any trouble with this updated version. Happy coding!


golang-google-cicd to 0.0.22

Promote golang-google-cicd to version 0.0.22

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


TypeError: Object.fromEntries is not a function

OS: Windows
Node: 10.16.3
After running npx export-size uuid, throw a error called TypeError: Object.fromEntries is not a function

it is working after upgrading esbuild to v0.7.21.

Deps updated. Thanks.


Setup configuration to pull Google Maps API key

Use the instructions at the opencage enrichments page along witht the source code copied from that project as the starting point for implmenting API key retrieval from a local yaml configuration file.
Here's a screen shot of the instructions as of today

Looking at them, this may be fairly simple. I have an enviornment variable set already: $MAPS_API_KEY
It looks like I'll need a four line addition to my configuration file I'm already using, and then to change the name of the environment variable everywhere it's mentioend in the code.

Forgot you have to refresh the query page after refreshing, but after that, this worked like a champ. Pushing the associated yml file in the rm_rnb_history project now.


LazilyRequire broccoli plugin

addon mains must load quickly

[Current coverage][cc-pull] is 96.07% (diff: 100%)

Merging [#100][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #100   diff @@
==========================================
  Files             3          3
  Lines           153        153
  Methods          15         15
  Messages          0          0
  Branches         36         36
==========================================
  Hits            147        147
  Misses            6          6
  Partials          0          0

Powered by Codecov. Last update [328ae11...c85680c][cc-compare]
[cc-base-branch]: https://codecov.io/gh/rickharrison/broccoli-asset-rev/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/rickharrison/broccoli-asset-rev/compare/328ae11a31659690388c101c4b0ed9e8d9045abe...c85680c3a53eb7f88cfe7a10784a1af94316a056?src=pr
[cc-pull]: https://codecov.io/gh/rickharrison/broccoli-asset-rev/pull/100?src=pr

published as 2.4.5


Interpolation warnigns have been introduced in main.tf

Lines 192, 205, and 214 of main.tf are all using the deprecated interpolation syntax.

Fixed with the latest release, thanks for your help.

Thank you for the prompt response and resolution!


[www] add map scale

https://user-images.githubusercontent.com/217057/224865377-336aa39b-ba12-4af3-a191-29aaba50e03d.mp4
There wasn't quite enough room for the attribution and the map scale on some mobile devices, so on mobile, I've bumped the scale up to the same line as the "geolocate" button.

You can tap the map scale to swap units, and it'll remember it for next time.
I'm a little worried that on mobile this tap target will be too close to the geolocate button, but let's try it out.
Speaking of worries, I'm not sure about the debounce. The delay between zooming and seeing the scale update feels strange, but I felt a shorter delay still felt choppy. At least now it feels a little more explicable - you finish panning/zooming and then it updates. Having no debounce at all is an option, but it seems like it could be problematic on older devices.

In the end the choppiness irritated me too much, so I got rid of the debounce. It's not free though - it's possible we'll want to revisit this, especially if it slows down panning / zooming for some clients.
Maybe we could do something clever like have the debounce related to the level of zoom — if someone is panning around at global scale, the bar can change quickly, and we'd want to do the calculation more often than someone panning around their neighborhood where the scale is unlikely to quickly change.


Update Remote API support to v1.16

Update API version to 1.16
Add Docker::Exec#json
Add exitstatus to array returned by Docker::Exec#start
Add check for new Docker#info parameters
Remove Docker::Exec#resize tests because they were not working reliably.

@tlunter fixed your note about documentation and rebased on the latest master.

Looks like we're still running into an error on travis. Any ideas?

Looks like the errors are occurring because of the latest PR. I'm currently trying to work through the solution.

+1 I was looking for the exec ExitCode too.
In exec by just returning an array it is getting limited, only ExitCode is returned from all the data docker exposes in inspect, and it doesn't return the ordered output (with both stdout and stderr)
Should it return a hash with all the data? it would be a breaking change though

Release in v1.19.0


Simulator::addObject should add to the active scene graph

Motivation and Context
In response to issue #283.
Simulator::addObject takes a sceneID parameter for multi-scene use case. Since we don't support multi-scene physics presently, this should always add to the active scene graph instead.
This will need to be changed back in the future as we support multi-scene simulation.
How Has This Been Tested
Local testing with multiple sim.reconfigure() to create several sceneIDs in the Simulator.
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

IMO, it would make more sense to just set the default value of sceneID to activeSceneID_.

IMO, it would make more sense to just set the default value of sceneID to activeSceneID_.

Good thought, but there are multiple levels of default value = 0 as the function is passed through python bindings and into the simulator.py.


audit: only check undeclared deps for standard installations.

In fact, we don't really care about undeclared dependencies for optional
installations. Because, this is mainly used to help us to detect breakage
for bottles so we can do a revision bump.
cc @DomT4

This does cut out a lot of the false positives, which is a 👍 for reducing user confusion & me spending less time repeatedly explaining this particular edge case. I remain unconvinced this particular :linked check is really a net gain for us at this point, but this at least eases off one edge case.

I remain unconvinced this particular :linked check is really a net gain for us at this point

It is important to have it so we can avoid missing formulae whenever there is a version bump.

It is important to have it so we can avoid missing formulae whenever there is a version bump.

@xu-cheng In which case: you should be helping explain this to contributors who are struggling with this in homebrew/core.


Preflight EKF error checking is linked to GPS

If bad IMU data causes the EKF error checks here to fail here:
https://github.com/PX4/Firmware/blob/master/src/modules/commander/PreflightCheck.cpp#L690-L698 ,
then the failure to arm could be interpreted by the user as a GPS error. If the user then decides to fly without GPS, they will set COM_ARM_WO_GPS =1 to bypass the check and be unaware that there is a problem with the IMU. This can lead to a loss of height, position and possibly attitude control.
Work Required

Check error reporting messages for the EKF checks and rectify if misleading.
Add a unique circuit breaker for the EKF checks
Update documentation to reflect the changes

Fixes will be pushed here: https://github.com/priseborough/Firmware/tree/pr-ekfPreFltCheck