[facebook] Download Facebook authenticated only videos

Please follow the guide below
Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.08.04. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[X] I've verified and I assure that I'm running youtube-dl 2018.08.04

Before submitting an issue make sure you have:

[X] At least skimmed through the README, most notably the FAQ and BUGS sections
[X] Searched the bugtracker for similar issues including closed ones
[X] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[X] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
bash-3.2$ ./youtube-dl https://www.facebook.com/Chefclubcocktailsuk/videos/1556391614435227/ --username MyUsername --password MyPassword -v
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'https://www.facebook.com/Chefclubcocktailsuk/videos/1556391614435227/', u'--username', u'PRIVATE', u'--password', u'PRIVATE', u'-v']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.08.04
[debug] Python version 2.7.10 (CPython) - Darwin-15.6.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
[facebook] Downloading login page
[facebook] Logging in
[facebook]<PHONE_NUMBER>435227: Downloading webpage
[facebook]<PHONE_NUMBER>435227: Downloading webpage
[facebook]<PHONE_NUMBER>435227: Downloading webpage
ERROR: Unable to download webpage: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
File "./youtube-dl/youtube_dl/extractor/common.py", line 599, in _request_webpage
return self._downloader.urlopen(url_or_request)
File "./youtube-dl/youtube_dl/YoutubeDL.py", line 2211, in urlopen
return self._opener.open(req, timeout=self._socket_timeout)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 437, in open
response = meth(req, response)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 550, in http_response
'http', request, response, code, msg, hdrs)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 475, in error
return self._call_chain(*args)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 409, in _call_chain
result = func(*args)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 558, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

Description of your issue, suggested solution and other information
When trying to download a private video on Facebook, even if the authentication is successful. This issue similar to closed #17050. But this fix doesn't work anymore.

I have the same issue

$ youtube-dl -v --proxy socks5://<IP_ADDRESS>:9350 --netrc https://www.facebookcorewwwi.onion/InsidersABC/videos/544227449349547/
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'--proxy', u'socks5://<IP_ADDRESS>:9350', u'--netrc', u'https://www.facebookcorewwwi.onion/InsidersABC/videos/544227449349547/']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.09.01
[debug] Python version 2.7.12 (CPython) - Linux-4.15.0-33-generic-x86_64-with-LinuxMint-18.3-sylvia
[debug] exe versions: avconv 2.8.15-0ubuntu<IP_ADDRESS>, avprobe 2.8.15-0ubuntu<IP_ADDRESS>, ffmpeg 2.8.15-0ubuntu<IP_ADDRESS>, ffprobe 2.8.15-0ubuntu<IP_ADDRESS>
[debug] Proxy map: {u'http': u'socks5://<IP_ADDRESS>:9350', u'https': u'socks5://<IP_ADDRESS>:9350'}
[facebook] Downloading login page
[facebook] Logging in
[facebook]<PHONE_NUMBER>49547: Downloading webpage
[facebook]<PHONE_NUMBER>49547: Downloading webpage
ERROR: This video is only available for registered users. Use --username and --password or --netrc to provide account credentials.
Traceback (most recent call last):
File "/home/andrewm/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 792, in extract_info
ie_result = ie.extract(url)
File "/home/andrewm/bin/youtube-dl/youtube_dl/extractor/common.py", line 502, in extract
ie_result = self._real_extract(url)
File "/home/andrewm/bin/youtube-dl/youtube_dl/extractor/facebook.py", line 471, in _real_extract
video_id, fatal_if_no_video=True)
File "/home/andrewm/bin/youtube-dl/youtube_dl/extractor/facebook.py", line 351, in _extract_from_url
self.raise_login_required()
File "/home/andrewm/bin/youtube-dl/youtube_dl/extractor/common.py", line 903, in raise_login_required
expected=True)
ExtractorError: This video is only available for registered users. Use --username and --password or --netrc to provide account credentials.
I did have a more complex password that had spaces and many words (long), I changed by password to be more simple (still random letters and numbers and 30 characters), but it still fails

There are no problems with fb over .onion address for videos that don't need a login.


Add patches to fix calculation of num_osd

Original commit message:
Subject: [PATCH] ceph-config: fix calculation of num_osds
The number of OSDs defined by the lvm_volumes variable is added to num_osds in task Count number of osds for lvm scenario. Therefore theses devices must not be counted in task
Set_fact num_osds (add existing osds).
There are currently three problems with the existing approach:

Bluestore DB and WAL devices are counted as OSDs
lvm_volumes supports a second notation to directly specify logical volumes instead of devices when the data_vg key exists. This scenario is not yet accounted for.
The difference filter used to remove devices from lvm_volumes returns a list of unique elements, thus not accounting for multiple OSDs on a single device

The first problem is solved by filtering the list of logical volumes for devices used as type block.
For the second and third problem lists are created from lvm_volumes containing either paths to devices or logical volumes devices. For the second problem the output of ceph-volume is simply filtered for lv_paths appearing in the list of logical volume devices described above.
To solve the third problem the remaining OSDs in the output are compiled into a list of their used devices, which is then filtered for devices appearing in the list of devices from lvm_volumes.
Fixes: https://github.com/ceph/ceph-ansible/issues/7435

iThis does not seem to move along upstream, so I propose to add the patches in our container build

quincy patch fixed, CI is happy now


Question: How to use Datetime for Axis

I want to make a graph that shows a cumulative count over time.
The closet thing I could figure out is a cumulative count over the days since the first datetime. But that is not really suitable.
#let data = csv("data/cypress-release.csv").slice(1)
#let dates = data.map(row => str_to_datetime(row.at(0).trim("Z"))).rev()
#let first_date = dates.at(0)
#let day_differences = dates.map(date => int(datetime_day_difference(first_date, date)))
#let x_axis = axis(min: 0, max: day_differences.last(), step: 250, location: "bottom", title: "Days since first release")
#let y_axis = axis(min:0, max: day_differences.len(), step: 10, location: "left", title: "Cumulative release count")
#let enum = day_differences.enumerate()
#let enumT = enum.map(row => (row.at(1), row.at(0)))
#let pl = plot(data: enumT, axes: (x_axis, y_axis))
#graph_plot(pl, (100%, 25%))
// this could probably also be a lot cleaner

I know about the value field on the axis, but I don't know how I could get the spacing correct with this.
Is this possible with the current version of this?

Sadly this currently isn't possible because values are exactly what gets drawn - to allow for not showing every values on an axis, we'd need to change how it gets drawn.
This will become a feature on the next release.

Okay, that makes sense. I'll probably pivot to something else right now, or is there some more or less concrete plan for the release?

Of course :)
Thanks for the great lib


Load object groups / objects, and add auto-reload support

This adds basic support for rectangular objects (including tile sprite objectes!) in Orthographic mode. We also add auto-reload support via asset events.
Note: this branch includes my other PR changes (tile rotation fix and dependent assets) as well as @framp's bevy 0.4.0 changes
if you want me to squash commits together to make it more mergeable, please LMK
Objects without tile maps also may be made visible by way of passing the debug configuration object to the TiledMapComponents bundle:
debug_config: DebugConfig {
    enabled: true,
    ..Default::default()
},

When an object is created, it fires an ObjectReadyEvent event which includes the map asset handle and the entity ID for the newly-created object. This allows additional custom behavior in consuming application (e.g. collision).
I haven't done any testing/implementation of isometric, as I haven't been working with isometric maps in my project :)
There isn't yet any support for round or polygon objects, but I wanted to do that next. Because it's hard to visualize and I like the bevy_tiled having the responsibility for spawning entities, I was going to add lyon as a dependency to allow debug visualizations of circle/polygon cases. However, I recognize how it might not make sense to open PRs after adding a new dependency, so I wanted to issue this PR first...
OTOH, if you like this direction, I will write up some documentation. and maybe find time to look at isometric objects.

This has been squashed into one commit on the bevy-0.4-objects branch and will soon be on main


system tests: LOCAL_IP_ENV setting ignored/broken in some cases

Building.md mentions a LOCAL_IP_ENV environment variable, which it says controls what local IP etcd will bind to but it doesn't seem to be honoured by all of the test code:
I ran sudo LOCAL_IP_ENV=<IP_ADDRESS> make st and it looked like it started etcd correctly:
docker run --detach \
--net=host \
--name calico-etcd quay.io/coreos/etcd:v2.0.11 \
--advertise-client-urls "http://<IP_ADDRESS>:2379" \
--listen-client-urls "http://<IP_ADDRESS>:2379,http://<IP_ADDRESS>:2379"

But the tests then fail at this stage, using the wrong IP (<IP_ADDRESS>):
======================================================================
ERROR: Test using different AS number for the node-to-node mesh.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/tests/st/test_base.py", line 45, in setUp
    self.curl_etcd("calico", options=["-XDELETE"])
  File "/tests/st/test_base.py", line 118, in curl_etcd
    shell=True)
  File "/usr/lib/python2.7/subprocess.py", line 574, in check_output
    raise CalledProcessError(retcode, cmd, output=output)
CalledProcessError: Command 'curl -sL http://<IP_ADDRESS>:2379/v2/keys/calico?recursive=true -XDELETE' returned non-zero exit status 7

@lwr20 You might be better placed to resolve this than me?

Yep - I'll take a look today


(doc) Link in the installation guide is not working

WHAT:
The link https://github.com/operator-framework/operator-lifecycle-manager/blob/master/deploy/tectonic-alm-operator/values.yaml is not working.
WHERE:
https://github.com/operator-framework/operator-lifecycle-manager/blob/master/Documentation/install/install.md

Our install docs should be up to snuff now. Thanks!


BUG: Scorecards for public repositories without issues sections won't be created

Describe the bug
We found out that if a respository has no issues section, then it's not possible to get a scorecard. The output in this case is  empty. An example Respoitory would be: https://github.com/onlyfyio/community.aws
Reproduction steps
Steps to reproduce the behavior:

Execute  scorecard --repo=github.com/onlyfyio/community.aws
Observe the result

Expected behavior
The previous command should display a scorecard as result
Additional context
Add any other context about the problem here.

What version of Scorecard are you using?
scorecard --repo=github.com/onlyfyio/community.aws works for me both at HEAD and v4.13.1.

Can't reproduce, but we can always re-open if you provide more info.

I'm using the newest version which is available in brew

I'm still unable to replicate.
brew install scorecard
scorecard version # returns v4.13.1
scorecard --repo=github.com/onlyfyio/community.aws

Works as expected
RESULTS
-------
Aggregate score: 4.0 / 10
...


[WIP] Model fuselage walls

Description

Implementation of fuselage walls based on the python implementation of @MarAlder. This fixes #587.
How Has This Been Tested?

So far, it was tested if the code properly generates the walls from the CPACS examples, see next section.
Screenshots, that help to understand the changes(if applicable):

test_fuselage_walls_ex1.xml

test_fuselage_walls_ex2.xml

test_fuselage_walls_ex3_labyrinth.xml

Checklist:

[ ] A test for the new functionality was added.
[x] All tests run without failure.
[x] The new code complies with the TiGL style guide.
[x] New classes have been added to the Python interface.
[ ] API changes were documented properly in tigl.h.

@joergbrech what is the current status? Still WIP, or can this be merged?

The implementation is finished. The only thing missing are unit tests. So we could either wait, or merge now and open a new issue. Up to you, @rainman110!

I think we don't need any special tests. Maybe add one test, where you load one of the cpacs files, create the walls and check that you get a shape. That should be enough.
Then I am okay to merge this.

@joergbrech The code looks good. Could you please just replace the MakeFace function with the one from tiglcommonfunctions?


Fast refresh doesn't seem to be enabled after updating next package

First of all, thank you for this amazing template.
I updated next package to 10.x with the hope to have fast refresh enabled but it seems it doesn't fast refresh. Any idea why?

Closing as this should be resolved now. It was due to components not being named properly. Related documentation here https://nextjs.org/docs/basic-features/fast-refresh#limitations


Organise Trait definitions page starting letter A-Z

Hi {austraits} team! Big fan 😃
I have been trying to go through the incredible number of traits by using the handy Trait definitions page on the package website. At the moment, there are so many traits that when using the website, the menu in the right hand pane doesn't work correctly (it doesn't scroll until you reach the very bottom).
Would it be possible to sort this list by setting the top headers as the letters A-Z, rather than the trait names? I think this will make it easier to search traits and hopefully fix the right-pane menu. For example:
# A
### accessory_cost_mass
### accessory_cost_fraction

# B
### bark_mass_area
### bark_density

# etc...

Hi @daxkellie ! Thanks for the positive work and feedback.
The documentation of trait definitions is actually moving to it's own repository, https://traitecoevo.github.io/APD/
We now have the dictionary accessible as

human readable text at https://traitecoevo.github.io/APD/ and via https://w3id.org/APD/
on zenodo at https://zenodo.org/record/8040790
on ARDCs Research Vocals at https://vocabs.ardc.edu.au/viewById/649

We will but haven't yet updated the documentation in this repo to point to these locations
Interested to hear how usable you find these other sources!

Oh yeah, and a paper available at https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>5047.abstract

I will close this issue in favour of #74 which has a much clearer scope! I do like Dax's suggestion about the alphabetical ordering which the APD has already.


Allow users to set default heartbeat & retry times

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
UI Feature
🔖 Feature description
Everytime you add a new monitor, you must change the default tie to something else unless you want it at 60s with no retries. For example, I like to use 180s heartbeat, 3 retries, 30s apart
✔ Solution
In settings, allow a field to change the default value for heartbeart, retries and retry time.
❓ Alternatives
There's no alternative.
📝 Additional Context
No response

This feature would be really handy for those with custom preferences

What is the difference between cloning+grouping monitors and what you requested.
I think this functionality is already here, but in an slightly different formfactor


Flash Radio

Comp bot's radio (router) must be updated to the latest firmware.
Flashing
A complete guide on flashing the radio can be found here: https://docs.wpilib.org/en/latest/docs/getting-started/getting-started-frc-control-system/radio-programming.html
Settings
Make sure to use the following settings for the radio:
Team: 5024
WPA Key: raiderrobotics
Radio: OpenMesh
Mode: 2.4GHz Access Point
Robot Name: CarterIsChaotic
Firewall: <un-checked>
BW Limit: <checked>

Pushing this back to week 2.
@SRJacks  can you do this at lunch time or after school on Monday and Wednesday?

The radio names are:

Robot Name
Radio name

MiniBot
DarianIsDaring

Competition bot
CarterIsChaotic

Router in the grey tote
(unknown for now)

Requirements have been updated in description


Vite preview mode

vite has a preview command allow locally preview production build, steps:

vite build
vite preview

now you can start you application in preview mode (using production built files)
since vite use esbuild in dev mode, and rollup in production mode, preview mode is useful to debug production only issues.
It is awesome if vite_ruby can support preview mode.

You can already leverage auto-build, which is enabled by default in development. When not starting the Vite dev server, a build will be triggered, and the app will use the built assets (which is what preview mode does).
If you want to test something production specific, you can always run bin/vite build --mode production and start your Ruby app in production mode.


python3Packages.pysmart: init at 1.1.0

Motivation for this change
The other similar project already packaged pysmart-smartx is in an abandoned state
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

It does the same thing but is maintained


restrict certificate type for builtin SSH server

While doing some sanity checks over OpenSSH's code for how they handle certificates authentication. I stumbled on an condition that checks the certificate type is really an user certificate on the server-side authentication. This checks seems to be a formality and just for the sake of good domain seperation, because an user and host certificate don't differ in their generation, verification or flags that can be included.
Add this check to the builtin SSH server to stay close to the unwritten SSH specification.

(cherry picked from commit de35b141b79a3d6efe2127ed2c73fd481515e481)
Refs: https://codeberg.org/forgejo/forgejo/pulls/1172
:warning: BREAKING :warning:
This is an breaking change for setups where the builtin SSH server is being used and for some reason host certificates were being used for authentication.

Breaking label added, good to go imho.

In the unlikely event this is breaking someone's workflow, I guess a option could be introduced to skip this check, but as I see it, this is not configurable in OpenSSH either.


Menu BG is pink?

FAQ

[X] I have checked the FAQ and it didn't resolve my problem.

Announcement

[X] I have checked Breaking change announcement.

Description
When I use my menu it is pink and despite setting:
" gray
highlight! CmpItemAbbrDeprecated guibg=#000000 gui=strikethrough guifg=#808080
" blue
highlight! CmpItemAbbrMatch guibg=#000000 guifg=#569CD6
highlight! CmpItemAbbrMatchFuzzy guibg=#000000 guifg=#569CD6
" light blue
highlight! CmpItemKindVariable guibg=#000000 guifg=#569CD6
highlight! CmpItemKindInterface guibg=#000000 guifg=#569CD6
highlight! CmpItemKindText guibg=#000000 guifg=#569CD6
" pink
highlight! CmpItemKindFunction guibg=#000000 guifg=#569CD6
highlight! CmpItemKindMethod guibg=#000000 guifg=#569CD6
" front
highlight! CmpItemKindKeyword guibg=#000000 guifg=#569CD6
highlight! CmpItemKindProperty guibg=#000000 guifg=#569CD6
highlight! CmpItemKindUnit guibg=#000000 guifg=#569CD6

Is there not a bg color setting?
Expected behavior
Bg is a senseble color that is easily readable by default
Actual behavior
Bg is pink

nvim-cmp doesn't define any color for the menu but instead links to existing colorscheme group (i.e. Pmenu). perhaps your config/colorscheme doesn't have any highlighting defined for Pmenu, so it fallbacks to its default colors (that pink background)

thank you Can you document this it would have saved a lot of time


运行devika.py报错

用pyhton运行devika.py之后，提示：
No sentence-transformers model found with name sentence-transformers/all-MiniLM-L6-v2. Creating a new one with MEAN pooling

用pyhton运行devika.py之后，提示： No sentence-transformers model found with name sentence-transformers/all-MiniLM-L6-v2. Creating a new one with MEAN pooling


Spotify song metadata is blank on fresh start

The global metadata from the Spotify app sometimes is empty. Switching to a different app and then back to Spotify fixes it.
Switching songs shows the proper metadata and then it goes blank again.

Another clue: The IC song selection displays the current song but doesn't restart it when clicking.

I believe this is because the Connected Spotify app is updating its playback progress to the car, even though it isn't the active app. The latest version of Spotify does not seem to show this behavior. I haven't yet figured out why the car stops showing this blank screen after switching apps.

The latest version of Spotify does not seem to show this behavior.

The latest version of the Spotify app for Android seems to have dropped support for the iDrive integration.
see  https://community.spotify.com/t5/Other-Partners-Web-Player-etc/BMW-Connected-Drive-deprecation/m-p/5011216#M71993

I think this will be fixed with #103 since my app will be posting its own global metadata

This can be closed as well I think - or is #103 not merged into master yet ?

Yeah I believe this can be closed. It has been merged, but mostly the problem disappeared on its own because the official Spotify stopped supporting the car protocol.
The only situation that it would come up now is if a user has downgraded to an old version of Spotify to enable Searching through MediaBrowserService support. Once #104 is implemented, there should be no reason to run anything older than the latest version of Spotify, and this problem will never exist again :)


Optimize lightmapper using triangle clusters on the acceleration structure.

Originally suggested by @reduz in this post.
Add an additional layer of indirection to the grid used by the lightmapper to store fixed-size triangle clusters. Greatly speeds up baking times on scenes with high triangle density, as the clusters will help to avoid unnecessary checks when the triangle density is high on the scene.
Unreal Sun Temple (from https://github.com/godotengine/godot/issues/75440).
Master: Done baking lightmaps in 00:04:39.
PR: Done baking lightmaps in 00:01:10.

Sponza
Master: Done baking lightmaps in 00:00:56.
PR: Done baking lightmaps in 00:00:37.

So far I haven't been able to see if this introduces any errors as the results look identical to me (which is good news as the results would be invalidated otherwise). We should double check as much as possible that nothing breaks before we're sure we want this merged.
Feel free to test it out if you get similar reductions in baking speed and ensuring nothing breaks. Don't expect much gains in scenes with low geometry density, as the optimizations are oriented entirely around reducing ray-triangle intersections in scenes where there was a significant amount of triangles per cell.

Rebased to fix conflicts with indirect bounces, taking it out of drafts for further testing.

Can we just talk about how terrible these shadows are? And yes, I understand that they can be improved in the settings, but they are still incredibly low resolution, is there any solution to make shadows at least look normal in baked maps?

Can we just talk about how terrible these shadows are?

This is unrelated to this pull request, but they look like this for two reasons:

I left Angular Distance to 0, so there is no variable penumbra for the static directional shadows.
Bicubic sampling isn't reimplemented yet.

Re-ran the test (with higher quality settings) with the rebased version, the performance differential remains pretty much the same in the Unreal Sun Temple.
Master: Done baking lightmaps in 00:15:02.
PR: Done baking lightmaps in 00:03:28.

Lightmap texel size decreased to 0.05 (reimported)
Angular Distance set to 0.5
Denoising is enabled
Baking on Ultra crashes instantly, but after adjusting and finally baking it still looks horribly low res, I know this has nothing to do with this pull request but it's just insaine.

Lightmap texel size decreased to 0.05 (reimported) Angular Distance set to 0.5 Denoising is enabled Baking on Ultra crashes instantly, but after adjusting and finally baking it still looks horribly low res, I know this has nothing to do with this pull request but it's just insaine.
Please pay attention to these terrible shadows, it’s simply unbearable to release first half-baked 4.0 and then 4.1 and now 4.2 with this

Ultra has absolutely nothing to do with what you're trying to fix here. You want higher resolution and better mapping, not more rays. Please move this discussion elsewhere. The goal of the PR is for the results to look identical and it is a very low level optimization that has zero relation to the lightmapper's behavior (it just traces the rays faster).

Thanks!


slots when using with component

I try to change default messages in vue-infinite. I am using infinite within imported component. Where should I put slots in order them to take effect

...
<infinite-loading :on-infinite="onInfinite" ref="infiniteLoading" key="infinite" spinner="circles"</infinite-loading>

            this does not effect

</template>```

Put your code inside the component tags, like this:
<infinite-loading>
  content
</infinite-loading>

Gotcha! Thanks again!

You're welcome :P


Link failures in CI when I use this action

With this action I get link errors in CI (failure to find a Foundation symbol!) that I don't get if I use swift-actions/setup-swift@v1 instead.  I think you must be setting something up incorrectly.
Building for debugging...
dyld[7460]: Symbol not found: (_$s10Foundation11JSONDecoderC6decode_4fromxxm_AA4DataVtKSeRzlFTj)
  Referenced from: '/Users/runner/work/hylo/hylo/hylo/.build/plugins/tools/debug/GenerateHyloFileTests'
  Expected in: '/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation'
[5/14] Generating HyloFileTests.swift
Error: Process completed with exit code 1.

The complete log of my failing build is
here.

This is strange, never faced any linker errors in my repos where I am using this action. Would love feedback on what is being set as wrong, macOS specific implementation can be found here.

I have no idea; I've never written a GitHub action and wouldn't know what this source means.  I'd compare the code of the two actions if I were you to look for likely culprits.

As you can see from the build results on the  commit referenced above, that link error is not reproducing, so I'm going to close this issue.  Thanks for your attention!

Glad to know @dabrahams you got this resolved.


Variable name mismatch in Example 2 of Set-AzureOSDisk

Customer report via LiveFyre
https://docs.microsoft.com/en-us/powershell/module/Azure/Set-AzureOSDisk
Example 2: Set the host cache mode to ReadWrite
Mistake on second powershell command, you declared $VM
Check the variable $myVM2 is wrong => suppose to be $VM

PR#4497 merged - closing issue


Tests failing on GPU

I noticed we currently have some tests failing in GPU. @dereklhansen could you fix or change the vae ones depending on what you think is worth keeping? Thank you!
FAILED case_studies/sdss_galaxies/tests/test_location_encoder.py::test_sdss_location_encoder - RuntimeError: scatter_add_cuda_kernel does not have a deterministic implementati...
FAILED case_studies/sdss_galaxies/tests/test_location_encoder.py::test_location_encoder_plotting - RuntimeError: scatter_add_cuda_kernel does not have a deterministic implemen...
FAILED case_studies/sdss_galaxies_vae/tests/test_galaxy_flow.py::test_galaxy_flow - RuntimeError: index_add_cuda_ does not have a deterministic implementation, but you set 'to...
FAILED case_studies/sdss_galaxies_vae/tests/test_galaxy_vae.py::test_galaxy_autoencoder_toy_gaussian - assert 55.28435134887695 < 25
FAILED case_studies/sdss_galaxies_vae/tests/test_galaxy_vae.py::test_galaxy_autoencoder_bulge_disk - assert 34.46749496459961 < 30

I'll just raise the threshold - I didn't change the numbers from the auto encoder so they aren't applicable

EDIT: Didn't realize these were max residuals, so they are comparable. Still, I think raising the threshold is fine since the real data is working.

Sounds good, #487 should also address the 3rd error I think (along with the first two)


Move layerset logic into lua scripts

Working on #138.
Using an INI file to define the layers to load.  The main lua script (run.lua) and the post-processing SQL (run-sql.lua) both use the INI to load or not load layers.  Using LuaSQL to run the SQL Scripts.
Current status: works with manual steps outlined in docs/MANUAL-STEPS-RUN.md and via docker image built from this branch
Still todo

[ ] Ensure make works
[ ] Update osm.pgosm_flex process to use LuaSQL instead of the current hack

Note:  Post-processing SQL must happen in a distinct step AFTER osm2pgsql.  Attempting to run the post-processing in the same script that defines styles does not wait to run post-processing until after it's done, it ends up running against the temp/unlogged tables that osm2pgsql drops and recreates. It is unlikely this will change -- see joto's response on this discussion.

Not sure why make isn't working, the Docker image itself seems good.
This works.
docker build -t rustprooflabs/pgosm-flex .
docker run --name pgosm -d --rm     -v ~/pgosm-data:/app/output     -v /etc/localtime:/etc/localtime:ro     -e POSTGRES_PASSWORD=$POSTGRES_PASSWORD     -p 5433:5432 -d rustprooflabs/pgosm-flex
docker exec -it     -e POSTGRES_PASSWORD=$POSTGRES_PASSWORD -e POSTGRES_USER=$POSTGRES_USER     pgosm python3 docker/pgosm_flex.py     --layerset=default --ram=1     --region=north-america/us     --subregion=district-of-columbia --debug

This does not work.
make

Resulting error.
Traceback (most recent call last):
  File "/app/docker/pgosm_flex.py", line 641, in <module>
    run_pgosm_flex()
  File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.9/dist-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/app/docker/pgosm_flex.py", line 121, in run_pgosm_flex
    run_osm2pgsql(osm2pgsql_command=osm2pgsql_command, paths=paths)
  File "/app/docker/pgosm_flex.py", line 606, in run_osm2pgsql
    output = subprocess.run(osm2pgsql_command.split(),
  File "/usr/lib/python3.9/subprocess.py", line 528, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['osm2pgsql', '-d', 'postgresql://postgres:mysecretpassword@localhost/pgosm?application_name=pgosm-flex', '--cache=675', '--slim', '--drop', '--output=flex', '--style=./run.lua', '/app/output/district-of-columbia-latest.osm.pbf']' returned non-zero exit status 1.
make: *** [Makefile:34: build-run-docker] Error 1

Aha! Thanks @jacopofar!!  That helped highlight my error in the Makefile.  I had updated the docker exec to use --layerset=run instead of layerset=default.  That typo was the problem.
Before this change the layerset defined the .lua style to run with the proper imports.  With this change the .lua scripts won't need to change, only the config passed in.
In its current state it can only load ini files under the layerset/ subdirectory, I'd like to make that flexible for any path.  Otherwise it won't be possible to customize via Docker w/out building a custom image.


Get the benchmark compiling / running again

put dependencies under glide management, will make it easier to keep this benchmark functional.
disable benchmarking the echo framework

The Echo framework has changed a bunch of its interfaces, and no longer
implements http.Handler in doing so. As such, Echo no longer works
within this framework.

disable the rivet framework

In testing, the rivet framework was returning 200s but the body was always empty. This looks to be an issue within rivet and less to with the benchmark

The echo thing is arguably that I was mildly lazy when working on this and didn't feel like rewriting all of its usage. If you'd like me to fix it instead of disable it, I cant try to spend some time getting it working here. Although, thinking about it quickly it may end up being a shim around the package itself which may impact the benchmarks.
Let me know!

The current master is using Go modules and is compiling again. Thanks a lot anyway!


Registering for a sync from an iframe?

What do y'all think about sync.register from an iframe or from a service worker with a non-top-level window client? I'm concerned about background sync abuse from third party content.

I assume we're all in violent agreement here?

I have two thoughts here -- I think that generally, we probably don't want to allow background work to be initiated by any content that doesn't have a top-level window. If you're not the primary thing that the user is interacting with, then maybe you shouldn't get those kind of privileges automatically.
The other thought is that by being only a 'best efforts' API, and never making any sort of guarantees to the site about if and when a sync will occur in the background, that we can safely allow a 'foreground only' mode in some situations -- basically anywhere that access would be granted to navigator.connection.onchanged. We could allow any content to register a sync, and it would only fire when the user is actually interacting with that page.

What is the check going to look like if you invoke this from a worker? Or a nested worker?

What is the check going to look like if you invoke this from a worker? Or a nested worker?

Check if the Service Worker has any main-frame window clients.

I'm not sure that works for a normal worker, though it might, or would those not have access to this API anyway?

You'd need to have some connection to your service worker in order to access serviceWorkerRegistration.sync. Workers should have that through the WorkerNavigator, I think, but I don't know if that's implemented anywhere yet.
In the short term, workers could get around it by posting back to their controlling document, which could register for them, if it is allowed to.

The other thought is that by being only a 'best efforts' API, and never making any sort of guarantees to the site about if and when a sync will occur in the background, that we can safely allow a 'foreground only' mode in some situations -- basically anywhere that access would be granted to navigator.connection.onchanged. We could allow any content to register a sync, and it would only fire when the user is actually interacting with that page.

Interesting. The advantage here is that if a page that was not designed to be in an iframe is later embedded in one, it will continue to function. The disadvantage is the cognitive load of knowing when onsync will and won't fire.

So is the conclusion here that we do indeed want to limit this API to only be available from an iframe if some top-level browsing context exists for the same origin as well?


Mobile and tablet: Dismissing notification bar leaves empty space

How to reproduce

Go to the site using a mobile device (I have used android and iphone)
Click on the x button on the beta banner

What happens
The message is removed, but leaves a white space underneath:

What should happen
The message should be removed, and the page should move up.

Fixed by #3420.  Thanks @yeraydiazdiaz !


refactor(robot-server): Use a non-nullable indexed enum for protocol_kind

Overview
Some tweaks to the protocol.protocol_kind SQL column, to throw in with database changes that we're doing anyway.
Changelog

Use an enum (both in the SQL sense and in the Python sense), to stop us from storing bad values, and to make the whole Python side a bit more type-safe. Follows the pattern set in #15650. Before, we were just using a plain str.
Do not allow NULL values. NULL was semantically identical to ProtocolKind.STANDARD and was only stored by the 4->5 migration. Our older migration system could only add nullable=True columns, but that's no longer the case.
Add an index so queries like "get all the quick-transfer protocols" or "count how many standard protocols there are" don't have to linearly scan the whole table. The higher-level code doesn't take advantage of this yet because it currently does its filtering in Python, but we should aim to move this kind of thing into SQL.

Database compatibility and merge sequencing
This intends to follow the plan started in #15650, which I understand as this:
The current public release is on schema 4. edge is on schema 5. #15650 abandons schema 5 in favor of 5.1. After #15650 merges, this PR, and a few others from @sanni-t, will merge in quick succession to modify 5.1 in-place. Then, a final PR will turn 5.1 into 6 and create a 5.0->6 migration. The aim of all of this is to make a few improvements on the database from what we have in 5, without introducing a migration for each of those improvements, and without tossing away the schema-5.0 data that's accumulated on all our internal robots.
Test Plan and Hands on Testing

[x] Run EXPLAIN QUERY PLAN in the sqlite3 CLI and make sure the index is working properly.

Otherwise, I'm leaning on automated tests.
Review requests

Am I understanding the merge sequencing plan correctly?
Is the merge sequence stack already too precarious for us to put this on top of it, too?

Risk assessment
This will make the final PR in the plan, which finalizes the 5->6 split, slightly more complicated. It's one more change that we have to remember to handle correctly.

Discussed with @sanni-t: Will rebase and reimplement atop https://github.com/Opentrons/opentrons/pull/15818, instead of merging into edge following https://github.com/Opentrons/opentrons/pull/15650.


Error: 'Browser.setWindowBounds' wasn't found

Using chrome latest (unstable). What is even more strange is when I call console.log(Browser) I see it defined but cannot use it.

Full Stack:
{ Error: 'Browser.setWindowBounds' wasn't found
    at ProtocolError (/Users/anton/personal/node-selenium-starter/node_modules/chrome-remote-interface/lib/chrome.js:14:9)
    at /Users/anton/personal/node-selenium-starter/node_modules/chrome-remote-interface/lib/chrome.js:69:28
    at Chrome.handleMessage (/Users/anton/personal/node-selenium-starter/node_modules/chrome-remote-interface/lib/chrome.js:247:13)
    at WebSocket.<anonymous> (/Users/anton/personal/node-selenium-starter/node_modules/chrome-remote-interface/lib/chrome.js:224:27)
    at emitTwo (events.js:106:13)
    at WebSocket.emit (events.js:191:7)
    at Receiver._receiver.onmessage (/Users/anton/personal/node-selenium-starter/node_modules/ws/lib/WebSocket.js:143:54)
    at Receiver.dataMessage (/Users/anton/personal/node-selenium-starter/node_modules/ws/lib/Receiver.js:385:14)
    at extension.decompress (/Users/anton/personal/node-selenium-starter/node_modules/ws/lib/Receiver.js:354:40)
    at _inflate.flush (/Users/anton/personal/node-selenium-starter/node_modules/ws/lib/PerMessageDeflate.js:279:12) code: -32601 }

Yeah, that's strange actually, it seems that the method is present in the protocol descriptor (even with the remote option) but it's not actually implemented.
You should file an issue to the Chromium project or to the devtools-protocol. Feel free to link to this issue if you do so.

when I call console.log(Browser) I see it defined but cannot use it

This is just FYI, please note that the version you're seeing there (unless you're passing the remote option) is the local version of the protocol.json which may or may not be in sync with the version of Chrome you're using. More info here and here.

I'm closing this as there's nothing I can do about it, but if you decide to open an upstream issue please post the link here. Thanks!


❌ netlify build failing

We have an open issue reported at netlify/build: https://github.com/netlify/build/issues/4689
When this gets resolved, we should see our builds passing. Then, we can check what we can improve on our end.
Keeping this issue here open for everyone's attention, so do not worry if you see some ❌ on your PRs for now 🙂
What's important is that the Build and Test pipelines are kept passing ✅

This is now resolved on Netlify and confirmed working for both of our apps.


Avoid remediation loops by not restoring node's status.

The node's status should be set by the node itself. Otherwise, we restore the node conditions that created the unhealthy state which might lead to remediation loop

/lgtm
/test e2e-test
(the latter should have been trigger automatically, but maybe it needs some time)


Bug in monomorphization

The BPL file bpl.zip produces the following errors when run by Boogie:
Prover error: line 22 column 19: invalid datatype declaration, unknown sort 'T@$TypeName'

Prover error: line 22 column 19: invalid datatype declaration, unknown sort 'T@$TypeName'

Prover error: Prover died

...

Command line (after unzipping):
boogie -doModSetAnalysis -printVerifiedProceduresCount:0 -printModel:1 -enhancedErrorMessages:1 -proverOpt:PROVER_PATH=/home/wrwg/bin/z3 -proverOpt:O:smt.QI.EAGER_THRESHOLD=100 -proverOpt:O:smt.QI.LAZY_THRESHOLD=100 -vcsCores:12 output.bpl

The culprit seems to be the application of the generic function function $ForceTrigger<T>(x: T): bool { true }. I have tried to nail this down to a smaller use case but was not able to do so.
@shazqadeer

Please add -monomorphize option to the command line.  When I add that option, I get the following output:
Boogie program verifier finished with 5 verified, 0 errors
Regardless, the output you see is not ideal.  I will look into providing a better error message.

The root problem is that datatypes and generics do not work together currently.  So, if both  are used in the same file then monomorphization must be enabled using the flag I mentioned.  Monomorphization is turned off by default because currently only generic functions and datatypes are supported; generic procedures and implementations cannot be monomorphized right now.

@wrwg :
I just merged a PR that should provide a better error message if datatypes and generics are combined without using monomorphization.
Boogie also supports a flag -lib which automatically links a collection of useful libraries including finite vectors with native equality.  See here for an example.  If you use -lib on the command line, -monomorphize is implied.


Modifying rule parameter doesn't change 'Description' in the table

Pretty much that. Steps to reproduce:

Open Preferences on Rules tab.
Choose a rule.
Click gear to modify.
Change the parameter field.
Click 'OK'.
Description field in the table doesn't reflect the modification (unless it's just arbitrary description and filled only when adding?)

Please elaborate, maybe I'm just implying something that shouldn't work as I think :)

It is initialized on add but not again after that. Not something I plan on changing.


Move Analysis Framework to Istiod

istioctl analyze can remain use the existing framework. Merge with distribution status controller is also good to have.

Any updates on this? Just wasted an hour digging through 100s of callbacks and async processes

Still WIP. You mean debugging the processing pipeline?

Yes, I am interested in this issue so we can delete all of this code and never have to debug it again :slightly_smiling_face:

I am hoping to do it soon. I will likely refocus on this later this week. Why do you have to do debug galley code? It is just running analysis.

https://github.com/istio/istio/issues/25893 is the issue

ok. do you have an idea on how to fix it or you are waiting for the code to be removed.

not stale
On Sun, Oct 25, 2020 at 12:02 PM Istio Policy Bot<EMAIL_ADDRESS>wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2020-07-27.
It will be closed on 2020-11-09 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/23943#issuecomment-716195204, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXMQCOYIASUAKBA4LX3SMRY4VANCNFSM4NEM4U3Q
.

is this planned for 1.9?

No, likely 1.10, design in 1.9.

Not stale
On Tue, Sep 21, 2021 at 10:01 PM Istio Policy Bot @.***>
wrote:

🧭 This issue or pull request has been automatically marked as stale
because it has not had activity from an Istio team member since 2021-06-23.
It will be closed on 2021-10-06 unless an Istio team member takes action.
Please see this wiki page
https://github.com/istio/istio/wiki/Issue-and-Pull-Request-Lifecycle-Manager
for more information. Thank you for your contributions.
Created by the issue and PR lifecycle manager.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/23943#issuecomment-924585251, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIWRORI5IPVFKCYFFLUDFPKRANCNFSM4NEM4U3Q
.
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.

this is done!


Also bump CI matrix include jobs to latest stable CPython version.

Not sure where those requirements are configured? Direclty in the GitHub UI?

Not sure where those requirements are configured? Direclty in the GitHub UI for protected branch rules?

Updated.

Thanks both - my family and I were out of action sick for the past week, better now thankfully, just catching up on everything I missed!


refactor: Descriptions on Well-Known Annotations/Labels/Taints

Fixes https://github.com/kubernetes/website/issues/32990

@zacharysarah thanks for taking the time to comment, I'll get on this!

I'm closing this PR as this PR has not addressed comments/suggestions
Please feel free to reopen (with /reopen) when the author is ready to address the comments/suggestions
/close


Intercom doesn't get loaded locally in Firefox

It works fine in Chrome, but in Firefox the script just doesn't get loaded.
This is the output from console (I also tried including the script in html, but with the same effect):

Yet after pasting content of the script into console it starts to work:

Some of our users have problems with chat not working at all - I wonder whether this might be the reason.

Hi sharq1,
I was unable to re-create this issue. Did you have trouble installing the Intercom-Rails Plugin? i.e. did this problem occur after you installed it or did this occur intermittently? If it is still an issue then you should reach out to our support team<EMAIL_ADDRESS>with some more info on the steps that you took to set this up and any other errors or problems you are seeing. Alternatively, we are trialing a Developer Forum for issues like this where you might be able to discuss them with other developers: https://gitter.im/intercom/intercom-rails. But please feel free to re-open this if you are still having issues.
Cheers
Cathal


Trimming VK_KHR_get_surface_capabilities2 and Adjuest MemoryRequirements

CI gfxreconstruct build queued with queue ID 27349.

CI gfxreconstruct build queued with queue ID 27360.

CI gfxreconstruct build # 1910 running.

CI gfxreconstruct build # 1910 passed.


[bugfix]: limit the time of a single test execution

limit the time of a single unit test execution.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


ActiveRecord enum attribute with i18n translation doesn't work?

I'm reading the document from https://github.com/justinfrench/formtastic/blob/f94423144eee14ccc03a64267fcafd583d3cdf85/lib/formtastic/inputs/radio_input.rb#L107
But it doesn't work.
This is my form code:
 f.input :position, :as => radio
model:
enum position: {LT: 1, CT: 2, RT: 3,
                  LM: 4, CM: 5, RM: 6,
                  LB: 7, CB: 8, RB: 9}

i18n file:
zh-CN:
  activerecord:
    attributes:
      watermark:
        positions:
          one: 位置
          LT: 左上
          CT: 中上
          RT: 右上
          LM: 左中
          CM: 正中
          RM: 右中
          LB: 左下
          CB: 中下
          RB: 右下

Am I missing something?  My formtastic version is 3.1.5

Hi @oni7uka, I'm not sure what you mean by "doesn't work". if this is still an issue for you, can you please provide some more information? Closing for now.


Remove [SERVICE: Logging] Unable to create the logger: getting the extra config for the krakend-gologging module

We should change the policy of logging errors as it works in the rest of the components:
https://github.com/krakendio/krakend-ce/blob/master/executor.go#L302
The error shouldn't display unless it is an error. The absence of configuration is not an error.

Fixed in https://github.com/krakendio/krakend-ce/commit/2270a4531693af280cf6322320911d3a30c5f1be


Project Crud Operations.

Description of your changes

Fixes #
I have:

[ ] Read and followed Crossplane's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

pending:

Need To Decide Features Will be in support for Project(project parameters)
Project Delete Function Need to be checked.
Need to define compare method to generate diff.
Abandon,Acquire feature check


[Bug] Page 6510 TestTempSpecificationExists

This function is used to make sure that the user doesn't define a particular lot more than once.
However, it doesn't take the Reclassification(P393->P6510) scenario into consideration:
When a user wants to split an original lot in several smaller lots, he should be allowed to insert several lines with the same value in the "Lot No." field: what matters here is the "New Lot No." which will be the basis for new Item Tracking.
This is working fine in WMS Reclassification (P7365->P6550): users can introduce several lines with the same "Lot No." and different "New Lot No."
There are 2 options to solve this, no. 2 is of course a more thorough solution, but it will require a new key on T336 for "New Lot No.","New Serial No.":

Totally disable check within this function by using the FormRunMode variable
if FormRunMode <> FormRunMode::Reclass then begin
perform the existing checks

Split the check in two:
if FormRunMode <> FormRunMode::Reclass then begin
perform the existing checks
end else
perform identical checks against "New Lot No."/"New Serial No."

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


[SUGGESTION] Parser::applyVisitorToBuffer to support early termination

Parser::applyVisitorToBuffer is an extremely useful function.
If we can control the traversal from within the visiting callback and decide whether it should continue or terminate, that will be awesome!
I think if the callback has bool as the return value, the implementation will be easy.
Any idea?

it can be surely done. Don't be afraid to send a PR yourself ;)

Hi, please take a look at changes made to fix #37
I think it address your use case too

That's great! Thank you!
I've tested the new code on various workloads, the results are great:
workload 1:  29.3s  -> 3.3s
workload 2:  2.8s -> 0.64s
workload 3:  47.2s -> 3.0s
I'm closing this issue now.


X axis / labels Manual Scale Help Please

Hello
i am having issues finding a way to manual scale the x axis between a range  of 0.6-1.5 on a line graph.  i am dealing with arrays with lengths of 1001 values between this range but its trying to auto scale to fit all the points in and it is just a big gray blob. i need the to have the x axis in increments of 0.1 is their anyway to achieve this with chart.js global  options?

You need to use v2 for this. Take a look at the scatter sample for ideas.


General CSS problems - specific fgt-mah-ssapp/code/pages/modals/registrationModal.html may overflow screen size without scroll

fgt-mah-ssapp/code/pages/modals/registrationModal.html may overflow screen size without scroll

There is no scrollbar, and the fields at the bottom are not accessible (unless browser zoom-out is used).
How to solve this ? By CSS ?
https://privatesky.xyz/?Cardinal/components/psk-modal
does not seem to help.

Closed in issue #13


Add ACDC dataset

This dataset is for multi-structure (LV, RV, MyoC) segmentation in cardiac MRI images.

Please adapt to have the function get_acdc_data, which downloads the data and returns the paths, similar to the upcoming changes in #252. Same for #248 #249  #250


Firing api.tasks.on.add event after finishing drawing task

First of all, i would like to thank you guys for this awesome tool.
I wanted to show a modal with filled information of drawn task, so I used api.tasks.on.add event. The issue is, when i start drawing and holding the button to arrange time, event automatically fires and shows me the modal with information of unfinished drawing. So basically, i want to fire an event after the task has been finished drawing. Any recommendations?
Sample code here;
myApp.controller('here', ['$scope', function ($scope) {
        $scope.registerApi = function (api) {
            api.core.on.rendered($scope, function () {

                // Call API methods and register events.
                api.tasks.on.add($scope, function (task) {
                    console.log(task);
                    $('#CreateTaskSteps').modal('show');
                });
            })}};

@bahadircyildiz I think now there is no such possibility. Or are you already found a solution?

@idoo yes, my solution was checking if other event related. Simply;
´´´javascript
if (api.tasks.on.add)
if (api.tasks.on.resizeBegin)
if (api.tasks.on.resizeEnd)
api.tasks.on.resizeEnd($scope, function (task) {
$scope.CreateTaskFormFiller(task)
})
´´´


change volume

Hello,
is there a way to make it play with a set volume / change the volume whilst playing (without changing the system wide volume) ?

Yes!
Just use your arrow keys, or + & -.
If those don't work, try updating lowfi.

Oh man, I'm dumb🤦♂
Thank you!


Create online translator

Similar to the Container Linux validator there should be an host version of FCCT.
Rough proposal:

A service that wraps FCCT and acts as an HTTP endpoint for translation. Run it in a container for easy hosting.
Static page with some kind of text box that makes requests to that service to do the translation.
The page should be able to read URL params (or something similar) to autofill the text box. This enables people to create links to specific configs when reporting bugs and allows the FCCT documentation to have "try it" links for the examples.

Link: https://github.com/zonggen/fcct-online
Stack: Vue.js, Flask

[x] Front end that contains a text box and button to submit a HTTP request to server
[x] Front end that reads URL to autofill the text box
[x] Server that reads HTTP request & URL parameter for translation
[x] Run inside a container
[ ] Deploy on Heroku (or other platform)
[ ] Need a button for generating URL with FCC encoded
[ ] Need to format the returned error message more elegantly
[ ] Need to parse the error message returned from server to highlight origin of error in original FCC

Discussion thread on deployment location: https://github.com/coreos/fedora-coreos-tracker/issues/260

I was looking for similar tool and decided to build my own with WebAssembly (it can take some time to load, compiled WASM is quite big): Butane Translator.
I have a source code available here: https://github.com/m0nhawk/coreostools


Pass variables to layout

Hi, I read code example. And I found the way to pass variables to layout:
res.locals = {
    title: 'Example',
    message: 'This is a message'
  };

It seem lost old res.locals variables. But I can resolve it by:
let locals = res.locals;
res.locals = {
    ...locals
    title: 'Example',
    message: 'This is a message'
  };

But It looks pretty complicated. So, can pass variables to layout by  res.render('views', {variables})?;

That's correct. Alternatively, you can use Object.assign:
res.render(Object.assign({}, res.locals, {
    title: 'Example',
    message: 'This is a message'
})


jessie images don't contain apt-get

Hi guys,
looks like jessie images don't contain apt-get command, which can brake building images based on jessie (in case of using apt-get command in dockerfile).
I believe that because of this error most of microsoft/dotnet images based on jessie-scm aren't working at the moment (Failed to initialize CoreCLR, HRESULT: 0x80131500). Probably they were built with non-working apt-get and libicu52 wasn't installed, which is the root of problem with CoreCLR.

Probably I did something wrong, as it works on another machine now. I mean apt-get command on jessie image.


Review No.09 - what-happens-inside-the-pipeline-function-(tensorflow)…

….srt
Modified!
Review No.09 - what-happens-inside-the-pipeline-function-(tensorflow).srt

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

ref #390


Add support for Schaltaktor 2/2-fach

Hi,
Love the work so far. However, I have a number of 2/2-sensor / schaltaktor actors. Would it be possible to add support for those as well?
Thanks in advance!
William

Hm, this is odd. I believe I posted a description to this issue yesterday too. Never mind. So I’m looking for 2/2-fach Schaltaktor support in this plugin. would be great if it could be realized. I tried looking up the device ID’s but could not find them. Be willing to help if you can direct me there.

Hello,
glad you like it. To add support for 2/2-fach Schaltaktor, I need the device ID's. If you send me the json formatted info file, I can get the ID's myself and the corresponding data points needed to communicate with the actuator.
Please run the following command from your local server:
http://localhost:8080/info > actuators.json

Please send me the file actuators.json via email (listed in my profile).

Hello,
thank you very much. Support has been added in commit 696d0c604ecd28889653cfab250920e6104cc168 and a new version 1.3.0 released.
Please update the npm module with npm update homebridge-buschjaeger.

Hi Henry,
Looks like I updated the bunch tonight but they are not popping up after restarting the API and Homebridge, nor after re-pairing homebridge to the iPhone. Please check the screenshot attached that shows the location of the index.js file, as well as the content, and the terminal screen, showing that homebridge ignores the 2/2-fach Schaltaktor. Any thoughts? Did I overlook something? The 1/1-fach's are showing up.

You don't need to repair the bridge. Restarting home bridge should be enough. Are you sure that the updated version is running? You may try to reboot your pi to make sure no old processes are running.
I have double checked and it should definitely not print "not supported".

I wanted to be thorough. :)
I rebooted the Pi and checked the version: 1.3.0. The readme shows the 2/2-fach's as well. Could it have anything to do with the channels? I do see that it displays the channels after the device ID's for the initialised ones but not for the ignored ones.

That is very weird.
Please try to replace line 90 in index.js with:
this.log('Ignoring non-supported accessory ' + actuator['typeName'] + ' with serial ' + serial + ' deviceId ' + deviceId);

The module can be found in node_modules/homebridge-buschjaeger.
Restart home bridge and check the log if it displays the device id now.

Hi Henry,
Just updated index.js, but not much of an effect. It still ignores them and neither do they appear in the Home app on my iPhone. The log is shown below. Could it be that there are two device ID's or something like that given there are two physical buttons on the switch?

Hello,
it definitely should show a log message if you manually edit the source. Do you have installed the module globally? Please check with npm list -g | grep homebridge-buschjaeger. If it produces output then you have installed it globally and you need to update the module with npm update home bridge-buschjaeger -g

Whoops! That did the trick, yes. Apologies for overlooking that. It was installed globally and still on 1.2.0. Upgrading it now activated all the 2/2-fach actors.
Thanks again!

Happy to hear that ;)


Create Unit Tests for Contacts

Should add some unit testing for Contacts, if only to demonstrate the API.

Added a unit test which demonstrates the contact object.


Need the feature of Browse the repository at this point in the history

Feature Description
It is on the GitHub commits page, not sure if Gitea has this feature though I can't find it on Gitea's commits page.

Screenshots
No response

Yes.

(But yes, you need an extra click at the moment as you must first select the respective commit, and then click on Browse Source)

cool, that's it, thanks


POC: Add traits to support generalising the apply methods

POC for #75
Some brief notes to guide review:
This started off implementing the idea in the description of #75: adding traits to describe the cardinality of our transforms and defining an intermediate _apply method that dispatched on the traits.
But after some refactoring at the end, I noticed that the key difference boiled down to how the data was prepared before going into a ManyToOne transform (LinearCombination).
So I refactored a bit more to create two simple formatting functions:

_preformat structures the input to _apply according to the cardinality of the transform. Effectively, this just calls eachslice before calling _apply for LinearCombination.
_preformat structures the output of _apply according to the cardinality of the transform. This is really only needed for append_apply because LinearCombination returns a Vector, if we are appending it as a row cat throws a DimensionMismatch. So we have to pivot the data before doing so.

I added some TestUtils with Fakes for the above transforms and an example testset for how we might test a new data type in a more manageable way in the future.
The idea being that: once a datatype supports each type of transform (and returns correct result for the kwargs) then it should support any  of the transforms defined in the package.
Then, each transform just needs to be tested against Arrays and nothing else, which should give us full test coverage but in a much simpler way.

closed in favour of https://github.com/invenia/FeatureTransforms.jl/pull/80


UI does not render fixtures for Argo-lite jobs

Steps to reproduce:

Try to submit any job with fixtures.
Navigate to job details page

Job details page don't show any dynamic fixture

fixed


VS 15 preview 4 crashes when I try to open project properties dialog

@vasily-kirichenko Which workload did you select?

Workload?..

One of these:

I'll try and repro today when I'm at my office, but after installing the Data Science workload I was able to retarget an F# project through the Property Pages.  However I hadn't tried doing that in any other Workload.

@OmarTawfik @brettfo @KevinRansom Any idea if this is still an issue, and/or does it deserve the "Urgency Now" label?  I presume not?

It works for me with the latest preview build, so it must have been fixed.
If it still fails please re-open with a detailed repro
Thanks
Kevin


⚠ Bofrost.fr has degraded performance

In 873c7a2, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 2491 ms

Resolved: Bofrost.fr performance has improved in 5ee1e54 after 8 minutes.


Build: build lazy machine doc with nix and on CI

So the lazy machine doc can be built with nix and built by CI.
I tried to make it so everything in the docs attr set gets built on linux, let's see if I succeeded.

Hydra being weird, but this succeeded.


0.3.0 release on pypi

Which tag or release number does the https://pypi.org/project/grumpy-runtime/ for 0.3.0 come from? I can only see a v0.2.2 in the project.

Sorry for that. Looks like I had not pushed the tag. Fixed.
It cames from https://github.com/grumpyhome/grumpy/commit/3dc88e66bbaba62ea11324091176acf0403d3f5f, issued on Jul 24, 2018

master still bears 0.2.2 version tag, because the version bump was on separate commit that was not merged https://github.com/grumpyhome/grumpy/compare/master...v0.3.0

I added the necessary merge to #139 with other cleanups.

#139 was merged. Thanks @abitrolly.


Gradle fails to download Groovy through JCenter in macOS images

Description
I am trying to run a Detox testing session for Android on the Mac hosted GitHub Actions environment. It works up until the point where Task :app:lintVitalApptestRelease needs to download Groovy through JCenter where instead of doing that it fails with a network error.
This does not happen in the Ubuntu Latest image but I can't use Ubuntu because it does not support hardware acceleration for the Android emulator.
Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[X] macOS 10.15 (example build: https://github.com/valora-inc/wallet/runs/4211504356?check_suite_focus=true).
[X] macOS 11 (example build: https://github.com/valora-inc/wallet/runs/4211454673?check_suite_focus=true#step:11:2507).
[ ] Windows Server 2016
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
20211106.1
Is it regression?
Not sure
Expected behavior
To successfully download Groovy.
Actual behavior
Use '--warning-mode all' to show the individual deprecation warnings.
* What went wrong:
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
Execution failed for task ':app:lintVitalApptestRelease'.
1167 actionable tasks: 1167 executed
> Could not resolve all files for configuration ':app:lintClassPath'.
   > Could not download groovy-all-2.4.15.jar (org.codehaus.groovy:groovy-all:2.4.15)
      > Could not get resource 'https://jcenter.bintray.com/org/codehaus/groovy/groovy-all/2.4.15/groovy-all-2.4.15.jar'.
         > Could not GET 'https://jcenter.bintray.com/org/codehaus/groovy/groovy-all/2.4.15/groovy-all-2.4.15.jar'.
            > Connection reset

Repro steps
https://gist.github.com/noisypigeon/6922b380582802d257f77b9f5b4473b8

@noisypigeon Hello!
Thanks, we will take a look.

Thank you! Hope you have a great day! 🥇

@noisypigeon What is the best way to reproduce the issue? I see in the original repo you are using a self-hosted runner, but in the repro steps you are referencing the yaml file with the github-hosted runner.

@mikhailkoliada I am working on this branch: https://github.com/valora-inc/wallet/tree/np/github-actions-hosted-android-e2e.

Hello @noisypigeon. Could you please try to run your workflow again? Looks like it was temporary issue with Gradle 7.2. Gradle has been updated up to 7.3 version and the issue should be resolved. My last run was successful.

Thanks! I've kicked off a build: https://github.com/valora-inc/wallet/runs/4257003017?check_suite_focus=true. Will report back it's conclusion. :) thanks for the help!

@dibir-magomedsaygitov Unfortunately, it's still happening: https://github.com/valora-inc/wallet/runs/4257003017?check_suite_focus=true#step:11:2504. :)

@noisypigeon looks like I was able to resolve the issue by adding following lines in android{} in app\build.gradle:
lintOptions {
    checkReleaseBuilds false
    abortOnError false
}

You can check my edited app\build.gradle file here and run here.

Thank you @dibir-magomedsaygitov! I'll try this.

This is resolved (still failing but for an unrelated issue as you mentioned. Thank you for the help @dibir-magomedsaygitov and @mikhailkoliada.


python312Packages.pyeconet: 0.1.22 -> 0.1.23

Diff: https://github.com/w1ll1am23/pyeconet/compare/refs/tags/v0.1.22...v0.1.23
Changelog: https://github.com/w1ll1am23/pyeconet/releases/tag/v0.1.23

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

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

5 packages built:

home-assistant-component-tests.econet
python311Packages.pyeconet
python311Packages.pyeconet.dist
python312Packages.pyeconet
python312Packages.pyeconet.dist

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

5 packages built:

home-assistant-component-tests.econet
python311Packages.pyeconet
python311Packages.pyeconet.dist
python312Packages.pyeconet
python312Packages.pyeconet.dist


RecursiveIterableComparisonAssert first implementation with isEqualTo and contains methods

Check List:

Fixes #1238
Unit tests : YES
Javadoc with a code example (API only) : YES

@haruntuncay I have finished the first round of review, I have looked at the tests into too much details though, I'll do that after the other comments are addressed.

Hello @joel-costigliola,
I have gone through the issues and applied the changes you have requested. I only wasn't able to fix this one:

reuse RecursiveComparisonAssert.DIFFERENT_SIZE_ERROR.
In addition, we should display the two iterables to help users figure out the difference. (I was planning to do that in RecursiveComparisonAssert).

Because DIFFERENT_SIZE_ERROR was private in RecursiveDifferenceComparisonCalculator and I wasn't sure whether it was okay to make it public for one use case, so for the time being, I just used the AssertionError with the message similar to DIFFERENT_SIZE_ERROR.
By the way, thank you for the time you've spent reviewing and thanks for the opportunity given to help this project. I am really learning a lot about api design just by studying this project 😄 .

By the way, I realized that, because we use IterableAssert with new IterableElementComparisonStrategy(new RecursiveComparisonDifferenceComparator(new RecursiveComparisonConfiguration())), and since IterableAssert has it's own error report mechanism, differences found by RecursiveComparisonDifferenceCalculator gets swallowed.
  // Since  RecursiveIterableComparisonAssert#isEqualTo calls IterableAssert#isEqualTo
  // and this is what IterableAssert#isEqualTo boils down to:

  public void assertEqual(AssertionInfo info, Object actual, Object expected) {
    if (!areEqual(actual, expected))
      throw failures.failure(info, shouldBeEqual(actual, expected, comparisonStrategy, info.representation()));
  }

  // differences found by `RecursiveComparisonDifferenceCalculator` are completely ignored.

What can we do about it so that actual error report could point out the differences found by RecursiveComparisonDifferenceCalculator ? Delegating to IterableAssert seems unfulfilling here.

Hello @joel-costigliola
Hope you are doing well. When you have the time, could you please check out the updates and let me know what you think ? Thanks in advance 😊

Let's not worry too much about DIFFERENT_SIZE_ERROR, I think it would actually be better to use "actual and expected are iterables of different sizes (I used the word values in the DIFFERENT_SIZE_ERROR to express that they were field values not top level objects as in our case - I might change that to be clearer).
For isEqualTo we need to think of a way to report the differences found.
When the collection order is enforced, since we compare elements at the same index, we would ideally report the differences found per index, concretely if elements at index 2 and 5 differ, we would report something like:
elements at index 2 differ:
- actual element was: ...
- expected element was: ...
Differences found: ...

elements at index 5 differ:
- actual element was: ...
- expected element was: ...
Differences found: ...

You get the idea.
When the comparison is not ordered, it is way more complicated to show the differences since we have to compare each actual elements with all expected ones!
For example if actual element 2 was not found in expected, should we report the differences between it and each expected elements:
elements at index 2 was not found in expected:
- actual element was: ...

Differences found with expected element 1 : ...
Differences found with expected element 2 : ...
Differences found with expected element 3 : ...
...
Differences found with expected element n : ...

It's going to be super long and might not be so useful2

I'll continue the review tomorrow (if I have the time), in the meantime let's think about the best way to report the differences.

Hello @joel-costigliola,
Hope you are well. I have had the time to implement a proof of concept solution for error reporting and wanted to ask for your opinion. In short, I found that using already existing Iterables class for custom error report is not very easy since it handles iteration implicitly, where I think that we would benefit more handling iteration explicitly, instead.

Hello @joel-costigliola,
Hope you are well. I have had the time to implement a proof of concept solution for error reporting and wanted to ask for your opinion. In short, I found that using already existing Iterables class for custom error report is not very easy since it handles iteration implicitly, where I think that we would benefit more handling iteration explicitly, instead.

Hello @joel-costigliola,
First of all, I apologize that I have accidentally hit "close and comment" button instead of comment.
Second, I hope you are well. I have had the time to implement a proof of concept solution for error reporting and wanted to ask for your opinion.
In short, I found that using already existing Iterables class for custom error report is not very easy since it handles iteration implicitly, where I think that we would benefit more handling iteration explicitly, instead. I have opened another branch, seperate from this one, so that my demo commits wouldn't go to PR. When you have the time, could you please check it out from here ?
To give a clearer idea of how it currently works:
  public static void main(String[] args) {
    Person person1 = new Person("harun", 1, new Field("field1", "val1"));
    Person person2 = new Person("harun2", 2, new Field("field2", "val2"));

    List<Person> list1 = Arrays.asList(person1, person2, person1);
    List<Person> list2 = Arrays.asList(person2, person1, person1);

    assertThat(list1)
      .usingRecursiveComparison()
      .isEqualTo(list2);
  }

This code currently yields this error message:
Exception in thread "main" java.lang.AssertionError:
Expecting iterable:
  <[[name=harun, age=1], [name=harun2, age=2], [name=harun, age=1]]>
to be equal to:
  <[[name=harun2, age=2], [name=harun, age=1], [name=harun, age=1]]>
when recursively comparing iterables field by field, but found the following 2 differences:

elements at index 0 differ:
- actual was: [name=harun, age=1]
- expected was: [name=harun2, age=2]
Differences found:
field/property 'age' differ:
- actual value   : 1
- expected value : 2
field/property 'field.name' differ:
- actual value   : "field1"
- expected value : "field2"
field/property 'field.val' differ:
- actual value   : "val1"
- expected value : "val2"
field/property 'name' differ:
- actual value   : "harun"
- expected value : "harun2"

elements at index 1 differ:
- actual was: [name=harun2, age=2]
- expected was: [name=harun, age=1]
Differences found:
field/property 'age' differ:
- actual value   : 2
- expected value : 1
field/property 'field.name' differ:
- actual value   : "field2"
- expected value : "field1"
field/property 'field.val' differ:
- actual value   : "val2"
- expected value : "val1"
field/property 'name' differ:
- actual value   : "harun2"
- expected value : "harun"

The recursive comparison was performed with this configuration:
- overridden equals methods were used in the comparison
- these types were compared with the following comparators:
  - java.lang.Double -> DoubleComparator[precision=1.0E-15]
  - java.lang.Float -> FloatComparator[precision=1.0E-6]
- actual and expected objects and their fields were compared field by field recursively even if they were not of the same type, this allows for example to compare a Person to a PersonDto (call strictTypeChecking(true) to change that behavior).
- comparing iterables with arrays was not allowed.

	at app.Main.main(Main.java:22)

I ended with adding usingRecursiveFieldByFieldElementComparator(configuration) to iterable assertions - https://assertj.github.io/doc/#assertj-core-recursive-comparison-for-iterable


Trying to Handle Auth using API/Golang

Question
I'm trying to configure auth when I perform an Import Images command on a target repository in Golang. But cannot find an example or syntax on how to do it successfully. I'm trying against a JFrog Artifactory private docker repository.
I've tried to do this from regctl cli as well, but was unsuccessful to understand the required cli arguments for adding auth. Could you provide and example?
Version
{
  "VCSRef": "732c2a3a6312fc70dfcfcd821505ef0ad1ed230f",
  "VCSTag": "v0.4.5"
}

Environment
Linux amd64

Registry description: JFrog Artifactory

Anything else
This is what I'm starting from
package main

import (
	"bytes"
	"context"
	"fmt"
	"os"
	"strings"

	"github.com/regclient/regclient"
	"github.com/regclient/regclient/config"
	"github.com/regclient/regclient/types/ref"
)
const (
	endpoint = "example.artifactory.com"
	registryPath= ""
	regAuthUser = ""
	regAuthPass = ""
	regAuthToken = ""
        archiveName = "busybox.tar"
        container = "busybox:latest"
)
func main() {
	file, err := os.Open(archiveName)
	if err != nil {
		return err
	}

	defer file.Close()
	fileInfo, _ := file.Stat()
	var size int64 = fileInfo.Size()
	buffer := make([]byte, size)

	// read file content to buffer
	file.Read(buffer)
	fileBytes := bytes.NewReader(buffer)

	ctx := context.Background()
	var configHost config.Host

	if regAuthUser != "" && regAuthPass != "" {
		configHost = config.Host{Hostname: endpoint, TLS: config.TLSInsecure, User: regAuthUser, Pass: regAuthPass}
	} else if regAuthUser != "" && regAuthToken != "" {
		configHost = config.Host{Hostname: endpoint, TLS: config.TLSInsecure, User: regAuthUser, Token: regAuthToken}
	} else {
		configHost = config.Host{Hostname: endpoint, TLS: config.TLSInsecure}
	}
	rc := regclient.New(regclient.WithConfigHost(configHost))

        repository := strings.Split(container, ":")[0]
        tag := strings.Split(container, ":")[1]
        var project string
        var image string
        var containerTarget []string
        if strings.Count(repository, "/") < 1 {
	        project = "library"
	        image = repository
        }
        if strings.Count(repository, "/") > 1 {
	        project = strings.Split(repository, "/")[1]
	        image = strings.Split(repository, "/")[2]
        }
        if registryPath != "" {
	        containerTarget = []string{registryPath, project, image}
        } else {
	        containerTarget = []string{project, image}
        }
        err = rc.ImageImport(ctx, ref.Ref{Registry: endpoint, Repository: strings.Join(containerTarget, "/"), Scheme: "reg", Tag: tag}, fileBytes)
        if err != nil {
	        fmt.Println(err.Error())
        }
}

Hi @zach-mitchell-rtx , change the initialization of config.Host from Hostname to Name. The Hostname value lets you point to a registry with a different DNS than the registry name itself.

Thank you!! That did the trick.


Hacket upgrade not running as configured in daemon

I realized that hacknet-upgrade-manager.js isn't being executed as intended by daemon.js
In daemon.js we have this configuration, but in the logs it just calling the 8h one as show in the picture.
// Buy every hacknet upgrade with up to 4h payoff if it is less than 10% of our current money or 8h if it is less than 1% of our current money
        { interval: 32000, name: "hacknet-upgrade-manager.js", shouldRun: shouldUpgradeHacknet, args: () => ["-c", "--max-payoff-time", "4h", "--max-spend", ns.getServerMoneyAvailable("home") * 0.1] },
        { interval: 33000, name: "hacknet-upgrade-manager.js", shouldRun: shouldUpgradeHacknet, args: () => ["-c", "--max-payoff-time", "8h", "--max-spend", ns.getServerMoneyAvailable("home") * 0.01] },

Also, how can I set it to be very agressive regarding hacknet upgrades?
I tried to set it to 30m and 0.5 of my money but still not buying upgrades

Check your currently running scripts on home. Is another one still running? shouldUpgradeHacknet is configured to only let 1 of the 3 run at a time.

Also, try setting tail: true on your modified version. I'm betting it is
running, but there's no purchases remaining that pay off in under 30
minutes.
On Thu., Jan. 20, 2022, 12:44 p.m. archraziel, @.***>
wrote:

I realized that hacknet-upgrade-manager.js isn't being executed as
intended by daemon.js
In daemon.js we have this configuration, but in the logs it just calling
the 8h one as show in the picture.
// Buy every hacknet upgrade with up to 4h payoff if it is less than 10% of our current money or 8h if it is less than 1% of our current money
{ interval: 32000, name: "hacknet-upgrade-manager.js", shouldRun: shouldUpgradeHacknet, args: () => ["-c", "--max-payoff-time", "4h", "--max-spend", ns.getServerMoneyAvailable("home") * 0.1] },
{ interval: 33000, name: "hacknet-upgrade-manager.js", shouldRun: shouldUpgradeHacknet, args: () => ["-c", "--max-payoff-time", "8h", "--max-spend", ns.getServerMoneyAvailable("home") * 0.01] },
[image: image]
https://user-images.githubusercontent.com/68472054/150382362-2d980e0a-c6d2-4a3f-b806-83b76c3517db.png
Also, how can I set it to be very agressive regarding hacknet upgrades?
I tried to set it to 30m and 0.5 of my money but still not buying upgrades
—
Reply to this email directly, view it on GitHub
https://github.com/alainbryden/bitburner-scripts/issues/39, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AARN33JARJ5EHTL2GSCZDY3UXA3VRANCNFSM5MNIBZFQ
.
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 are subscribed to this thread.Message
ID: @.***>

Using the default daemon.js with no modifications. I don't see it running even when the 8h appears on the log.

this is the tail from the hacknet-upgrade-manager.js that is configured inside the asynchronousHelpers variable
   { name: "hacknet-upgrade-manager.js", tail: true, args: ["-c", "--max-payoff-time", "1h"] }, // Kickstart hash income by buying everything with up to 1h payoff time immediately

I don't think I made it clear, but the problem is with the ones inside periodicScripts variable, the line with 4 hours just run when I comment the line with 8 hours.
When I change to 1m and to use 0.9. I get this tail. I also added a log on the hacknet upgrade script. I am confused but I think there is something wrong, I am sending 1minute  payoff but is comparing with 1hour:14minutes.
        log(ns, `payoffTimeSeconds: ${payoffTimeSeconds} and maxPayoffTimeSeconds: (${maxPayoffTimeSeconds})`);
        log(ns, `The next best purchase would be ${strPurchase} but the ${strPayoff} is worse than the limit (${formatDuration(1000 * maxPayoffTimeSeconds)})`);
        return false; // As long as maxPayoffTimeSeconds doesn't change, we will never purchase another upgrade
    }

A few more info about the variable that make the
let payoffTimeSeconds = 1 / (hashDollarValue * (shouldBuyNewNode ? newNodePayoff : bestUpgradePayoff));
hashDollarValue: 250000
shouldBuyNewNode: false
newNodePayoff: 9.705877567456382e-10
bestUpgradePayoff 1.0349621569813014e-9

I'm not sure you understand what the payoff time means it will only buy
upgrades that will pay for themselves in that amount of time. You are
setting it too low. If you want to buy more upgrades, you have to be
willing to buy upgrades that take hours or days to pay off.
On Thu., Jan. 20, 2022, 1:44 p.m. archraziel, @.***>
wrote:

A few more info about the variable that make the
let payoffTimeSeconds = 1 / (hashDollarValue * (shouldBuyNewNode ?
newNodePayoff : bestUpgradePayoff));
hashDollarValue: 250000
shouldBuyNewNode: false
newNodePayoff: 9.705877567456382e-10
bestUpgradePayoff 1.0349621569813014e-9
—
Reply to this email directly, view it on GitHub
https://github.com/alainbryden/bitburner-scripts/issues/39#issuecomment-1017759764,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARN33P7J2R6I6T73LP37TLUXBCZPANCNFSM5MNIBZFQ
.
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 commented.Message ID:
@.***>

Jeez dude, mb!
I put it 24h with 0.9 and now is upgrading very agressive. I will close this.
I am deeeply sorry for the misunderstood. Thank you very much


The workflow for solving jitters in ASTER images with csm model failed due to lack of matches

Hello,
I have been testing the new csm model for removing common jitters in the ASTER DEMs. I absolutely followed the same workflow described in Sec. 16.35.8. in the instructions, but used different images. However, the jitter_solve command failed due to no matches can be found.
error message: "Loaded 0 matches. Failed to build a control network. Check the bundle adjustment directory for clean matches. Or, consider removing all .vwip and .match files and increasing the number of interest points using --ip-per-image or --ip-per-tile, or decreasing --min-matches, and then re-running bundle adjustment."
So, which option should I tune for collecting sufficient interest points? And why?
Just for tesing, the source image I used: AST_L1A_00310162016041942_20230329121407_20863.zip

Maybe you can share a screenshot with the left and right image. Some ASTER data have clouds and this can mess things up.

Ok, here is the snapshot of the images, they are basically cloud free.  I just wonder why jitter_solve loaded 0 matches?

Hi Tristan,
Can you confirm if the dense match files produced from stereo is being passed to jitter solve correctly using match-file-prefix flag? Jitter solve should not make matches itself, as it requires dense matches from stereo to run successfully. I ran into similar errors when there were slight variations in the name of the match file which is produced from stereo and the name which jitter_solve expects to decipher using the match-file-prefix. If you share your commands, we can help debug this.
Thanks,
Shashank

Indeed. There are detailed step-by-step instructions for how to create and copy match files. See for example https://stereopipeline.readthedocs.io/en/latest/tools/jitter_solve.html#id3, and the text above that for background.
I will also suggest doing all those plots done there, to ensure the residuals and errors are as expected.

Hi Both,

Indeed. There are detailed step-by-step instructions for how to create and copy match files. See for example https://stereopipeline.readthedocs.io/en/latest/tools/jitter_solve.html#id3, and the text above that for background.

I followed exactly the same workflow to test the jitter_solve program. The .match file was copied from the output of parallel_stereo and renamed to be input to jitter_solve.

Hi Tristan, Can you confirm if the dense match files produced from stereo is being passed to jitter solve correctly using match-file-prefix flag?If you share your commands, we can help debug this.

I have confirmed again the name of the .match file, it should be correct when companied with the parameter set in match-file-prefix flag. Also, the match file should be valid, since its size is ~5.9 mb.

I suggest 2 options. Rename your images and cameras without the tmp prefix. So the new file names would be:
  $tmp/ba-align-run-run-Band3N.adjusted_state.json \
  $tmp/ba-align-run-run-Band3B.adjusted_state.json```

Then the command will run, hopefully. Right now jitter solve does not know how to map with your currently provided prefix. Currently it would search probably for the match file to have the name like: `jitter/run-tmp-Band3N__tmp-Band3B.match`. If you remove the `tmp` letters from the images and cameras currently passed to jitter solve, it should be fine :)

Hi Shashank,
Thanks, now I understand, the prefix of the .match file much exactly match the file name of the images. This problem has been solved.
However, I encountered into another problem, the solution of jitter_solve did not converge after reaching max iterations. So how could I refine this step? Like add --ip-per-image option in the bundle_adjust?
Error message:
Termination: NO_CONVERGENCE (Maximum number of iterations reached. Number of iterations: 10.)
Found a valid solution, but did not reach the actual minimum.

Don't worry about the solution not converging, the cost function goes down enough during the specified number of iterations to remove jitter. Plotting the results as mentioned in the rest of the tutorial prepared by Oleg would hopefully bring the improvement out :)

Thanks for your reply. Now I should close this issue as solved.

@TristanBlus , glad to hear you figured out the issue, and fine to close the github issue, but if you don't mind reporting back on your results (with a figure or two), we would really appreciate it.  A lot of this was developed/implemented recently, and requires further testing and validation.  And there may be lingering bugs or other issues that can need to be fixed.  Thanks!

Of course. I will continue testing this program and see how it would improve the ASTER DEM generation. The figures will be uploaded later when I go through the whole procedure. Thanks.

I added a blurb to the error message about "Termination: NO_CONVERGENCE" and another small blurb to the error message about not finding matches to check for the naming convention. Also will explain the naming convention in the doc. (Will check this in soon.) Longer term this needs to be handled in a more integrated way.
Yes, looking forward to results and error plots.


⚠ Roblox Site has degraded performance

In 6a3d8ae, Roblox Site (https://roblox.com/) experienced degraded performance:

HTTP code: 200
Response time: 3816 ms

Resolved: Roblox Site performance has improved in fb4e7ba after 11 minutes.


tree-sitter-ledger incorrectly parses multiword commodity names

I've found that the parser doesn't correctly parse multiword commodity names that results in weird highlighting. See "Hoi Zäme" and "Hammer's German Grammar":

An additional issue visible in that screenshot is that the parser doesn't take non-ASCII characters into account.
I'm using the most recent neovim and tree-sitter plugin.

Hey, thanks for reporting that.
Regarding the non-ASCII characters, I'm waiting for https://github.com/tree-sitter/tree-sitter/pull/906 to be done/merged to have proper regexes available for Unicode letters. If this bothers you too much, feel free to submit a PR, I just don't want to personally spend time on a workaround just to throw it away in a few days (hopefully).
I'll fix the multiword commodities though.

This will land in nvim-treesitter when https://github.com/nvim-treesitter/nvim-treesitter/pull/945 is merged :)

Sure thing, thanks!


Why would an error be reported when I run the project following the step

And then, run the following command:
python script/optimize_blendshape_coeffs.py
--blendshapes_coeffs_out_dir "<output_coeffs_dir>"
ImportError: cannot import name 'metric' from partially initialized module 'said' (most likely due to a circular import) (C:\Users\22355.conda\envs\SAiD\lib\site-packages\said_init_.py)

I met the same problem, how did you solve it at last?

I met the same problem, how did you solve it at last?

I copied the packages needed for the file to be executed into this file by refactoring the code. It's a little complicated, but it works.