build failed

Hi! I am trying to make ebuild of dart for gentoo linux, i found a ebuild for old version and addatping it for newer version. But at compile phase i have this error:
[49/3432] /usr/lib/llvm/10/bin/clang++ -MMD -MF obj/runtime/bin/gen_snapshot_dart_io.filter.o.d -DDART_IO_SECURE_SOCKET_DISABLED -DNDEBUG -DNDEBUG -DDART_USE_TCMALLOC -DDART_PRECOMPILER -DTARGET_ARCH_X64 -DTARGET_OS_LINUX -I../runtime -I../third_party -I.. -Igen -I../runtime/include -I../third_party/tcmalloc/gperftools/src -I../third_party/zlib -m64 -march=x86-64 -msse2 -fno-exceptions -fPIC -fcolor-diagnostics -Wall -Wextra -Werror -Wendif-labels -Wno-missing-field-initializers -Wno-unused-parameter -Wno-tautological-constant-compare -fdebug-prefix-map=/home/wneo/tmp/path_for_dart/dart-2.9.0/dart=.. -no-canonical-prefixes -Wheader-hygiene -Wstring-conversion -O3 -fno-ident -fdata-sections -ffunction-sections -g3 -ggdb3 -Werror -Wall -Wextra -Wno-unused-parameter -Wno-unused-private-field -Wnon-virtual-dtor -Wvla -Woverloaded-virtual -Wno-comments -g3 -ggdb3 -fno-rtti -fno-exceptions -Wimplicit-fallthrough -O3 -fvisibility-inlines-hidden -fno-omit-frame-pointer -std=c++11 -fno-rtti -fno-exceptions -c ../runtime/bin/filter.cc -o obj/runtime/bin/gen_snapshot_dart_io.filter.o ninja: build stopped: subcommand failed.
for build i use this ninja -v -j17 -l0 most
Also i tried to do it manually (not by portage and ebuild) and have same error. Will pleasure for any advices)

The actual error from the compilation is not captured in your description above, could you elaborate a bit more on the kind of error you are seeing. Also please note gentoo linux is not a supported host configuration.

Here a full build log https://pastebin.com/LNpH6brF
Also i forgot to say, that i try to build 2.9.0 version

I do not see any error in your full build log from any of the compilation lines.
I see this text in the log, do you know what it means ?
/bin/sh: /usr/lib/llvm/10/llvm-ar: Нет такого файла или каталога

Нет такого файла или каталога means "No such file or directory" according to Google translate.

@athomas right in translation
I found llvm-ar on that path: usr/lib/llvm/10/bin, what i should do?

See this command in your build log
rm -f obj/runtime/bin/libcrashpad.a && /usr/lib/llvm/10/llvm-ar rcs obj/runtime/bin/libcrashpad.a
figure out where it is getting generated from and replace /usr/lib/llvm/10/llvm-ar with /usr/lib/llvm/10/bin/llvm-ar


SSH Advanced usage examples

Connected issue: #74
Add a page with "advanced" ssh usage examples - ssh client config, tunneling and jumping

I have also added additional CSS rule for justified text alignment for paragraphs in  - it's optional, toggled by adding a class "justified-paragraphs" to  tag


Preparation for Undertow 1.3.0.Beta2.

Actual statistics implementation to come in a subsequent PR.

Linux Build 6719 is now running using a merge of 63ab947a2be5b4cc62cf6ec72e22b1daeaacf1cb

Linux with security manager Build 1620 is now running using a merge of 63ab947a2be5b4cc62cf6ec72e22b1daeaacf1cb

Windows Build 1793 is now running using a merge of 63ab947a2be5b4cc62cf6ec72e22b1daeaacf1cb

Linux with security manager Build 1620 outcome was SUCCESS using a merge of 63ab947a2be5b4cc62cf6ec72e22b1daeaacf1cb
Summary: Tests passed: 833, ignored: 322 Build time: 0:05:35

Windows Build 1793 outcome was FAILURE using a merge of 63ab947a2be5b4cc62cf6ec72e22b1daeaacf1cb
Summary: Tests failed: 1 (1 new), passed: 2877, ignored: 377 Build time: 0:46:49
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase(SYNC-tcp).testFormAuthSingleSignOn: <no details avaliable>

Linux Build 6719 outcome was SUCCESS using a merge of 63ab947a2be5b4cc62cf6ec72e22b1daeaacf1cb
Summary: Tests passed: 2877, ignored: 377, muted: 1 Build time: 0:47:42

Windows Build 1797 is now running using a merge of 63ab947a2be5b4cc62cf6ec72e22b1daeaacf1cb

Windows Build 1797 outcome was SUCCESS using a merge of 63ab947a2be5b4cc62cf6ec72e22b1daeaacf1cb
Summary: Tests passed: 2878, ignored: 377 Build time: 0:47:53


Wait for lifecycle commands to complete

envbuilder was forking lifecycle commands but not waiting for them. This would lead to unexpected behavior, and also flakiness in TestLifecycleScripts.

cc @coryb

@kylecarbs reviewed this out-of-band


prefer const for variables that are only assigned values once

Please update version nr in package.json before merging this

thx =)


Problem with the device port

I want to connect to my yamaha wx-ad10.
The device is correctly detected by swyh
[...]
17:06:56 [INFO] SSDP discovery: new Renderer found at : http://<IP_ADDRESS>:49154/MediaRenderer/desc.xml
[...]

But after swyh try to communicate with the device, it use the 80 port instead of 49154. And it receives a 404 error.
[...]
17:08:31 [DEBUG] (1) ureq::stream: connecting to <IP_ADDRESS>:80 at <IP_ADDRESS>:80
17:08:31 [DEBUG] (1) ureq::stream: created stream: Stream(TcpStream { addr: <IP_ADDRESS>:52753, peer: <IP_ADDRESS>:80, socket: 1004 })
17:08:31 [DEBUG] (1) ureq::unit: sending request POST http://<IP_ADDRESS>/AVTransport/ctrl
17:08:31 [DEBUG] (1) ureq::unit: writing prelude: POST /AVTransport/ctrl HTTP/1.1
Host: <IP_ADDRESS>
Connection: close
User-Agent: swyh-rs-Rust/0.x
Accept: */*
SOAPAction: "urn:schemas-upnp-org:service:AVTransport:1#Play"
Content-Type: text/xml; charset="utf-8"
accept-encoding: gzip
Content-Length: 304
17:08:31 [DEBUG] (1) ureq::response: Body of unknown size - read until socket close
17:08:31 [DEBUG] (1) ureq::unit: response 404 to POST http://<IP_ADDRESS>/AVTransport/ctrl
17:08:31 [ERROR] <= SOAP POST error: http://<IP_ADDRESS>/AVTransport/ctrl: status code 404
[...]

I manually tried the same request but on the 49154 port, and it responds with a 200.
> curl -d<EMAIL_ADDRESS>http://<IP_ADDRESS>:49154/AVTransport/ctrl -H "SOAPAction: \"urn:schemas-upnp-org:service:AVTran
sport:1#Stop\"" -v
*   Trying <IP_ADDRESS>:49154...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 49154 (#0)
> POST /AVTransport/ctrl HTTP/1.1
> Host: <IP_ADDRESS>:49154
> User-Agent: curl/7.81.0
> Accept: */*
> SOAPAction: "urn:schemas-upnp-org:service:AVTransport:1#Stop"
> Content-Length: 327
> Content-Type: application/x-www-form-urlencoded
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: Network_Module/1.0 (WXAD-10)
< Content-Type: text/xml; charset="utf-8"
< EXT:
< Content-Length: 278
<
* Connection #0 to host <IP_ADDRESS> left intact
<?xml version="1.0" encoding="utf-8"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:StopResponse xmlns:u="urn:schemas-upnp-org:service:AVTransport:1"></u:StopResponse></s:Body></s:Envelope>%

So maybe there is a problem with the port parsing ?

Can you attach the complete debug logfile of session here? Port 80 is certainly not hardcoded anywhere in swyh-rs.
I suspect some unexpected (non-standard ?) AV-Transport data in the service description xml.

The device advertises a bad urlbase in the service description:
<yamaha:X_URLBase>[http://<IP_ADDRESS>:80/](http://<IP_ADDRESS>/)</yamaha:X_URLBase>
I'll see what I can do.

Can you try tyhe new beta ?

Perfect, with the fix it works like a charm !
Thank you very much


Feat create redux action to change task status #44

@taylorpage @mcpatte @LLo1
This PR includes adding a 'task' reducer that creates a new task and changing the status of a task, as well as new actions for those that reducer.
Please note that I have not implemented adding an updated task to the list of tasks, as I wasn't quite sure how to do that with the current "tasks" reducer. Thank you

Addressed in future pull request, will integrate addTask ideas with that code


Allow localhost graceful shutdown

#3581 Add gracefully shutdown
In Apache Aurora, it is necessary to allow a graceful shutdown on localhost.

Nice work.. ^^;
[I 201214 14:47:11 web:1811] 200 GET /health (<IP_ADDRESS>) 0.64ms
[I 201214 14:47:31 web:1811] 200 GET /health (<IP_ADDRESS>) 0.53ms
[I 201214 14:47:46 killexecutorhandler:51] Received 'Killing process' request
[I 201214 14:47:46 web:1811] 200 POST /quitquitquit (<IP_ADDRESS>) 1.08ms
[I 201214 14:47:46 killexecutorhandler:44] Killing parent executor

@thinker0 or @Code0x58 Is this PR ok to be further reviewed and merged?


Scoped scss doesn't work

Example code:
<style scoped lang="scss">
.svg-dashboard {
  &.active {
    path {
      fill: #f4a660;
    }
  }
}

Output:
.svg-dashboard.active path[data-v-f20d224e] {
  fill: #f4a660;
}

Scoped css is generating but data attribute doesn't add to path inside svg. When I paste svg code inline without loader, scoped attribute is added.

I saw that I use an old version, after update, everything works fine. An issue to deleting ;)


plotbase.make_checkplot should also output to a JSON file

Said JSON file will contain:

objectinfo
period-search info (LSP peaks, best periods, etc.)
base64 or binary representations of the LSP and LC plots

This is so a future version of checkplot-viewer can read these JSON files and generate an interactive webpage instead of just showing the checkplot PNG. The webpage should have options to mark objects as interesting, etc. and output these selections and extra metadata into another JSON file (or perhaps just use the browser localstorage).

Copied from the latest commit:
We now have a checkplot.checkplot_pickle function. This can take in lspinfo dicts from multiple period finder methods for an object, and generate a gzipped pickle containing the object info,
finder chart, mag series plot, and for each lspinfo dict: a periodogram, and phased mag series plots for up to however many 'best' peaks the user wants.
This is intended for use with the more advanced checkplot viewer to be implemented as a Tornado webapp: checkplotserver. This will also enable updating varinfo and objectinfo to set the
object's best periods and epochs, and tags based on variability type and object type.
Remaining stuff to do in checkplot.py: write a checkplot pickle file to PNG function that replicates the functionality of twolsp_checkplot_png for arbitrary number of period-finding methods. This will look something like:
[    finder    ] [  objectinfo  ] [ variableinfo ] [ unphased LC  ]
[ periodogram1 ] [ phased LC P1 ] [ phased LC P2 ] [ phased LC P3 ]
[ periodogram2 ] [ phased LC P1 ] [ phased LC P2 ] [ phased LC P3 ]
[ periodogramN ] [ phased LC P1 ] [ phased LC P2 ] [ phased LC P3 ]

for up to N independent period-finding methods producing:

periodogram1,2,3...N: the periodograms from each method
phased LC P1,P2,P3: the phased lightcurves using the best 3 peaks in each periodogram

I'll work on the checkplotserver next.

Continuing work on the checkplotserver UI. Here's what it looks like at the moment:

Working:

on-demand load of checkplot file list
on-demand load of checkplot pickle
images from checkplot pickle straight to UI via base64 decoding

Next:

adding in variability info from checkplot pickle
adding in periodograms and phased LC plots for each period-finding method in checkplot pickle
saving changes on-the-fly back to the checkplot pickle

Big fan of this. Will probably make what I'm currently running -- just eb_checkplot .pngs over the ~20 fields you've given me -- redundant. That said, the pngs may still help fine-tune cuts on the periodicity search to reduce the number of obviously-not-EBs. E.g., finding wide peaks in the periodograms from stellar rotation, finding harmonics of 1-day, cutting through things that have too-few points in the LC, etc., and then sorting appropriately. TBD!

Some more progress:

Will finish this up this weekend.

Related to this effort, checkplot_pickle is super slow when writing pickles. It takes about 3 seconds to a write one, and about 300 msec to read one in Python 3.6, and about 12 seconds to write one and about 400 msec to read one in Python 2.7. I did some profiling using ipython's %prun and it turns out the gzip function is responsible for the slow writes. Leaving this out makes the pickle write MUCH faster. It also appears that we don't save much space gzipping the pickles: 29 MB vs 35 MB for protocol v3 pickles from Python 3.6.
Profiling in Python 3.6:
In [53]: %prun with gzip.open('test.pkl.gz','wb') as outfd: pickle.dump(xdict,outfd,protocol=3)
         56 function calls in 2.386 seconds

   Ordered by: internal time

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    2.264    2.264    2.264    2.264 {method 'compress' of 'zlib.Compress' objects}
        1    0.045    0.045    2.374    2.374 {built-in method _pickle.dump}
        2    0.037    0.018    0.037    0.018 {built-in method zlib.crc32}
       11    0.026    0.002    0.026    0.002 {method 'write' of '_io.BufferedWriter' objects}
        1    0.007    0.007    0.007    0.007 {built-in method io.open}
        1    0.005    0.005    0.005    0.005 {method 'close' of '_io.BufferedWriter' objects}
        1    0.001    0.001    2.329    2.329 gzip.py:247(write)

In [55]: %prun with open('test.pkl','wb') as outfd: pickle.dump(xdict,outfd,protocol=3)
         5 function calls in 0.124 seconds

   Ordered by: internal time

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        1    0.109    0.109    0.109    0.109 {built-in method _pickle.dump}
        1    0.011    0.011    0.011    0.011 {built-in method io.open}
        1    0.005    0.005    0.124    0.124 <string>:1(<module>)
        1    0.000    0.000    0.124    0.124 {built-in method builtins.exec}
        1    0.000    0.000    0.000    0.000 {method 'disable' of '_lsprof.Profiler' objects}

Python 3.6 speed tests with gzip on:
In [18]: %timeit -n 20 with gzip.open('test.pkl.gz','wb') as fd: pickle.dump(xdict,fd,protocol=4)
20 loops, best of 3: 2.58 s per loop

In [19]: %timeit -n 20 with gzip.open('test.pkl.gz','wb') as fd: pickle.dump(xdict,fd,protocol=3)
20 loops, best of 3: 2.58 s per loop

In [20]: %timeit -n 20 with gzip.open('test.pkl.gz','wb') as fd: pickle.dump(xdict,fd,protocol=2)
20 loops, best of 3: 13.3 s per loop

In [22]: %timeit -n 20 with gzip.open('test.pkl.gz','wb') as fd: pickle.dump(xdict,fd,protocol=1)
20 loops, best of 3: 13.4 s per loop

In [23]: %timeit -n 20 with gzip.open('test.pkl.gz','wb') as fd: pickle.dump(xdict,fd,protocol=0)
20 loops, best of 3: 2.96 s per loop

Python 3.6 speed tests with gzip off:
In [12]: %timeit -n 20 with open('test.pkl','wb') as fd: pickle.dump(xdict,fd,protocol=4)
20 loops, best of 3: 296 ms per loop

In [13]: %timeit -n 20 with open('test.pkl','wb') as fd: pickle.dump(xdict,fd,protocol=3)
20 loops, best of 3: 299 ms per loop

In [14]: %timeit -n 20 with open('test.pkl','wb') as fd: pickle.dump(xdict,fd,protocol=2)
20 loops, best of 3: 583 ms per loop

In [15]: %timeit -n 20 with open('test.pkl','wb') as fd: pickle.dump(xdict,fd,protocol=1)
20 loops, best of 3: 586 ms per loop

In [16]: %timeit -n 20 with open('test.pkl','wb') as fd: pickle.dump(xdict,fd,protocol=0)
20 loops, best of 3: 382 ms per loop

Therefore, commit 8f63120fd32c7c21a05cd845ecbd33f5d5588c56 turns off the gzip for the output pickles. checkplot.checkplot_pickle was also refactored in commit d167e278ad811967df55193c70010c96ad3c2eaa to call a checkplot.checkplot_dict function, that does most of the heavy lifting and whose output could go to other (faster) serialization methods in the future.
This should make checkplotviewer.py and anything else that uses checkplot_pickle much more responsive at the cost of ~5-6 MB disk used.

Checkplotserver is done for now (modulo bugfixes). The last bit of functionality added in 5b76bb444d29bd1b3891266c7ef5321ac5d3202c:
Saving reviewed objects
Added controls for downloading CSVs and JSONs for all objects that have been reviewed and saved. These contain all the info in the objectid, comments, objectinfo, and varinfo keys.
Keyboard shortcuts
movement and editing

ctrl-right: save this, move to next checkplot
ctrl-left: save this, move to prev checkplot
ctrl-enter: done, save this and move to next checkplot
shift-enter: done, just save this checkplot, don't go anywhere
ctrl-backspace: clear variable tags and variability flag
ctrl-shift-backspace: clear all info
ctrl/shift-down: select the next phased LC in the plot tiles, set best period and epoch to those of this selection
ctrl/shift-up: select the prev phased LC in the plot tiles, set best period and epoch to those of this selection

NOTE: the navigation between phased LC plot tiles is down and then to right.
setting the variability flag
NOTE: pressing more than one of the shortcut keys below in succession appends tags to the appropriate tag lists. Repeating a tag invocation doesn't add another tag of the same type to the list.

alt+shift+v: set the flag to 'object is probably a variable'
alt+shift+n: set the flag to 'object is probably not a variable'
alt+shift+m: set the flag to 'object is maybe variable, but not sure'
alt+shift+u: unset the flag, so the variability status is unknown

tagging variables

ctrl+shift+1: planet candidate
ctrl+shift+2: RRab pulsator
ctrl+shift+3: RRc pulsator
ctrl+shift+4: starspot rotation
ctrl+shift+5: flare star
ctrl+shift+6: contact EB
ctrl+shift+7: semi-detached EB
ctrl+shift+8: detached EB
ctrl+shift+9: weird variability (should use comments box for details)
ctrl+shift+0: period harmonic (object's actual period may be a harmonic of current best period)

tagging object types

alt/cmd+shift+1: white dwarf
alt/cmd+shift+2: hot star (OB)
alt/cmd+shift+3: A star
alt/cmd+shift+4: F or G dwarf
alt/cmd+shift+5: red giant
alt/cmd+shift+6: K or M dwarf
alt/cmd+shift+7: giant star
alt/cmd+shift+8: dwarf star
alt/cmd+shift+9: blended with neighbors
alt/cmd+shift+0: weird object (used for truly strange things)


Get an issue with starting jibri controller pod

I think I have got issues with Dockerfile because the jibri pod show that the container could not be restarted (back-off)
However, running the docker build with the Dockerfile had no error.
Could you help me to solve this problem?

Look at the logs of the container to see why it is crashing on startup.

actually I could not exec to the container or get log from pod :(

You can't exec to a container that is not running. You can get the logs using kubectl though.

From your screenshot, there do not appear to be any environment variables configured for the jibri-pod-controller container. jibri-pod-controller will be logging an error about the missing environment variables on startup and then exiting.  Please have a look at the example deployment manifest in the README.

From your screenshot, there do not appear to be any environment variables configured for the jibri-pod-controller container. jibri-pod-controller will be logging an error about the missing environment variables on startup and then exiting. Please have a look at the example deployment manifest in the README.

Maybe I miss understand the documents I will add the environment to the jibri controller
Thanks for your help,


Add Common Subexpression Elimination for PsysicalExpr trees

Please note that this PR is WIP and contains the changes of https://github.com/apache/datafusion/pull/13005 and https://github.com/apache/datafusion/pull/13002 too. Once those PRs get merged only the last commit of this PR remains.
Which issue does this PR close?
Part of https://github.com/apache/datafusion/issues/12599.
Rationale for this change
As described in https://github.com/apache/datafusion/issues/12599, there is a CSE rule for logical plans already, but some projects create physical plans directly that could benefit from physical CSE.
What changes are included in this PR?
This PR:

Adds EliminateCommonPhysicalSubexprs rule to eliminate common subtrees for Arc<dyn PhysicalExpr> trees. This initial implementation targets ProjectionExec nodes only. Follow-up PR can add support for other nodes like aggregates and filters.
Adds DynHashNode trait and implements it for PhysicalExprs.
Contains some code cleanup in CommonSubexprEliminate rule.

Are these changes tested?
Added new UTs.
Are there any user-facing changes?
No.

cc @alamb, @andygrove

Thanks @peter-toth. I plan on testing this out with Comet.

@andygrove  -- since you asked for this feature, can you help figure out what to do with this PR?


chore(release): 1.9.2

1.9.2 (2020-09-10)
Bug Fixes

Change happo command to check for github user (#451) (cd0add9)

Documentation & Examples

storybook: Upgrade to 6.0.12 (#418) (65d91cc)
Improve documentation for new contributors, trussels (#402) (0849a30)

Reviewed this  git diff https://github.com/trussworks/react-uswds/compare/1.9.1...release-1.9.2


feat/size_manager

This PR includes:

The size manager setup for the application to be able to responsively draw dimensions with respect to the device screen height and width.

LGTM!


githubfs

Given a GitHub repository and access token, this filesystem will use the GitHub API to expose a read-write filesystem of the repository contents. If not given a branch, its root will contain all branches as directories.
This is for an upcoming demo to make live edits to a GitHub Pages site by modifying files in the gh-pages branch directly. Long-term versions of this will possibly actually use Git in Wanix or provide some kind of copy-on-write then manually push mechanism. For now this is just a direct file read and file replace mutable filesystem.
Although this would normally be something user configurable/mountable, that depends on working out #14. For the demo we can just use a custom build of the kernel for deployments that need this.

Btw, implementing this in Go using the net/http package will use the browser fetch when compiled to JS. And so far, making requests to just get file contents like https://api.github.com/repos/tractordev/wanix/contents/README.md doesn't seem to have CORS getting in the way.

Using https://raw.githubusercontent.com/tractordev/wanix/master/README.md will be blocked by CORS.

If not given a branch, its root will contain all branches as directories.

Perhaps instead of being configurable, this should be the default behavior. It'd simplify the implementation and UX; queries always with the branch name (e.g. master/src/main.go). Running ls in the root would list all branches. We'd also have the ability to expose a default_branch subdir, though 90% of use cases probably won't need it.

sounds fine


Unit tests for storio-common-annotations-processor module to increase code coverage from 29% to 96%

This pull request is focused on package com.pushtorefresh.storio.common.annotations.processor. Code coverage is measured using JaCoCo. This pull request increases code coverage of the storio-common-annotations-processor module 67%.

Metric
Before
After

Coverage %
29%
96%

Lines Covered
45
157

Total Lines
161
161

Please let me know if you have any questions.
Furkan
DevFactory - Code Quality Team

Hi @artem-zinnatullin, I gathered all your comments. I'll ping you when I'm done.
Have a nice day.

Thank you @furknyavuz
LGTM

Hey guys, I made new commit. Can you check it?

@furknyavuz thank you for doing this! Feel free to rebase on latest master and squash into one commit!

Everything squashed into one commit.

Thanks a lot! I'm on vacation and will try to take a look in a few days :)
On Mon, Jan 4, 2016, 22:30 Furkan Yavuz<EMAIL_ADDRESS>wrote:

Everything squashed into one commit.
—
Reply to this email directly or view it on GitHub
https://github.com/pushtorefresh/storio/pull/579#issuecomment-168744780.

--
@artem_zin

You'r welcome ;) @artem-zinnatullin

Merged as #589 (rebased, you're still author of the commit).
Thanks a lot, @furknyavuz!
@nikitin-da thanks for review :)


Adds AddTextScreen and refactors SelectChannel screen

Sorry for the big PR, this took me a little while to figure out the right way to do it.


Cast to opaque type

Hi, I would like to use custom opaque type build on top of number type, but working with opaque types seems to be problematic.
Unfortunately, it is impossible to reproduce that on http://flow.org/try because it requires more than one file (one which exports opaque type and other which imports it).
Here is my problem:
Exported types e.g. index.js.flow
export opaque type People: number = number;

Imported types e.g. index.js
import type { People } from './index';

const x: People = 10; // error
const x: People = (10: People); // error
const x = (10: People); // error (WHY THIS IS NOT POSSIBLE?)
const x: People = (10: any); // this is OK, but verbose a little

const x = ((parseInt('123', 10): any): People); // this is also OK, but looks terrible

// more problematic are function calls e.g.
function countPeople(a: People, b: People) {
  return a + b;
}
countPeople(10, 123); // error
countPeople(((10: any): People), ((123: any): People)); // THIS IS TERRIBLE TO READ and WRITE
countPeople((10: any), (123: any)); // ok, but doesn't help much in type checking

Is there any casting method which I'm not aware of?
Message in error cases is similar to this:

Cannot cast 10 to People because number [1] is incompatible with People [2].

You can reproduce this in Flow Try using declare opaque type.
I think that you may be misunderstanding the purpose of opaque types.
The entire point of opaque types is that (10: People) is supposed to
be a type error. All your examples boil down to this core fact.
Consider the following example. We can have a module nonneg.js that
defines a type of non-negative numbers. By taking advantage of opaque
types, we can ensure that every value of type NonNegative really is
not negative. Like this:
// @flow
export opaque type NonNegative: number = number;

export function asNonNegative(x: number): NonNegative {
  if (x < 0) throw new Error("negative: " + x);
  return x;
}

export function add(x: NonNegative, y: NonNegative): NonNegative {
  return x + y;
}

From another module, it is not valid to write (-10: NonNegative). The
module can interact with the opaque type only through the public API:
import { asNonNegative, add, type NonNegative } from "./nonneg";
const one: NonNegative = asNonNegative(1);
const two: NonNegative = add(one, one);

Because NonNegative is bounded as a subtype of number, it is legal
to write
const works: number = one - two;

because one and two can be upcast to number and then subtracted.
But note that the result of this subtraction is a number, not a
NonNegative, so the following is not valid:
const fails: NonNegative = one - two;  // fails to typecheck (good!)

If we could just write (10: Person) or (-1: NonNegative), we would
be defeating the purpose of opaque types: the nonneg module would not
be able to provide any encapsulation.
Again, you can reproduce this example in a Flow Try.

Many thanks for such a descriptive answer. I was looking for a way to define a millisecond timestamp type in my application to avoid providing other timestamp types (e.g. microseconds) for functions that expect exactly a millisecond timestamp.
Is it a valid use case for opaque types? If not how, is there any other construction to achieve that.
Here is an example:  Flow Try - opaque types

Depending on your constraints, another reasonable solution would be to
encode the units in the values themselves:
type TimeUnit = "SECONDS" | "MILLISECONDS" | "MICROSECONDS";
type Duration = {|+unit: TimeUnit, +scalar: number|};

If you control the implementations of all the functions that you’re
interested in, then this could be a good solution. But if you have to
interface with third-party code that expects raw numbers in particular
units, then this might be too cumbersome.

This is exactly the answer I was looking for. Many thanks for that.

Great; glad to have helped.

It sounds like flow-runtime is broken and must be fixed. :-)
(Opaque types are a pretty critical feature. It’s not heartening that
they promise “full Flow compatibility” when they’ve left this issue
unacknowledged and unattended for over three months.)

(Opaque types are a pretty critical feature. It’s not heartening that
they promise “full Flow compatibility” when they’ve left this issue
unacknowledged and unattended for over three months.)

I have recently took over development of flow-runtime project. Will prioritise fixing this. If there is any interest to contribute a PR, will happily streamline it.


Deprecated before_filter in favor of before_action

Quick & dirty fix for #756.

This change is

THis might be a good thing to do for 1.0.

@Ch4s3 maybe v1.0 should support only Rails >= 4.0? Then there's no need for this check at all, it could always use before_action

@arnvald I agree. We could release security fixes only for 0.9.x in the future and support Rails >= 4.0 for 1.0. So let's hold off on this for after we release 0.9.2.


Snap to other DnD objects or array of custom coordinates?

Imagine I want to drag a box and snap it another dnd box with-in a specific pixel range.
Is there any way to do it? In documentation there's only a solution for Snap to grid but not Snap to custom points

To achieve snapping of draggable items within a certain pixel range, you will need to implement a custom solution. dnd-kit provides a set of built-in modifiers which you can find in their repository here: https://github.com/clauderic/dnd-kit/tree/master/packages/modifiers/src
While dnd-kit doesn't offer a direct solution for snapping to custom points, you can refer to a snapping mechanism I've implemented in a previous project: https://github.com/pixelass/react-mops/blob/master/packages/react-mops/src/guides/snapping.ts#L89
Although the code might appear complex, due to additional functionalities like resizing and rotation, the core concept is straightforward:

Compare the position of the dragged item with the positions of other items.
Determine if the items should snap based on certain conditions, such as proximity within a threshold or sides and/or center

Here's a simplified function to illustrate the snapping logic on the x or y-axis:
function inRange(value1: number, value2: number, threshold: number): boolean {
  return Math.abs(value1 - value2) <= threshold;
}
const snap = {
  x: siblings.find(sibling => inRange(dragging.x, sibling.x, 10)),
  y: siblings.find(sibling => inRange(dragging.y, sibling.y, 10))
}

This function checks if the dragged ttem is within a 10-pixel range of any otherItems (siblings) on both the x and y axes. You can customize the snapping behavior by defining different rules for snapping, such as center-to-center or edge-to-edge alignment.
Note: Keep in mind that the sample codse above is just a simplified logic that does not look for the closest item but rather the first match in the collection. I hope this helps.

Here's an example to snap the dragged item to the container's center points
export function snapToCenter({
	containerNodeRect,
	draggingNodeRect,
	transform,
}: ModifierArguments) {
	if (!draggingNodeRect || !containerNodeRect) {
		return transform;
	}

	const dragging = {
		x: draggingNodeRect.left + draggingNodeRect.width / 2,
		y: draggingNodeRect.top + draggingNodeRect.height / 2,
	};
	const container = {
		x: containerNodeRect.left + containerNodeRect.width / 2,
		y: containerNodeRect.top + containerNodeRect.height / 2,
	};
	return {
		...transform,
		x: inRange(dragging.x + transform.x, container.x) ? container.x - dragging.x : transform.x,
		y: inRange(dragging.y + transform.y, container.y) ? container.y - dragging.y : transform.y,
	};
}


typeof with extended generic class

TypeScript Version:  2.4.0+
Code
interface AP {
    id: string;
}

class A<T extends AP = AP> {
    foo(a: T) { }
}

interface BP extends AP {
    n: number;
}

class B<T extends BP = BP> extends A<T> {
}

let y: typeof A;
y = B; // <<<

Expected behavior:
No errors.
Actual behavior:
Error in ts 2.4+ (in 2.3.4 no errors)
Type 'typeof B' is not assignable to type 'typeof A'.
  Type 'B<BP>' is not assignable to type 'A<T>'.
    Types of property 'foo' are incompatible.
      Type '(a: BP) => void' is not assignable to type '(a: T) => void'.
        Types of parameters 'a' and 'a' are incompatible.
          Type 'T' is not assignable to type 'BP'.
            Type 'AP' is not assignable to type 'BP'.
              Property 'n' is missing in type 'AP'.

looks like the same issue as https://github.com/Microsoft/TypeScript/issues/18387. please see https://github.com/Microsoft/TypeScript/issues/18387#issuecomment-328611169

so, you mean this behaviour correct?

@mhegazy so, you mean this behavior is correct?

yes. it is unsafe to substitute a generic constructor with one that is not generic in the general case. you can either change your base class, to be non-generic, or use --noStrictGenerics to suppress the error.

So, in this case you just can't extend React component in that simple way. Pretty common scenario but ts failed, ok :(

Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed.


Bug: Unable to open detail of package

Unable to open URL https://componette.com/vojtech-dobes/nette.ajax.js/
But this page is linked from: https://componette.com/vojtech-dobes/

Probably same as #110.

Thank you. Should be fixed.


hey i added my solutions to css-exercise could ypu merge it for me

Complete the following REQUIRED checkboxes:

[x] I have thoroughly read and understand The Odin Project Contributing Guide
[x] The title of this PR follows the location of change: brief description of change format, e.g. 01-flex-center: Update self check

Complete the following checkbox ONLY IF it is applicable to your PR. You can complete it later if it is not currently applicable:

[x] I have ensured that the TOP solution files match the Desired Outcome image

1. Because:

Closes #XXXXX
2. This PR:

3. Additional Information:

thank you for your great exercises

Hi @darkness4every, you checked off that you had read through The Odin Project Contributing Guide but looks like you might have missed this section on Exercise Repos:

Exercise Repos
Please do not open pull request (PR) with your solutions to any exercise repo. Your PR will be immediately closed without being merged. The exercise repos are for you to do and keep any work on your own local machine or your personal GitHub.


Cost sensors are created with unit_of_measurement as suffix, instead of as a prefix

Version of the custom_component
v1.1.0
-->
Configuration
# Updated 1 July 2023 for new Red Energy Rates
# Updated 1 October 2023 for new Red Energy Rates
# Updated 4 January 2024 to replace static FIT rate with a sensor that allows for use with variable FIT providers

template:
  - sensor:

#  Current_Price_RedEnergy_TOU provides a backup method to allow selecting the 'Use an entity with current rate' in Energy Dashboard.
#  If you set the prices here, remember to ALSO set them in the 'electricity_import_rate_???' and daily supply charge sensors.

    - name: "Electricity - Price"
      unique_id: electricity_price
      unit_of_measurement: "$/kWh"
      device_class: monetary
      state:  "
        {%set Peak = 0.41745 %}
        {%set WeekdayShoulder = 0.35695 %}
        {%set OffPeak = 0.26928 %}
        {%set H = as_timestamp(now())|timestamp_custom ('%-H')|float(0) %} {##Hour (24-hour clock) as a decimal number. 0, 1, 2, ... 23##}
        {%set w = as_timestamp(now())|timestamp_custom ('%w')|float(0) %} {##HWeekday as a decimal number, where 0 is Sunday and 6 is Saturday.	0, 1, …, 6##}
        {##0 for weekday, 1 for weekend##}
        {% if (w == 0) or  (w == 6) %} {% set weekday = 0 %}
        {% else %} {% set weekday = 1 %}
        {% endif %}
        {% set charge = 0 %}
        {##peak##}
        {% if (weekday == 1) and (H >= 7) and (H < 9) %} {{Peak}}
        {% elif (weekday == 1) and (H >= 17) and (H < 20) %} {{Peak}}
        {##weekday shoulder##}
        {% elif (weekday == 1) and (H >= 9) and (H < 17) %} {{WeekdayShoulder}}
        {% elif (weekday == 1) and (H >= 20) and (H < 22) %} {{WeekdayShoulder}}
        {##off peak##}
        {% else %} {{OffPeak}}
        {% endif %}
        "

#  Current FIT rate, rate 1 & 2 allows setting a second rate if variable FIT rates (i.e. $0.15 for first 10kWh, then $0.07 thereafter)

    - name: "Electricity - FIT"
      unique_id: electricity_fit
      unit_of_measurement: "$/kWh"
      device_class: monetary
      icon: mdi:cash-plus
      state: >
        {## Enter compensation per kWh rates below ##}
        {% set rate1 = 0.07 %}
        {% set rate2 = 0.07 %}
        {% set fit_exported_today = states('sensor.hs_grid_exported_daily') | float %}
        {% if fit_exported_today <= 10 %} {{rate1}}
        {% else %} {{rate2}}
        {% endif %}

####################################
# IMPORT UTILITY METERS
# See: https://github.com/zeronounours/HA-custom-component-energy-meter

# utility_meter:
energy_meter:

  hs_grid_imported_daily:
    unique_id: hs_grid_imported_daily
    name: HS Grid - Imported Daily
    source: sensor.power_meter_consumption
    source_type: from_grid
    cycle: daily
    price_entity: &electricity-price sensor.electricity_price
    tariffs:
      - peak
      - shoulder
      - offpeak

  hs_grid_imported_monthly:
    unique_id: hs_grid_imported_monthly
    name: HS Grid - Imported Monthly
    source: sensor.power_meter_consumption
    source_type: from_grid
    cycle: monthly
    price_entity: *electricity-price
    tariffs:
      - peak
      - shoulder
      - offpeak

  hs_grid_imported_yearly:
    unique_id: hs_grid_imported_yearly
    name: HS Grid - Imported Yearly
    source: sensor.power_meter_consumption
    source_type: from_grid
    cycle: yearly
    price_entity: *electricity-price
    tariffs:
      - peak
      - shoulder
      - offpeak

#########################
# EXPORT UTILITY METERS
# See: https://github.com/zeronounours/HA-custom-component-energy-meter

  hs_grid_exported_daily:
    unique_id: hs_grid_exported_daily
    name: HS Grid - Exported Daily
    source: sensor.power_meter_exported
    source_type: to_grid
    cycle: daily
    price_entity: &fit-rate sensor.electricity_export_rate

  hs_grid_exported_monthly:
    unique_id: hs_grid_exported_monthly
    name: HS Grid - Exported Monthly
    source: sensor.power_meter_exported
    source_type: to_grid
    cycle: monthly
    price_entity: *fit-rate

  hs_grid_exported_yearly:
    unique_id: hs_grid_exported_yearly
    name: HS Grid - Exported Yearly
    source: sensor.power_meter_exported
    source_type: to_grid
    cycle: yearly
    price_entity: *fit-rate

#########################
#
# GROUP - TO SUM UP THE DAILY / MONTHLY / YEARLY IMPORT KWH and $ SENSORS
#         TO GIVE A TOTAL OF EACH
#

sensor:

# DAILY
  - platform: group
    name: HS Grid - Imported Daily - Total kWh
    unique_id: hs_grid_imported_daily_total_kwh
    device_class: energy
    type: sum
    entities:
      - sensor.hs_grid_imported_daily_peak
      - sensor.hs_grid_imported_daily_shoulder
      - sensor.hs_grid_imported_daily_offpeak

  - platform: group
    name: HS Grid - Imported Daily - Total Cost
    unique_id: hs_grid_imported_daily_total_cost
    unit_of_measurement: '$'
    device_class: monetary
    type: sum
    entities:
      - sensor.hs_grid_imported_daily_cost_peak
      - sensor.hs_grid_imported_daily_cost_shoulder
      - sensor.hs_grid_imported_daily_cost_offpeak

# MONTHLY
  - platform: group
    name: HS Grid - Imported Monthly - Total kWh
    unique_id: hs_grid_imported_monthly_total_kwh
    device_class: energy
    type: sum
    entities:
      - sensor.hs_grid_imported_monthly_peak
      - sensor.hs_grid_imported_monthly_shoulder
      - sensor.hs_grid_imported_monthly_offpeak

  - platform: group
    name: HS Grid - Imported Monthly - Total Cost
    unique_id: hs_grid_imported_monthly_total_cost
    unit_of_measurement: '$'
    device_class: monetary
    type: sum
    entities:
      - sensor.hs_grid_imported_monthly_cost_peak
      - sensor.hs_grid_imported_monthly_cost_shoulder
      - sensor.hs_grid_imported_monthly_cost_offpeak

# YEARLY
  - platform: group
    name: HS Grid - Imported Yearly - Total kWh
    unique_id: hs_grid_imported_yearly_total_kwh
    device_class: energy
    type: sum
    entities:
      - sensor.hs_grid_imported_yearly_peak
      - sensor.hs_grid_imported_yearly_shoulder
      - sensor.hs_grid_imported_yearly_offpeak

  - platform: group
    name: HS Grid - Imported Yearly - Total Cost
    unique_id: hs_grid_imported_yearly_total_cost
    unit_of_measurement: '$'
    device_class: monetary
    type: sum
    entities:
      - sensor.hs_grid_imported_yearly_cost_peak
      - sensor.hs_grid_imported_yearly_cost_shoulder
      - sensor.hs_grid_imported_yearly_cost_offpeak

#######################
#
# Checks the time and based upon TOU rate times, updates the 'hs_grid_imported_daily/monthly/yearly' entities to use Peak / Shoulder / OffPeak tariff
#

automation:
### adjust the time triggers below to match when your standard electricity tariff changes (peak, shoulder, offpeak). Adjust the template in the action block as required to match your plan.
  - alias: Set Electricity Tariff
    description: 'Set Electricity Tariff (Huawei Solar) depending upon the day of week and time'
    trigger:
      - platform: time
        at: '07:00:30'
      - platform: time
        at: '09:00:30'
      - platform: time
        at: '17:00:30'
      - platform: time
        at: '20:00:30'
      - platform: time
        at: '22:00:30'
      - platform: homeassistant
        event: start
    condition: []
    action:
      - service: select.select_option
        data:
          option: >-
            {% set t = now() %}
            {%- if (( t.hour >= 7 and t.hour < 9 ) or ( t.hour >= 17 and t.hour < 20 )) and
            is_state('binary_sensor.workday_sensor', 'on') %}
              peak
            {%- elif (( t.hour >= 9 and t.hour < 17 ) or ( t.hour >= 20 and t.hour < 22 )) and
            is_state('binary_sensor.workday_sensor', 'on') %}
              shoulder
            {%- else -%}
              offpeak
            {%- endif -%}
        target:
          entity_id:
#  Selectors used by utility_meter / energy_meter
            - select.hs_grid_imported_daily
            - select.hs_grid_imported_monthly
            - select.hs_grid_imported_yearly
    mode: single

#######################

Describe the bug
Hi @zeronounours / Gauthier,
Whilst the 'cost' sensor that energy_meter creates/uses correctly shows the sensor value with the $ (or as an Australian user in my case, the A$ prefix), as per:

I note that by default any energy_meter sensors are being created with a suffix of the currency (AUD), such as:

Is there any way to get the energy_meter to create these sensors (tariff rates in this case) with the correct $ or even A$ prefix ?
Assuming this a 'bug' (more of an overlooked situation), same recently added feature for 'source_type', would there be a way to add a cost_sensor or is_currency feature (default: no) so when you set it to 'is_currency: yes' it will check the default currency sign of the HA installation (i.e. $ / £ / € etc) and prefix that on the displayed sensor value?

Hello @Roving-Ronin, the issue comes from utility_meter themselves. The unit is not showed properly because the device_class: monetary is not defined like it is for the cost entity.
The builtin utility_meter defines only energy device class, which is defined from units:
https://github.com/home-assistant/core/blob/dev/homeassistant/components/utility_meter/sensor.py#L99-L102
I can extend the builtin utility meter to prevent that. However, I doubt it is the best way to tackle this problem. I'll try to do a PR on the main component.
As a temporary workaround, you can create a template sensor which takes the same value, but for which will be able to change the class.

Hi @zeronounours
If you could PR the main (utility meter) it would be great. Just replacing utility_meter with energy_meter would be ideal ;-)
Thanks !

Hi, I'm closing it, as it was fixed in utility meter since 2024.5 (https://github.com/home-assistant/core/pull/114368). Utility meters (therefore energy meter too) now track the source entity device_class


Add ilx icon

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Add the ilx icon.
(Requested by Merrilee Benson)

Examples 🌈
No response
Motivation 🔦
No response

I added upload the svg, but I can't see it in dark mode, so here it is in a zip file.
ilx.icon.svg.zip


Apostrophe-Area-Editors objects are confusing

1eb10b0: the apostrophe-area-editors object was confusing, moved those methods onto the apostrophe-areas singleton in the browser where they make intuitive sense - Tom Boutell


[BPF/fv] fix a flake in Felix bpf test counters

We could have collected the counters before we saw the last update. We need to wait for the condition to be eventually true.
Description

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

TBD

Reminder for the reviewer
Make sure that this PR has the correct labels and milestone set.
Every PR needs one docs-* label.

docs-pr-required: This change requires a change to the documentation that has not been completed yet.
docs-completed: This change has all necessary documentation completed.
docs-not-required: This change has no user-facing impact and requires no docs.

Every PR needs one release-note-* label.

release-note-required: This PR has user-facing changes. Most PRs should have this label.
release-note-not-required: This PR has no user-facing changes.

Other optional labels:

cherry-pick-candidate: This PR should be cherry-picked to an earlier release. For bug fixes only.
needs-operator-pr: This PR is related to install and requires a corresponding change to the operator.

/merge-when-ready

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and leave the branch after I've merged it.


Next.js 13.2 new route.js support (app directory)

I realize this is bleeding edge as this won't even be released until Next 13.2, but just wanted to get the ball rolling ahead of time.
Currently, I don't see a way you can use iron-session with the upcoming route.js architecture.
My current implementation of iron-session uses withIronSessionApiRoute which requires a handler: NextApiHandler. This works for now, however, this is being removed in favor of a more generic request: Request when the pages directory goes away in favor of the app directory.
Thanks!

Would be great if iron-session could expose a hook we can use in server-componets

Next.js 13.2 is now out, dropping the link for reference:
https://nextjs.org/blog/next-13-2
Looking forward to hearing what can be done to support this, cheers!


Can't specify common name of registry certificate

Need to set external IP or FQDN to registry certificate.

Added registry_hostnames variable.

fixed in release 1.0.2


I have a simple program that just includes a file named maintenance_windows.go.
What did you see happen?
The build seems to automatically exclude maintenance_windows.go, resulting in the build failing.
Any other name works fine.
What did you expect to see?
The file would be included in the build.

Related Issues and Documentation

cmd/go: failed to build if the testdata contains broken symlinks #53305 (closed)
go compiler: file named windows.go is not being compiled #8361 (closed)
cmd/go: build failed #59694 (closed)
go/build: file name build constraints incorrect when name contains dots #46662
go tool compile #55111 (closed)
cmd/go: go build ./... may or may not write executable to disk depending how many packages the import path pattern matches #39515
go build #52634 (closed)
cmd/go: Setting up a go workspace breaks building  #57738 (closed)
cmd/go: go work causes go build to error when symlinks are involved #53343
+build tags not honored #31878 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

A file named maintenance_windows.go is only compiled when building for Windows systems.  This is documented at https://pkg.go.dev/cmd/go#hdr-Build_constraints.
If you have any further questions about this, please see https://go.dev/wiki/Questions.

@ianlancetaylor I just searched through the link you provided, but I don't see any direct reference to file naming or maintenance_windows.go. Can you point me a more specific location for the docs, or could we update the docs to make this more clear?  Thanks!

Oh nm ... I see what you mean. Any file that ends with _windows will only be compiled on windows. Thanks again.


Remove HTML from guides preview

Clean up the search results for guides by removing the html hard returns from previews.
Related to #743

Fixed.


Externalising JS

This is a large number of commits, tried rebasing and squashing - failed miserably.
This ultimately externalises all JS files, apart from report-validity which breaks github pages (any directory beginning with "repo" will prevent include_relative from working.

High level comment: I think there's great value in extracting out the JS for all of our samples. It's easier to tinker and debug in DevTools (which doesn't have adequate support for inline-JS debugging), easier to run existing JS tooling on (linting, code-style w/o extraction) and generally (imo) makes the authoring experience a lot more pleasant.
:+1: from me.

Woo! Thank you @gauntface!
Looks great to me.

Much appreciated, @gauntface! :+1:, other than that one comment.
There are a couple of in-flight samples that can be adjusted to the new format once this PR is merged.

This is a large number of commits, tried rebasing and squashing - failed miserably.
This ultimately externalises all JS files, apart from report-validity which breaks github pages (any directory beginning with "repo" will prevent include_relative from working.

javhd.com

Much appreciated, @gauntface! 👍, other than that one comment.
There are a couple of in-flight samples that can be adjusted to the new format once this PR is merged.

Woo! Thank you @gauntface!
Looks great to me.

This is a large number of commits, tried rebasing and squashing - failed miserably.
This ultimately externalises all JS files, apart from report-validity which breaks github pages (any directory beginning with "repo" will prevent include_relative from working.

High level comment: I think there's great value in extracting out the JS for all of our samples. It's easier to tinker and debug in DevTools (which doesn't have adequate support for inline-JS debugging), easier to run existing JS tooling on (linting, code-style w/o extraction) and generally (imo) makes the authoring experience a lot more pleasant.
👍 from me.


Add a comment about dotty type inference issue #702

Add a comment about dotty type inference issue #702

@VladKopanev Looks great! And if you're so motivated, you might consider filing an issue here, similar in nature to this one, so the Dotty team has a chance to fix these issues early on.

Created a dotty issue https://github.com/lampepfl/dotty/issues/6199

@VladKopanev Superb writeup! Thank you! 🙏


ext_authz: fix handling of non-UTF-8 bodies calling http_service

Commit Message: Commit 664f3fce4730544f34ae767e10150fb6be11cdc6 changed how this data is handled, but was only intended to apply when calling grpc_service.
Additional Description:
Risk Level: low
Testing: added new tests
Docs Changes: updated
Release Notes: added
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue] #27386
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest


Allow to call Transaction.sign() several times

Proposal:  make it possible to call .sign several times
tx.sign([zkAppPrivateKey]);
tx.sign([deployer]);

It will allow to call the function that signs the tx without disclosing the privateKey:
tx.sign([zkAppPrivateKey]);
await signWithDeployerKey(tx);

I guess that now the code at the addSignature prevents doing it:
https://github.com/o1-labs/o1js/blob/main/src/lib/mina/account-update.ts#L1867
Example:

the tx that requires several signatures (like deploying or creating a token account or any other custom tx)
I want to be able to apply those different signatures in the different environments:

frontend
wallet
backend
two backend environments

Specifically, I'm interested now in being able to run the code at zkCloudWorker AWS instance and provide from the zkCloudWorker to running code the possibility to sign the txs without disclosing the privateKey (as even the dust funds will be stolen sooner or later):
https://github.com/zkcloudworker/zkcloudworker-lib/blob/main/src/cloud/cloud.ts#L72
We've successfully resolved the challenge to serialize txs to move them between the various environments; now the blocker is to be able to sign the same transaction in the different environments:
https://github.com/o1-labs/o1js/issues/1221
https://discord.com/channels/484437221055922177/1228326948078489642

I'm not sure how to reconcile this use case with the changes in #1574. On one hand, the idea of a partial signature seems like a footgun without some type-level tracking (#1570). On the other hand, @dfstio has a clear use case: constructing a transaction signed by two private keys, which live in different environments. My sense is that this should be possible, but not necessarily as the "happy" path. Perhaps we could have some kind of placeholder utility.
const a = tx.prove().sign([knownPk, _("deployerPk")]) // `Transaction<true, Missing<"deployerPk">>`

This would make sense given we intend to serialize the transaction a and then hydrate it in a different environment. The hydration step would require the placeheld pk.

well, the signing code is already lying about the types. it puts a dummy signature on the account update if it needs signing but there's no private key
we could very easily enable signing twice by removing the limitation that an already signed tx can't be signed again. the Signed type just needs to get the .sign() method back, and the runtime code needs to replace the signature even if it's no longer "lazy"

Will it be enough to replace the code
    if (i === -1) {
      // private key is missing, but we are not throwing an error here
      // there is a change signature will be added by the wallet
      // if not, error will be thrown by verifyAccountUpdate
      // while .send() execution
      Authorization.setSignature(accountUpdate, dummySignature());
      return accountUpdate as AccountUpdate & {
        lazyAuthorization: undefined;
      };
    }

with
    if (i === -1) {
      // private key is missing, the sign() should be called one more time later
      return accountUpdate;
    }

at https://github.com/o1-labs/o1js/blob/main/src/lib/mina/account-update.ts#L1867 ?

no @dfstio, I'd prefer to not change that code, because that would break our model of capturing signed status with a type.
I'd rather change this code, such that it doesn't skip signing if a signature (not lazy signature) already exists and the private key matches
if (accountUpdate.lazyAuthorization?.kind !== 'lazy-signature') {
  return accountUpdate as AccountUpdate & { lazyAuthorization?: LazyProof };
}

Multiple signatures are necessary for zkApp transactions. This is especially crucial for operations such as fungible token transactions and deployments. To facilitate these operations from the browser, changes are needed on both the wallet and o1js sides to support multi-signature functionality.


Update _config.yml

Description

Type of change

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

How has this been tested

[ ] I have run bash ./tools/deploy.sh --dry-run (at the root of the project) locally and passed
[x] I have tested this feature in the browser

Test Configuration

Browser type & version:
Operating system:
Ruby version:
Bundler version:
Jekyll version:

Checklist

[x] I have performed a self-review of my code
[ ] I have commented on my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings

updating config file


Add ValidIdentityProvider condition

There's scenarios where the identity provider might have been conflicted, e.g. delete by accident. In that case the HC is not able to operate successfully e.g. aws endpoints, ec2 machines... and there's no clear signal in the HC. This is also true if the HC is in deleting state, which will hang forever with no clear signal.
This PR tries to allivites those scenarios by capturing them in a condition.
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Ref HOSTEDCP-660
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/lgtm
/retest-required

/hold
@enxebre there is a unit test failure in hypershift-operator/controllers/hostedcluster

/retest

/test e2e-aws

/hold cancel
/test e2e-aws

/test images

/hold cancel

Hey @enxebre one more thing that occurred to me while looking at this once more. I think the name of the condition might be misleading in that you can specify other identity providers for authentication which have nothing to do with the AWS OIDC one. Can we rename the condition to something like ValidOIDCIdentityProvider or ValidAWSOIDCIdentityProvider ?

/lgtm


Units in plot_spectrum, upper limits, photometry off model wavelength range, magnitude conversion, and other small things

Hello Tomas,
I gave myself a little refreshment break from another project and ran species again :smile:, now trying photometry. Here are a few issues (maybe in my understanding!) and suggestions:
1.) About units= of plot_spectrum: the y part needs to be given the units of the flux density, even if the plotted quantity is "flux" = lambda*F_lambda. This is actually practical (one needs to change only quantity, not its units too, if exploring different options) but at first surprising. Actually, could there be a units conversion issue too? I am using quantity='flux', units=("µm","erg s-1 cm-2 Å-1") in plot_spectrum and the result, comparing to a plot from someone else but also to a call without setting the units explicitly, seems to be off by 1 dex from what it should be in erg/s/cm². There seems to be the same problem when adding a spectrum for an object through add_object(…, spectrum=…, units=spec_units) (instead, I changed the units in the file externally to W/m²/µm).
2.) Currently, can it be that one can include a photometric upper limit only through flux_density ("The flux_density can also be used for an upper limit on a photometric flux, by setting the flux to zero and the uncertainty to the 1 sigma upper limit.")? Doing this with a magnitude (using e.g. 99 mag instead of zero flux) leads to plotting problems afterwards, and I am not sure whether it is used for the fit. Also, with flux_density={'filter': (0, onesigmaupplim)}, could the data point automatically be an upper limit symbol (horizontal bar + downward arrow of length 1 sigma)? Currently, it gets treated like the others.
3.) I tried using the AMES-Cond models for SDSS ugriz data. I had forgotten that the AMES-Cond spectra start at 0.5 µm and got the error:
Interpolating SLOAN/SDSS.g... [DONE]
Interpolating SLOAN/SDSS.i... [DONE]
Interpolating SLOAN/SDSS.r... [DONE]
Interpolating SLOAN/SDSS.u...---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
…
IndexError: index 0 is out of bounds for axis 0 with size 0.

Removing the u-band data (lambdaeff = 0.3546 µm) was enough to avoid the error. In hindsight, this is logical but (a) it might be useful to catch these cases at a higher level in species; actually, it could be sensible to just print a warning that the data points will be ignored, but maybe it is better to force the user not to use those data points (to avoid misunderstandings or "bad surprises"). (b) Why was there no problem with the g-band photometry, however, for which lambdaeff = 0.4670 µm < 0.5 µm?
Smaller ones:
4.) Small typo in https://species.readthedocs.io/en/latest/species.data.html#species.data.database.Database.add_object: "to the 1:math:sigma upper limit".
5.) By default, inc_spec is set to True in FitModel() even if the data do not contain spectra but only photometry; the error message is a bit obscure (TypeError: type of the return value must be dict; got NoneType instead, pointing to a line inc_spec = list(self.object.get_spectrum().keys()), from which one can guess what happened). Maybe make a warning and/or set the default to activating inc_spec only if there are such data?
6.) In the tutorial "Fitting data with a grid of model spectra", one now needs tag= in get_residuals(), and datatype='model' and spectrum=… should be removed. Note that for multi_photometry(), the parameter datatype='model' is (still) needed; maybe this is ok or maybe a very slight inconsistency.
7.) In Calculate multi-photometry (but also when preparing for model fitting), when printing the data, order the filters by wavelength within the instruments? It is weird to see the order H, J, Ks or g, i, r, u, z :nerd_face:.
8.) In plot_spectrum, you could allow 'lin' as a synonym for 'linear', and 'logarithmic' for 'log' and make default a "symmetric" pair (for instance "lin"/"log", which is conveniently short yet clear).
9.) When fitting a photosphere and a blackbody component (with 'disk_teff' and 'disk_radius' for bounds= in FitModel()), what is "R_bb" in the corner posterior plot? It is different from R_disk.
10.) Is there an easy way to convert from magnitudes in the AB system (as e.g. SIMBAD yields for SDSS data, at least in the "Basic data" section from which I copy the data by hand into the species script) to the Vega system (as species needs)? These kinds of conversions are always error-prone…
11a.) After adding several photometry for several bands (the normal way: database.add_object(… app_mag=…)), the magnitudes information printed to screen has Mean wavelength (um) = 1.2808e+01 for all bands… :).
11b.) When you correct this, could you also print on the same line the filter width used to calculate "Flux (W m-2 um-1)" (actually, this should be "Flux density)", for convenience? Often one needs actually the filter-integrated flux (e.g. in W/m²), e.g. to compare the possible contribution of an accretion line to the total filter flux.
11c.) For the magnitudes, maybe print three digits after the period because sometimes, the precision is better than 0.01 mag (so currently it gets rounded to 0.00).
12.) Add R_V (ism_red) in legend entry for the model if present in the fitting (through bounds); I looked into the source and it is not quite clear why ism_ext (A_V) does get added but not ism_red. Tiny one: I guess also the variable name prefix ism_ could be made more general… ext_val (for "value") and ext_red? But "ism_" is easy to remember.
13.) Would it be possible (well, any is possible…) and easy to allow (implicit) wildcards (as for the inflation parameters) in the filter names for in the data styles? For instance, in the β Pic b example, to have all photometry from Paranal/NACO or from GPI in the same style, one could do plot_kwargs=[{ …, 'Paranal/NACO': {'marker': 'o', 'color': 'red', …}, 'GPI_': {'marker': 's', 'color': 'blue', …}, …}] instead of listing by hand every filter. An extra nice feature would be to allow one to additionally set by hand one label for one of those filters for the legend (e.g., … 'Paranal/NACO.J': {'label': 'NACO'}, …) to have only one entry in the legend. Obviously, this is just an idea and does not have priority…
Thanks again for this great tool!
Gabriel

14a.) In Calculate residuals, a photometry point is outside the wavelength range of the models, so the flux is set to NaN, which is fine. However, right after (in the residuals part), species prints:
Number of data points = 10
Number of model parameters = 8
Number of fixed parameters = 0
Number of degrees of freedom = 2

chi2 = nan
reduced chi2 = nan

but actually I was fitting only four data points; I just wanted to plot the other data points too. I guess they should not enter the chi2 calculation.
14b.) The second, related issue is that the NaN somehow leads to ValueError: zero-size array to reduction operation maximum which has no identity, coming from max_tmp = np.max(np.abs(residuals.photometry[item][1][finite])) in plot_spectrum.py. Of course, one could set by hand which filters to include through get_residuals(…, inc_phot=…) but that will change depending on the wavelength range covered by the atmospheric models…
Thanks again!

Adding to the list (let me know if you prefer smaller-length "Issues"!):
15.) There is one extra space: In species/data/database.py at line 1560: f" correlation matrix into a covariance " → f"correlation matrix into a covariance "
16.) For FitModel, the documentation says that "With bounds=None, automatic priors will be set for all mandatory parameters" but I got an error: argument of type 'NoneType' is not iterable pointing to the  if "teff" in self.bounds part of fit_model.py:532. Same thing if doing just fit = FitModel(object_name='myPMC, model='atmo'). At least one parameter (teff or logg or…) currently needs to be set.
17.) About the output directory for fit.run_multinest(tag=…, …, output=…), the "Path that is used for the output files from MultiNest": I did not realise that one needs to put a slash at the end by hand! Otherwise the eight files per run are next to the empty directories (one of them normally hidden because it is called .txt), which is a bit of a mess. And this cannot be changed easily after the fact, right?, because all the names in the database would need to be updated too. Maybe silently (or with a warning) add a slash at the end if the user does not? This is a problem only for MultiNest. By the way, maybe the two functions run_ultranest and run_multinest could be unified to one (with n_or_min_num_live_points) with an option choosing the variant? But just an idea like that…
18.) In another list but I again ran into the issue :frowning_face:: Convert silently resolution in database.add_object() to a float? Currently: type of argument "spec_res" must be one of (float, NoneType); got numpy.int64 instead, which is a bit too strict. Keeping resolution an integer makes it easy to combine it with filenames, for instance, and one usually thinks of integer resolution, not fractional numbers…
19.) Add an option to print (i) the model name and/or (ii) the bounds and/or the (iii) the evidence and/or or some other information on the posterior plot? At least the name would be quite practical. Currently, one half of the page is free for useful information… :smiley:

Edit: I added to Nr. 11 above a suggestion to print the filter width, for convenience.

20.) Still in the category "Small tweaks": for many filters, the peak transmission is much lower than 100% (e.g.: SDSS/z, peaking at 8%), but the transmission subplot always goes to 1, so that the profile can be hard to see. Add the option of automatically adjusting the ymax to the maximum of the visible curves (plus a little margin, of course, to avoid the curve touching the top axis)?

type: feature, priority: low

[ ] 2.) Currently, can it be that one can include a photometric upper limit only through flux_density ("The flux_density can also be used for an upper limit on a photometric flux, by setting the flux to zero and the uncertainty to the 1 sigma upper limit.")? Doing this with a magnitude (using e.g. 99 mag instead of zero flux) leads to plotting problems afterwards, and I am not sure whether it is used for the fit. Also, with flux_density={'filter': (0, one_sigma_upper_limit)}, it could be meaningful to let the data point be by default an upper limit symbol (horizontal bar + downward arrow of length 1 sigma); currently, it gets treated like the others.

[ ] 3.) I tried using the AMES-Cond models for SDSS ugriz data. I had forgotten that the AMES-Cond spectra start at 0.5 µm and got the error:

Interpolating SLOAN/SDSS.g... [DONE]
Interpolating SLOAN/SDSS.i... [DONE]
Interpolating SLOAN/SDSS.r... [DONE]
Interpolating SLOAN/SDSS.u...---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
…
IndexError: index 0 is out of bounds for axis 0 with size 0.

Removing the u-band data (lambdaeff = 0.3546 µm) was enough to avoid the error. In hindsight, this is logical but (a) it might be useful to catch these cases at a higher level in species; actually, it could be sensible to just print a warning that the data points will be ignored, but maybe it is better to force the user not to use those data points (to avoid misunderstandings or "bad surprises"). (b) Why was there no problem with the g-band photometry, however, for which lambdaeff = 0.4670 µm < 0.5 µm?

[ ] 13.) Would it be possible (well, any is possible…) and easy to allow (implicit) wildcards (as for the inflation parameters) in the filter names for in the data styles? For instance, in the β Pic b example, to have all photometry from Paranal/NACO or from GPI in the same style, one could do plot_kwargs=[{ …, 'Paranal/NACO': {'marker': 'o', 'color': 'red', …}, 'GPI_': {'marker': 's', 'color': 'blue', …}, …}] instead of listing by hand every filter. An extra nice feature would be to allow one to additionally set by hand one label for one of those filters for the legend (e.g., … 'Paranal/NACO.J': {'label': 'NACO'}, …) to have only one entry in the legend. Obviously, this is just an idea and does not have priority…

Thanks again for this great tool!
Gabriel


RDKit Recipe

This PR adds a recipe for rdkit makes some minor modifications to the standard conda-rdkit recipe at https://github.com/rdkit/conda-rdkit (addresses #381). Namely,

The hard-coded requirement for boost == 1.56.0 is removed.
A passing test suite is no longer required for a successful build (I've noticed that one test out of 81 can be quite flaky, and I've been disabling it in practice)

The Travis-CI builds fail because they run out of time. @rmcgibbo @jchodera: Have either of you run into similar issues in the past?

I haven't had a build timeout like this before.

It looks like it almost finished -- it was tarring up the final result when it died, I think, so maybe it'll just get lucky and finish next time.
Adding the parallel make flag might also be enough to get it over the edge.
Alternatively, you might be able to package the AvalonTools and Inchi separately, and then have then as build-dependencies, so that each build was lighter. But that's a hassle.
The build could be run manually and uploaded. With the new linux docker setup, you get the same exact build environment if you run this command on your machine, or if it runs on travis, since it's containerized.

Ok, I've changed make to use make -j $CPU_COUNT. I'm hoping this caries the build through travis. If it doesn't, then I'll move this PR over to docker.

Here's the OS X linker failure.
Undefined symbols for architecture x86_64:

  "boost::archive::basic_text_iprimitive<std::istream>::~basic_text_iprimitive()", referenced from:

      RDKit::FilterCatalogParams::initFromStream(std::istream&) in FilterCatalog.cpp.o

      RDKit::FilterCatalog::FilterCatalog(std::string const&) in FilterCatalog.cpp.o

      boost::archive::text_iarchive::~text_iarchive() in FilterCatalog.cpp.o

      boost::archive::text_iarchive::~text_iarchive() in FilterCatalog.cpp.o

      RDKit::FilterCatalogEntry::initFromStream(std::istream&) in FilterCatalogEntry.cpp.o

      boost::archive::text_iarchive::~text_iarchive() in FilterCatalogEntry.cpp.o

      boost::archive::text_iarchive::~text_iarchive() in FilterCatalogEntry.cpp.o

      ...

  "boost::archive::basic_text_oprimitive<std::ostream>::~basic_text_oprimitive()", referenced from:

      RDKit::FilterCatalogParams::toStream(std::ostream&) const in FilterCatalog.cpp.o

      RDKit::FilterCatalog::Serialize() const in FilterCatalog.cpp.o

      boost::archive::text_oarchive::~text_oarchive() in FilterCatalog.cpp.o

      boost::archive::text_oarchive::~text_oarchive() in FilterCatalog.cpp.o

      RDKit::FilterCatalogEntry::toStream(std::ostream&) const in FilterCatalogEntry.cpp.o

      boost::archive::text_oarchive::~text_oarchive() in FilterCatalogEntry.cpp.o

      boost::archive::text_oarchive::~text_oarchive() in FilterCatalogEntry.cpp.o

      ...

ld: symbol(s) not found for architecture x86_64

clang: error: linker command failed with exit code 1 (use -v to see invocation)

@rmcgibbo: Where did you get the failing linker output?
The travis link says that the OS X build ran, while the linux build again runs out of time (see https://travis-ci.org/omnia-md/conda-recipes/builds/90001408).  The linux build seems to fail since the rdkit test tries to rebuild rdkit(!). I'll try disabling tests and seeing if the build completes

Click "download log" near the upper right of the output box. Links to: https://s3.amazonaws.com/archive.travis-ci.org/jobs/90001410/log.txt

No, the test did not try to rebuild RDKit. Actually the build looks like it worked just fine on linux.

The apparent problem is just that the PR is trying to build the recipe for multiple different versions of Python (27, 34, 35). It finished the first build, but couldn't make it through the second or third.

And that's totally okay, because we can merge it, and I can just hit "restart" a couple times, and within a day, we'll have all of the versions built and uploaded.

Ah, I see. In that case, let me re-enable tests for rdkit before we merge changes.
For the MAC linker error, this seems to be linked to boost 1.59.0 (see https://trac.macports.org/ticket/48717). I don't have a MAC handy, so this one is a little tough to debug though.

Okay. Can you just disable mac and windows then? The syntax is like this: https://github.com/omnia-md/conda-recipes/blob/master/subprocess32/meta.yaml#L10-L12

Ok, I've disabled osx/windows builds for now. It would be nice to get these back in later though, but I'll have to get access to an OSX/Windows machine for testing first.

Yeah. The windows one would be (in part, at least) fixed by pulling from http, not git, but there could be other downstream problems too.


Should Temporal objects  be polyfilled into the global namespace?

Currently, this polyfill requires import-ing or require-ing to use. Another option could be to polyfill Temporal into the global namespace.
https://github.com/tc39/proposal-temporal/issues/778 has discussion about why we didn't do this so far.
But as browsers start shipping Temporal, it may make sense to have this polyfill more closely match built-in behavior.

So long as the existing module is still available I do think it would be more convenient for most users to automatically assign to the global Temporal symbol.
That being said, I'd strongly prefer this assignment be done separately from the module defining the Temporal namespace object, so that it can still be treated only as a module without having the side-effect of polluting the global namespace.


When choose 'not selected' availability zone to deploy, backend not return error, deploying status always show deploying.

polling 3 minutes:

backend always polling , the status not be changed.

polling 6 minutes:

@Alice1319 i cannot reproduce this issue. can you please attach the complete server log?
sure

@Alice1319 is this problem still there, otherwise we can close this issue ?

not reproducible


No redirect for /spenden

Resolves the bug that /spenden is redirecting to /21565/spenden because there is still an old page. Due to the new alias system a redirect would be triggered. It also implements the logic that /spenden is treated like /search (where the cookie determines the backend).

@kulla Ready for merge, have implemented your code suggestion in a new PR. Feel free to merge :smile:


Get IntermediateOutputPath from csproj

This change will use the $(IntermediateOutputPath) from the evaluated target csproj to determine the location of the TargetPath if no [-t, --TargetPath] argument is provided.
This change does cause the output to display the full path to the csproj and output folders now instead of relative paths.
Microsoft Reviewers: Open in CodeFlow

since my last approval there have been some non-trivial changes, I would like to test the pr's behavior locally before we merge this in.


Stationary and Non Stationary objects

@niosus @stachnis @ovysotska @tano297  Hi team thanks for sharing the code base , just wanted to  know if we can object segments of stationary objects like builidings lampost trees and non stationary objects from the  current code base, if so can you let us knw the process and the type of data since i want to try it other dataset and custom dataset !!!!!

This is not possible in this code. This code just performs the segmentation. You would need to write a tracker that would estimate if the clusters generated by this code represent a moving or a static object.


url for website to visit

doesn't seem to want to get an actual url and I didn't specify one, maybe can try too but should work without like going to google and searching etc

it seems if you specify it does pick it up in the end, I guess google is a good start ahh
`CRITICISM:  I need to make sure that I am browsing the website efficiently and not wasting time on irrelevant pages. I also need to ensure that I am analyzing the website's code and performance regularly to identify areas for improvement.
NEXT ACTION:  COMMAND = browse_website ARGUMENTS = {'url': '<website_url>', 'question': "What is the website's current monetization strategy?"}
Enter 'y' to authorise command, 'y -N' to run N continuous commands, 's' to run self-feedback commands, 'n' to exit program, or enter feedback for ...
Asking user via keyboard...
Input:url is www.google.co.uk
SYSTEM:  Human feedback: url is www.google.co.uk
THOUGHTS:  It seems like the website we are analyzing is Google. Since we cannot interact with Google's search results page, let's use the 'get_text_summary' command to get a summary of the website's content and analyze it for monetization opportunities.
REASONING:  Since we cannot interact with Google's search results page, we need to find an alternative way to analyze the website's content for monetization opportunities. The 'get_text_summary' command will allow us to extract relevant text from the website and analyze it for monetization opportunities.
PLAN:

Use the 'get_text_summary' command to get a summary of the website's content and analyze it for monetization opportunities.
Use the 'analyze_code' command to analyze the website's code and identify areas for improvement.
Use the 'write_to_file' command to save the website's code to a file for future reference.
Use the 'execute_python_file' command to run scripts that implement and optimize
various monetization methods such as display advertising, affiliate marketing, and
sponsored content.
Use the 'get_hyperlinks' command to find new monetization opportunities by extracting hyperlinks from the website's content.
CRITICISM:  I need to make sure that I am analyzing the website's content efficiently and not wasting time on irrelevant text. I also need to ensure that I am analyzing the website's code and performance regularly to identify areas for improvement.
NEXT ACTION:  COMMAND = get_text_summary ARGUMENTS = {'url': 'https://www.google.co.uk/', 'question': 'What are the monetization opportunities on this website?'}
Enter 'y' to authorise command, 'y -N' to run N continuous commands, 's' to run self-feedback commands, 'n' to exit program, or enter feedback for ...
Asking user via keyboard...`


Slow loading when scrolling

As lazy defined images seem to have some kind of delay when coming into view. The behaviour seems to be the same as described on https://github.com/aFarkas/lazysizes/issues/434 but I encountered it in current Chrome, Firefox and Safari on Mac and IE11. The following is an example video from IE11. Also note, that the images repeat (same source) but still don't show instantly. The server is local and responses very fast.

Also note, that when additional images are loaded a certain amount is loaded, then nothing happens again for a few seconds. Looking at the source I think you only load a certain amount of images at a time? Could this probably be made configurable, since it depends on use case?
Also note:

The images are <picture> elements
We also use picturefill to support IE11

We are experiencing same effect but sometimes is faster:
https://kavehome.com/pt/pt/moveis <= little bit faster
https://kavehome.com/pt/pt/s/ralf/ <= secuencial

Hello,
@aFarkas
I have also same issue in Iphone  and safari device .
when ever load my page then image is too slow loading.

Hello,
@aFarkas
I have also same issue in Iphone and safari device .
when ever load my page then image is too slow loading.

give test case or it didnt happen

Hello

Hello,
@aFarkas
I have also same issue in Iphone and safari device .
when ever load my page then image is too slow loading.

give test case or it didnt happen

Ahahah I understand.
Basically, the issue that I'm facing is that if the webpage is opened up for the first time in any system (i.e. images aren't in browser cache), then the images take too long to load. As with lazysizes, first content gets rendered and then the image. However, the images take too long to load.
Moreover, this is not a configuration issue, as this issue only occurs with the iOS devices i.e. safari browsers. If we do the same operation in other devices or browsers then the outcome is correct.
Hope this provides you some clarity on the issue that I'm facing. Any help is highly appreciated.
Regards,
Pankaj C.

Hello

Hello

For anyone stumbling up on this ticket somewhen: we finally fixed this problem when we worked on an other ticket and realized that we wrongly applied lazyloading classes to source elements on our page. This caused a mayor slow down on the script execution.

Thank you, @patric-eberle! Just been tearing my hair over this – your comment saved me, 4 years down the road 😄


mismatch between gemspec version and rubygems.org

There have been 3 versions published to rubygems.org (1.4.0, 1.4.1, 1.4.2) since 1.3.13 (which is the current listed version in the gemspec here).  Was updating the gemspec just missed?

The gemspec is automatically generated from the Hoe spec in the Rakefile, and was not updated.
It will be updated for the upcoming 1.4.3 release.


Bug fix/ui collection 404

Pull Request Guidelines
Scope & Purpose
In case a document got requested via the UI of a collection which does not exist, the UI now properly displays an error view instead of having a bad display state.

[x] Bug-Fix for devel-branch
Backports for all supported versions needed.

Related Information

[x] There is an internal planning ticket: https://arangodb.atlassian.net/browse/BTS-94

Testing & Verification
This change is a trivial rework / code cleanup without any test coverage.

http://jenkins01:8080/view/PR/job/arangodb-matrix-pr/10722/


fix(filedrop): support multiple tries with same file

Summary

fix, FileDrop drag and drop wouldn't trigger the upload on the second drop of the same file if we used the upload button
feat(EditPage): add isLoading styles to the EditPage

Acceptance Test (how to verify the PR)

Verify in the FileDrop story that you can upload files and it always triggers the onData action even without clearing the files
Verify the new isLoading Edit page stories

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-beta.9 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.69.2 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


Update @whatwg-node/fetch to avoid punycode deprecation warning in Node

Is your feature request related to a problem? Please describe.
It looks like this package is using an old version of @whatwg-node/fetch. After upgrading to Node v22.0.0, I see warnings about punycode being deprecated. The source is graphql-codegen.
Describe the solution you'd like
Upgrade @whatwg-node/fetch to the latest version.
Describe alternatives you've considered
No response
Is your feature request related to a problem? Please describe.
punycode is deprecated but used by old versions of @whatwg-node/fetch.

Have you tried to update your lockfile?

This issue doesn't have anything to do with the lockfile.
Very simple reproduction steps:

Make an empty directory
run node --version and confirm node is version 22.0.0 or newer
run npm init -y to create package.json
run npm install -D @graphql-codegen/cli @graphql-codegen/typescript @graphql-codegen/typescript-resolvers
run npx graphql-code-generator init

The punycode warning appears immediately:
npx graphql-code-generator init
(node:2916) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

This same warning appears when running graphql-codegen

I think this actually breaks on node 22.4.x the watch mode when running codegen.

Seeing the same issue

It looks like there is a dependency for @whatwg-node/fetch that is out of date which is depending on punycode. Perhaps all that is needed is to update that dependency?

Can anything be done about it? It's currently stopping us from using watch mode as it breaks on node 22.x.

same am I ,
npm ls punycode
+--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>|   --<EMAIL_ADDRESS>|     --<EMAIL_ADDRESS>|       --<EMAIL_ADDRESS>it  looks like cause by  the dependency of<EMAIL_ADDRESS>

Here's the related fast-url-parser issue: https://github.com/petkaantonov/urlparser/issues/20

Ah, looking at the dependencies, it seems like @whatwg-node/fetch is using a different url parser (https://github.com/kamilkisiela/fast-url-parser) with its most recent version 0.9.20 but we're currently depending on 0.8.0. So, I think upgrading @whatwg-node/fetch is the right move here.

is there any update? is the codegen team going to release a new version with support for node 22 packages?

Is your feature request related to a problem? Please describe.
It looks like this package is using an old version of @whatwg-node/fetch. After upgrading to Node v22.0.0, I see warnings about punycode being deprecated. The source is graphql-codegen.
Describe the solution you'd like
Upgrade @whatwg-node/fetch to the latest version.
Describe alternatives you've considered
No response
Is your feature request related to a problem? Please describe.
punycode is deprecated but used by old versions of @whatwg-node/fetch.

Looks like this has been fixed in this commit https://github.com/dotansimha/graphql-code-generator/commit/e0092b548f51c95be19c232515cf9a72873e7b83
So now we're just waiting for a release!

Hi all, https://github.com/dotansimha/graphql-code-generator/pull/10076 has been merged so could you please check if the released versions work as expected?


How to generate random value from given list?

Support I want to generate a car lists with random brand. But brands are from my given list.
Can I do that in your autofixture?

You can try using the ChoicesGenerator (https://github.com/gregmuellegger/django-autofixture/blob/master/autofixture/generators.py#L230), like this:
from models import YourCarModel
from autofixture import generators, register, AutoFixture

class YourCarModelAutoFixture(AutoFixture):
    field_values = {
        'brand': generators.ChoicesGenerator(values=your_list_of_brands),
    }

register(YourCarModel, MyModelAutoFixture)


New version: Libtask_jll v0.4.0+0

Autogenerated JLL package registration

Registering JLL package Libtask_jll.jl
Repository: https://github.com/JuliaBinaryWrappers/Libtask_jll.jl
Version: v0.4.0+0

[noblock]
This version of Libtask_jll is only compatible with Julia 1.3: https://github.com/JuliaPackaging/Yggdrasil/blob/a9bd57bc8e0899c26b1a1432cda9689f5c100ef7/L/Libtask/build_tarballs.jl#L68 I assume this causes the automerge problems?

@devmotion BTW have you already tested whether it really works there? For libcxxwrap_julia_jll, our 1.3 binary does not actually work on macOS (see discussion on https://github.com/JuliaPackaging/Yggdrasil/pull/2106)

No, I was about to check it when I realized that it is not available in the registry. BTW that's also why I haven't opened any of the subsequent PRs to Yggdrasil yet.

You can test it already now w/o needing to wait for the registry: you can add URL the JLL repository

Thanks for the tip! I just tested it and all tests passed :slightly_smiling_face:

I noticed that it is even possible to load it with Julia > 1.3. I would have assumed that this would error but instead Pkg just prints
julia version requirement for package `Libtask_jll [3ae2931a]` not satisfied

Maybe it's since I added the JLL repo manually?


[<IP_ADDRESS>] Creating Work Breakdown Structure

Description
Creating a Work Breakdown Structure (WBS), to define and organize the work required for M2, M3 and the remainder of M1.
Success or Completion Criteria

An image of our WBS in here and our report.

Allocated Time
7 Days.
Start Date: 10/09/23, 2200
End Date: 17/09/23, 2359

Wrote a draft of the WBS which contain the outlines of the main activities.

Created an initial WBS using lucidchart.

Reformatted the WBS to ensure that it can fit within a single page whilst maintaining readability.

Updated the numbering of the tasks in the WBS.

Issue Comments
Description
Completed the WBS and added it into the report.
Changes to success or completion criteria? y/n (if y, describe)
n
Start Date: 11/09/23, 1000
End Date: 17/09/23, 1800


Cow: Blacklist accountingadvice.co

Cow requests the blacklist of the website accountingadvice\.co. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

accountingadvice\.co has been seen in 5 true positives, 0 false positives, and 0 NAAs.


Edit polygon does not take care of allowIntersection

When drawing a polygon, the option allowIntersection appears to work correctly.
But thereafter when I edit the polygon the option allowIntersection does not work as expected, I mean on edit polygon I am able to intersect the lines which is not correct and expected as long as I set in draw to explicit not allow this !

same here

You have to set in the options.
let options = {
    edit: {
        poly: {
            allowIntersection: false
        }
    }
}

I set it in Edit.Poly.js
I modified a little bit to use drawError here
L.EditToolbar = L.Toolbar.extend({
     statics: {
       TYPE: "edit"
     },
     options: {
       edit: {
         selectedPathOptions: {
         }
       },
       remove: {},
       poly: {
         allowIntersection: false,
         drawError: {
         }
       },
       featureGroup: null
     },
     ....
   }


Move test_resources into tests/resources

Resolves #27

Coverage remained the same at 85.208% when pulling bca29f8710a893b666ec4abe79a4fa48bea68170 on test/move_resource_dir into 1aff504485a21bdf627543f8a4c6b0dc9ca61830 on master.

@jslee02 Feel free to merge at will.

Coverage remained the same at 85.208% when pulling 58f79cdb7b2b7df96b255b03f237cf1d7465fa3d on test/move_resource_dir into bc5308261b8ff3d209d2726ac2d95e8181f16488 on master.


Performance of provided FPointNet

Hello, xinzhuma.
Thanks for your great work of patchnet. I noticed that you also provide your realization of FPointnet and PseudoLiDAR in your repository. And I try to run both of two only for test. The results of FPointNet are a little different from official code of FPointNet.
Did you test your realization of FPointNet, and can you give your results on KITTI val set for reference? Thanks a lot.

The default setting in provided codes is different from that in FPointNet's official repo, especially for the training schedule. We use some different hyper-params for faster convergence. For pseudo-LiDAR, it can accelerate training and get the same or better results, while the performance of FPointNet is slightly reduced. If you want to reproduce the performance reported in the FPointNet paper, you can try to adjust the training schedule.


feat: remove the change ID from the PR description

The change ID is stored in the commit message and in the GitHub HEAD branch name. We can remove it from the pull request description to make it prettier.
Change-Id: I56e44be6d6aff6de89d80e1f649568c2c199406c
Depends-On: #334

This pull request is part of a stack:

test: add coverage on PR content (#334)
feat: remove the change ID from the PR description (#335) 👈
test: abstract commits with GitMock (#336)


Questions about the theory in the mausctript

Hi!
Thanks for the valuable research about Heteropyily and Oversmoothing in GCN.
I am aware of some questions about the manuscript, could I communicate with you,
for instance, about the metric's define of 'Relative Degree' at the initial layer, and the 'effective relative degree' .  For the initial layer, all neighbor nodes j are considered. However, for deeper layer l, only the positively neighbor nodes j are considered. Why are negative contributing neighbors not considered in Deeper Layer, but considered in the initial layer?

and the second question,
at Section3.3.4 in the manuscript, about 'Relation between the problems' for '(2)-In homophilous graphs',  why the homophilous graph have node's label is 'Class 2' ?    Shouldn't the nodes of the homophilous graph all be of the same label 'Class 1' ?

and the third question.
as the layer be deeper, the i node's 'effective homophily' would get lower?
thanks

and the fouth question.
At the Equ(41), The symbol in the red box should be a minus sign？

Thanks for your interest in our paper.

For both initial and deeper layers, we consider positive and negative contributing nodes. In our proofs (A.1 and A.2), we use whether a neighbor's representation at k-th layer contribute positively or negatively as the condition, and decompose the total expectation into the sum of conditional expectations, e.g. (Eq. 12 and second equality in Eq. 34).

You are right that in heterophilous graphs, most nodes belong to class 1 (e.g., table 3, Texas, Wisconsin, Actor & Cornell). However, in some real datasets (e.g. table 3,  Squirrel & Chameleon), we also found non-neglectable # of nodes in class 2. That's  why we analyze the phenomenon in heterophilous graphs by considering both nodes in class 1 and class 2.

yes, the effective homophily will get lower in heterophilous graphs. We have experiments provided in the appendix to show that: table B.3

It should be a + here because the two negative signs offset each other in equation 40. And the total expectation (equation 41) should be a sum of equation 39 and equation 40. That's why we have a positive sign instead of negative sign there

Thanks for your interest in our paper.

For both initial and deeper layers, we consider positive and negative contributing nodes. In our proofs (A.1 and A.2), we use whether a neighbor's representation at k-th layer contribute positively or negatively as the condition, and decompose the total expectation into the sum of conditional expectations, e.g. (Eq. 12 and second equality in Eq. 34).

Thanks for your response. And i have learned the appendices except A.4.
The reply for my questions 2-4 are well understood. And i have learned the appendices except A.4)
For the Question 1:
1.1- How to define 'positive contribution' or 'negative contribution'? Is it based on the label after classification? Is it mentioned in 'B.3 Measurement of effective homophily'?

1.2- the positive and negative contributing nodes are indeed considered in proofs (A.1 and A.2). However, for the definitions of 'relative degree' , the range of j is the i node's neighbor, but why in the 'effective relative degree' of 3.3.2 (2), the domain of j is only the positive neighborhood?  What is the theoretical  basis of the definition of 'effective relative degree'? Is it a subjective variable that matches proof A.2 ?

I have a preliminary understanding of most theories about appendices (except A.4). But I still have some doubts. and I hope you could support me. Sorry to have troubled you.
5.1- In 3.3.4 "Oversmoothing problem", Case1 and Case2 trigger over-smoothing?  What is the definition or quantification of over-smoothing?
5.2- In this article, over-smoothing means that 'effective homophily' is reduced to a lower limit(in other papers, the over-smoothing problem is more about the Dirichlet energy)?  What is the connection or difference between 'effective homophily' and 'Dirichlet energy'?

In 3.3.4, The node of Case2 transforms into Case1 in deep layers, resulting in 'pseudo-heterophily'.
However, if the homophily h=1 graph data is taken into account, namely only Class1 in graph data. Is there still 'pseudo-heterophily'? If not, why is GCN still too smooth on homophily h=1 graph data ?

7-1 In 3.3.3, 'the movement of representations towards the other class' is it Case2?
7-2 In 3.3.3, What is the meaning of 'opposeite classes swap places', can there be A general, summative conclusion, rather than having to refer to the theoretical reasoning of A.4.

8.1- In 4.1, formula 7 represents the weighting of messages on different nodes (i.e., giving edge weights τ), why was the definition of the relative degree of 'Thm 3.1' changed? Is this mathematically equivalent to putting τ in the formula 14?

9.1- In 4.1, for the 'Strusture-based Edge Correction', since λ0 and λ1 are obtained by learning, how to ensure that formula (8) satisfies to 'Intuitively, when r is small, we would like to compensate for it via a larger τ '? Just because the r of formula (8) is in the denominator?

10.1- In A.1.Proof of Theorem 3.1, Is the symbol in the gray part of the figure a negative sign?

10.2- Formula (51), whether the gray part should have a u?

10.3- Formula (27), whether the gray part should be fj?

I wonder whether I have the honor to have your contact information? e.g. chat app or others


Fix the reported line/column for syntax errors.

As reported at eventualbuddha/decaffeinate#54, CoffeeScriptRedux syntax errors always point to line 1 column 1. This is very annoying when trying to figure out what part of the file it actually can’t parse. This updates the peg override to match the new signature for peg$computePosDetails which now takes a pos argument.

Yeah, unfortunately this hack is the most fragile part of the compiler (see the comment above). Thanks for fixing it. I wish we had a better way.