::1 should pass IPv6 validation

Version 3.34.0
I'm getting that ::1 is not a valid IPv6 address, but this is a valid address for localhost:
http://en.wikipedia.org/wiki/Localhost#Name_resolution
https://github.com/json-schema/JSON-Schema-Test-Suite/blob/develop/tests/draft4/optional/format.json#L96-L98

Can you provide steps to reproduce?
In test/validators.js#L333, ::1 is explicitly checked for being a valid address, and the test works both in 3.34.0 and current master.
(I’m commenting on this because I recently re-wrote the IPv6 address validation code, so if this does not work propery, it’s probably my fault)

Oh, sorry my bad. I've messed up something with the packages in my repo. All good here.

Ok, great :)


Cleanup  script "Make clean"  is not removing /opt/dev-scripts directory

[#Minor] Make Clean script is not removing /opt/dev-scripts directory .
Though this issue is minor one.
When I tried to re-run the make script with user "user2" my installation fail as user2 does not have permission to write files inside /opt/dev-script/ironic folder ,as this folder is owned by pervious user "bkr"
"make" failed with error message:
Writing manifest to image destination
Storing signatures
63c4f7bb2f7917d7397796f2e12dd36a8e6920a8c66716307f36afd55debb6ae
+ pushd /opt/dev-scripts/ironic/html/images
/opt/dev-scripts/ironic/html/images ~/dev-scripts
+ '[' '!' -e rhcos-410.8.20190410.0-compressed.qcow2 ']'
+ '[' '!' -e rhcos-410.8.20190410.0-compressed.qcow2.md5sum -o rhcos-410.8.20190410.0-compressed.qcow2 -nt rhcos-410.8.20190410.0-compressed.qcow2.md5sum ']'
+ ln -sf rhcos-410.8.20190410.0-compressed.qcow2 rhcos-ootpa-latest.qcow2
ln: cannot remove ‘rhcos-ootpa-latest.qcow2’: Permission denied
make: *** [ironic] Error 1

Content of this directory are:
ls -l /opt/dev-scripts/
total 8
drwxrwxr-x. 4 **bkr  bkr**    34 Apr  2 14:57 ironic
-rw-r--r--. 1 root root 3865 Apr 11 19:20 ironic_nodes.json
drwxr-xr-x. 2 root root  210 Apr 12 14:02 pool
-rw-r--r--. 1 root root  222 Apr  2 14:50 volume_pool.xml

Attaching the host_cleanup logs.
host_cleanup-2019-04-12-142513.log

IMHO this isn't a bug, we deliberately don't remove $WORKING_DIR or you'd have to download multi-gigabyte qcow2 files every single test iteration.
Sounds like you changed users after the initial run, so some manual cleanup seems acceptable in that case, if the alternative is causing every other user to spend more time/bandwidth during testing?

I guess the alternative in common.sh is to change this:
if [ ! -d "$WORKING_DIR" ]; then
  echo "Creating Working Dir"
  sudo mkdir "$WORKING_DIR"
  sudo chown "${USER}:${USER}" "$WORKING_DIR"
  chmod 755 "$WORKING_DIR"
fi

to
if [ ! -d "$WORKING_DIR" ]; then
  echo "Creating Working Dir"
  sudo mkdir "$WORKING_DIR"
fi
sudo chown -R "${USER}:${USER}" "$WORKING_DIR"
chmod 755 "$WORKING_DIR"

I'm going to close this as I think the recursive chown is likely to break things where we've got existing files owned e.g by root and not $USER.  In the case where you choose to switch to a different non-root user I think it's acceptable to do some manual cleanup.


Different behaviours between remix dev/build and vite dev/build

What version of Remix are you using?
2.2.0 (also tested with the latest commit on the dev branch)
Are all your remix dependencies & dev-dependencies using the same version?

[X] Yes

Steps to Reproduce
There are steps to reproduce in this repo: https://github.com/mrm007/remix-vite-vanilla-repro
There's also a branch where I tested with a snapshot of @remix-run/dev: https://github.com/mrm007/remix-vite-vanilla-repro/tree/with-remix-snapshot
Expected Behavior
CSS defined via Vanilla Extract to be extracted the same way as it works with remix build.
Actual Behavior
See reproduction repo for all the details.

Thanks for comprehensive reproduction!
I experimented with your repro and it seems there are two issues with current vite build.
The 1st issue is on remix plugin side, which is similar to what I mentioned before in https://github.com/remix-run/remix/issues/7901#issuecomment-1793262909 (and partially workarounded by https://github.com/remix-run/remix/pull/7911).
Currently, remix vite plugin potentially "mutates" other plugins in an unusual way, and in this case, @vanilla-extract/vite-plugin seems to be affected by this.
(I'm currently experimenting with a PR to fix this issue in https://github.com/remix-run/remix/pull/7990. I'll put a further note there since I think it's mostly about remix internal and @vanilla-extract/vite-plugin is not doing anything wrong.)
The 2nd issue is that your package.json has "sideEffects": false. Probably vite/rollup is more strict about this (compared to non-vite remix), so to make import "./global.vanilla.css" (which actually resolves to global.vanilla.css.ts) contribute to build output, removing "sideEffects": false seems necessary.
Still my investigation is in progress and also I didn't have any experience with vanilla extract, so I could be missing.
I'll make a PR on your repository with fixes, so that you can also confirm if it works as expected.

@hi-ogawa thanks for picking this up.
Re: sideEffects: false — I actually tested with both and got the same result. I forgot to update the flag when I created the repro repo.
I tested with a build from latest dev (which includes your fix from #7990) and it all works flawlessly :clap: :bow:
Thanks a lot for fixing it so quickly!

Fixed in #7990


AAC(0xaac0) audio : Missing audio or no stream

This bug seems related to some streams particularity. Maybe AAC(0xaac0) audio.
Bug is different according to selected buffer option in TF.

No buffer : No audio
Buffered with ffmepg : Stream doesn work at all

When I input direct stream in the m3u, not passed to TF, everything works. Exemple of 2 freetv streams with the problem:
TV5 Monde Info
https://ott.tv5monde.com/Content/HLS/Live/channel(info)/variant.m3u8
TVA
https://tvalive-dai01.akamaized.net/Content/HLS/Live/channel(575b93c5-be31-ee34-6285-14620fd14048)/index.m3u8

Threafin version : 1.2
Official Docker on Synology
Player used for testing the proxied m3u: Tivitmate, Sparkle IPTV player, Potplayer

What ffmpeg options are you doing? The default one simply copies the stream, so that shouldnt effect it

@Fyb3roptik Ffmeg options?  What do you mean?
I only have to choose between these options. I tried No buffer and FFmpeg, that's it.

Both lead to differents problems, like i explained in my post.
Again:
No buffer : No audio
Buffered with ffmepg : Stream doesn work at all

That's just the selection on which app handles it. The options under it are how you manually control what it outputs.
The issue is your client application does not support the stream, you need to set options to transcode either audio or video as necessary to make your client happy.

Client doesn have problem with the direct link stream. Problem only occurs when Threadfin handle it.

You said you get no audio, which tells me its probably a codec issue for your client. With a buffer, you should look at your Threadfin logs to see what it says

Are you using a ffmpeg with AAC codec enabled?
If you use direct your client player needs to be able to support the AAC audio and have the codecs capable of playing it
If you are a windows user use this ffmpeg as it will have all codecs enabled
https://www.gyan.dev/ffmpeg/builds/ffmpeg-git-full.7z


mount: ensure the root’s ref prop gets attached to the actual root

Fixes #2253.
After merging, this will need adapter-utils bumped and published, and then every adapter's minimum utils version bumped, and then they'll also need a publish.

Isn't this exactly what I wanted to do in #2101 originally which wasn't deemed backwards compat safe?

@eps1lon you're right that it's trying to solve the same problem, and in a very similar way - i believe I did it in a backwards compatible way here, and I admit I forgot #2101 existed when working on this :-/
However, #2101 may be worth rebasing to better handle React 0.13, if you're willing.

However, #2101 may be worth rebasing to better handle React 0.13, if you're willing.

I won't have the time for that. But thanks for releasing this. Allowed us to remove a couple of seemingly useless fragments :+1:


bootstrap refactoring

Summary
Add a short summary of the changes, and a reference to the original issue using # and the issue number, like #1
REFACTOR: About Pages #1417
-converted files to tsx
-incorporated bootstrap in SupportMapleCardContent
-removed css file for SupportMapleCardContent
Screenshots

Steps to test/reproduce

Click on about
Select "How to Support Maple"
See that component loads fine with bootstrap modifications

@all-contributors please add @azheng1991 for refactoring contributions

@sashamaryl deleted all js and css files, all tsx files use bootstrap, could you clarify on the component re-use again? Based on the code I'm seeing, a lot of the components being used seem to be customized (e.g. within the ForIndividualsCardContent component, you have customized components like WhyMapleCardContent and BenefitsCardContent). Since the components are different as per each card, wasn't sure where to start

Thanks for the PR! This is no longer needed - we've finished the migration for these components. Going to close this.


Display P3 has a D65 whitepoint

in the documentation the white point for display p3 is given as D50. It should be D65. Display P3 is identical to sRGB in transfer curve, viewing contitions, whitepoint, image state. The sole difference is the display primaries.

Yup. The implementation was using the right white point, but the docs said differently.

Yup. The implementation was using the right white point, but the docs said differently.


pb_type: fix addition of blif model to muxes

Signed-off-by: Alessandro Comodi<EMAIL_ADDRESS>This PR solves an issue with the generation of the blif attribute for pb_types when the primitive class is defined as mux.

Please rebase and add a test.

@mithro Done


Optimize bitvec

This speeds up the solver by 28% (measured in macro-benchmarks with time cargo run --release ./samples/sample3.csv -x 100 -y 100 -z 100. The optimization was guided by profiling.
BitVec::len is called very often by the solver, and internally it was calling u64::count_ones intrinsics which showed up significantly on the flamegraph. The patch changes BitVec::len to instead return a cached length of the bit vector. The length is stored in the last eight bits of data, so our module count decreased from 256 to 248.
A couple of unused methods were removed from BitVec so that they didn't have to be adapted to the new data layout.
~The PR is still draft, because I didn't test it integrated with GH just yet (I was on linux, because it getting a profiler to work under windows is trying). I'll test in GH soon and then undraft the PR, but it can be reviewed meanwhile.~
UPDATE: Tested with grasshopper integration.

The 27%-28% speedup is now confirmed on Windows, but windows in about 17% slower than Linux on the same machine 👀 Might make sense to play with some build options in the future.

Just increased the speedup to around 34% by tweaking the release build profile. I turned on fat LTO and decreased codegen units count to 1. Release builds now take insanely long, but that's just how life is.


Conv csim fix

C simulation of KERAS_conv1d example model fails due to the size of mult array, which get allocated on stack. Synthesis however, works as expected. So instead stack allocation, allocate using malloc during csim, but still use standard [] allocation during synthesis.

what happens if we keep the fix for c-sim in synthesis?  @benjaminkreis can also comment but he's traveling at the moment

You can't use malloc/free or new/delete or any other dynamic memory allocation functions in synthesis, meaning it would fail when it encounters these functions. This is documented in "Dynamic memory usage" section of UG902 (on page 302), and the proposed fix is taken from the example on page 325 (assuming guide for version 2017.2, probably slightly different for later versions of the document).
I have jumped the gun when I said "synthesis works as expected". It appears to be working (doesn't fail or get stuck), but it takes enormous amount of time. I have tried running it for a few hours, there is progress, but I didn't wait for it to complete. I don't think that is related to this change, as synthesis takes the same code path as before.


Set terminals_available to False when not enabled

Suggested by @lp9052 in https://github.com/jupyter-server/jupyter_server_terminals/issues/85#issuecomment-1883917428

by looking at the source code, it does respect the terminal config.
However, I believe it should update termina_avaliable to False instead of just return.
nbclassic actually read this field and will fail to launch if the value is missing.
I know they should have a default value for missing fields(issue raised). But I also believe it should be populated, instead of just missing.
Link to nbclassic issue: jupyter/nbclassic#255

this allows us to be consistent with Jupyter Server 1.x behaviour: https://github.com/jupyter-server/jupyter_server/blob/1.x/jupyter_server/serverapp.py#L363

@blink1073 Can you take a look at your convenience?


S-RET is broken in occur mode

What did you expect to happen?
S-RET in occur mode should jump to the search result without changing focus
What actually happened?
The key is now bound to +default/new-line

This issue should now be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!


Add UpSampling2D neuron

This PR adds the upsampling2D operations, neuron, and unittest. I also try to add it into the computation graph.  I plan to add the 1D and 3D implementation later.

Awesome PR, thank you Jianxin!


[SPARK-45781][BUILD] Upgrade Arrow to 14.0.0

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

Was this patch authored or co-authored using generative AI tooling?

Test first

https://github.com/LuciferYang/spark/actions/runs/6747430528

Merged to master for Apache Spark 4.0.0!


Double persistence

I'm stuck in a scenario where im using Mutators an Accessors in my model. This works fine up until i want to create a model. Because the attributes are set twice. Let me explain.
These are my accessors and mutators. You have to give somekind of enumeration class on those fields. And the mutator tranforms it into a string.
        /**
         * @param $value
         * @return AccessorType
         */
        public function getAccessorTypeAttribute($value)
        {
            return new AccessorType($value);
        }

        /**
         * @param AccessorType $accessorType
         */
        public function setAccessorTypeAttribute(AccessorType $accessorType)
        {
            $this->attributes['accessor_type'] = $accessorType->getValue();
        }

This goes fine the first time and the internal attributes table is set with the string.
But after the saved event is catched by the Observer.
The model tries to fill itself a second time but now with the data from the attributes table without using the mutators first.
Problem is internally AccessorType is a string but when used you or set you need it wrapped in the enumeration class. So PHP throws an error because the typehinting fails.
The first setAttribute is called in the
Model->fill() function
The second after
setSingleTableInheritanceType();
and then it calls the magic method __set()

I'm not 100% clear on the problem but it does strike me as strange that your getter takes a parameter. Thats not have Eloquent expects get/set methods to work and perhaps something is going wrong there.

Both mutators and accessor need a parameter.
http://laravel.com/docs/4.2/eloquent#accessors-and-mutators

A failing unit test as part of a pull request (ideally with a fix) would help track this down.

I almost tracked the issue, il keep you posted

See PR #9


"How to configure your learning rate schedule" tutorial

It would be really useful to have a tutorial on configuring learning rate schedule.  Right now, you basically dig around on the internet and look for schedules and try them.  Even if this is actually the optimal way to tune your learning rate schedule, it would be great to have some docs to tell beginners how to go about this.

Hi @LukeWood ,
I think the documentation have enough information about custom learning rate scheduler here.
You can define your own learning rate function(eg. scheduler) and then pass it to the LearningRateScheduler callback callback  = tf.keras.callbacks.LearningRateScheduler(scheduler) and then this callback will be passed to model.fit(...,callbacks=[callback]). All the required information mentioned in the attached documentation source.
Thanks!


optimize async sends

small optimizations of attribute-access in zmq.sugar
use lower-level .get calls instead of attribute-access convenience APIs in internal code
reduce unnecessary checks of zmq.EVENTS
optimize optimistic async sends

The main change here is in the behavior of async sends that would resolve immediately where DONTWAIT is not given. If no sends are already waiting, a send is attempted immediately, with DONTWAIT (this was already the behavior if the caller passed DONTWAIT explicitly). Only if that send fails does the full async machinery kick in.
The benefit comes from skipping the check for zmq.EVENTS prior to send. Actually blocking sends will take a little longer, since they will attempt and fail to send (with EAGAIN), before being scheduled on the eventloop when the socket is ready.
closes #1209

Results from the benchmark in #1209:
17.1.2:

zmq_server: 754ms

zmq_asyncio_server: 7103ms (9.4x)

zmq_asyncio_server optimized: 1049ms (1.4x)
f = socket.send(f"{channel} {jsoned_data}".encode("utf8"), zmq.DONTWAIT)
if not f.done():
  await f

this PR:

zmq_server: 1x
zmq_asyncio_server: 1206ms (1.6x)
zmq_asyncio_server optimized (without DONTWAIT): 1049ms (1.4x)

The main change is that sends that would be resolved immediately (the vast majority of the time) take the same optimized path as when DONTWAIT is given in 17.1.2.


Updating an important link to the DSSAT paper

Original link no longer works. Paper is available for download from researchgate.net.

@david-clifford Thanks!


Prevent chrome download page as html with alt + click

Should fix #8648

Codecov Report

Merging #8669 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8669      +/-   ##
==========================================
+ Coverage   41.65%   41.66%   +<.01%
==========================================
  Files         530      530
  Lines       68597    68597
==========================================
+ Hits        28573    28579       +6
+ Misses      36365    36361       -4
+ Partials     3659     3657       -2

Impacted Files
Coverage Δ

modules/sync/unique_queue.go
78.57% <0%> (-10.72%)
:arrow_down:

modules/task/migrate.go
24.35% <0%> (-3.85%)
:arrow_down:

models/error.go
32.08% <0%> (-1.25%)
:arrow_down:

models/repo.go
48.94% <0%> (+0.05%)
:arrow_up:

modules/migrations/gitea.go
11.77% <0%> (+1.49%)
:arrow_up:

modules/migrations/migrate.go
22.9% <0%> (+1.67%)
:arrow_up:

models/repo_indexer.go
68.36% <0%> (+1.81%)
:arrow_up:

models/unit.go
67.56% <0%> (+5.4%)
:arrow_up:

Continue to review full report at Codecov.

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


spyder-remote-server daemon (3)

Tasks/Steps/Elements
The server-side is first implemented as a normal process, and then turned into a daemon.
Our first concern is that it runs on Linux, so one could use the stevens.py template, but for future compatibility to macOS and Windows, maybe there are better ways (read: libraries).
Task:

wrap the server-side process (from issue#2) into a daemon process

Versions checklist

Spyder version: >= 5
Python version: 3.7, 3.8
Qt version: all
PyQt version: all
Operating System name/version:

server : Ubuntu 20.04 Linux (aarch64 on RPI)
client : Windows/Linux/macOS

What is the stevens.py template 🙃 ?

deaemoniker : https://daemoniker.readthedocs.io/en/latest/
python-daemon : https://pypi.org/project/python-daemon/
... system-d stuff


LazyX issue with ContentPadding

When using LazyRow or LazyColumn, set a ContentPadding and set to each item fillMaxParentWidth for LazyRow or fillMaxParentHeight for LazyColumn will add the ContentPadding size to the item like padding modifier, and next item shows up on the screen

Hi!
This issue seems unrelated to the compose-samples repository directly, issues here are reserved for bug reports within the compose-samples apps or feature requests for the sample apps.
For questions related to Jetpack Compose - we recommend asking them on StackOverflow with the android-jetpack-compose tag.
If you find an issue with an Android Jetpack Compose components, report it using the Jetpack Compose issue tracker.


where is DAv protocol is used

The given code contains my sql database for data transfer, where is the testnet in ethereum is used. Can someone explain me how DAV protocol is used ?

The communication protocol you are referring to is a bit outdated. We are releasing a new version of the network and SDK very soon and will be working on detailed documentation as well.


Performance Improvements

When there are a lot of autocommands, from other plugins or in the .vimrc file, performance can suffer greatly.
I also changed s:maxdelay to 10 to make a more varied display.
This PR might...
Close #1
Close #2

I am fine with changing s:maxdelay if you were to put that in a separate pull request.
The noautocmd part I am a bit reluctant because it seem to cause a strange behavior with syntax highlighting.  To reproduce:

Open a file with syntax highlighting enabled.
Run :Matrix
Exit matrix, and now syntax highlighting is disabled (need to run ":sy on" to turn it back on).

I wasn't able to reproduce your observation about highlighting. Nevertheless, I changed the way autocommands are disabled. Does this fix things?

Looks good to me, thanks!


Iio v3

v3:

Exposing sol_util_fill_buffer() and using it;
More debug information;
Removed check for /dev/iio:deviceX existence on sol_iio_open: it should exist as sysfs was already checked - if it happens to not exist, an error will happen when trying to open the buffer;
Not checking SYSFS_TRIGGER_SYSFS_ADD_TRIGGER before writing;
.min and .max of packet sent adjusted to great and least values obtained from sample.

I intend to a issue new PR expanding use of sol_util_fill_buffer().
I did not advanced on mmap() stuff. Analysing carefully libiio code showed that it just doesn't make sense without kernel patches: every detail about the mapping is gotten from kernel via ioctl() requests that are not implemented on upstream (there is actually a queue of buffers). When they cannot use the 'high speed', they fallback to normal read() (and write()).
v2:
List of changes is too big to detail - but I should have addressed all issues raised on v1, or at least answered then. Highlights:
using config struct on API - avoiding lots of calls on unknown order on setup;
API calls to read data simplified - buffer reading is now implicit when buffer is enabled, but this only makes sense on 'data reader' callback.
using direction-vector type of scale and offset options on node - needed a small fix on generator;
sol_util_vwrite_file rewritten - it was hiding errors. Issue about allowing a string to be used to identify a device will be addressed on a future PR, on my TODO list.

Adding some support functions to ease creation of Linux Industrial I/O nodes. Also added a node for iio-gyroscope, that tests the code.

Merged. Besides fixing @glima issue, I also addressed a new warning raised by sanitizer by applying the following diff:
-s_data = data | (s_data << channel->bits);
+s_data = data | ~channel->mask;

I've also changed channel->mask to be a uint64_t.


Vulnerability roundup 110: libbpf-0.6.1: 2 advisories [6.5]

search, files

[ ] CVE-2021-45940 CVSSv3=6.5 (nixos-unstable)
[ ] CVE-2021-45941 CVSSv3=6.5 (nixos-unstable)

CVE details
CVE-2021-45940
libbpf 0.6.0 and 0.6.1 has a heap-based buffer overflow (4 bytes) in __bpf_object__open (called from bpf_object__open_mem and bpf-object-fuzzer.c).
CVE-2021-45941
libbpf 0.6.0 and 0.6.1 has a heap-based buffer overflow (8 bytes) in __bpf_object__open (called from bpf_object__open_mem and bpf-object-fuzzer.c).

Scanned versions: nixos-unstable: 5aaed40d22f.
Cc @martinetd
Cc @saschagrunert
Cc @thoughtpolice
Cc @vcunat

Thanks for this! I don't see how this crosses privilege boundaries (so probably not worth a CVE for me), but we've discussed upgrading libbpf despite the lack of release since these versions yet for bcc 0.24.
I'll proceed with it tomorrow evening (~now+25h) unless waiting just a bit more would get us a release to properly upgrade to.

Apparently these CVEs got reported automatically (!) and aren't real vulnerabilities.

To be fair some issues reported by OSS-Fuzz are real vulnerabilities. It's just that nobody seems to vet them before CVEs are assigned. Probably the idea is to get everybody to update their packages no matter what because unlike simple bugs "security" issues usually lead to updates/upgrades.

OSS-Fuzz is quite useful generally; I am aware of that.  This is the first time I hear about automated reports as CVEs, though.

I think it all started when https://www.openwall.com/lists/oss-security/2019/06/15/2 was posted. As far as I can remember the OSS-Fuzz project was opposed to the idea of filing CVEs automatically but eventually https://osv.dev/ was launched and since then those bash scripts (or whatever that is) have been automatically doing that. I've been trying to track them down since at least 2021 but unfortunately no luck so far.


RSS feeds don't work with iTunes because Apple doesn't accept Google's SSL certs

ugh. @sknebel and @jgmac1106, who may have more details.
CA is Organization: Google Trust Services, Common Name GTS CA 1D2, countersigned by Organizational Unit: GlobalSign Root CA - R2.

Not sure where to start with this. If anyone has steps to reproduce, that would definitely help!

I was just sharing historically. I have no idea if things have changed in
two years
I have not tried in awhile. I will record and push a show to see what
happens.
The Apple Validation tool always denied the SSL Google Cert on security
grounds,
On Fri, Feb 18, 2022 at 10:34 PM Ryan Barrett @.***>
wrote:

Not sure where to start with this. If anyone has steps to reproduce, that
would definitely help!
—
Reply to this email directly, view it on GitHub
https://github.com/snarfed/granary/issues/221#issuecomment-1045665835,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACQL5JT3NIAROOPZNEXP34DU34FVRANCNFSM4RYVXRWA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

--
J. Gregory McVerry, PhD
Assistant Professor
Southern Connecticut State University
twitter: jgmac1106

@jgmac1106 is this still happening? I still don't have a way to reproduce myself. Happy to try if you can post instructions?

Yes,
We can close the ticket as unresolveable
On Thu, Jan 12, 2023 at 12:01 AM Ryan Barrett @.***>
wrote:

@jgmac1106 https://github.com/jgmac1106 is this still happening? I
still don't have a way to reproduce myself. Happy to try if you can post
instructions!
—
Reply to this email directly, view it on GitHub
https://github.com/snarfed/granary/issues/221#issuecomment-1379816147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACQL5JXSYFVUXTN27EYILC3WR6F4HANCNFSM4RYVXRWA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
J. Gregory McVerry, PhD
Assistant Professor
Southern Connecticut State University
twitter: jgmac1106

Thanks! If it's still happening, I'll definitely keep the issue open to track.


Region support for the United Kindgom

The UK locale is not granular enough for holidays within the United Kingdom, and treats any holiday specific to a country within the UK as effective against the whole.
For specifically, today is the Battle of the Boyne, a national holiday only witnessed within Northern Ireland – the other countries are unaffected by this holiday.
An option to be more specific at the witnessed country (i.e. England, Wales, Scotland…) would be welcome.

Hmmm.. this sounds to be already there:
       # Battle of the Boyne         if self.country in ('UK', 'Northern Ireland'):             name = "Battle of the Boyne"             .....
For specific holidays only, you got
"England", "Wales", "Scotland", "IsleOfMan", "NorthernIreland"
while
"UK" (or "GB") sums up all country holidays.
Please let me know, cheers
dr-p

In [1]: from datetime import date

In [2]: import holidays

In [3]: holidays_in_england = holidays.England()

In [4]: date(2019, 8, 26) in holidays_in_england
Out[4]: True

In [5]: holidays_in_england
Out[5]:
{datetime.date(2019, 1, 1): "New Year's Day",
 datetime.date(2019, 4, 19): 'Good Friday',
 datetime.date(2019, 4, 22): 'Easter Monday',
 datetime.date(2019, 5, 6): 'May Day',
 datetime.date(2019, 5, 27): 'Spring Bank Holiday',
 datetime.date(2019, 8, 26): 'Late Summer Bank Holiday',
 datetime.date(2019, 12, 25): 'Christmas Day',
 datetime.date(2019, 12, 26): 'Boxing Day'}

Apologies, meant to get back to you on this one. Can confirm all looks good, not sure if this is something I just missed on the documentation.


Being stunned counts as being dead for SSS

Looking at the code that checks the winning conditions, I don't see how this could happen.
However, people who are in critical don't count as alive.

Intentional I think, closing.


TSServer Types2.0

TSServer Types2.0

replacing TSD with Types 2,0
Note:  tests to follow shortly

@vladima:  will add more tests - the current iteration fixes up the ones we already have


Implement pseudo Huber loss for Flux and SD3

This change set implements pseudo Huber loss functionality that was missing from Flux.1 and SD3 model training.
This also introduces a new parameter huber_scale for controlling base threshold of the Huber function. The previous logic had a fixed threshold that worked very poorly with Flux.1 models; This is something that needs to be tuned to the loss "profile" of each model (mean abs latent error, variance, etc.). The existing huber_c could only be used for adjusting the decay of the exponential schedule, so a new parameter was required.
Refactoring notes:

Moved most of the loss estimation logic inside the conditional_loss function, huber_c is no longer passed through the rest of the code; most of the file changes were due to this.
Added an explicit error message when "snr" schedule is used with a model currently incompatible with it.

Tested with:

SDXL Lora
Flux.1 Dev Lora
SD3.5 Medium Lora (only checked that it doesn't crash)

For use with Flux.1 I recommend using huber_scale = 1.8 (or a bit higher) and huber_c = 0.25. YMMV.

This is great, I was literally just considering asking for Huber loss to be implemented for kohya Flux somehow. It was one of the biggest steps forward for my SDXL training. I'll try to give it a go soon.

Thank you, this is great. I think it makes sense to split get_timesteps_and_huber_c.
However, regarding the responsibilities of the methods, I personally don't want to pass args to conditional_loss. We may refactor it after merging to call get_timesteps, get_huber_threshold, and conditional_loss in order from each script. We appreciate your understanding.

I also do not like the current approach, there should be a "step context" object that collects information about the training context, then it would get passed to all the various methods/strategy/utility functions instead of having to pass around a handful of separate parameters everywhere. But that is a bigger refactoring that I'd like to make here.

I gave it a try... I'm not seeing good results so far. :(  I went for:
--loss_type huber --huber_c 0.25 --huber_scale 1.8 --huber_schedule="exponential"

Learning with Huber loss enabled seemed a lot slower for the same LR, and I didn't see any big image quality improvements either.  Maybe it's dataset-specific, and it'll work better for someone else? My training dataset is around 200 images in size, mostly high quality, but with some poorer quality ones mixed in, so I hoped Huber would help with that.

Also, from past experience with this type of loss function in other models I don't expect this to improve image quality much, this usually helps more with getting consistency in the outputs.

I have some better news to report now. Without changing anything from the settings I gave above, I've let the training continue longer. And the image quality has been rising steadily for a while now, and I'm getting some nice output. Maybe Huber just has different learning characteristics.

I'm seeing a little bit of grid artifact creeping back in though. I don't know why it is, that when my image quality gets to be very good, that DiT artifact appears. Maybe we need block-specific learning rates? I don't fully understand the problem though.
This is the grid artifact I'm referring to (although this one seems mostly vertical):

It seems to be particularly bad at the right hand edge of the images for some reason, although I can see it faintly across the whole image sometimes.

I usually observe this kind of thing when pushing LoRA strength way above 1.0 during inference, or when applying multiple LoRAs simultaneously without lowering the strength of each. I suspect this is related to having very large weight magnitude due to stacking, or over-training.
Training at 5e-4 seems super high to me, I usually don't go above 2e-4.
What are your average_key_norm and max_key_norm values (in tensorboard)?  These give an indication on how much the trained model has "deviated" from the base model.

I usually have a lower LR, but once the gradient accumulation value goes up, I find I usually have to push the LR higher, as I think the gradient update is divided by the number of accumulations, unlike batch size.
And higher LRs actually work amazingly well with Flux. The images I've been getting have rich colors and interesting camera angles (i.e. the Flux DPO seems to still be active), but also include the trained objects. The pictures I get out from flux_minimal_inference.py (which is what I use for sample images) are honestly the kind of thing I'd put up on my art page, if it wasn't for the grid artifact appearing on them.
I really should get tensorboard up and running with my runs. I do wonder if maybe what we need for Flux is the ability to set the LR individually for each of the 19 double and the 38 single blocks. Maybe the average_key_norm and max_key_norm sizes would guide me towards which ones.

I've been told that high gradient accumulation (with 16-bit floats) can cause numerical instability and/or loss of precision, not sure if that applies here.
From tests I've made usually these types of visual artifacts tend to appear when average_key_norm starts to go above ~1.2 (in datasets with around 50 to 100 images). Usually I try to reduce the LR and see if it converges to optimal results in the same number of steps.  average_key_norm tends to grow proportional to the LR used, but this is affected by the size and diversity of the dataset, with larger ones it seems to grow more slowly. You could also try to use max norm regularization to penalize weights growing above a certain threshold, by setting scale_weight_norms to something like 4.0 or 5.0.
I suspect it would be even more effective to set distinct scale_weight_norms at block level but that is currently not implemented.

Okay, so I have so more good news: my training run at 1e-4 with @recris's Huber loss went very well. Now I have some very high quality images, with the concept in the training images learned close to perfectly. (It's still training).
The big thing to note is how long it took. Training with gradient accumulation 16 at 1e-4 took pretty much a whole day of training to get it to work. But it did make continuous steady progress throughout this time. Without Huber loss, I either found the learning of the training concept would get stuck and sample images would continually mis-draw the objects being learned, or that the sample images would lose their high image quality and draw boring scenes. That doesn't seem to be the case with Huber loss.
@recris, I've heard things about high gradient accumulation being bad too, but it hasn't seem to have affected me here. Before Huber loss was implemented, I pushed up from accumulating 8 to accumulating 16 to try to reach better image quality, and that did seem to work. But yeah, gradient accumulation feels a bit suspect in general compared to increasing batch size. It does use less memory though, and another avantage to gradient accumulation that people often miss is that batch size only works on images that are in the same bucket for image dimensions. And often buckets only have single images in them, silently preventing batch size from working for them. Gradient accumulation is immune to that.
Anyway, I'm glad that this PR has made it into the SD3 branch, as it seems worthwhile to me.

All insights about how to use it are great - but having them in this PR makes it very hard to use them in future.
So please put it also in a documentation file so that it can be looked up anytime in the future!

@bmaltais can we have this i would like to test this ty

You could also try to use max norm regularization to penalize weights growing above a certain threshold, by setting scale_weight_norms to something like 4.0 or 5.0.

Hey there @recris, I gave this a try (with 4.0), and yeah that lets me get to the higher LRs without those vertical lines; great suggestion.
I hope we can get individual LRs for individual blocks at some point, like we had for SDXL with --block_lr=.... That would probably mean that whatever keys are growing very fast wouldn't get so big and need clipped in length. But in the meantime, renormalizing them seems to do the job.

Okay, I found something I think is pretty cool, and I thought I'd put it here cause it relates to what's been said so far.
I found that using --scale_weight_norms did get rid of the vertical lines on the image when I used higher LRs... but it also seemed to limit the amount of learning that occurred. The object I was trying to learn didn't contain all the fine details that I wanted.
I tried pushing up the value for --scale_weight_norms, but then my images became 'constrasty', with faces often being bright and washed out.
I suspected that the issue was that the later single blocks were getting overtrained, and they can't deal with the higher key lengths - but the earlier double blocks were not overtrained and needed the longer key lengths available to them to be able to learn the trained object.
So I added this code to lora_flux.py: (round about line 1145)
            # Attempt a different max scaling for single blocks
            if downkeys[i].find('single') != -1:
                this_max_norm_value = 1
            else:
                this_max_norm_value = max_norm_value

and changed the next couple of lines to use the new this_max_norm_value instead of max_norm_value:
            norm = updown.norm().clamp(min=this_max_norm_value / 2)

            desired = torch.clamp(norm, max=this_max_norm_value)

This seemed to immediately get rid of the constrasty look, and let me increase my value for --scale_weight_norms, allowing the object I was learning to be learned far more accurately.
Maybe we need a --scale_weight_norms_single 1.0 option?

Like you said before, we need a way to control the learning rate at block level. I find it too easy to create a burned Lora before it properly learns the target concept(s).
Alternatively, there is a chance this could be mitigated with a better loss function - maybe the work in https://github.com/kohya-ss/sd-scripts/discussions/294 should be revisited and translated to Flux training.

@araleza If you're training a style you may wish to have a look at https://github.com/kohya-ss/sd-scripts/pull/1838 , it could help improving learning issues.


crash thing

Description
in settings i click prefrences then it closed than a notification said something about me reporting this biug
Steps To Reproduce
go to settings
click on prefrences
a notification pops up
it closes
Expected behavior
it works now but
it was supposed to not crash when picking prefrences to change your setings
Files Version
Version: <IP_ADDRESS> OS Version: 10.0.22504.1000
Windows Version
windows 11 dev 22504.100 (there is a pending update i havent installed yet)
Relevant Assets
debug_fulltrust.log
debug.log

Thanks for the report. Could you share a screenshot of Files after opening? Does the sidebar take a long time to load?

This issue should be fixed in #7017.


EPoSe Movement #2 - Proposing Changes in Mixin

Prerequisite: DB Implementation
Instead of utilizing ring confidential transaction (hiding information),
We should think about using statistics to make it more difficult to trace and pinpoint txs.

Here we see the pretty amounts for making outputs. From our blockchain history, the chain can analyze the population of each output in each digit space (statistical term). If conventional mixin focuses on mixing sudo and real inputs to obfuscate real outputs. What I am suggesting is to populate certain outputs so that their population grows over time and tracing txs more difficult because they all look the same or alike.

When high mixin is selected, outputs with most population in each digit is used to create txs and vice versa.
Any thoughts, guys?

Like Where is Wally?

I don't know if that would be to much but what's about analyzing the data from the past and create the outputs by AI, just as an idea.

This change is based on individual chain's historical data. Adaptive approach.

DB on our block data is required to proceed further.

Thanks for taking our idea again Turtlecoin. Please work on your originality.

Will reopen this issue if necessary.


removed contents read permission

get permission error on pushing ghcr.io.  So I tried to change the permission for contents

Codecov Report

Merging #12 (c6bbdff) into main (860cbb3) will increase coverage by 1.12%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   53.92%   55.04%   +1.11%
==========================================
  Files          14       14
  Lines         625      625
==========================================
+ Hits          337      344       +7
+ Misses        268      262       -6
+ Partials       20       19       -1

Impacted Files
Coverage Δ

internal/proxy/conn.go
82.14% <0.00%> (+25.00%)
:arrow_up:

Continue to review full report at Codecov.

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


Fix #368

Summary
Fixes #368
Details and comments
This also ensures that an empty result can be printed without raising any errors.

Please hold off merging this as I want to include another fix with regards to the behavior when the stored values are complex

Thanks @manoelmarques! This is good for review again now :+1:


Is this a free service are there charges per document?

Can you please confirm what the costs are for this serivce?

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

ID: 7e0acd95-5498-9acf-1d97-698e76d99d7d
Version Independent ID: 55e87498-2992-45cb-2956-53ddbec08d7e
Content: Work with Incoming Documents - Business Central
Content Source: business-central/across-income-documents.md
Service: dynamics365-business-central
GitHub Login: @SorenGP
Microsoft Alias: sgroespe

Hello Ben,
Thank you for your feedback! The cost depends on the external OCR service that you use for the processing of physical documents or images, such as ReadSoft Online: https://store.readsoftonline.com/nav.
This will be made clearer in the next doc update.


Add some way to prepare data / run arbitrary code at startup --> for manual tests

In addition, print and generate some authentication medium for the user

You can run arbitrary code in Program.cs that intializes the state of the database


Fix parsing for boolean expressions starting with negation

Fixed antlr grammar to correctly resolve boolean expressions starting with negation.
Before fix:
Expression !True && False:

would resolve to true which is wrong.
antlr would parse it to: Negate(And(Property("True"), Property("False")))

After fix:
Expression !True && False:

would resolve to false as expected.
antlr would parse it to: And(Negate(Property("True")), Property("False"))

Also created PR to update compliance tests.
Issue link: #65

Awesome, thank you for the contribution. I will try to merge this and deploy a new version as soon as I can, but apologies if it takes a few days.

Thanks for approval. Do you have expected date for a new version to be deployed?

v0.5.1 has been released and should show up in Maven central soon.


add Kubelet logs to T2 logs

Sometimes when troubleshooting a test, it could be helpful to have a look in the output of the Kubernetes Kubelets, so having them in the Log index could be a good idea.
Unfortunately, it is quite a huge task to achieve this:
K3s: In the K3s-based clusters, it should be fairly easy, as we have access to the nodes and can perhaps create a DaemonSet of Pods which can access the journal and pipe the stuff into vector.
managed K8s: The managed K8s environments are usually designed to offer the users means of logging/monitoring which are operated using the cloud vendors' UIs. Furthermore, the logs are usually (?) not kept longer than the lifespan of the cluster.
As we have 4 managed K8s providers in store, it would really cost us A LOT to do this...

Some (maybe) helpful links:
https://docs.aws.amazon.com/prescriptive-guidance/latest/implementing-logging-monitoring-cloudwatch/amazon-eks-logging-monitoring.html
https://docs.microsoft.com/en-us/azure-stack/aks-hci/view-logs

T2 is discontinued


I  trained my own database ,but there loss are  null

@dazhangzhang Hey I was also trying to train the network but I also got all loss as null. How did you solve this issue??
Please help. Thanks.


[tests actually pass] Add unicode to tnetstring3

This PR...

rewrites the tnetstring module for Python 2/3 cross-compatibility.
adds a unicode datatype to our tnetstrings implementation
adjusts flow.io_compat to transparently accept dumpfiles and convert them to the native Python str encoding.

Ok, this is ready for a final review :smiley:
Needed to include the SNI changes to fix some failing tests.


Need to update peer dependencies to Payloadcms 2.0

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/payload
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@payloadcms/bundler-webpack
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   3 more (@payloadcms/db-mongodb, ...)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@payloadcms/plugin-sentry
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/payload
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@payloadcms/plugin-sentry
npm ERR<EMAIL_ADDRESS>from the root project

Can't use sentry logging after upgrading to 2.0

Hi @treturner - this has been updated, you can now upgrade to v0.0.5 to get the latest change.


Upgrade to ktfmt 0.53

Move to the latest version of ktfmt. It includes a change that's not compatible
with the Spotless plugin version we were using, so upgrade that as well;
unfortunately the only version that fixes the compatibility issue is a beta
release, but none of the breaking changes in the beta appear to be relevant to
our code base.

#2649
#2648  👈 (View in Graphite)
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 4, 6:32 PM EST: A user started a stack merge that includes this pull request via Graphite.


Fixup create command flag application.

Previously StringSlice flag defaults were not respected.  These use
special handling and that handling did not take account of default
values, always over-writing them.  Expand the CommandLine interface to
take advantage of the underlying codegansta/cli.Context IsSet method and
guard default string slice overwrites with an IsSet test.
This addresses #3242
Signed-off-by: John Sirois<EMAIL_ADDRESS>

Noting that the amazon IT ran green as well:
DRIVER=amazonec2 \
AWS_ACCESS_KEY_ID=XXXXX \
AWS_SECRET_ACCESS_KEY=YYYYY \
AWS_VPC_ID=vpc-9224f2f7 \
AWS_DEFAULT_REGION=us-west-2 \
AWS_ZONE=b \
make test-integration test/integration/amazonec2
test/integration/run-bats.sh test/integration/amazonec2
=> test/integration/amazonec2/createwithkeypair.bats
 ✓ amazonec2: Should Create Instance with Pre existing SSH Key

1 test, 0 failures

=> test/integration/amazonec2/create-ebsinstance.bats
 ✓ amazonec2: Should Create an EBS Optimized Instance
 ✓ amazonec2: Check the machine is up

2 tests, 0 failures

=> test/integration/amazonec2/amazon.bats
 ✓ amazonec2: Should Create a default host

1 test, 0 failures

make: Nothing to be done for 'test/integration/amazonec2'.

LGTM
:+1:
Thanks for debugging it!


Update Discord Invite Link

Change to http://discord.eddiehub.org

[ ] .github/workflows/ISSUE_TEMPLATES/feature.md

Hey I updated the Discord link and raised a PR . Pls review it.


[topgen] Generate Linker Script Memory Definitions

As pointed out in the reviews of #2031, we can generate the MEMORY
sections of the linker scripts from the information known by topgen.
This commit updates the linker scripts to use this autogenerated
information. Unfortunately there are some slight name changes.
We now only generate a single memory definition (wheras before the flash
linker script did not even mention the ROM, as it is not usable by the
flash image in any reasonable way), which may be a slight drawback.

This was based on a suggestion by @eunchan.
One thing to note is this does not address Tock yet. Our downstream tock configuration currently uses the generic tock linker script, and at some point we should potentially use one that includes the information generated here instead.
I think this preemptively solves a bug, as the autogenerated information has the flash size at 0x80000 bytes, and the replaced linker scripts had that value at 0x100000 bytes.

That said, what's up with some of the diffs in the vendor files? Looks like a lot of them are funky spacing changes.

Please do not gaze at riscv-compliance for too long. The whitespace in that repo is very cursed.
As to passing -Wl,-L<…> - this has to be done in a specific order with respect to the linker script itself, so I'm not sure we can do this at the top level but I'll take a look and see if we can.


License fixes

I fixed some licences.

Thank you for the contribution. It was merged directly as f095855024b8f69fb6142f4c05094ec0d9297c3e to keep commit history cleaner. Your contribution is still credited to you.


emitting of janus errors and messages

Currently all errors emitted on Connection but messages are emitted on each instance they belong to. If message is on plugin level then it will be emitted on plugin, session, connection. If message is on session level then it will be emitted on session, connection. If message is on connection level then it will be emitted on connection only. On the other hand errors are emitted on connection only. Shall we emit plugin errors on plugin? session errors on session? and have the same mechanism as we have now with messages?
Shall we change this mechanism in the way that plugin messages will be emitted only on plugin and don't go further and be emitted on session and connection?
@zazabe

Would be nice to keep things at the level they belong to, so error and message should be emitted on the sender only.
Maybe the tricky part is about knowing who is the instigator in processIncomeMessage, we should not rely on the message content itself i guess... wdyt?

on the sender only

Do you mean that if message belongs to plugin then it should be emitted only on plugin?

who is the instigator in processIncomeMessage, we should not rely on the message content itself i guess... wdyt?

We can find the way if needed without relying on message content.

yes, i meant if a plugin send a request, error/message should be emitted on it only, same for connection and session.

@zazabe please review


Argos Hentai - pt source request

Source name
Argos Hentai
Source link
https://argoshentai.com/
Source language
Portuguese
Other details
No response
Acknowledgements

[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I will fill out all of the requested information in this form.

The domain has been unified, so you can use filters in the search to retrieve information from the old domain <https://argoshentai.com>.
Extension:
Argos Comics
<EMAIL_ADDRESS>


”DUMBRĂVENI” is listed in the drop-down menu

Description:
"DUMBRĂVENI" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "DUMBRĂVENI" in the search bar.

Expected results
The location is listed in the drop-down menu as "Oraș DUMBRĂVENI, SIBIU".


Fix link in README.md (minor)

My understanding is that markdown doesn't require special syntax if the full link is used. The current link is broken.

This was fixed in another PR, closing this


校验器添加具体错误

Feature Request
Is your feature request related to a problem? Please describe:

校验器只能检验文件合格性，无法精确到第几行错误
Describe the feature you'd like:

抛出文件第几行错误，以及具体错误，比如类型错误还是校验规则错误
Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

Hi @XiaoK29, thank you for your feedback. This is the relevant issue: #253 cc @zong-zhe

Hi @XiaoK29, thank you for your feedback. This is the relevant issue: #253 cc 您好，感谢您的反馈。这是相关问题：#253 cc@zong-zhe

好的

@XiaoK29 PRs welcome. ❤


ModuleNotFoundError: No module named 'interface'

Hi,
first of all thank you for creating  this library. however i'm trying to get it to work.
I'm encountering the following errors.
My environment.

Windows 10
Python 3.6.4

First error i encountered:
ModuleNotFoundError: No module named 'interface'
what i tried.
install interface and zope.interface. tested it again, still dindt work. then i changed all import lines from from interface import implements with from zope.interface import implements
this seems to work but then i encounter the following error.
Traceback (most recent call last):
  File "C:\Python36\lib\site-packages\impy\ImageLocalizationDataset.py", line 30, in <module>
    from .BoundingBoxAugmenters import *
  File "C:\Python36\lib\site-packages\impy\BoundingBoxAugmenters.py", line 59, in <module>
    class BoundingBoxAugmenters(implements(BoundingBoxAugmentersMethods)):
  File "C:\Python36\lib\site-packages\zope\interface\declarations.py", line 483, in implements
    raise TypeError(_ADVICE_ERROR % 'implementer')
TypeError: Class advice impossible in Python3.  Use the @implementer class decorator instead.

what i tried
roll back to a older version of zope.interface 4.5.0 to 3.8.0. this gives me the following error.
Traceback (most recent call last):
  File "main.py", line 1, in <module>
    from impy.ImageLocalizationDataset import *
  File "C:\Python36\lib\site-packages\impy\ImageLocalizationDataset.py", line 11, in <module>
    from zope.interface import implements
  File "C:\Python36\lib\site-packages\zope\interface\__init__.py", line 56, in <module>
    _wire()
  File "C:\Python36\lib\site-packages\zope\interface\interface.py", line 823, in _wire
    from zope.interface.interfaces import IAttribute
  File "C:\Python36\lib\site-packages\zope\interface\interfaces.py", line 23, in <module>
    class IElement(Interface):
  File "C:\Python36\lib\site-packages\zope\interface\interface.py", line 497, in __init__
    raise InvalidInterface("Concrete attribute, " + name)
zope.interface.exceptions.InvalidInterface: Concrete attribute, __qualname__

from this point on im basically stuck.
thanks in advance

Hi @julianklumpers thanks for trying out my scripts. As I can see the problem is with the interface library that seems to have a problem with Python3. I am using the following interface module for python https://pypi.org/project/python-interface/ I suggest you install that one.
In the case that does not work. I recommend you changing the following lines:

from BoundingBoxAugmenters.py change the following line:

class BoundingBoxAugmenters(implements(BoundingBoxAugmentersMethods)):

to:

class BoundingBoxAugmenters(object):

That should not cause any other problem with the interface library you are using. Do the same for ColorAugmenters.py if you encounter the same error.

from ColorAugmenters.py change the following line:

ColorAugmenters(implements(ColorAugmentersMethods)):

to:

ColorAugmenters(object)

I hope this works.

Hi,
thanks for replying so quickly,
i just solved my issue by doing the following.
in ImageLocalizationDataset.py i changed from interface import implements to from zope.interface  import implementer
then i changed the:
class ImageLocalizationDataset(implements(ImageLocalizationDatasetPreprocessMethods, ImageLocalizationDatasetStatisticsMethods)):
...

To:
@implementer(ImageLocalizationDatasetPreprocessMethods, ImageLocalizationDatasetStatisticsMethods)
class ImageLocalizationDataset():
...

I did this for all the files where you import the from interface import implements
Also be aware that if there is a hidden .DS_Store in the image folder. It gives me a warning that only jpgs and pngs are allowed. took me 30 min to find out.... haha
Anyway thanks for making this awesome library!
Greetz Julian

I faced the same problem, pluss a few more missing dependencies. Everything worked like a charm once I installed the missing dependencies, but might be an idea to add to the readme that these three dependencies are required:
python-interface
tqdm
opencv-python


issues --> possibilities (don't know if this is an issue) :)

I love your reflections. When you're done you should edit, make a 'process document' that includes the best parts, and your discussions. @masak's reflections (I think that Carl is the main vehicle when it comes to reflections in this project) and his discussions with @vendethiel and others.
My contention is that this would be valuable to others. Perhaps it could be included in some kind of 'history'/'process' section at the project homepage?
Another idea would be  - ok, perhaps I'm stretching it now/again - to write 'a how to write a compiler' text and link to the different issues, so the reader can get a sense of (possible) problems, complications (issues) and so on. The main advantage would that the reader would  see, 'meet' 'real' problems.
I think this would be particularly good for junior developers who don't grasp the whole process of writing a compiler, get a sense of 'real' issues (or how to put it). Often 'tutorials' or even whole books are way to 'easy'; you're provided with a solution, not the problems... and this is not always helpful. What not to do, is often equally important as what you should do (at least, I think, to the beginner programmer).
Who knows what lovely and cool spin-offs would emerge from such a procedure? It would be a truly honest project. And from honesty emerges the possibility to close in on truth, I would say.
Anyhow! I love reading your discussions and reflections.

Re process document: thank you for the kind words. I think you will enjoy the planned fallout of the #401 documentation and also https://github.com/masak/007/issues/415#issuecomment-434622308 — basically, my plan is to document for each language-extending module what forces went into shaping that feature the way it is, comparing and contrasting with alternatives.
Re "how to write a compiler" tutorial: I like the idea. As you're aware, there's a book in the very early stages. But your idea sounds like something smaller/earlier than that — maybe even something that can serve as an early version/prototype of the book. Being a fan of getting results early, I approve/agree. It will by necessity be a separate effort/project out-of-scope from 007, but of course we can link to the resulting post(s) from here.
Closing this issue due to its overlap with existing things.


THREESCALE-9985: go1.19

Fixes https://issues.redhat.com/browse/THREESCALE-9985

should this pr include go.sum as well?

should this pr include go.sum as well?

no changes in go.sum :shrug:

Are there any verification steps for this or is the code running enough?

code running is enough, which happens in the e2e tests,which pass.

ah nice, in that case
/lgtm


[NO MERGE] Split hi res geocoding

Just to get an idea of how many tests I broke

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

What's here:

Split the former Geocoder (here) into HiresGeocoder and HiresBatchGeocoder: now they know about the service and API they work with but not much about db's, tables or the rest.
A new class HiresGeocoderFactory to decide whether to instantiate one or another.
Many changes to the TableGeocoder to accommodate the above. E.g: moved the state polling loop on the here service to the HiresBatchGeocoder, so from the client classes that's kind of transparent.
Stuff from public to protected/private
Fixes for legacy tests, now turned into kind of white box (accessing their privates :stuck_out_tongue_winking_eye: )
Many small details, bugfixes and some TODO's.

Some comments about this:

I'd like to add more tests, they're easier now but this task will have to be "time boxed" so I'll do my best.
I have not thrown away the existing tests yet because they proved to be useful to check against expected behavior, though ideally they're to be deleted.
Please don't be too hard on it, I don't like remaining TODO's there but again I tried to carry on by priority and the TODO's let me capture things in context that otherwise are lost in wiki pages/tickets...

@Kartones and / or @juanignaciosl please review
cc/ @ethervoid so that you can get familiar with the code.


unvmap of xsmatrix in PreMODIT

Vmap used here limits the device memory in PreMODIT.
Buffer 1:
Size: 34.57GiB
Operator: op_name="jit(xsmatrix_first)/jit(main)/broadcast_in_dim[shape=(40, 11, 100, 52729) broadcast_dimensions=()]" source_file="/home/kawahara/anaconda3/lib/python3.8/site-packages/ExoJAX-1.3-py3.8.egg/exojax/spec/modit_scanfft.py" source_line=37
XLA Label: broadcast
Shape: c128[40,11,100,52729]
==========================

Buffer 2:
Size: 34.57GiB
Operator: op_name="jit(xsmatrix_first)/jit(main)/transpose[permutation=(1, 0, 2, 3)]" source_file="/home/kawahara/anaconda3/lib/python3.8/site-packages/ExoJAX-1.3-py3.8.egg/exojax/spec/modit_scanfft.py" source_line=37
XLA Label: fusion
Shape: f64[40,11,100,105456]
==========================

The memory allocation is (N_broadening) x (number of free parameters) x (N_layer) x (N_wavenumber x 2) x 8 byte (F64), and x 2 (c128, f64).  For instance,

f64[40,11,100,105456] -> 40 x11 x 100 x 105456 x 8byte = 34.57GB

So, we would make an unvmapped version of xsmatrix.  Some thought:

refactoring: zeroth, first, second diffmode are different xsmatrix, and some parts are duplicated. computing LSD and vmap/unvmap FFT should be separated?

related topic in #263. vmap may be faster but requires larger device memory.

Some experiments for jit / unjit
when removing jit here
unjit
premodit_spectrum_test.py
BufferAssignment stats:
             parameter allocation:   42.17GiB
              constant allocation:         0B
        maybe_live_out allocation:   42.17GiB
     preallocated temp allocation:         0B
                 total allocation:   84.34GiB
              total fragmentation:         0B (0.00%)
Peak buffers:
	Buffer 1:
		Size: 42.17GiB
		Entry Parameter Subshape: f64[100,20000,10,283]
		==========================


Error creating testnet funded wallet

Jsng and js-sdk on latest development:

After clicking submit again:

I had to close this popup and switch to another page and come back to see my wallet. But no Testnet TFT was added unfortunatly.

we can harden indeed by always first checking the stellar and token services before continuing
this should be done on all chatflows and levels

verified

(js-sdk-NQNSzBV5-py3.8) root@tfwallet-prod:/opt/js-sdk# git log -1
commit 21bfa54881c733b7d7480f3c76fe9bbbed3293d2 (HEAD -> development, origin/development, origin/HEAD)
Author: Mahmoud Ayoub<EMAIL_ADDRESS>Date:   Thu Sep 17 09:24:39 2020 +0200

    added demo label in marketplace app bar (#1200)


[BugTrapServer] Email SSL support

I'm surprised that BugTrapServer e-mail reporting doesn't support SSL/TLS.

Very nice! Again, excellent work m8! LGTM. You should be able to merge once CI goes green.
Ops, build results just came in. Seems like this line here:
RequestHandler.aspx.cs
smtpClient.EnableSsl = this.applicationSettings.SmtpSSL;

appSettings is passed in as an argument so (this) reference isn't needed. :+1:

Yeah, my mistake. I don't have ASP.NET support on my VS installation so I've just copy-pasted this feature to webapp. Should be fixed now.


Sanne: JavaScript, Chapter 1

Study Plan
Week 1

[x] I have pushed my progress to my fork of exercises repo

Check-In
I Need Help With:
I am studying everyday in different ways to really try and understand JavaScript, I am not there yet, but I cannot clearly say anything specific I need help with currently... just need to study study study
What went well?
I am redoing the Codecademy Course on JS because I more or less forgot everything from 2 months ago, the great thing is it m makes a bit more sense now the second time, I am doing projects to help the understanding.
What went less well?
I am not a big fan of math and for me JavaScript reminds me of math, but I am determined to learn it
Lessons Learned
Sometimes I need to redo things over to get the point
Sunday Prep Work
I want to try and finish the course on Codecademy and I am also doing over the suggested study
---- END CHECK-IN TEMPLATE ----
-->

[ ] 🥚 Three Audiences: You can explain how a single file of code is used to communicate with 3 different audiences:Developers: You can explain how code formatting, comments, logs and variable names make it easier (or harder!) for a developer to understand a program.Computers: You can explain how a computer follows your instructions to store, read and modify data in program memory.Users: You can explain how the computer creates a dynamic user experience by following different executions paths depending on user input.
[ ] 🥚 Listening and Reading: You can read code out loud, and understand your classmates when they read code to you. You don't need to understand how a program works to master these learning objectives!Listening You can exactly re-write a program that a classmate has readReading You can read a program out loud and guide your classmates to re-write exactly the same code without them seeing the program. (every indentation, semi-colon, comment and spelling must be identical) to you, without seeing the program they are reading.
[ ] 🥚 Static vs. Dynamic Analysis: You can explain and use these two ways of studying a program, each can help you understand different aspects of your code. To help understand this concept, the options panel in Study Lenses is organized into static and dynamic study options:Static: Studying the text in a code file without running it. Some static study methods are creating a flowchart, analyzing variables, filling out a trace table, and drawing on code.Dynamic: Running code and studying the computer's behavior. Some dynamic study methods are running code and reading console logs, using the trace button, and stepping through in the debugger or JS Tutor.
[ ] 🥚 Analyzing Variables: You can list all the variables in a program, and answer these 5 questions for each variable:Where is the variable declared?What is the variable's scope?Is the variable initialized with a value?How many times is it's value used (read) in the program?How many times is the variable assigned a new value?What types are assigned to this variable during the program's execution?
[ ] 🐣 Imperative Programming: You can explain what the Imperative Programming paradigm is, and can explain how you know the programs in Welcome to JS are Imperative.
[ ] 🐣 Tracing Execution: You can complete a "steps" trace table and correct your table using console output from the "trace" button.
[ ] 🐣 Describing Programs: You can read a program and describe it with comments using to the methodology from /describing-programs: zooming out -> zooming in -> connections -> goals
[ ] 🐣 Completing Programs: You can successfully fill in blanks for a program when the missing words are provided, including distractors.
[ ] 🐥 Constructing Programs: You can reconstruct a program's lines and indentation, successfully ignoring distractor lines.
[ ] 🐥 Modifying Programs: You can make small changes in a program to change it's behavior without breaking it.
[ ] 🐔 Stepping Through: You can pause a script in a step debugger, arrange the debugger, collapse extra panels, and step through a script written with Just Enough JS. At each point in execution you can make a prediction of the next line before executing, and can check your prediction using the scopes panel.
[ ] 🐔 Authoring Programs: Given starter code with labeled goals, you can write a small program to match specs (user stories + test cases).


Updates installer issues and resolves the pyomo logging error

This PR resolves several issues.

Closes #50 -- For some reason, either the pyomo or logging libraries ignores the logging.setLevel function. I resolved this by following the solution from this stackoverflow.
This PR updates package installation by retiring the setup.py file and adding a pyproject.toml file. The recent NumPy update to 2.0 caused some dependency issues with Pyomo. These issues have apparently been resolved in version 6.8.0 of pyomo. Since the current build works I have not pinned any versions.

Closes #55
Closes #59
Closes #60

Closes #56 by adding windows and macos to the CI build. Along with several versions of Python (3.9-3.12).

This PR also addresses some comments from @fredshone JOSS review:

Adding a windows machine to the CI
Adding a code coverage test -- it does not however add a badge to the readme because this project does not have codecov enabled and the "free" badge solutions seem extremely hacky. I'm also not keen on manually updating a badge icon. Happy to hear suggestions, though.

[!NOTE]
Contrary to @fredshone's request in #56, I changed the default solver to cbc for the test suite, instead of having GLPK. The Calliope project had a nice example for installing CBC on a windows machine via GitHub CI. I haven't found an equivalent command line only guide to installing GLPK.

Local Checks

[x] Passing tests (yes, with a single numpy deprecation warning -- from a dependent package).
[x] Docs build (yes, with a couple of warnings)
[x] Examples run successfully

@victoraalves
@fredshone

Thanks @yardasol! Care to merge?
(Merging was previously blocked by a ruleset waiting for a status update from the "Build and test" job. I'm not entirely sure why it wasn't being triggered, even though all of the checks within that job passed).


Bringing Tensor::gather() behavior closer to torch.gather()

Definition:

input and index must have the same number of dimensions. It is also required that index.size(d) <= input.size(d) for all dimensions d != dim. out will have the same shape as index. Note that input and index do not broadcast against each other.

In our case we were effectively constraining the requirement to:
index.size(d) != input.size(d); where d != dim
This PR removes the != constraint and allows the op to go through as long as:
index.dims()[d] <= input.dims()[d]; where d != dim
Added tests with data generated and validated against torch's ScatterGather tests.
Tested on arm64, x86_64, cuda and metal. I don't have access to mkl and others, so unsure if the kernels hold true!

That's odd .. All tests are passing for my test run on Ubuntu x86_64. Let me see if I can replicate this.

Looks more like an issue with the github CI infrastructure, I've relaunched the failed action.

Thanks, I've merged the changes after running the tests locally on my linux box and it was all fine.

Thanks a ton @LaurentMazare .. this unblocks another PR :)


Support Java 17

Support Java 17.
See JDK-17 for changes.
How Ares interacts with JDK-17:

A warning will be printed to the error output that informs about the security manager as specified by JEP-411.

Currently waiting for adoptium/adoptium#74

https://github.com/actions/setup-java/issues/233#issuecomment-925039615


Build error when using url_for(request.endpoint)

Expected Behavior
I put this IF statement in my base.html template:
    {% if "dashboard" in url_for(request.endpoint)  %}
    <script src={{ url_for('static', filename='js/dashboard.js') }}></script>
    {% endif %}

I added an endpoint with a value. For example:
@app.route("/accountmgmt/<int:userid>",methods=["GET","POST"])
@login_required
def accountmgmt(userid):
   ... etc

Actual Behavior
The above code causes a build error, but only when an endpoint has a value (as above).
When I remove the above IF statement from the template, the code does not error. But when it is included, I get this error (I am using the URL: http://<IP_ADDRESS>:5000/accountmgmt/123):
Could not build url for endpoint 'accountmgmt'. Did you forget to specify values ['userid']?
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/app.py", line 2309, in __call__
return self.wsgi_app(environ, start_response)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/app.py", line 2295, in wsgi_app
response = self.handle_exception(e)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/app.py", line 1741, in handle_exception
reraise(exc_type, exc_value, tb)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/app.py", line 2292, in wsgi_app
response = self.full_dispatch_request()
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/app.py", line 1815, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/app.py", line 1718, in handle_user_exception
reraise(exc_type, exc_value, tb)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask_login/utils.py", line 261, in decorated_view
return func(*args, **kwargs)
File "/Users/brendon/dev/nelliedata/nellieapp/routes.py", line 43, in accountmgmt
return render_template("accountmgmt.html",users=userlist, current_user=current_user,title="Nellie Data: Account Management")
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/templating.py", line 135, in render_template
context, ctx.app)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/templating.py", line 117, in _render
rv = template.render(context)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/jinja2/asyncsupport.py", line 76, in render
return original_render(self, *args, **kwargs)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/jinja2/environment.py", line 1008, in render
return self.environment.handle_exception(exc_info, True)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/jinja2/environment.py", line 780, in handle_exception
reraise(exc_type, exc_value, tb)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/jinja2/_compat.py", line 37, in reraise
raise value.with_traceback(tb)
File "/Users/brendon/dev/nelliedata/nellieapp/templates/accountmgmt.html", line 1, in top-level template code
{% extends "base.html" %}
File "/Users/brendon/dev/nelliedata/nellieapp/templates/base.html", line 115, in top-level template code
{% if "test" in url_for(request.endpoint)  %}
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/helpers.py", line 356, in url_for
return appctx.app.handle_url_build_error(error, endpoint, values)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/app.py", line 2061, in handle_url_build_error
reraise(exc_type, exc_value, tb)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/_compat.py", line 35, in reraise
raise value
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/flask/helpers.py", line 345, in url_for
force_external=external)
File "/Users/brendon/dev/nelliedata/flask/lib/python3.6/site-packages/werkzeug/routing.py", line 1776, in build
raise BuildError(endpoint, values, method, self)
werkzeug.routing.BuildError: Could not build url for endpoint 'accountmgmt'. Did you forget to specify values ['userid']?

Environment

Python version: 3.6.5
Flask version: 1.0.2
Werkzeug version: 0.14.1

Well that's because you are not supposed to use url_ror like this. If you want to check if the user is on a certain page, check if request.endpoint == 'accountmgmt'


[docs][windows]: Pod OS field update

xref: https://github.com/kubernetes/enhancements/issues/2802
cc @marosset @liggitt @jsturtevant @aravindhp @jayunit100

/sig windows

/assign @mehabhalodiya

@ravisantoshgudimetla Can you please do some updates as per the suggested changes above?

Is there general guidance that we should include to configure this properly like you must also set the node selector == windows for the time being?

Typically, we don't make recommendations that cluster operators enable alpha features. There are exceptions and this might be a situation where we clearly point out the feature but stop short of formally recommending that folks enable it.
How does that sound as a compromise?

@ravisantoshgudimetla would you be willing to update this PR based on feedback so far?

/lgtm

/lgtm
/approve

Thanks for working out that final nit!
/lgtm
/approve


Appstudio update test-component-pac-atqt

Pipelines as Code configuration proposal

Pipelines as Code CI/test-component-pac-atqt-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
42 seconds
appstudio-init

✅ Succeeded
26 seconds
clone-repository

✅ Succeeded
18 seconds
appstudio-configure-build

✅ Succeeded
3 minutes
build-container

✅ Succeeded
24 seconds
show-summary

Pipelines as Code CI/test-component-pac-atqt-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
8 seconds
appstudio-init

✅ Succeeded
19 seconds
clone-repository

✅ Succeeded
9 seconds
appstudio-configure-build

✅ Succeeded
2 minutes
build-container

✅ Succeeded
8 seconds
show-summary


Improve footnote rendering in tex

Two things:
(1) there are two new lines after a footnote inline close. I think we can improve this a bit!
(2) We should raise and show errors in latex, e.g. when a reference to a foot note is not found!

Thoughts @fwkoch?

This PR fixes the trailing whitespace issue: https://github.com/executablebooks/mystjs/pull/277
It also adds warnings when a footnote definition is not found... However - this case will not usually come up because the markdown-it parser does not parse references without definitions  - See this issue: https://github.com/executablebooks/mystjs/issues/278

The other issue is tackled here:

https://github.com/executablebooks/myst-theme/pull/26

🚀  Thanks @fwkoch


parser and AST as a separated library?

I want a library that implements AST for TOML for node.js. this eslint plugin looks to have that mechanism but is not a simple library. Could you publish it as a separate library?

Sorry, i found the AST tree doesn't have full information about TOML file like whitespace so this is not what i want.


navbar bug fixed && active styling added

Please mention the issue number so that I can assign the correct labels on your PR


Reconfigure main funfix project to not bundle dependencies

Fixes #83.
The main funfix project bundles everything. This can lead to issues like #83 because the data types in funfix won't be seen by the JS runtime as the data types in the sub-projects. So for example funfix-effect.IO will be a different class from funfix.IO.
Which shouldn't count for much, but because of the duplication we can end up with unforeseen effects, plus this takes users by surprise.
Going forward the main funfix no longer bundles its sub-projects, but treats them as normal (imported) dependencies.

Already on master, to be released in 7.0.0-rc.3.


YARP: Another Recursive Acronym Project

"YARP: A Reverse Proxy" really is the preferred project name.


Add animating to play/pause animation for ProgressRing like in CupertinoActivityIndicator

Is your feature request related to a problem? Please describe.
A nice-to-have, like for indicating that a process is intentionally halted.
Describe the solution you'd like
ProgressRing(
  //...
  animating: false,
)

Describe alternatives you've considered
Additional context

The Win UI guidelines don't provide a guidance for a stopped indeterminate progress indicator.  Learn more
Would setting value: 0 do it for your case?

Not what I want, but I guess I'll try another way


Failed during dump collection cannot recover

I am trying to sync mongodb replica to elasticsearch using mongo-connector. It works fine when I insert the first doc in my collection "check". But getting "Failed during dump collection cannot recover" error in mongo-connector.log during the second doc insertion. Due to this error, the second doc is getting loaded into an elasticsearch index.
The command I used is:
To start Mongo replica: sudo mongod --port 27017 --dbpath /_/__/_/** --replSet rs0
To start Mongo Connector: mongo-connector -m localhost:27017 -t localhost:9200 -d elastic_doc_manager --auto-commit-interval=0 -n a.check
Mongo-connector.log :
2016-10-13 17:27:45,381 [CRITICAL] mongo_connector.oplog_manager:630 - Exception during collection dump
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/oplog_manager.py", line 583, in do_dump
upsert_all(dm)
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/oplog_manager.py", line 567, in upsert_all
dm.bulk_upsert(docs_to_dump(namespace), mapped_ns, long_ts)
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/util.py", line 43, in wrapped
reraise(new_type, exc_value, exc_tb)
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/util.py", line 32, in wrapped
return f(_args, *_kwargs)
File "/usr/local/lib/python2.7/dist-packages/mongo_connector/doc_managers/elastic_doc_manager.py", line 214, in bulk_upsert
for ok, resp in responses:
File "/usr/local/lib/python2.7/dist-packages/elasticsearch/helpers/init.py", line 160, in streaming_bulk
for result in _process_bulk_chunk(client, bulk_actions, raise_on_exception, raise_on_error, **kwargs):
File "/usr/local/lib/python2.7/dist-packages/elasticsearch/helpers/init.py", line 89, in _process_bulk_chunk
raise e
ConnectionFailed: ConnectionTimeout caused by - ReadTimeoutError(HTTPConnectionPool(host=u'localhost', port=9200): Read timed out. (read timeout=10))
2016-10-13 17:27:45,381 [ERROR] mongo_connector.oplog_manager:638 - OplogThread: Failed during dump collection cannot recover! Collection(Database(MongoClient(host=['localhost:27017'], document_class=dict, tz_aware=False, connect=True, replicaset=u'rs0'), u'local'), u'oplog.rs')
2016-10-13 17:27:46,376 [ERROR] mongo_connector.connector:304 - MongoConnector: OplogThread <OplogThread(Thread-2, started<PHONE_NUMBER>19584)> unexpectedly stopped! Shutting down
FYI, I am using elasticsearch 2.3.1 ,mongodb 3.0.12 and mongo-connector 2.4.1

Looks like you are hitting a ReadTimeoutError on Elastic. Try increasing the timeout using a config file such as:
{
  "mainAddress": "localhost:27017",
  "verbosity": 3,
  "namespaces": {
    "include": ["a.check"]
  },
  "docManagers": [
    {
      "docManager": "elastic_doc_manager",
      "targetURL": "localhost:9200",
      "autoCommitInterval": 0,
      "args": {
        "clientOptions": {"timeout": 30}
      }
    }
  ]
}

You also can use the continueOnError option to force mongo-connector to log and ignore errors during the collection dump.

I'm also running in this error suddenly, when doing a resync. It worked for a long time.
2017-01-19 12:43:52,690 [CRITICAL] mongo_connector.oplog_manager:666 - Exception during collection dump
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/mongo_connector/oplog_manager.py", line 621, in do_dump
    upsert_all(dm)
  File "/usr/local/lib/python2.7/dist-packages/mongo_connector/oplog_manager.py", line 607, in upsert_all
    mapped_ns, long_ts)
  File "/usr/local/lib/python2.7/dist-packages/mongo_connector/util.py", line 44, in wrapped
    reraise(new_type, exc_value, exc_tb)
  File "/usr/local/lib/python2.7/dist-packages/mongo_connector/util.py", line 33, in wrapped
    return f(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/mongo_connector/doc_managers/elastic2_doc_manager.py", line 367, in bulk_upsert
    for ok, resp in responses:
  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/helpers/__init__.py", line 162, in streaming_bulk
    for result in _process_bulk_chunk(client, bulk_actions, raise_on_exception, raise_on_error, **kwargs):
  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/helpers/__init__.py", line 91, in _process_bulk_chunk
    raise e
ConnectionFailed: ConnectionTimeout caused by - ReadTimeoutError(HTTPConnectionPool(host=u'localhost', port=9200): Read timed out. (read timeout=60))
2017-01-19 12:43:52,703 [ERROR] mongo_connector.oplog_manager:674 - OplogThread: Failed during dump collection cannot recover! Collection(Database(MongoClient(host=[u'localhost:27017'], document_class=dict, tz_aware=False, connect=True, replicaset=u'singleNodeRepl'), u'local'), u'oplog.rs')
2017-01-19 12:43:53,241 [ERROR] __main__:357 - MongoConnector: OplogThread <OplogThread(Thread-3, started<PHONE_NUMBER>56672)> unexpectedly stopped! Shutting down

I'm using mongo-connector version 2.5.0, pymongo version 3.4.0, MongoDB version 3.2.10 and elastic2_doc_manager version 0.3.0.
I already raised the timeout to 60 like you can see in the log.
Previously, the following error appeared already so that I had to start the resync:
2017-01-19 08:58:36,553 [ERROR] mongo_connector.doc_managers.elastic2_doc_manager:412 - Exception while commiting to Elasticsearch
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/mongo_connector/doc_managers/elastic2_doc_manager.py", line 406, in commit
    successes, errors = bulk(self.elastic, action_buffer)
  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/helpers/__init__.py", line 190, in bulk
    for ok, item in streaming_bulk(client, actions, **kwargs):
  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/helpers/__init__.py", line 162, in streaming_bulk
    for result in _process_bulk_chunk(client, bulk_actions, raise_on_exception, raise_on_error, **kwargs):
  File "/usr/local/lib/python2.7/dist-packages/elasticsearch/helpers/__init__.py", line 91, in _process_bulk_chunk
    raise e
ConnectionTimeout: ConnectionTimeout caused by - ReadTimeoutError(HTTPConnectionPool(host=u'localhost', port=9200): Read timed out. (read timeout=10))

Don't know if this affects the newest error.
Should I just set continueOnError? Are documents ignored (=>not synced), when an error appears and this option is set?

With continueOnError, documents that fail to sync during the collection dump period will be ignored. The general problem is that the Elasticsearch doc managers do not retry on connection/operation failure, see https://github.com/mongodb-labs/elastic2-doc-manager/issues/18.
For now, I can only recommend increasing the Elasticsearch client timeout again. Do you see any errors or warnings in the Elasticsearch logs?


refactor: consider deleting rapid_domain and move its content to the default domain package of each project

This include updates so every non default domain package has a ref on the default domain package in order to use the value object and its related classes

Discarded because better solution was added


Dockerslim comms port and ssl issues while running in Tekton task

Expected Behavior
Image should be optimised and pushed to registry.

Actual Behavior
Dockerfile is failing with ssl issues, even though ports are open and firewall has no restrictions.
docker-slim: message='join the Gitter channel to ask questions or to share your feedback' info='https://gitter.im/docker-slim/community'
docker-slim: message='join the Discord server to ask questions or to share your feedback' info='https://discord.gg/9tDyxYS'
docker-slim: message='Github discussions' info='https://github.com/docker-slim/docker-slim/discussions'
docker-slim[build]: info=probe message='changing continue-after from probe to enter because http-probe is disabled'
cmd=build state=started
cmd=build info=params context=./file=demo1/manifests/ocp4-np1-lz-aws/Dockerfile continue.mode=enter rt.as.user=true keep.perms=true
cmd=build state=building message='building basic image'
cmd=build info=basic.image.info tag=docker-slim-tmp-fat-image.13.20230603123528 dockerfile=demo1/manifests/ocp4-np1-lz-aws/Dockerfile context=.
cmd=build build logs (standard image) ====================
Step 1/6 : FROM quay.apps.lz-np2.ent-ocp4-useast1.aws.internal.das/openshift-base-images/ubi8-nodejs16-oracle-nettools-image-with-certs:latest
---> ee7720cc4911
Step 2/6 : USER root
---> Using cache
---> b28ff6e44cd4
Step 3/6 : COPY ./cacerts/cacerts /etc/pki/ca-trust/extracted/java/cacerts
---> f994e77ffb93
Step 4/6 : COPY ./cacerts/cacerts /usr/share/pki/ca-trust-source/anchors/cacerts
---> 42d01648e776
Step 5/6 : COPY ./cacerts/cacerts /etc/pki/ca-trust/source/anchors/cacerts
---> 8d5e4d861ff3
Step 6/6 : RUN yum install curl -y
---> Running in bb2b58f69a7d
Updating Subscription Management repositories.
Unable to read consumer identity
Subscription Manager is operating in container mode.
This system is not registered with an entitlement server. You can use subscription-manager to register.
Red Hat Universal Base Image 8 (RPMs) - BaseOS  0.0  B/s |   0  B     00:00
Errors during downloading metadata for repository 'ubi-8-baseos-rpms':

Curl error (6): Couldn't resolve host name for https://cdn-ubi.redhat.com/content/public/ubi/dist/ubi8/8/x86_64/baseos/os/repodata/repomd.xml [Could not resolve host: cdn-ubi.redhat.com]
Error: Failed to download metadata for repo 'ubi-8-baseos-rpms': Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
cmd=build end of build logs (standard image) =============

If i remove any RUN command from dockerfile it is giving comms ports error
docker-slim: message='join the Gitter channel to ask questions or to share your feedback' info='https://gitter.im/docker-slim/community'
docker-slim: message='join the Discord server to ask questions or to share your feedback' info='https://discord.gg/9tDyxYS'
docker-slim: message='Github discussions' info='https://github.com/docker-slim/docker-slim/discussions'
docker-slim[build]: info=probe message='changing continue-after from probe to enter because http-probe is disabled'
cmd=build state=started
cmd=build info=params context=./file=demo1/manifests/ocp4-np1-lz-aws/Dockerfile continue.mode=enter rt.as.user=true keep.perms=true
cmd=build state=building message='building basic image'
cmd=build info=basic.image.info tag=docker-slim-tmp-fat-image.12.20230603125012 dockerfile=demo1/manifests/ocp4-np1-lz-aws/Dockerfile context=.
cmd=build state=basic.image.build.completed
cmd=build state=image.inspection.start
cmd=build info=image id=sha256:f946673b3b279928e0ef4a58f1a04e0751664ac27c7050735ceac37dd6a3630d size.bytes=1352761934 size.human=1.4 GB
cmd=build info=image.users exe='root' all='1001,root,1001,root,1001,root,1001,root'
cmd=build info=image.stack index=0 name='slim-tmp-fat-image.13.20230529165610:latest' id='sha256:ee7720cc49118c5a8280baf154006d8ebfeae5866c3897a6400635f61e1a5f34'
cmd=build info=image.stack index=1 name='docker-slim-tmp-fat-image.12.20230603125012:latest' id='sha256:f946673b3b279928e0ef4a58f1a04e0751664ac27c7050735ceac37dd6a3630d'
cmd=build info=image.exposed_ports list='8080'
cmd=build state=image.inspection.done
cmd=build state=container.inspection.start
cmd=build info=container status=created name=dockerslimk_12_20230603125014 id=7d0b000fb36d1a7583452b9ecfc3cc9a30c4c9db91570c434aaf06de25a85260

Steps to Reproduce the Problem

Specifications

Version: latest
Platform: Tekton

@pashaimran looks like you are using slim to build your regular image for you by pointing at your Dockerfile. And when the image is building Docker can't resolve the cdn-ubi.redhat.com domain. This is normally addressed with extra flags to the docker build command and slim has similar parameters (e.g., cbo-add-host and other cbo-* flags). Either way, I would recommend starting simple where you don's use slim to build the original image for you. You should also start with a local setup first before you do it in Tekton. It'll make it much easier to debug :-)
For additional debug information you should add the global --debug flag and the --show-clogs flag for build command: slim --debug build --show-clogs YOUR_OTHER_FLAGS_HERE YOUR_TARGET_IMAGE_NAME_HERE
It also appears you are using an older version of slim. The current version is 1.40.2. Note the executable name changes there.


Enhancement: Review and determine mandatory parameters for comment.createInlineComment method

Hi Vladislav @MrRefactoring,
Are you still looking for help with these issues?
I've recently used this package to build a feature at work and found it helpful. I'm not very experienced with open source, but I'd like to help.


Trying to use COMTE and TSR but facing when plotting features #43

Hello,
I am doing multivariate time series classification with 2 features.
When using the plot function with either COMTE or TSR only a portion of the features are being plotted for each instance.
When I debugged I suspected an issue with the reshape done in the plot.
BEFORE Reshape: In the below screenshot is the item values we can see 2 features starting both from 0 value:

AFTER Reshape: here we see that the reshape didn't conserve all the values of the feature (we can that not both features are starting at 0)

This is happening inside both plot functions: plot_in_one in CF.py at line 181 when it reshape the item
and plot in Saliency_Base.py at line 61 when it reshape the item
Note: I am using tensorflow
can you please help ? am I missing something or there is a bug ?

Hello @JHoelli
Thank you for your reactivity !
Since you marked it as a bug do you any estimations when will you submit a fix?

Hi,
I am currently fixing it. I hope to finish it in a few hours (afternnon / evening CEST ). (Checking for side effects unfortunately needs some time).

Hi,
you can install the patch with https://github.com/fzi-forschungszentrum-informatik/TSInterpret/archive/refs/heads/swpaxes.zip would be great if you could provide feedback, before I merge everything into the main branch.
Thanks for reporting the issue.

Great, I just merged it in the Main Branch.
The code will be available via PyPi with Release 0.4.4. (The release might take one or two more weeks.)


how to active draggable after search

Hi... i want to make draggable maker after search, but i read the documentation i not find about draggable. Thanks

@SamSamskies you have references about it ? thanks


Add tabular view

Can you expand on this issue?
I'm not sure I should open a separate issue but one thing I've found is that after clicking on a frame, I have to refresh the page to go back to the full view. It might be nice if there was a menu at the top to undo zooming into specific frames


gstDecoder fail!!

Hi,
I've been using the jetson inference and I want to stream a video from the jetson to my PC so I tried to use the RTP protocol as mentioned in the docs. I run the command "video-viewer --device=/dev/video0 --input-codec=h264 rtp://:
and I run in this issue :

I'm using jetson as headless mode with an USB camera

Hi @Aziz-repo, try this command line instead:
video-viewer --input-codec=h264 /dev/video0 rtp://<IP_ADDRESS>:5000

Replace <IP_ADDRESS> with the IP address of your PC (or hostname of your PC)


Cyclic calls in NonCyclicNetwork generation

See Sort() in lower left corner

not an issue. it's recursive


LICENSE: respect MIT by rolling back license

MIT doesn't allow you to change the LICENSE information.
I'm rolling back the LICENSE file and adjusting the attribution on README seeking to respect the original licensing.

I'd also would like to know if you'd like to join Oh My Fish organisation as a maintainer of oh-my-fish/plugin-gvm. We could replace the current version by the one in this repository. If you'd like to, I could add you as maintainer and you could push a commit replacing the current code by this one. What you think about?

Ah, so sorry about that 😐
Also yep, I'd like to do that. Thanks!