Occasional Mesa error that breaks graphical acceleration

Describe the bug
When dealing with more than one checkout of nixpkgs (ex: a unstable + master)  sometimes one may find an error like the following:
DRI drivber not from this Mesa build ('24.0.3' vs '24.0.5')
failed to bind extensions

That seems to happen when there is a Mesa bump in between your system current nixpkgs commit and the nixpkgs commit of a checkout one is working on.
Steps To Reproduce
Steps to reproduce the behavior:

Have graphical app
Have your system in a somewhat older nixpkgs revision
Run the graphical program built in a newer nixpkgs version
You may reproduce this issue

Expected behavior
All programs should at first try to use the system Mesa through /run/opengl-driver/lib for example and if it's not available then use their own, or just crash with a friendly error.
Screenshots
Example inside of Durden that Xarcan is having this exact issue

Additional context
Add any other context about the problem here.
Notify maintainers
@primeos @vcunat

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

Add a :+1: reaction to issues you find important.

Whoa, I found a workaround
At least Xarcan, in my case, only used libgbm.so from pkgs.mesa, so solving the issue is a matter of adding ${pkgs.mesa}/lib/libgbm.so to LD_PRELOAD. That way the error is gone.

There are lots of open discussion threads around similar problems.  You can also run e.g. into glibc mismatch between your SW and mesa drivers.  So far the only reliable recommendation I know is not to combine different versions for these graphical apps (i.e. match nixpkgs commit for your booted NixOS and the app, or at least not too far like stable+unstable).

There are lots of open discussion threads around similar problems. You can also run e.g. into glibc mismatch between your SW and mesa drivers. So far the only reliable recommendation I know is not to combine different versions for these graphical apps (i.e. match nixpkgs commit for your booted NixOS and the app, or at least not too far like stable+unstable).

Often this isn't a option. LD_PRELOAD seems to be working well when stuff like this are an issue.

I believe it doesn't always work.


fix evaluate_and of ComparisonPredicateBase has logical error

Proposed changes
Issue Number: close #xxx
Problem summary
evaluate_and of ComparisonPredicateBase has logical error. When flag is true, we should evaluate new predicator, and continue the loop if flag is false.
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[x] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[x] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 38.66 seconds
load time: 585 seconds
storage size:<PHONE_NUMBER>0 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20221102074410_clickbench_pr_38063.html


Can't use retweet twitter API from node.js - error code 34

Hello,
I'm trying to figure out of a simple node.js script to retweet using Twitter API. I was able to create favorites, post status, but a simple retweet is not working.
// rt.js
var Twitter = require('twitter');
var config = require('./config.js');
var T = new Twitter(config);

T.post('statuses/retweet/:id', {
  id: '870436914322472960'
}, (err, data, response) => {
  if (err) {
    console.log(err)
  } else {
    console.log(`${data.text} retweet success!`)
  }
})

The error message is :
[ { message: 'Sorry, that page does not exist', code: 34 } ]

I'm using<EMAIL_ADDRESS>(from npm list)
Thanks for your help.

Hello,
I was also faced with this error. It occurs because node-twitter don't implement parameters in path.
I release an update with this feature on my forked repo.
In order to use it, you'll have to uninstall node-twitter :
npm uninstall twitter
Then install the github version :
npm install git+https://github.com/JulienSol/node-twitter.git#update
Finally, you'll be able to retweet anything 🙂

@JulienSol
Strange, my id is passed with the following variable, don't nike to hardcode it.
But whatever, i've tried your code sample, with two different id :
[ { code: 144, message: 'No status found with that ID.' } ]

Ah ! Yes, you have to convert id to string :
T.post('statuses/retweet/' + '870436914322472960', (err, data, response) => {
    if (err) {
        console.log(err)
    } else {
        console.log(`${data.text} retweet success!`)
    }
});

@JulienSol It's working, thanks


Updated overlay modal demo to just use overlay modal

The overlay modal demo was actually using a modal confirm which had a overlay modal within it. Demo now shows overlay modal in isolation.

It's literal, but it works.


Dynamic whitelist of intrinsics

This issue tracks the code changes needed to facilitate dynamic changes to the whitelist of intrinsics against which WebAssembly code in eosio::setcode actions are allowed to link.
Background
Currently, nodeos is configured with a static set of intrinsics that it recognizes and has an implementation for. This set of intrinsics can be called the "recognized intrinsics set".
The protocol maintains a set of intrinsics against which a WebAssembly contract is allowed to link. If a contract was set at a time when linking to a particular intrinsic was allowed, it is not appropriate to suddenly take away the ability to link to the intrinsic. In particular, it would break consensus if attempted naively, since when a contract is used for the first time after a restart of nodeos, its WebAssembly code must be instantiated and cached on that node which involves linking to the intrinsics.
However, it is perfectly acceptable to disallow any new contract or updates to an existing contract to link against certain intrinsics that are to no longer be supported. The appropriate place to check the linking to enable this kind of behavior is during a eosio::setcode action. One can think of a subset of the "recognized intrinsics set" called the "whitelisted intrinsics set" which is the set of intrinsics against which WebAssembly code in a eosio::setcode action is allowed to link.
The "whitelisted intrinsics set" is allowed to change over time (or over blocks), which includes both additions and removals to the set, without any consensus problems as long as the changes are deterministically derived from the block data. It should also at all times remain a subset of the "recognized intrinsics set".
Currently, nodeos does not support a dynamic "whitelisted intrinsics set". One can think of the current behavior as if an implicit "whitelisted intrinsics set" exists that remains equivalent to the "recognized intrinsics set".
Changes to the state database
To maintain a deterministically changed "whitelisted intrinsics set", that set must exist inside of the chain state. This requires either adding a new index into the ChainBase state database specifically for this set, or adding the set as a field to an existing global object in the state database, e.g. the global_property_object. Either way, this change will require a new chain_snapshot_header version (e.g. version 2).
Furthermore, in order to simplify implementation of the code, it will be best if the "whitelisted intrinsics set" is initialized at genesis to the original "recognized intrinsics set" prior to any additional intrinsics that may be added via consensus protocol upgrades. Then consensus protocol upgrade features can simply add new intrinsics by inserting the name of the new intrinsic into the "whitelisted intrinsics set" during the execution of the protocol feature's trigger function (see #6429 for details). However, this approach means that a replay from genesis is required to support the code changes tracked by this issue.
Changes to eosio::chain::webassembly::common::root_resolver:
Default constructor continues to set validating to false.
Another constructor that takes a const reference to a set of intrinsic name strings would set validating to true and keep a pointer to the set. The set to be passed in would need to be comprised of the names of the intrinsics in the current "whitelisted intrinsics set".
In the resolve method, if validating == true, it would check that the export_name is in the set before calling Runtime::IntrinsicResolver::singleton.resolve.
Changes to eosio::chain::wasm_interface::validate:
The line containing root_resolver resolver(true); should be modified to instead pass in the "whitelisted intrinsics set" (or at least the appropriate form of it).

I guess this can be done without the change to chainbase database structure. we can use the generic contract's multi_index table to maintain this dynamic list. for example:
[[eosio::table]] struct newfuncs {
  uint64_t index; // unique for each intrinsics
  string signature; // the string used to link with WebAssembly.
};

This table should be created under "eosio" in such a way that it needs 2/3 of BP to modify it. In the beginning of each block we can go through this multi_index table then put all new intrinsic functions into std::map or some cache for fast validation.
because of all multi_index table use the same int64 index in chainbase this doesn't require any structure change to chainbase.

@arhag in the Background section the second paragraph, last sentence does not make sense and needs to be corrected (“In particular, it would break consensus if attempted naively, since after a restart of nodeos when a contract is first time a contract used its WebAssembly code must be instantiated and cached which involves linking to the intrinsics.”).

@taokayan:
Since these are core EOSIO features, I don't think the data structures needed to track these changes should belong in the contract tables. A contract, even a privileged one, should not be able to modify this data directly; changes should only be done through the privileged intrinsics that guarantee certain invariants.
@gleehokie:
Thanks. I fixed it.

Resolved by #6831.


Moved Transaction into function newTransaction

Not gonna lie I thought the same, its not actually helping, but thought just moving the string manipulation to a function wasn't making much a difference either @aasseman

Not gonna lie I thought the same, its not actually helping, but thought just moving the string manipulation to a function wasn't making much a difference either @aasseman, so decided to move more to make more sense of having a function but now it looks like it was better before too

OK, perhaps let's close this one then?

Closing this, not really necessary


Update repo and bump proto version

Two main changes here:

Updates this repo to capture changes made in the original repo, effectively syncing the fork.

Note: proto still on syntax 2 (as per README), with versions:

protoc-gen-go v1.34.2 ~> v1.35.1
protoc        v4.25.3 ~> v5.28.3

Update to go1.22, which is required for certain updated deps. This change is needed regardless of this update, to effectively catch up to all other services. There is a potential option here to update further to 1.23, as there is 1 dep which requires it goquery~v1.10, but is bumped down to 1.5 due to the usage of 1.22 over 1.23. I've left for now - this is a different kettle of fish.

Looks good.
The only minor inconvenience is that re-introducing example_test.go adds a direct dependency on aws-sdk-go-v2/config, which adds a load of indirect dependencies that won't actually be part of the runtime of the library. But anything that imports this will have its own dependence on the config module, so probably all good.

Yeah good point. Let's go with it added for now. If the downstream services kick up a fuss when building them, we can revisit this.


Add Maplin Remote Controlled Mains Switches

@bennuttall @waveform80 @lurch
I am writing a class to control the following remote control sockets from Maplin:
https://www.maplin.co.uk/p/remote-controlled-mains-socket-set-single-n78ka
They need a 433MHz transmitter to operate them.  You can buy these cheaply from eBay:
https://www.ebay.co.uk/itm/433MHz-RF-Transmitter-and-Receiver-Pair-for-Pi-Arduino-ASK-OOK-Remote-Wireless/181863740559
This is somewhat similar to the Energenie socket but you can put the 433MHz transmitter on any GPIO pin you choose and you could have multiple 433MHz transmitters  (to make it more generic, let’s call them OOKTX as the radio frequency is a function of the transmitter, not gpiozero).
I have fully working code but it’s not currently OOP. I’m thinking of the following:
OOK extends OutputDevice and represents an On Off Key (OOK) transmitter.
class OOK(OutputDevice):
    def __init__(self, pin=None, active_high=True, initial_value=False, pulse_width=1, bursts=1, burst_delay=1, pin_factory=None):

RadioSocket extends ??Device??  and represents a remote controlled mains socket.
class RadioSocket(Device):
    def __init__(self, pin=None, socket=None, active_high=True, initial_value=False):

Methods for the RadioSocket would be the same as the Energenie sockets but in this case, there are 16 sockets.

Sounds great!

I will probably have the following (publicly accessible) classes:
OOK (extends SharedMixin, OutputDevice)
RemoteSocket (extends Device) - so that other types of remote sockets can have classes
MaplinRemoteSocket (extends RemoteSocket) - one type of many 433Mhz OOK radio controlled sockets

Are these sold anywhere else now Maplin is gone?

These look to be the same https://www.amazon.co.uk/gp/product/B0053XRZ9I

Let's see if Maplin online sell them :-)


One test stub created when wildcard * used to specify all proto files

protoc -I ./Protocols --lile-server_out=. --go_out=plugins=grpc:. .Protos/*.proto ;\
This generates only one test stub for the first file under /Protos. Expected output is creating as many stubs as number of files under /Protos

Removing -I and then using * works

This is because of difference in behavior in bash/cmd. Above works fine in bash. But for cmd something like should work:
for %i in (./Protocols/*.proto) do protoc -I ./Protos --lile-server_out=. --go_out=plugins=grpc:. ./Protos/%i


Fragment on  not working

When I am using a fragment which implements on an interface, the query doesn't get generated with that part
interface IUser {
    id: ID!
}

type User implements IUser {
    id: ID!
}

type Location {
    id: ID!

    users: [User!]!
}

type Query {
    locations: [Location!]!
}

fragment UserSummary on IUser {
    id
}

fragment LocationWithUsers on Location {
    id
    users {
        ...UserSummary
    }
}

query GetLocations {
    locations {
        ...LocationWithUsers
    }
}

Thanks for reporting this. I haven't been able to reproduce your issue (please take a look at the referenced PR). You do seem to have an error in your fragment as well:
fragment PersonSummary on IPerson {
  id: ID!
}

should probably be
fragment PersonSummary on IPerson {
  id
}

Some information that might be useful to help me help you is:

What version of graphql_codegen are you using?
Examples of generated code
Potential build errors.

Sorry, the schema I proved works. It happens when I am using nested fragments.
interface IUser {
    id: ID!
}

type User implements IUser {
    id: ID!
}

type Location {
    id: ID!

    users: [User!]!
}

type Query {
    locations: [Location!]!
}

fragment UserSummary on IUser {
    id
}

fragment LocationWithUsers on Location {
    id
    users {
        ...UserSummary
    }
}

query GetLocations {
    locations {
        ...LocationWithUsers
    }
}

I have a feeling this comment could be the issue https://github.com/zino-hofmann/graphql-flutter/issues/994#issuecomment-1059139588

So is this a problem with the data  not being sent to/from your server on runtime, or the built serialisers?

The query that gets sent to the server doesn't contain the required information like users.id

This library shouldn’t be manipulating your queries, can you elaborate a
bit on what you mean by

query that gets sent to the server doesn't contain the required
information

On Tue, 9 Aug 2022 at 16:22, Sander Jochems @.***>
wrote:

The query that gets sent to the server doesn't contain the required
information like users.id
—
Reply to this email directly, view it on GitHub
https://github.com/heftapp/graphql_codegen/issues/158#issuecomment-1209448858,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA2UFSZESTT64FI7UHYOYIDVYJSTHANCNFSM556QSKAQ
.
You are receiving this because you commented.Message ID:
@.***>

The query that should get sent to the server is
query GetLocations {
    locations {
      __typename
      users {
        __typename
        id
      }
    }
}

But the query that is sent is
query GetLocations {
    locations {
      __typename
      users {
        __typename
      }
    }
}

Cheers. The library does no such changes to queries.
Please make sure you've rebuild your serialisers. If this doesn't work please share the generated file + the original query + an example on how you're calling the query.

I'm going to close this issue for now. Let's revisit if you have more information.


feat(config): add the previewFeatures option

Closes #112
This PR implements the previewFeatures option.

This idea looks unnecessary complex. It should be enough having a note in the docs (also in the release notes) and a TSDoc remark in the code: https://github.com/tstyche/tstyche/pull/237/commits/592dcdb7953e0ec3b4b1bc76d0c690f68db15230


Add Portal steps

Diagnostic logs can be configured from Azure Automation accounts in the Azure portal now. Please add those steps to this doc, in the current state it seems to imply that you can only set them with PowerShell.

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

ID: a52eb74e-6880-eb97-8cfd-c7c88feb64d7
Version Independent ID: 612bb48d-0b43-1dbf-9053-14e55edb5095
Content: Forward Azure Automation job data to Azure Monitor logs
Content Source: articles/automation/automation-manage-send-joblogs-log-analytics.md
Service: automation
Sub-service: process-automation
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@dcbrown16  Thank you for your feedback, our team will look into it and get back to you at the earliest.

@dcbrown16 - Thanks for raising this.  This is a recent change to Azure RPs and I'll be updating/rewriting this article in our next sprint, because it also includes storage accounts and sending via Event Hub.  #please-close


Inconsistency between tag and version

Hi,
You have inconsistency between tag in Git (latest 2.4.0) and version of NPM module in package.json (latest 2.5.0).
Thanks,
Anatoli

@lexxanatoli  Thanks for pointing that out, forgot to push the tag, now done 👍


Cluster Provisioning stuck on vSphere - [[controlplane] Error getting node test1: "test1" not found]]

Describe your issue here
The deployment of a Rancher on an all-in-one node on vCenter 6.5 is failing. I'm getting this error message on the Rancher UI:
[controlPlane] Failed to upgrade Control Plane: [[[controlplane] Error getting node test1: "test1" not found]]

I can see that the Rancher containers are up on the node:
docker@test1:~$ docker ps
CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS              PORTS               NAMES
656f97b99279        rancher/hyperkube:v1.18.8-rancher1    "/opt/rke-tools/entr…"   42 minutes ago      Up 42 minutes                           kube-scheduler
c10b92aff9b9        rancher/hyperkube:v1.18.8-rancher1    "/opt/rke-tools/entr…"   42 minutes ago      Up 42 minutes                           kube-controller-manager
fd23b070a466        rancher/hyperkube:v1.18.8-rancher1    "/opt/rke-tools/entr…"   43 minutes ago      Up 43 minutes                           kube-apiserver
cc1fc36e7389        rancher/coreos-etcd:v3.4.3-rancher1   "/usr/local/bin/etcd…"   43 minutes ago      Up 43 minutes                           etcd
b26ea18f7c79        rancher/rancher-agent:v2.4.8          "run.sh --server htt…"   45 minutes ago      Up 45 minutes                           quirky_cori

Here an extract of the ERROR message on the Rancher Server
2020/09/17 08:48:48 [ERROR] Cluster c-bt57q previously failed to create
I0917 08:48:53.933661       6 http.go:122] HTTP2 has been explicitly disabled
E0917 08:49:27.130548      39 watcher.go:214] watch chan error: etcdserver: mvcc: required revision has been compacted
2020/09/17 08:49:27 [ERROR] Failed to upgrade worker components on NotReady hosts, error: [Failed to start [kubelet] container on host [<IP_ADDRESS>]: Error response from daemon: path /var/lib/rancher is mounted on / but it is not a shared mount]
2020/09/17 08:49:52 [ERROR] Host test1 failed to report Ready status with error: [controlplane] Error getting node test1:  "test1" not found
2020-09-17 08:52:17.001276 I | mvcc: store.index: compact 246195
2020/09/17 08:50:17 [ERROR] Failed to upgrade hosts: test1 with error [[controlplane] Error getting node test1:  "test1" not found]
2020-09-17 08:52:17.028182 I | mvcc: finished scheduled compaction at 246195 (took 25.784259ms)
2020/09/17 08:50:17 [ERROR] cluster [c-bt57q] provisioning: [controlPlane] Failed to upgrade Control Plane: [[[controlplane] Error getting node test1:  "test1" not found]]
2020/09/17 08:50:17 [ERROR] ClusterController c-bt57q [cluster-provisioner-controller] failed with : [controlPlane] Failed to upgrade Control Plane: [[[controlplane] Error getting node test1:  "test1" not found]]

Thank you for your help!

Useful
Info

Versions
Rancher v2.4.8 UI: v2.4.34

Route
undefined

vCenter
6.5

Kubernetes
v1.18-rancher1-1

Network Provider
flannel

Node template
boot2docker Latest rancher-vmware image

Hello. Have your problem solved ?
I have the same issue

Hello. Have your problem solved ?
I have the same issue


Add support for id as Number in table rows

vue.runtime.esm.js?2b0e:619 [Vue warn]: Invalid prop: type check failed for prop "id". Expected String with value "1", got Number with value 1.
found in
--->
When using id as a field in the table rows, the above error is thrown to the console. In my model ID is a Number, but it seems that the plugin is using the id field for other things rather than just displaying it as a normal column.

@cabassi I don't think I will implement this. But I just finished rewriting the entire library as Blitzar!
See #16
feel free to open new issues over there

@cabassi I don't think I will implement this. But I just finished rewriting the entire library as Blitzar!
See #16
feel free to open new issues over there


Update AppServiceProvider.php

Modified AppServiceProviders to include a default string length for when database migration is needed. This is to help deal with errors if specified key is too long.

@Tahir-K
Thanks for PR,
Please notice that we didn't start programming yet,
we only started API spec sheet design,
I'll keep this PR for later


PUB on http, SUB on mqtt

BUG REPORT

What were you trying to achieve?
Test the multiprotocol broker, publish on http and subscribe on mqtt

What are the expected results?
The message should be available on mqtt.

What are the received results?
Did not receive the message on mqtt after publishing on HTTP.

What are the steps to reproduce the issue?
Follow the getting started guide, on docker, subscribe to mqtt with the following:

mosquitto_sub -d -v -h x.x.x.x -u 2572a806-d504-11e7-9c5d-0242ac110004 -P eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE1MTE5NTk5NDQsImlzcyI6Im1haW5mbHV4Iiwic3ViIjoiMjU3MmE4MDYtZDUwNC0xMWU3LTljNWQtMDI0MmFjMTEwMDA0In0.poMiDvG6duO7EvPzE38MFm2Emv0n18T2z8ayiUDfMJA -t mainflux/channels/49f06660-d504-11e7-9c5e-0242ac110004/messages/senml-json

Publish with:
curl -s -S -i -X POST -H "Content-Type: application/senml+json" -H "Authorization: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE1MTE5NTk5MDIsImlzcyI6Im1haW5mbHV4Iiwic3ViIjoiMGM1MmMzNzUtZDUwNC0xMWU3LTljNWMtMDI0MmFjMTEwMDA0In0.gDDBndpG_UmrZk_5AoQyWcyL_LdylpqZpkRJuezHWH0" x.x.x.x:7070/channels/49f06660-d504-11e7-9c5e-0242ac110004/messages -d '[{"bn":"some-base-name:","bt":1.276020076001e+09, "bu":"A","bver":5, "n":"voltage","u":"V","v":120.1}, {"n":"current","t":-5,"v":1.2}, {"n":"current","t":-4,"v":6.0}]'

In what environment did you encounter the issue?
Docker on ubuntu server

@hendrikdm thanks for submitting the issue, we're on it.

@mijicd I am getting in mqtt-adapter:
{ channel: 'e8ca2f5c-d897-11e7-a234-9cb6d0e58817',
  publisher: 'eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOjE1MTIzNTMxMjMsImlzcyI6Im1haW5mbHV4Iiwic3ViIjoiOTY4OGZlNDEtZDg5Ny0xMWU3LWEyMzMtOWNiNmQwZTU4ODE3In0.PERptP7w0adleb24ll-QVD02tsKyT3BYD1-lXq3_hBI',
  protocol: 'http',
  content_type: 'application/senml+json',
  payload: 'W3siYm4iOiJzb21lLWJhc2UtbmFtZToiLCJidCI6MS4yNzYwMjAwNzYwMDFlKzA5LCAiYnUiOiJBIiwiYnZlciI6NSwgIm4iOiJ2b2x0YWdlIiwidSI6IlYiLCJ2IjoxMjAuMX0sIHsibiI6ImN1cnJlbnQiLCJ0IjotNSwidiI6MS4yfSwgeyJuIjoiY3VycmVudCIsInQiOi00LCJ2IjoxLjN9XQ==' }

content_type should be parsed and senml-json should be produce out of it, as it is used here: https://github.com/mainflux/mqtt-adapter/blob/master/mqtt.js#L56

Should be fixed by https://github.com/mainflux/mqtt-adapter/commit/4df7bc63b16cb7a31af76a391071aecbf45e9f47

resolved, thank you.


[Bug]: AttributeError: 'dict' object has no attribute 'to_dict'

Is there an existing issue for the same bug?

[X] I have checked the troubleshooting document at https://opendevin.github.io/OpenDevin/modules/usage/troubleshooting
[X] I have checked the existing issues.

Describe the bug
Refresh browser:
12:03:56 - opendevin:INFO: agent_controller.py:190 - Setting agent(CodeActAgent) state from AgentState.LOADING to AgentState.INIT
INFO:     <IP_ADDRESS>:48692 - "GET /api/litellm-models HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:48694 - "GET /api/messages/total HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:48712 - "GET /api/litellm-models HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:48698 - "GET /api/refresh-files HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:49178 - "GET /api/agents HTTP/1.1" 200 OK
INFO:     <IP_ADDRESS>:49192 - "GET /api/agents HTTP/1.1" 200 OK

Prompted with: https://i.imgur.com/H7kaWFe.png
Unfinished Session Detected

You seem to have an unfinished task. Would you like to pick up where you left off or start fresh?

Select "Start New Session":
INFO:     <IP_ADDRESS>:43238 - "DELETE /api/messages HTTP/1.1" 200 OK
12:06:24 - opendevin:INFO: msg_stack.py:95 - Deleting messages...
ERROR:asyncio:Task exception was never retrieved
future: <Task finished name='Task-32' coro=<MessageStack._del_messages() done, defined at /mnt/p/opendevin/opendevin/server/session/msg_stack.py:94> exception=AttributeError("'dict' object has no attribute 'to_dict'")>
Traceback (most recent call last):
  File "/mnt/p/opendevin/opendevin/server/session/msg_stack.py", line 102, in _del_messages
    new_data[sid] = [msg.to_dict() for msg in msgs]
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/mnt/p/opendevin/opendevin/server/session/msg_stack.py", line 102, in <listcomp>
    new_data[sid] = [msg.to_dict() for msg in msgs]
                     ^^^^^^^^^^^
AttributeError: 'dict' object has no attribute 'to_dict'

https://i.imgur.com/Zy8jWRV.png
Current Version
0.5.3

Installation and Configuration
`make run`

Model and Agent
ALL
Reproduction Steps
listed above
Logs, Errors, Screenshots, and Additional Context
No response

Check in incognito mode

That seemed to have worked.
I am running Firefox 125.0.3 (64-bit)

I received the same error again when refreshing the same private browser window and restarting OpenDevin with make run


Updated fetch-csv to use new file structure.

Good PR. Thank you for improving this new connector.


Onboarding Hello Robot - first steps

Description

Onboards Hello Robot's Stretch to enable

teleop from the dashboard
look, turn commands

Renames locobot_mover_utils -> robot_mover_utils and moves it to droidlet/lowlevel/ so that it can be shared by other agents. Same for rotation.py. These need to consolidated later.
Adds an interface for mover (robot_mover.py) to capture the essential mover APIs an agent should implement. This is part of streamlining agent onboarding.
Script changes to download dataset/models

The follow-up work to complete Hello's onboarding is at https://github.com/facebookresearch/droidlet/issues/476.

To launch the hello robot agent, do the following:
On the robot:

Copy droidlet/lowlevel/hello_robot/remote/ to the robot
Run ./launch.sh - this will also check for the battery status of the robot and calibrate the robot if necessary.

On the agent:

export LOCOBOT_IP=<ip of hello robot>
python hello_robot_agent.py

Fixes # (issue)
Type of change
Please check the options that are relevant.

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[x] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[x] I want a thorough review of the implementation.
[x] I want a high level review.
[ ] I want a deep design review.

Testing
Manually.
Checklist:

[x] I have performed manual end-to-end testing of the feature in my environment.
[ ] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[ ] New and existing unit tests pass locally with my changes.
[ ] I have added relevant collaborators to review the PR before merge.

This PR is stale now, a lot of this code is already in main from other PRs.


adds a CI

merging it, I need to trigger after it is merged

It works

Hint: mm: orc; threads: on; opt: none (DEBUG BUILD, -d:release generates faster code)
74781 lines; 2.563s; 143.02MiB peakmem; proj: /home/runner/work/nif/nif/nif/src/nifler/nifler.nim; out: /home/runner/work/nif/nif/nif/src/nifler/nifler [SuccessX]


Change of projet

In mode off multi-project, it's very long to change of projet.
It will be great to display all project with then différent branches ?

You mean show a tree with 2 projects and flow branches for each project?
I was thinking about that approach, but that really complicates a lot of things for me. I would like to avoid it, because for that I need to record the whole extension because the main architecture has to be changed.

I that I mean....
I know that is a big change, but when you work on différent project in a same workspace, you have to change of projet, refresh , ...
It's long ;-)


SameSite Support

Are there any plans to update this to support the SameSite attribute?
https://web.dev/samesite-cookies-explained/

I'd be open to PRs. :)

sameSite support is now included in v1.4.0, thanks to @maciekbb's PR (#54)!


RESTEasyConnector: Support RESTEasy 3.6.3.Final

Avoid extending the ResteasyProviderFactory and using the
related protected methods.
@asoldano
@mwperina
@NicoNes
@ronsigal
Would be very nice, if one of you can have a look at this change.

Verified manually on oVirt 4.3 and oVirt 4.2, and on ovirt-system-tests basic-suite-4.2.

This definitely looks better to me. If it works for you, I'm +1 for the changes.

@asoldano , thank you very much.

network-suite-4.3 is happy, too.


Streaming: No support for retry on connect for now

So need to return NATS_NO_SERVER instead of NATS_NOT_YET_CONNECTED. See #176

To be clear, the PR #179 is not adding support for that, just making sure that the option is properly disabled internally and correct error status is returned in cased on failed connect.
Reason for no support at the moment are documented in #176


FIX: Do not attempt to calculate TA if SliceTiming is degenerate

Fixes #2867.

Codecov Report
Base: 45.24% // Head: 45.83% // Increases project coverage by +0.59% :tada:

Coverage data is based on head (2ff25cb) compared to base (bdcc1d1).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2901      +/-   ##
==========================================
+ Coverage   45.24%   45.83%   +0.59%
==========================================
  Files          43       44       +1
  Lines        3437     3637     +200
==========================================
+ Hits         1555     1667     +112
- Misses       1882     1970      +88

Impacted Files
Coverage Δ

fmriprep/workflows/bold/outputs.py
22.46% <100.00%> (+0.16%)
:arrow_up:

fmriprep/_version.py
42.09% <0.00%> (-2.63%)
:arrow_down:

fmriprep/cli/tests/test_version.py
99.04% <0.00%> (-0.96%)
:arrow_down:

fmriprep/cli/run.py
3.50% <0.00%> (-0.84%)
:arrow_down:

fmriprep/workflows/bold/base.py
16.39% <0.00%> (-0.56%)
:arrow_down:

fmriprep/reports/core.py
53.84% <0.00%> (ø)

fmriprep/interfaces/multiecho.py
79.31% <0.00%> (ø)

fmriprep/workflows/bold/confounds.py
10.49% <0.00%> (ø)

fmriprep/workflows/bold/resampling.py
10.32% <0.00%> (ø)

fmriprep/utils/debug.py
20.00% <0.00%> (ø)

... and 4 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Yes.


develop gtfs cleaner to handle repeated pair (trip_id, departure_time) warnings

Description of the Feature to be Added

Calling is_valid() regularly leads to repeated pair (trip_id, departure_time) in stop_times.txt but these are not cleaned by clean_feed(). Further investigation shows that:

typically this is because neighbouring rows in stop_times.txt, within a given trip, have duplicate trip_id, arrival_time, departure_time, and stop_id. It's clear this circumstance is an erroneous duplication.
less often, there are neighbouring stops very close together, but they have different stop_ids - it's possible for these to be timetabled with the same time because of their proximity. Here is an example where a bus turns around and serves two stops on either side of the road (near Dingestow):

(OPTIONAL) Suggested Implementations

In stop_times.txt, when records have duplicate trip_id, arrival_time, departure_time, and stop_id these can be safely dropped (represent the same trip, stop and time). Develop a clean which drops these from the stop_times feed, to prevent these warnings from remaining.
Additional context

@ethan-moss
I need help in understanding the issue:
1	typically this is because neighbouring rows in stop_times.txt, within a given trip, have duplicate trip_id,
arrival_time, departure_time, and stop_id. It's clear this circumstance is an erroneous duplication.

2	less often, there are neighbouring stops very close together, but they have different stop_ids - it's possible for
these to be timetabled with the same time because of their proximity. Here is an example where a bus turns around
and serves two stops on either side of the road (near Dingestow):

Point 1 seems straight forward - whenever consecutive trips have the same trip_id, arrival_time, departure_time, and stop_id, drop the duplicate.
Point 2 - I am uncertain if it asks for any intervention. 2 different stops that are very close together and have the same arrival / departure time (not specified above). As these have different stop_ids they would not qualify for cleaning in point 1. Therefore I am uncertain as to whether this point calls for any treatment. Could you let me know if I have misunderstood the ask?

Migrated to https://github.com/datasciencecampus/assess_gtfs/issues/5


Added Feature to save and display pdfs on homescreen

Changes Made :

Wrote code to save the path of newly created pdfs to SharedPreference. we are appending the path to the List Object that is stored in the sharedPreference.
The sharedpreference is checked every time a user opens the homepage to know if he has saved pdfs or not. If yes , then the pdfs are displayed in a grid view , else we show a message "No PDFs Created Yet".
Added a refresh button in the homepage app bar to refresh the screen to see if new pdfs are added or not.

Fixes issue #62
@smaranjitghose @anushbhatia Kindly have a check. Thank you. I have attached the working in the following comment.

https://user-images.githubusercontent.com/40236624/106996207-7a5bca00-67a6-11eb-949e-78178bd28af9.mov

Great work @infiniteoverflow !
I guess @anushbhatia we can do some UI tweaks after this stage


Uncaught type error in new version

Hi,
Having a few issues with the new update (using the CDN links), where it will not show the body of the stepper. This seems to also be an issue on the demos here. Any ideas?
The error on the demo page (and similar in my code is):
Uncaught TypeError: Cannot read property 'setAttribute' of null
at util.js:33
at Array.forEach ()
at m (util.js:31)
at new t (index.js:34)
at HTMLDocument. (main.js:5)
Nick

Hi,
Having a few issues with the new update (using the CDN links), where it will not show the body of the stepper. This seems to also be an issue on the demos here. Any ideas?
The error on the demo page (and similar in my code is):
Uncaught TypeError: Cannot read property 'setAttribute' of null
at util.js:33
at Array.forEach ()
at m (util.js:31)
at new t (index.js:34)
at HTMLDocument. (main.js:5)
Nick

Same error too, switch to the previous version: 1.4.0 to avoid the error.

Hi :)
As it mentionned in the CHANGELOG.md the last release include a breaking change.
You have to be sure that the child element of your .steps elements have the .step-trigger class.
Be sure you follow the following HTML markup: https://github.com/Johann-S/bs-stepper#html-markup
The demo use this markup too: https://johann-s.github.io/bs-stepper/

Hey,
Got it working like so:
`					var stepper1 = null
				stepper1 = new Stepper(document.querySelector('#stepper1'), {
					linear: false,
					animation: true
				})`

and then this code...

 								<button type="button" class="step-trigger" role="tab" id="stepper1trigger1" 									aria-controls="test-l-1"> 									1 									Email 								</button>

 								<button type="button" class="step-trigger" role="tab" id="stepper1trigger2" 									aria-controls="test-l-2"> 									2 									Password 								</button>

 								<button type="button" class="step-trigger" role="tab" id="stepper1trigger3" 									aria-controls="test-l-3"> 									3 									Validate 								</button>

 							<form onSubmit="return false">

 										Email address 										<input type="email" class="form-control" id="exampleInputEmail1" 											placeholder="Enter email">
 									<button class="btn btn-primary" onclick="stepper1.next()">Next</button>

 										Password 										<input type="password" class="form-control" id="exampleInputPassword1" 											placeholder="Password">
 									<button class="btn btn-primary" onclick="stepper1.previous()">Previous</button> 									<button class="btn btn-primary" onclick="stepper1.next()">Next</button>

 									<button class="btn btn-primary mt-5" onclick="stepper1.previous()">Previous</button> 									<button type="submit" class="btn btn-primary mt-5">Submit</button>
 							</form>


Added contributing.md file

I am submitting a -

[] ** Added Feature**

Enchancement
Added the CONTRIBUTING.md file which has the steps to raise a PR and also steps for how to open an Issue which will help people who are new to open source contribution.

Hi, it's a duplicate of #146, @Parikshit-Hooda message conveyed that if the PR you are working on does not have an existing issue, then the issue needs to be created.


Add Deploy to Fly.io with SQLite how-to guide

When you review this, please take a look at the "TODO" comments and let me know your thoughts.
Once this PR has been approved and merged, I'll create a PR to add the 'Add SQLite Backups on Fly.io' how-to guide.

I don't understand the question

Jumped the gun on making this ready for merge. I can't get it to render in OSS, will update when I have got that working.

Alright, I think it is safe to merge now. Here is a sample project as well: https://github.com/platformatic/plt-fly-example


game keep show 0 scrap value result after ship take off

When we finish a moons with some scrap and the result screen keep saying we found 0 scrap and we don't get any exp for that.

What mods are you using? I just tried to reproduce this, but it showed me the value I collected and game me XP.

Better exp by Swaggies

Does it start working when you only disable HostFixes?

hmm my assumption is wrong it still show 0 scrap value after disable host fixes

probally another mod is causing this incompability


Wrong timer

With the recent changes on the timer that adds 1:30, when you have the affix "Challenger's Peril". The timer doesn't count the extra 1:30 added. Then when you +2 a key sometimes you will see that you didn't on the timer.
I don't have example but this happend to me few days ago and today. I'm of course on the latest version

Hi, thanks for the report. A big refactor of the core timer functionality (as well as new features like splits, global scaling, and a few other things) is in the works, which fixes this. Would you be interested in beta testing the new release? It's at the point where I would give it to other people for testing, but not quite ready for release.

The rewrite has been completed and released as 4.0. I'll close this for now since the timer code has been changed around a lot, but feel free to reopen if the issue still exists!

Hi, thanks for the report. A big refactor of the core timer functionality (as well as new features like splits, global scaling, and a few other things) is in the works, which fixes this. Would you be interested in beta testing the new release? It's at the point where I would give it to other people for testing, but not quite ready for release.

Hello, I'm not really interesting for beta testing sorry. But keep up the great work, I very like your addon !

I did a run now and still bugged It says +2 on the addon's timer but ingame its a +3

It does not look like you're on the latest version - can you make sure you're on at least 4.0?

Can you try 4.0.1? I'm confused since we just display information from the blizzard API as-is at the end of the key (as of 4.0), so there shouldn't be any discrepancies between what we display vs what the blizzard API displays. Will investigate further.

I will try to pay attention to it tomorrow and give a feedback when this happen

Again Timer say +2 and the game +3

Okay interesting, you're also getting another bug (the objectives saying " defeated" instead of just the boss names) which I haven't seen before. I think some logs would be very valuable here.
I suspect that blizzard changed something with regards to +2 being 80% and +3 being 60% of the time limit, which is why the bars don't match up even though the time reported is completely correct.
I'll create a new release with logging added around this issue specifically for you. Would you be ok with running some of your keys with that release and relaying the logs back to me?

Just looked through the comments on the M+ Timer WeakAura and through some other sites, and it seems like this is an issue that most addons have right now (even raider.io seems to calculate this incorrectly at the moment). Apparently the peril time is not calculated into the end time for +3 chests or something weird. I don't have the capacity to do extensive testing on this at the moment, but as soon as someone figures out the correct math here I'll adapt that.

Ok, its not a big problem but I just wanted to report it anyway. Hope you will find a fix rapidly.

Hi!
Sorry to intrude. I'm the author of the ‘iP mythic timer’ addon and I had a similar report. Last week I fixed the cutoffs for +2 and +3. If interested, in this comment I described how to now correctly calculate timers for +2 and +3 with the "Challenger's Peril" affix.
Hope this helps ;)
https://github.com/ipzaur/ipmythictimer/issues/17#issuecomment-2458001689

@ipzaur Thanks a lot for that! I've been reading through the comments on Reloe's M+ Timer WeakAura, and they curreently have the calculation as ((timer - 90) * 0.8) + 90, I'll have to check which is correct.

@ipzaur Ok, after testing and looking at other timers again, it seems like I was right at first. The calculation should be the following:
local timeLimit = ... -- Original time limit
local timeLimitWithoutPerilBonus = timeLimit - 90
local plus2TimeLimit = (timeLimitWithoutPerilBonus * 0.8) + 90
local plus3TimeLimit = (timeLimitWithoutPerilBonus * 0.6) + 90

You're welcome! Glad I could help :)


Emissions Accounting of Synthetic Fuels / (short-term) CCU

Dear all,
there is a general confusion in IAM projects about where to account for carbon contained in synthetic fuels produced via CCU. The emissions variable definitions do not specify where to account for these emissions and there are some intricacies with the different options. I will try to describe the three options that exist and which one I prefer and why.
Options
Let's take the example that we capture some CO2 from an industry plant and use it to produce a synthetic liquid fuel e.g. via Fischer-Tropsch using electrolytic hydrogen and combust this synthetic fuel in the transport sector. There are three levels at which the positive/negative emissions could be accounted:
1.) CO2 provider: This would mean that the CO2 is accounted as emissions for industry, while to the synfuel producer (energy supply) sector and the synfuel user (transport sector) no emissions are accounted. Note that this would apply to both fossil and non-fossil CO2. If it was fossil CO2 that was captured, the industry plant would still have the full positive emissions, while if it was, for example, bioenergy the industry plant would have zero emissions instead of negative emissions (which it would get if it stored the carbon underground).
2.) Supply-side: This would account the carbon as emissions of the synfuel producer. It would mean that the CO2 is accounted as emissions for energy supply, while it would not account emissions (or account negative emissions) for industry and would neither account emissions for transport.
3.) Demand-side: This would account the carbon as emissions of the synfuel user. It would mean that the CO2 is accounted as emissions for transport, while there would be no emissions for the synfuel-producer and no emissions for industry (if CO2 is fossil) or negative emissions (if CO2 is non-fossil).
I would definitely want to include a short statement in the definition of emissions variables on where to account this CO2 because it is not that obvious from the IPCC emissions guidelines. I am generally in favor of option 1, see my arguments below.
Arguments
a) What would be desirable, of course, is if we had the same definition as the IPCC emissions accounting guidelines. However, I am not sure the 2006 guidelines had this fully thought through and also the 2019 update did not seem to have any major update on this, if I see it right. The guidelines say

"Should CO2 capture technology be installed and used at a plant, it is good practice to deduct the CO2 captured in
a higher tier emissions calculation. Quantities of CO2 for later use and short-term storage should not be deducted
from CO2 emissions except when the CO2 emissions are accounted for elsewhere in the inventory[4]. The default assumption is that there is no carbon dioxide capture and storage (CCS) taking place.5" (IPCC Guideline 2006, Vol. 3, Chapter 1, p. 17-18)."

So, this sounds like option 1.) However, the footnote with the exceptions where CO2 emissions are accounted elsewhere points e.g. to methanol production. It says

"Petrochemical processes may utilise CO2 captured elsewhere as a feedstock, and CO2 may also be captured from
petrochemical processes. This may create potential double counting issues. For example, some methanol plants may utilise by-product CO2 captured from other industrial processes as a feedstock for methanol production. To avoid double counting the CO2 captured should not be reported as CO2 emissions from the process from which
the CO2 is captured." (IPCC Guideline 2006, Vol. 3, Chapter 3, p. 357)

To me this sounds like an exception for methanol to account under approach 2), which would not make sense if it was only about this specific product. But maybe it only applies to by-product CO2 from petrochemical processes which CCU + green H2 would not be but in reality this will be hard to distinguish. To be fair, the 2006 guidelines date quite some time back now where the synfuel story was not yet as relevant.
In summary, I find the IPCC guidelines not completely clear on this, but they tend to support the logic of approach 1.).
b) The EU ETS is going in the direction of approach 1.). Capturing CO2 only frees you from submitting allowances if you show that they are stored. Moreover, a recent ETS directive specifically pointed out again that synthetic fuels should be regarded as emissions-free to aircraft operators in the aviation sector, that is, exclude approach 3.).
c) Thinking about the communication of IAM results to the broader public, I would also prefer approach 1.). This is because of this frequent criticism that IAMs tend to overemphasize CDR.  We would stress this at first glance even more in sectoral emissions plots with options 2.) and 3.) as there will be more "negative emissions" which are actually not CDR but just carbon used in other sectors.
d) Finally, a counterargument or at least a disclaimer to option 1.). It leads to some definition issues for gross emissions and CDR variables in my view.  Typically, we would want to define gross emissions to fulfill gross emissions + CDR = net emissions and gross emissions should always be greater or equal 0. However, so far the gross emissions only exclude CO2 captured from bioenergy not from synthetic fuels (which under option 1. would also be emissions-free on the demand-side). Including non-fossil CO2 in gross definition can still lead to the situation, though, that e.g. industry gross emissions can become negative, if somebody captured fossil CO2, produced synthetic fuel with it and industry would capture and store it. @strefler and I already had some discussion about that. I would want to create a separate issue on that. There are potentially more of these intricacies I am not aware of; maybe also with other options.
Let me know what you think.
Best,
Felix
@IAMconsortium/common-definitions-emissions

This is an excellent point and definitely worth clarifying in the top level of the Emissions|CO2 variable category.  To me I think it comes down to a choice between being more consistent with some policy frameworks (e.g., in the EU) for biofuels carbon accounting (option 1), or with the physical reality of where emissions or removals are actually occurring.
I'm slightly in favor of option 3 but would defer to others as well

I agree that the physical accounting logic would, generally, be the preferred one but I think it would get quite confusing when we relate to the current policy discourse.
We talked about this in some internal discussions again and would make the following suggestion:

We account synfuel emissions on the side of the CO2 Capture (option 1). Biofuels and synfuels are closely related (in fact, you can argue that 2nd gen. biofuels are a form of synfuels) such that it makes sense to treat them equally. Moreover, the policy consistency is important. One additional example is that considering future trade of synfuels, accounting for physical carbon flows would make regional net-zero goals (e.g. in the EU) much harder to reach as imported synfuels will not be accounted carbon-neutral. For analysis of regional emissions goals, we would not like to switch to a physical accounting which does not correspond to the accounting typically used in policy analysis.

Given 1), there is a specific issue with the treatment of fossil-based synfuels and the definition of gross emissions and carbon removals. If the fossil carbon is obtained via CO2 capture, it has already been accounted as emissions in the CO2 capture sector, such that it should not be accounted another time when it is released to the atmosphere. That means it needs to be accounted as negative emissions for some sector once if the CO2 is again captured and permanently stored (see illustration below). However, these negative emissions are not carbon removal as it is fossil CO2. I would therefore propose to introduce a separate category like Emissions|CO2|Sector C|Accounted in Other Sectors that we also deduce from net emissions when we calculate gross emissions of a sector. That is,

Gross Emissions = Net Emissions - Carbon Removal - Emissions Accounted in Other Sectors.
Another option would be to argue that these emissions should not be substracted from the net emissions of sector C but of the original sector A. However, that would require to track the origin of all carbon flows through the system which seems hardly feasible once there are many closed loops / consecutive usages of carbon.

3.) The concept needs to be consistent with accounting of carbon in materials, more generally. That is, the question where emissions of chemical feedstocks / products / waste are accounted. This accounting deserves opening a separate issue but as soon as carbon accounting methods are chosen which do not align with physical carbon flows, the same problems arise, which should be solved in the same way.
This solution in 2.) is a little tedious, I admit, but it is an edge case, which allows us to stay with a more policy-relevant accounting.
Do you have concerns about this?


Containers logs: lifecycle and metrics

Good evening there,
Firstly, thanks a lot for this version of Logspout container. Logging containers logs output works very well in my infra on ELK.
I understood that logspout collect stdout and stderr of a container. When I start, stop, kill a container, I can't see these logs (I can see only the logs of the app inside the container, ex: <14>2015-07-27T17:28:42Z 67e0a929b430 logging_logspout_1[1]: 2015/07/27 17:28:42 logspout v2 serving http on :8000). What would you recommend to monitor containers lifecycles and upcomming errors.
And is there a similar tool to logspout to pull container metrics (CPU, RAM,...) and send to syslog? I saw a possible future features with CAdvisor+ELK.
I am quite new to monitoring containers, if someone could point me to right direction it could be great.
Thank you for your time and very good week to everyone!
Greg.

Interesting idea. I can't think of anything other than cAdvisor for that sort of stuff. And using the event stream for events. Anybody else know of anything?

I just saw a post about Logentries, which is a commercial monitoring provider, and they released a Docker container combining those outputs for their platform:
https://logentries.com/logentries-launches-all-inclusive-monitoring-of-docker-environments-using-advanced-logging-container/
Their code is written in Node and available here:
https://github.com/logentries/docker-logentries/blob/master/index.js
Looks like the logging portion is similar to logspout, and then they transmit the Docker events stream like you mentioned. For stats they use the Docker stats endpoint.

i have been toying with the idea of "comprehensive monitoring" of containers as well. see this blog: https://www.sumologic.com/2015/06/16/comprehensive-monitoring-for-docker-more-than-just-logs/ - i have an implementation that plugs into the collection framework we have at Sumo. the logic i came up with is as follows

connect to the Docker daemon

call the /info API, turn the result into JSON, and forward it

list all running containers, and for each container

call the /inspect API to get the details of the container
start to listen for logs
use the /stats endpoint to listen for metrics

subscribe to the event stream

each event received, turn that into JSON and forward it
when you see a container stop event, stop listening for logs and metrics
when you see a container start event, start listening for logs and metrics

so you can get metrics without needing cAdvisor, actually, as @mgood says.
adding events and the inspect output to the mix is useful in intracking lifecycles, and knowing a bunch of details about the containers that are running.
all of this actually works against a Swarm master even, so you can get all of this for all of the daemons in the Swarm by just connecting to the master. i think that's really cool.
poking around Logspout for the last 6 months or so has been very educational for me in getting to the above and i would frankly love to see Logspout do all of these things. i have a very silly implementation that does the /stats thing lying around.
@progrium i would be very happy to help with this. i haven't managed to find a good way to introduce this functionality in the same modular fashion as say an output module, without touching the core of Logspout. if you think adding this is in scope for Logspout, maybe we can talk/prototype something?

Yeah, I'm open to talk about it and collaborate. For the longest time I've
figured stats would be handled in a sister tool to logspout. It's a pretty
different domain. But injecting stats into logs is a reasonable pattern.
Stats events and docker events would also require either an opinion or
configuration for how they are added to the log stream so you can have
consistent logs. Though I suppose they could be log types (currently only
stdout, stderr, soon syslog, maybe additionally: lifecycle and stats) and
selectively routed.
If you want to talk more sometime I can invite you to a new community Slack
we're setting up for Glider Labs.
On Tue, Jul 28, 2015 at 11:32 AM, Christian Beedgen <
<EMAIL_ADDRESS>wrote:

i have been toying with the idea of "comprehensive monitoring" of
containers as well. see this blog:
https://www.sumologic.com/2015/06/16/comprehensive-monitoring-for-docker-more-than-just-logs/

i have an implementation that plugs into the collection framework we have
at Sumo. the logic i came up with is as follows

connect to the Docker daemon

call the /info API, turn the result into JSON, and forward it

list all running containers, and for each container

call the /inspect API to get the details of the container
start to listen for logs
use the /stats endpoint to listen for metrics

subscribe to the event stream

each event received, turn that into JSON and forward it
when you see a container stop event, stop listening for logs and
metrics
when you see a container start event, start listening for logs
and metrics

so you can get metrics without needing cAdvisor, actually, as @mgood
https://github.com/mgood says.
adding events and the inspect output to the mix is useful in intracking
lifecycles, and knowing a bunch of details about the containers that are
running.
all of this actually works against a Swarm master even, so you can get all
of this for all of the daemons in the Swarm by just connecting to the
master. i think that's really cool.
poking around Logspout for the last 6 months or so has been very
educational for me in getting to the above and i would frankly love to see
Logspout do all of these things. i have a very silly implementation that
does the /stats thing lying around.
@progrium https://github.com/progrium i would be very happy to help
with this. i haven't managed to find a good way to introduce this
functionality in the same modular fashion as say an output module, without
touching the core of Logspout. if you think adding this is in scope for
Logspout, maybe we can talk/prototype something?
—
Reply to this email directly or view it on GitHub
https://github.com/gliderlabs/logspout/issues/121#issuecomment-125672934
.

--
Jeff Lindsay
http://progrium.com

cool. definitely looking forward to the invite when you're ready!

Folks, Sematext's Docker Container will collect Docker Metrics (host + containers) AND Events AND Logs - https://github.com/sematext/spm-agent-docker .  And https://github.com/sematext/docker-spm-client will also grab all application metrics shortly (for apps listed at http://sematext.com/spm/integrations ).


DevContainer Setup for Kubernetes Marketplace

To provide a more streamlined development/contribution experience, created a dev container.  This will allow for creating a consistent environment, as well as the use for more cloud-based development environment (Github Codespaces, DevPod, etc).
Also looking to be a baseline to assist in Dagger integration in the Kubernetes Marketplace repo.

@DMajreka @rytswd @milindchawre ☝ Thoughts?


fixing case of contact model in tests

Fixes issue with case of contact model. Doesn't effect functionality but prevents IDE error.

Thanks!


[es] localize content/en/docs/concepts/storage/storage-classes.md to Spanish

This is a Feature Request
What would you like to be added
Localize content/en/docs/concepts/storage/storage-classes.m to Spanish
Why is this needed
Comments

/language es

/assign @edithturn

PR: https://github.com/kubernetes/website/pull/41118

@edithturn  como estas? te puedes dar assign para este issue por favor ! Gracias

/assign @edithturn

/assign @edithturn

@krol3  dejame saber si esta correcto lo que hice. Gracias de antemano :)

/close by https://github.com/kubernetes/website/pull/41118

/close


Bug of draw_circuit function

I fixed a bug,

IndexError: index 1 is out of bounds for axis 0 with size 1

, when  we use draw_circuit method while there is no gate on the circuit.
In a result, when there is no gate on the circuit, 'draw_circuit' shows lines(-)  representing the number of qubits.

I have read the CLA Document and I hereby sign the CLA


fix(js-decisions): passed provided decisions through to the js-scaffolder factory

fixes passing the decisions to the js-scaffolder properly. i've gone back and forth a number of times in my head on the right way to thread this through, but was able to prove the correct way through the integration test for the @pragmatic-divops/cli

we only leverage certain decisions per scaffolder so I suppose the same decisions blob can be used for multiple levels

yeah, the key is to keep the keys between the scaffolders unique across the scaffolder so that there arent conflicts in the combined decisions map. this was actually the detail mentioned in the other PR about the two PROJECT_TYPE question names that resulted in the value change of one of them. hopefully being unique about this wont become too dangerous over time.

ah, okay that also makes sense in hindsight to what you were pointing out as you mentioned. 👍 all sounds good, and good to know.


Notification not triggered when services comes UP

⚠ Please verify that this question has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
I have setup notify check healthy my gitlab server. Also i have setup notify webhook through to Lark Suite. It has sent alert when services down but when services up, it not alert again.
📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
Ubuntu 20.04
🌐 Browser
Chrome
🖥 Deployment Environment

Runtime: K8s
Database: sqlite/embedded
Filesystem used to store the database on:  NFSv3 on HDD
number of monitors: 1

From your description this could be multiple things.
What was the log output?
How have you configured the monitor in terms of retention settings?

So, I will show you all my step to notification my Lark.

Create bot webhook in group chat Lark suite then it give me URL hook without credential.

Then I go to Lark Suite docs to read about custom layout notification: Docs Lark Custom

I have tested send message complete to Bot Lark but just only when services gitlab down time. It should be when gitlab uptime it with send notification that service is uptime. Finally, it sent again downtime notification. ( It mean it send 2 times downtime though service on uptime).

My Question with if gitlab uptime how uptime kuma send custom another notification uptime to bot ?

So we are talking about two differnt things. Your inital message gave the impression that NO allert is send out on a monitor coming UP

but when services up, it not alert again

You are talking about something different in the second message.

Finally, it sent again downtime notification

This is because you have configured the webhook to open the issue in larksuite.
Said webhook is send on both DOWN/UP/Certificate Expiry/Testing.
Currently, filtering what notifications get passed to which notification provider is not supported.
See https://github.com/louislam/uptime-kuma/issues/508 for the tracking issue
Please see https://github.com/louislam/uptime-kuma/issues/3715 for how to configure Lark via Feishu as the notification type or how to contribute a dedicated notifiaton type for Lark ^^

Thanks so much for answer to help me.


fix of hexl install bug

When SEAL_USE_INTEL_HEXL=ON,  cmake --install fails as cmake points to a non-existing directory for the hexl header files.  This commit fixes this ...

Thank you for fixing this! It will be pushed soon to update the current 3.6.4 version.


Add more information to the error printed when kafka producer is configured with an invalid Kafka cluster

Description:
Describe your problem(s)
When the kafka producer host name is invalid, only the following error is available.
error: Failed to initialize the producer: Failed to construct kafka producer {}

This can be quite challenging to debug in a Cloud environment.
Describe your solution(s)
Add more information about the error that would help the user to debug and fix the issue.
Related Issues (optional):
N/A
Suggested Labels (optional):
N/A
Suggested Assignees (optional):
N/A

When an invalid url is given, there is an error message as error: Failed to initialize the producer: Invalid url in bootstrap.servers:.  Can I know the exact url that created this error without a cause?


Job result Visualizations

This PR introduces client-side visualization of job results. On the backend, we detect nuclei and glands in an image as two separate jobs. The output from either job can be shown in the client by displaying dots over the detected structure centroids. Instead of calculating distance between these centroids as a job on the backend, this type of calculation is better fit for the client, once the client has access to the centroids' information.
The client does not yet display aggregate information such as the average distance. Right now, the distances are visualized as lines between a nucleus centroid and a gland centroid, appearing when either centroid point is moused over.
Since the backend can detect the presence of either nuclei or glands, the database model of DetectedNucleus was generalized as DetectedStructure and modified to contain information the client would need.

Just a heads up, your most recent force push changed the hash for your recent commits, so they don't match the comments you made on the review. I can manage for now but it would be a good idea to update the comments so they are accurate.

Just a heads up, your most recent force push changed the hash for your recent commits, so they don't match the comments you made on the review. I can manage for now but it would be a good idea to update the comments so they are accurate.

Nice catch, I updated the links in the resolved issues

Apologies for the several force pushes; I'm finding it difficult to merge in changes from main and reconcile the migration files. @mcovalt could you take a look at 3a07b11 and perhaps diagnose why this test failed?

Looks like the index name was autogenerated to be different when on a different model name. I reordered migrations to have my migration last. Let's see if it works. Ideally, we'd not reorder migrations as this will require dropping the DB (or at least rolling back to 008) to reconcile the new migration sequence. You may want to order them such that your migrations occur after the ones on main, but up to you.

Thanks for fixing that. Last question: Is it possible to supply a null/blank value for the fingerprint field? Now we have glands occupying the same model as nuclei, and I'd like to skip the fingerprint part in the detect_glands job.

Looks like the tests are failing due to fingerprint not being provided on glands. This exposes a bug in the CubeField: a NOT NULL constraint should be invalidated immediately, rather than providing what looks like bad data.
Correcting  this behavior in CubeField will still result in errors, though. A few options:

we can allow null in the field
we can just provide a dummy fingerprint=Cube([-9999]*100) with glands (probably easiest for now)

In either case, the similar nuclei code assumed DetectedNuclei was just nuclei. Expanding its definition to also include glands may break some of the similar nuclei code. I'll keep an eye on this behavior with further development of the similar nuclei features.

Ok, we can provide dummy data there. We do so for a lot of the fields on detected glands, since that data is made up. And yes, combining the two models does complicate the logic for your similarity search. If the design of these two features weren't done simultaneously, we may have had time to come up with a better design concept. Something to consider for Phase 2 perhaps.


broker init.sh - stops execution of a script if a command has an error

Type of change

Bugfix

Description
Broker's init.sh should stop execution and return a non-zero return code to the execution environment if an initialisation command ends in error.
Checklist

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

@enmasse-ci run tests profile=isolated

does it cause pod restart?

@kornys yes it should

does it cause pod restart?

indirectly, yes.  The init container will fail if any of the commands within the init script fail.  The pod's restartPolicy then applies.

So I think it is fine because pod restart always resolve this issue

So I think it is fine because pod restart always resolve this issue

Yes, that is my expectation and was my experience yesterday on your cluster.  That suggests in this case the the clock skew is small.  If the clock skew was large, with the new script option, the init container will fail (early) and the root cause (cert not valid) will be obvious from the logs.

nice, so tests and system will be more stable

@enmasse-ci run tests profile=isolated

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: isolated
TEST_CASE:
TOTAL: 18
PASS: 18
FAIL: 0
SKIP: 0
BUILD_NUMBER: 486

@enmasse-ci run tests profile=isolated

:x: Test Summary :x:
TEST_PROFILE: isolated
TEST_CASE:
TOTAL: 150
PASS: 145
FAIL: 2
SKIP: 3
BUILD_NUMBER: 487
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

testConnectorTLS in io.enmasse.systemtest.isolated.bridging.ConnectorsTest
testSendThroughConnector2 in io.enmasse.systemtest.isolated.bridging.ConnectorsTest

The ConnectorsTest failure seem unrelated to the change.


Polymorphic deserialization with System.Text.Json requires discriminator property to have the shortest JSON object key length

The following sample only works due to overriding the default discriminator property named $type (key length = 5) to $t (key length = 2). Otherwise, the deserialization throws an exception.
[JsonPolymorphic(TypeDiscriminatorPropertyName = "$t")]
[JsonDerivedType(typeof(WeatherForecastBase), typeDiscriminator: "base")]
[JsonDerivedType(typeof(WeatherForecastWithCity), typeDiscriminator: "withCity")]
public class WeatherForecastBase
{
    public DateTimeOffset Date { get; set; } // key length = 4
    public int TemperatureCelsius { get; set; }
    public string? Summary { get; set; }
}

public class WeatherForecastWithCity : WeatherForecastBase
{
    public string? City { get; set; } // key length = 4
}

The System.Text.Json (STJ) docs state:

The type discriminator must be placed at the start of the JSON object, grouped together with other metadata properties like $id and $ref [and $values].

It's a pretty annoying .NET runtime issue that has been raised upstream. Not sure why STJ is opinionated about that, maybe for backwards compatibility with legacy systems? 🤔
This conflicts with jsonb columns (re-)ordering JSON object keys by length:

By contrast, jsonb does not preserve white space, does not preserve the order of object keys, and does not keep duplicate object keys. If duplicate keys are specified in the input, only the last value is kept.
[...]
In general, most applications should prefer to store JSON data as jsonb, unless there are quite specialized needs, such as legacy assumptions about ordering of object keys.
[...]
Note that object keys are compared in their storage order; in particular, since shorter keys are stored before longer keys

Should we mention this quirk in the docs under Serialization with System.Text.Json?
Another idea is to let Marten align STJ and jsonb by configuring the STJ serializer via contract model.
Similar to the JsonNetContractResolver via Json.NET serializer options, we could add the STJ analog that does something like this:
public class SystemTextJsonContractResolver : DefaultJsonTypeInfoResolver
{
    public override JsonTypeInfo GetTypeInfo(Type type, JsonSerializerOptions options)
    {
        var jsonTypeInfo = base.GetTypeInfo(type, options);

        var isPolymorphic = type
            .GetCustomAttributes(typeof(JsonDerivedTypeAttribute))
            .Any();

        if (isPolymorphic)
        {
            jsonTypeInfo.PolymorphismOptions = new JsonPolymorphismOptions
            {
                TypeDiscriminatorPropertyName = "$t"
                // that works too and is even shorter
                // TypeDiscriminatorPropertyName = "!"
            };
        }

        return jsonTypeInfo;
    }
}

Not sure why STJ is opinionated about that, maybe for backwards compatibility with legacy systems? 🤔

See https://github.com/dotnet/runtime/issues/63747#issuecomment-1158624112

This is like a self-referential issue, I opened the original issue in the runtime repo due to discovering the problem whilst testing marten with STJ polymorphism and now it's come full circle and ended up back here. 😆
Use of a shorter type discriminator is an interesting solution, but I personally see it as a "hack" rather than "fix", and thus I wouldn't expect marten to patch this out of the box with a contract resolver. Adding something to docs mentioning this issue and some potential workarounds seems reasonable.
I'm still fine with using the PolyJson package until STJ resolves the particular issue.

Thus I wouldn't expect marten to patch this out of the box with a contract resolver. Adding something to docs mentioning this issue and some potential workarounds seems reasonable.

Seems reasonable.
Another option could be allowing users to override the default Marten contract resolver via Marten store options. Without having looked at the code, I could imagine that this could potentially lead to more issues down the road.

My personal take on this is that the STJ is terrible in that regard; some of the reasons you already mentioned. I also don’t see much benefit of having polymorphism in DTOs.
You can override the STJ settings, AFAIK know we’re not blocking anything here. If we do, then happy to enable that.
I’m sorry, but I don’t see happening changing the way we serialise things  just to enable this specific feature as it’s too high risk for too small a reward.
I’ll turn this into the discussion for now.


Running on Windows 10

Hi,
to get this to run on Windows 10 one must do some ninja parsing of the install directory to find the actual executable. Running from the start menu does not work.
Clearly this is a job for some post installation reg-exp with folder search (to do the ninja) and then maybe some in house co-ercing on your part to get a suitable startmenu icon magicked into life from this new info.
This first part I could do myself.  We use this app regularly with our tiny infants right thru to early years and have expounded its virtues evangelically to all of our parents since business began.
It would not be a tough step for a group such as ourselves (and in that I include all contrubutors to this project).
Comments?
Our dekstop icons work btw.

I also have it running on Windows 10.  I do see the taskbar showing up still while BabySmash is running though, which is annoying.  I haven't tried the installer on Windows 10 yet though - Sounds like it leaves something to be desired?  IIRC, Scott never fully open-sourced the Installer part, so I'm not sure it's something I could look at anyway?  I think we'd need him to chime in at this point.

Sorry, the installer is just ClickOnce. You can publish it yourself or not
use an installer at all, and run it from a folder. The "official" version
has to be Code Signed so that's why it's not 100% obvious.
I'll go through the PR and try to get http://babysmash.com updated in a few
weeks.
On Sat, Feb 20, 2016 at 8:22 PM, David Rieman<EMAIL_ADDRESS>wrote:

I also have it running on Windows 10. I do see the taskbar showing up
still while BabySmash is running though, which is annoying. I haven't tried
the installer on Windows 10 yet though - Sounds like it leaves something to
be desired? IIRC, Scott never fully open-sourced the Installer part, so I'm
not sure it's something I could look at anyway? I think we'd need him to
chime in at this point.
—
Reply to this email directly or view it on GitHub
https://github.com/shanselman/babysmash/issues/11#issuecomment-186737960
.

--
Scott Hanselman
Donate to fight diabetes: http://hnsl.mn/fightdiabetes

I'm not sure that I properly described the original problem. Cardinal sin.
I believe it was the default Babysmash Icon (That is created in the Start Menu) "not firing" despite ostensibly pointing to the exe that is installed by the click-once in %LocalAppData%\Apps\2.0\foor\bar
(I kind of thought Mr Hanselman had done a post about it, but I may be wrong.)
Anyway: this can be circumvented by simply doing a search for the "real" exe and creating a shortcut to it manually and then sticking THAT on the start menu - that works.
So this may be a shortcut format problem. I did find a post back in fab confirming the issue is "well known" and of course I can't find it now. When I turn it up or manage to get better test notes I will share.
Thanks very much for listening, we have a manual workaround for now.
If "Code signing" is indeed the issue, I don't recall any of those details from the time and fear that may be cross-purpose information.

Setting ResizeMode = ResizeMode.NoResize on MainWindow seems to fix showing a couple of pixels of the taskbar, at least when running the executable. I did not test on clickonce.

nice on @FormalDeterminism . This is still a fave with the kids here.  good catch on that.
I was toying with a custom scancode registry injection to UTTERLY remove access to special keys, but there are only a few computers here with such buttons so.. not sure it is worth it.
For the record, we have never got it to run from the Start Menu in Windows 10, but then again all manner of apps exhibit "unique" features with respect to the new start bar xml setup so... Kludge works fine.


Rewrite plugin using React

This PR replaces kibiter_menu with new React components and adds them to the top header using OpenSearch Dashboard's chrome API. The project name is taken from the projectName configuration variable in opensearch_dashboards.yml instead of fetching it from the /getprojectname route

I updated the PR to fix the /getmetadashboard route and reorder the header items.


issue

what version of node are you using？

Well i see the problem here. You need Node v18+ version to run. Mine is v19


[TwigComponent] Fix MountedComponent::$extraMetadata type doc

Q
A

Bug fix?
yes

New feature?
no

Tickets
-

License
MIT

MountedComponent::getExtraMetadata() has mixed as return type and it returns elements from this array.

You're right - thanks Matthias!


[NVIDIA] Update the algorithm to compute fp8 scales

This pull request implements updates to the algorithm for computing new FP8 scales, in line with the design outlined in the following documentation: https://docs.nvidia.com/deeplearning/transformer-engine/user-guide/api/jax.html#transformer_engine.jax.update_fp8_metas.
cc. @wenscarl @reedwm @lukaszlew @levskaya

The change looks OK, but mypy is now yielding a type error - would you mind double-checking if that's finding something real, or is it spurious?

Codecov Report

Merging #3441 (3a0e87a) into main (5557649) will decrease coverage by 0.05%.
Report is 2 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #3441      +/-   ##
==========================================
- Coverage   83.68%   83.63%   -0.05%
==========================================
  Files          56       56
  Lines        6808     6797      -11
==========================================
- Hits         5697     5685      -12
- Misses       1111     1112       +1

Files
Coverage Δ

flax/linen/__init__.py
100.00% <100.00%> (ø)

flax/linen/fp8_ops.py
100.00% <100.00%> (ø)

flax/training/train_state.py
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

@levskaya thank you for bringing this to my attention. I've removed the function return value annotation that was causing the previous mypy check to trigger. I don't believe it's necessary because this custom operation for FP8 is not configured to the layers, such as DenseGeneral, by default. There won't be any other type checking tracing back to this operation.

@levskaya Any updates? I see this PR has stayed in "pull ready" status for a couple of days.

@kaixih - super sorry for the delay, not sure why it didn't go through earlier!  It should have merged last night.


Use live bidding with InHouse

JIRA: EE-1225

Comments on commit messages:
1st and 2nd commits have the same titles

No, one is migrating the public API while the other is migrating the private one.

Do not consider null ad unit in InHouse module -> could you explain why in the commit desc

Done


"Link to a new dataset" may be confusing

The purpose of this option is to allow a dataset already in Girder to be used in Resonant Laboratory. As such, it may need a more precise description than "linking", which isn't quite what is going on.

In the future, I was planning to use the same field to paste other kinds of links (e.g. files hosted on dropbox). Linking to an existing girder item by ID is really a corner case that, really, only we developers are likely to use.
I agree for now we should change it, but maybe change it back if/when we add support for linked files?

This is one of those cases where what we imagine might balloon into a lot
of unexpected use cases. For instance, if someone uses a Python script to
upload a bunch of datasets, they may want to use this function to bootstrap
some of the datasets into Resonant Laboratory, etc. But I see what you mean
about it being a minority use case. I'd say let's figure out the wording to
use now, and then if we want to actually link in external files later, add
"link to dataset" back in as another option.
On Mon, Aug 22, 2016 at 10:56 AM Alex Bigelow<EMAIL_ADDRESS>wrote:

In the future, I was planning to use the same field to paste other kinds
of links (e.g. files hosted on dropbox). Linking to an existing girder item
by ID is really a corner case that, really, only we developers are likely
to use.
I agree for now we should change it, but maybe change it back if/when we
add support for linked files?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Kitware/candela/issues/364#issuecomment-241439983,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACxNJAahjaacyJUCkymf0187NLHRvyETks5qibiwgaJpZM4Jo0iL
.


Propagate model and column descriptions into the metadata of underlying tables

We should be able to automatically propagate model and even column descriptions as table description for engines that support this.

Closed by #1878


feat: redirect homepage datasets entities to dataset page on click

This PR adds a redirect for the dataset entities in the home page to their respective page

Thank you for your feedback 🙂 👍  I have refactored the code as suggested


Query if a lockId is released or not

No way to query if a lockId was released or not. releaseLock always returns OK.

Usually, you dont't need to query if a lockId was released or not. You should call releaseLock immediately after your operations of an object if you call getLock  first, which means you should not hold a lock for a long time.
The return value of releaseLock is always 'OK' yet. I'll change the return value if the lockId does not match the object's lockId  in the next version.

I agree that my use case is somewhat unique but it seemed like a reasonable ask. Thanks for taking care of it.


Add number of issues and individual contributions to the list

This is the first update to the automation suite. Needs more planning


Status bar layout glitch when using gestures to close side menu

This is a minor cosmetic issue that I noticed started happening in iOS 11.
I have a left side menu that can be opened via button or by gesture. The status bar is visible on the main controller, but is hidden when the left menu is open.
When the left menu is opened (by button or gesture), the status bar correctly disappears and the main controller leaves a space for the status bar on the navigation header.
When the left menu is closed by button, it will animate closed as expected, with the status bar reappearing. However, when it is closed via gesture, the primary view controller suddenly updates to remove the blank space for the status bar on the navigation header.
My best guess is that the setting of the view's transform on this line is doing some additional layout calculations that it wasn't doing before in iOS 9/10, but I'm not sure where to proceed from here.
https://github.com/Friend-LGA/LGSideMenuController/blob/master/LGSideMenuController/LGSideMenuController.m#L1926
Example: (Sorry for the large images)
Before -> After gesture start

Thanks!

@SticklyMan Did you solve this?

@Lailan Nope, we're still observing this issue.  I have unfortunately not had enough time to dig into a low priority issue like this.

Should be fixed now.
Feel free to reopen if the issue is still actual.


Subfolder names do not synchronize over IMAP

Overview
There appears to be a folder name synchronization issue when mail folders are renamed outside of K9.
Replicate

Open a mail reader that is not K9 (e.g., Thunderbird or browser-based web mail client).
Use a mail server that is not GMail, but uses IMAP.
Open Inbox using mail reader.
Create a new folder (e.g., Main).
Create 10 sub-folders under the new folder (e.g., Main/01, Main/02, Main/03, etc.).
Open K9.
Refresh the folder list using K9.
Return to other mail reader.
Rename a few of the sub-folders (e.g., Main/03 becomes Main/03 - done).
Return to K9.
Refresh the folders.

Expected
The renamed folder appears in K9 as Main/03 - done.
Actual
The folder name appears in K9 as Main/03.
Debug
To be added.

Please create a new issue if this is still a problem with K-9 Mail 5.7xx.


Push latest fixes for React 15 to NPM

Simply put, the version in the NPM repo doesn't have all the latest code fixes that are present on github.

Hello
You've done already a great job. It looks very good and works as it should.
I think your fixes would be really helpful. Eg. I have a warning with span marginTop being string '-1'. It's now fixed on GitHub. Could you push the changes into NPM?

@IonoclastBrigham @dciesielkiewicz My apologies for being slack on this, it has only just come to my attention. Version 1.0.0 has been published to mirror master.


Support automatically offloading of NumPy reduction operations and prange reductions to SYCL devices

Numpy reduction operations are not yet automatically offloadable to a SYCL GPU. To get around the issue, we are detouring to fallback on CPU execution for all reduction functions (refer PR IntelPython/numba#8). We need to support reductions by either directly generating a SPIR-V kernel for reduction inside Numba or calling a library routine that does the reduction.

Currently, NumPy reduction calls such as sum, product, dot are supported via dpnp library calls. Closing the issue as it is too broad, we can open newer issues for specific routines as needed.


Update README.md

Codacy badge link added in README.md file , which shows codacy code quality status and redirects to the codacy repository page.

Update README.md

@pujamudaliar The patch does not conform to Hare's patch requirements.

A patch SHOULD be a minimal and accurate answer to exactly one identified and agreed problem.

[...]

A patch commit message SHOULD consist of a single short (less than 50 characters) line stating the problem ("Problem: ...") being solved, followed by a blank line and then the proposed solution ("Solution: ...").

What problem is being solved?
cc @Saumya-Sunder

@NeeravChoudhari, Can you please take this forward as we had already made a practice to add Codacy badges for all the repos as,

Problem: Codacy Badge needs to be included in README.md file , which provides code quality status for every commit in the repository.It also contains link to the repository in Codacy.
Solution: Codacy badge link is copied from the settings tab under Codacy Hare repository and pasted in README.md file.

@NeeravChoudhari, Can you please take this forward as we had already made a practice to add Codacy badges for all the repos as I dont understand why the concern is raised for Hare

@mukul-seagate11 I speak some English, you can contact me as well. 🙂


cannot stat docker-entrypoint-initdb.d: No such file or directory

When i run the following command on windows 10 linux container option. I get the following error.
docker run -d -p 1521:1521 sath89/oracle-12c
cannot stat '/docker-entrypoint-initdb.d/*': No such file or directory

I had to map the volume to my local disk path. Then it worked.
docker run -d -p 1521:1521 -v /c/oracle/:/docker-entrypoint-initdb.d sath89/oracle-12c


Template rendering warning

[vue-language-server] Elements in iteration expect to have 'v-bind:key' directives.
=> th

  <template v-for="detail in collateralForm.detail">
    <template v-if="detail.m_type === 9">
      {{nm}}
      操作	// This warning
    </template>
  </template>

Yes

Please try filing an issue against your vue extension


Update Remote Desktop

Change WorkingArea to Bounds for fullscreen
Add NumericUpDown for select screen source
Add Client variable to send the number of screen available to the server

Thank you @thi67  for your cooperation and support! Good stuff


Define standard: Automated Traffic Recordings

Same as TMCs: This is a general issue and part of the "standard definition" piece

This one is a bit tough since there can be so many different schemas from different vendors. When I scraped the ATR's I was getting the total volume, classifications counts (# cars/motorcycles/heavy vehicles), and mean speed over a 24-hour period. I think most of the different schemas have these aggregate stats but I don't how much further we could expand on it.
Another thing is that some studies where done over 12-hour period or a 36-hour period. I think it might be best to normalize these stats so they're all on a "per hour" basis. That we could include a wider range of ATR studies.

@bpben @andhint @terryf82 @alicefeng @shreyapandit
I've attached a (txt, so it would upload) draft schema for traffic volumes in general. My idea is that it can store TMCs/ATRs, as well as other speed studies (Cambridge has the 85th percentile speeds).
I'm suggesting normalized 24 hour counts - for example the TMCs were only 11 or 12 hour totals but I normalized them to 24 hours based on the volume curve from the ATRs.

traffic-schemas.txt

Should we record the original time period the counts were collected over? Even if we're going to use the normalized 24 hour counts it might be useful to have that info.

Sounds good - how about a start datetime and end datetime?

I don't have them in front of me but I don't think they had a start/end time. I think it was just 12hr/24hr/etc. Either would be fine though depending on what they have.