couldn't find methods, modules , functions etc

Hi, I am reproducing your semantickitti result.
when I run the train.py. I got these issues as asked by this  link [https://github.com/mit-han-lab/torchsparse/issues/219]
train.py    # 65 F.set_conv_mode(2)
=> module 'torchsparse.nn.functional' has no attribute 'set_conv_mode'
core.models.utils.py # 9   from torchsparse.utils.tensor_cache import TensorCache
there is no tensor_cache
core.models.utils.py    # 38 hashmap = torchsparse.backend.GPUHashTable(hashmap_keys, hashmap_vals)
=> AttributeError: module 'torchsparse.backend' has no attribute 'GPUHashTable'
core.models.utils.py # 26 self._caches.idx_query = dict()
=> AttributeError: 'PointTensor' object has no attribute '_caches'
core.models.utils.py # 40, 41
make_tensor has no definitions.
I have downloaded all torchsparse source codes:  version 1.0.0, 1.1.0, 1.2.0, 1.4.0, 2.0.0, 2.1.0, but cannot find clues about these issues.
Could you please help to take a look at the problem?
Thanks a lot

Facing the same problem. Before the last commit commit, I could run training with torchsparse v1.4.0

Thanks a lot, I see, after changing back to original version of initial_voxelize(),  voxel_to_point().  voxel_to_point(), it works, the training and tutorial are able to run.
By the way,  In the trainers.py  there are some segments:
old :
for idx in range(invs.C[:, -1].max() + 1):
cur_scene_pts = (inputs.C[:, -1] == idx).cpu().numpy()
cur_inv = invs.F[invs.C[:, -1] == idx].cpu().numpy()
cur_label = (all_labels.C[:, -1] == idx).cpu().numpy()
new:
for idx in range(invs.C[:, 0].max() + 1):
cur_scene_pts = (inputs.C[:, 0] == idx).cpu().numpy()
cur_inv = invs.F[invs.C[:, 0] == idx].cpu().numpy()
cur_label = (all_labels.C[:, 0] == idx).cpu().numpy()
These are quite different. which one do you think is correct ?
Thanks for discussion.
Regards

Hi,
from the docs, it seems like for torchsparse <= 2.0.0 the coords are (x,y,z,batch_id), whereas for  torchsparse > 2.0.0 (batch_id, x,y,z).
So, if you are using  torchsparse <= 2.0.0 the first one:
for idx in range(invs.C[:, -1].max() + 1):
  cur_scene_pts = (inputs.C[:, -1] == idx).cpu().numpy()
  cur_inv = invs.F[invs.C[:, -1] == idx].cpu().numpy()
  cur_label = (all_labels.C[:, -1] == idx).cpu().numpy()

should be the correct one, since you are iterating trough the batches.

Please install the latest version (v2.1.0) with
python -c "$(curl -fsSL https://raw.githubusercontent.com/mit-han-lab/torchsparse/master/install.py)"

@zhijian-liu , Thanks, I got you.


Show [fixed] labels on table with deleted inputs

This PR adds to the context deletion listener to make sure that when a table is deleted all it's output tables get the string [fixed] appended to their title.
Notably, this title change does not flow through to further tables, so you can get the following scenario.

How do we think this case should be handled? Should we propagate the [fixed] notification to further tables, so we get Copy(Copy(People)) [fixed], or should we propagate the new table name so we get Copy(Copy(People) [fixed])?

Nice, Partition and aggregators look good now.
Now what I'm noticing is that when we delete a context and update the titles, our dataset selector dropdowns are still displaying the old titles. This is probably because we don't receive a notification on title change, and ContextSelector is just using useDataContexts.
Could we manually cause an update, ie by calling callAllContextListeners or something?

Ahh nice catch I hadn't noticed that. The callAllContextListeners approach definitely works. Is there a different way we should be doing it or is that good enough? I'll work on merging with main and adding support for editable clone.

Yeah not sure--Jason do you think there's a better way? @stardust66

I think all the points that were brought up are addressed now

Works with editable copy/partition
Works with SV transformers
Can't update description for now

Should we add something to the user documentation to explain [fixed] since we can't update descriptions?

Yeah that's a good idea--are there other corner cases or behavior that might be confusing that we should detail as well? We could have sections for those.

Yeah not sure--Jason do you think there's a better way? @stardust66

Since we just don't get notified, I don't think there's anything else we can do here.


Resolves the correct scope for namespaced scopes

What I was trying to do is addressed here #482. The documentation for namespace support is addressed here #392. In summary a bug exist when we call policy_scope for a namespace resource.
Previously when we called scope_policy([:admin, Post]), the correct Admin::PostPolicy::Scope class is found but scope in Admin::PostPolicy::Scope{@scope = [:admin, Post]} holds the passed in array instead of Post class.
This PR fixes the above issue to take into account the last argument of the passed in array as the scope if the passed in object responds to :each.

Just ran into this and came up with the same solution. 👍

@dgmstuart I have made some changes. Check out my last commit. Do you have any idea why the build is  failing on 2.4.1? (https://travis-ci.org/elabs/pundit/jobs/300633838)

@laertispappas Good stuff - I'll have a look.
Regarding the Travis failure, if I run 2.4.1 locally I get the same failures>
The issue is that the .rubocop.yml file specifies TargetRubyVersion: 1.9 but the latest rubocop (0.51.0) has dropped support for that.
Note that the last time master was built (6 months ago), the rubocop version was 0.48.0, which is why the repo shows the build as passing: https://travis-ci.org/elabs/pundit/jobs/231147775
There's no restriction on the rubocop version in the Gemfile, which means that effectively any PR happening after a new rubocop version first needs to update the code to support the latest version of Rubocop.
The earliest version which Travis builds is 2.1, so I'd recommend updating the .rubocop.yml to specify that as the target version, which should fix this.

@laertispappas Hi - I now work for Varvet, so maybe you could try rebasing and I'll see what I can do about pulling this through

Is this a duplicate of #391?

@Linuus  Yes it is.

Duplicate of: https://github.com/varvet/pundit/pull/391

Closing in favor of #391


[Feature] Add location / geotag / coordinates to message (linkifier & metadata)

I think an integration of of coordinates in the message editor would be awesome. In a nutshell:

It also seems very natural to me to have a timepicker and a location picker next to it, considering all modern social media platforms (Instagram, Facebook, Twitter, even YouTube etc.).
I am thinking about a twofold integration of location / geotag / coordinates to messages:

Depending on the platform, such a geolink could make it easier for people to share their location (ideally, a live location feature would be very neat, like WhatsApp and Telegram offer). There are e.g. already geolinks on Android devices that open specific apps (e.g. Google Maps, maps.me, osmand or even public transport apps for immediate schedule or ticket info) in the format:
geo:0,0?q=40.88331,8.06713 . If you click this link on Android it should open any apps, programmed to work with this format. On Apple it's usually nudging you towards Apple Maps; not sure whether that's a setting one can tweak. On Desktop there is no such feature.
One could use the Zulip linkifiers to parse the geotag and depending on mobile/desktop either chose/leave the geolink as mentioned above or set e.g. OSM or Google Maps (format: https://www.google.com/maps/dir/Current+Location/52.469302,13.279198)) as default for opening such tags. If e.g. the default would be the geotag after location picking the linkifier could convert it to e.g. Google Format if on Desktop. Not sure linkfiers could differentiate between mobile/desktop. Any opinions on that?

Instead of only sharing a location for whatever purpose, it would be nice if the location would be included in the message metadata. Why? This would enhance Zulip to become a geospatial platform (and would benefit the Zulip instance on https://gis.chat :tada: ). One could then search for messages in a certain area of interest, radius, city or country, leveraging e.g. PostGIS. The possibilities are endless. From my point of view (and the idea behind https://gis.chat), especially for highly specialized or niche communities but also large mainstream communities it would be nice to have an idea who is maybe nearby.
I know that there is already the possibility of defining a custom profile field one could leverage for coordinates or a reference to some geometry on OSM (e.g. country or city) but that's not reflecting the reality of people moving around (e.g. digital nomads):

While the latter point 2 is somewhat related to #13928 #18216 #2329 #1901, the first point isn't and would itself maybe also require a separate issue. Just wanted to keep it together for anyone searching for this issue and to point out that geospatial could bring value to our communities! :)
Would be happy to hear your thoughts!

Most chat platforms have a simple drop location pin - this is a must for us to share info - can link to maps.google.com or any other format

Thanks for sharing your feature idea, @do-me. Just off the top of my head, I can imagine some real privacy implications by storing geolocation data, especially of this level of precision.

Thanks for sharing your feature idea, @do-me. Just off the top of my head, I can imagine some real privacy implications by storing geolocation data, especially of this level of precision.

Thank you Karl - good point but look at what we use this for now:
We are sailors and captains and NEED to share geolocation - and it's not automatic ( although that would be a nice option to have )
example a vessel was anchored in the Las Perlas and suffered from an armed assault at anchor - they are in a remote location - and the pirates took every gadget from the yacht - this was an area without cell signal no vhf signal but they did have starlink - so they where able to call me using LINE.me ( a chat app we like but has no threading )  they also shared their location using the ships gps system(s) and we are able to help them -
we also share where there are fishing nets - rocks and other uncharted obstacles - and that is life saving.
in a closed group we a do not care soo much about privacy - we care about the accuracy of information. ( down to 4 meters is fine )
where does active updating your position come in handy ? when you sail through reef passes or badly charted waters.
So that is the use case which we want - check out this tracker to get a sense of the need for GPS sharing
check out
https://pacificposse.com/tracking

That's a fascinating use-case, @captaindietmar. This isn't anything we're planning to develop immediately, but I'll keep this issue open so we can discuss it further.

I have a $ 500 bounty to make it happen and a 12 year old bortle of rum

again this is optional location sharing not automatic - just like in whatsapp or line
here is a sample  ( obviously we can enter them manually )

https://maps.google.com/maps?z=18&t=k&q=loc:-15.926246121704578+-173.76037606907124
<iframe src="https://www.google.com/maps/embed?pb=!1m17!1m12!1m3!1d3746.749990001816!2d-173.76256478514338!3d-15.926246088969412!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m2!1m1!2zMTXCsDU1JzM0LjUiUyAxNzPCsDQ1JzM3LjQiVw!5e1!3m2!1sen!2sus!4v1687276674751!5m2!1sen!2sus" width="600" height="450" style="border:0;" allowfullscreen="" loading="lazy" referrerpolicy="no-referrer-when-downgrade"></iframe>

Thanks for sharing your feature idea, @do-me. Just off the top of my head, I can imagine some real privacy implications by storing geolocation data, especially of this level of precision.

I'd like to clarify a few things around my initial proposal.

The "share location" feature is something quite trivial that is supported by literally every messenger app I know of. I suppose it's also fairly simple to build leveraging the geolocation API from modern browsers, working on desktop and mobile too. In other words: no backend modifications required. It would just need an icon that runs something like this script. Leveraging custom linkifiers it could just insert an xml-like tag that is then picked up by a customized linkifier. I do not see any privacy issue here, as one decides actively to share it.

I totally agree with @captaindietmar that being able to share location data is fundamental nowadays.

My second idea is something very different I only saw on hiking/outdoor apps like Komoot until now (the app is awesome actually!).
The main idea is - how I imagine it - that you could use Zulip as a "geospatial diary", i.e. if you turn on some kind of toggle in the message compose box "add location metadata to message", it would add the coordinates from the browsers API to all messages until you turn it off.

I see very powerful use cases here mainly for closed organizations/companies.
a) Imagine you're going for a hike and you would like to document the best spots with text & pictures. If the location was added automatically (again, only when the toggle is on) you just need to type a "great view" and send the message. Afterwards you could filter for messages in the particular "hiking diary" topic and immediately get all "great view" coordinates on a map.
b) A more serious use case is e.g. documentation. We have clients who need to inspect and document streets/houses/infrastructure in general. They could go around and simply write a message in the "inspection" topic like "passed" or "needs thorough check". Again, this would all happen in a closed organization.

For @captaindietmar I even see another useful feature. When sharing the "live location" (which is very handy on WhatsApp/Signal/Telegram) it would be awesome if there was a simple checkbox for "record track" so that one could see and maybe export the track afterwards.

So far from the feature idea side.
Geoprivacy is important and unknowingly sharing your location is very bad for privacy. While features 1) and 3) are both one time actions where a user certainly is conscious of what is happening, feature 2) is something more exotic oriented towards a closed expert community.


Not activating mod

I use 1.19.2 quilt on modrinth app and when I start minecraft, the mod is not in my mod list or game.

Please share your client log

It is an older version of mclogs because they stoped updating 1.19

search for mclogs `[12:06:00] [main/INFO]:
Loading Minecraft 1.19.2 with Quilt Loader 0.21.0-beta.3
[12:06:00] [main/INFO]:
Loading mappings: jar:file:/C:/Users/{COMPUTER_USERNAME}/AppData/Roaming/com.modrinth.theseus/meta/libraries/org/quiltmc/hashed/1.19.2/hashed-1.19.2.jar!/mappings/mappings.tiny
[12:06:00] [main/INFO]:
Skipping mappings: Missing namespace 'intermediary'
[12:06:00] [main/INFO]:
Loading mappings: jar:file:/C:/Users/{COMPUTER_USERNAME}/AppData/Roaming/com.modrinth.theseus/meta/libraries/net/fabricmc/intermediary/1.19.2/intermediary-1.19.2.jar!/mappings/mappings.tiny
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/block_content_registry-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:

Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:01] [main/WARN]:
Unnecessary dependency range 1.19.2 at line 31 column 7 path $.quilt_loader.depends[1].versions[0] (resolves as [1.19.2, 2)), since it doesn't affect the result [1.19.1, 2)
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/block_entity-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:
Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:16] [Render thread/INFO]:
[STDERR]: 	JRE: Windows amd64 17.0.8
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/block_extensions-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:
Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:01] [main/WARN]:
Unnecessary dependency range 1.19.2 at line 31 column 7 path $.quilt_loader.depends[1].versions[0] (resolves as [1.19.2, 2)), since it doesn't affect the result [1.19.1, 2)
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/crash_info-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:
Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/registry-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:
Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:01] [main/WARN]:
Unnecessary dependency range 1.19.2 at line 31 column 7 path $.quilt_loader.depends[1].versions[0] (resolves as [1.19.2, 2)), since it doesn't affect the result [1.19.1, 2)
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/networking-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:
Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/lifecycle_events-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:
Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/resource_loader-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:
Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/tags-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:
Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:01] [main/WARN]:
Unnecessary dependency range 1.19.2 at line 31 column 7 path $.quilt_loader.depends[1].versions[0] (resolves as [1.19.2, 2)), since it doesn't affect the result [1.19.1, 2)
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/recipe-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:01] [main/WARN]:
Deprecated array format for dependencies: see https://github.com/QuiltMC/rfcs/pull/56 for more information.
[12:06:01] [main/WARN]:
Unnecessary dependency range 1.19.2 at line 31 column 7 path $.quilt_loader.depends[1].versions[0] (resolves as [1.19.2, 2)), since it doesn't affect the result [1.19.1, 2)
[12:06:01] [main/WARN]:
Warnings for quilt.mod.json at: '/qfapi-4.0.0-beta.30_qsl-3.0.0-beta.29_fapi-0.76.0_mc-1.19.2.jar!/META-INF/jars/advancement-3.0.0-beta.29+1.19.2.jar!/quilt.mod.json'
[12:06:17] [Render thread/WARN]:
Assets URL 'quilt.zfs://transformed-mod-minecraft.i0:0/data/.mcassetsroot' uses unexpected schema
[12:06:17] [Render thread/WARN]:
Assets URL 'quilt.zfs://transformed-mod-minecraft.i0:0/assets/.mcassetsroot' uses unexpected schema
[12:06:16] [Render thread/INFO]:
[STDERR]: 	Loaded from org.lwjgl.librarypath: C:\Users{COMPUTER_USERNAME}\AppData\Local\Temp\lwjglcarte\3.3.1-build-7\jemalloc.dll
[12:06:16] [Render thread/INFO]:
[STDERR]: 	Module: org.lwjgl.jemalloc
[12:06:33] [Render thread/INFO]:
[STDERR]: 	opengl32.dll not found in org.lwjgl.librarypath=C:\Users{COMPUTER_USERNAME}\AppData\Local\Temp\lwjglcarte\3.3.1-build-7
[12:06:16] [Render thread/INFO]:
[STDERR]: 	Loaded from org.lwjgl.librarypath: C:\Users{COMPUTER_USERNAME}\AppData\Local\Temp\lwjglcarte\3.3.1-build-7\lwjgl.dll
[12:06:16] [Render thread/INFO]:
[STDERR]: MemoryUtil allocator: JEmallocAllocator
[12:06:18] [Render thread/INFO]:
Setting user: {MINECRAFT_USERNAME}
[12:06:16] [Render thread/INFO]:
[STDERR]: Loading library: jemalloc
[12:06:16] [main/INFO]:
[Quilt Command] Networking support is enabled
[12:06:16] [Render thread/INFO]:
[STDERR]: 	Module: org.lwjgl
[12:06:33] [Render thread/INFO]:
[STDERR]: 	Module: org.lwjgl.opengl
[12:06:16] [Render thread/INFO]:
[STDERR]: 	JVM: OpenJDK 64-Bit Server VM v17.0.8+7-LTS by Microsoft
[12:06:16] [main/WARN]:
@Redirect conflict. Skipping #imm_ptl_core:imm_ptl.mixins.json:common.position_sync.MixinServerGamePacketListenerImpl from mod imm_ptl_core->@Redirect::redirectIsInTeleportationState(Lnet/minecraft/class_3222;)Z with priority 900, already redirected by #carpet:carpet.mixins.json:ServerGamePacketListenerImpl_antiCheatDisabledMixin from mod carpet->@Redirect::relaxMoveRestrictions(Lnet/minecraft/class_3222;)Z with priority 1000
|     6 | api                                               | gs_mclo_api                                          | 4.0.1                       | Fabric  | d4c3e124fbaccd10eea63b4cb7f6fe191ea14317 | \mclogs-fabric-1.4.1-1.19.jar                                                                                | /META-INF/jars/api-4.0.1.jar                                                                              |`

[12:08:15] [Render thread/WARN]:
Warning! Mod gs_mclo_api has a broken icon, loading default icon
showed up but mclogs is still not there

tried to install in different mod set and still wont work

It is configured to only run on servers for now.


Updated IsActiveAsync to also check for verified accounts

Added a check to ensure expected behavior on "IsActiveAsync". A useraccount who is authenticated and verified is an active useraccount. For all other scenarios "IsActive" should return "False". See #44

Hi @HenrikWM, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;


chore: cleanup empty default values (#694)

Backport
This will backport the following commits from k8s-22/main to k8s-21/main:

chore: cleanup empty default values (#694)

Questions ?
Please refer to the Backport tool documentation

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 708

Questions ?
Please refer to the Backport tool documentation


When I Use This Workflow in My Repo Its Is Not Working

I have the same issue

same

Using a personal access token that access to Issue and PR full access right.


How to specify Android 2?

I had been using this object to get prefixes for Android 2.3:
options: {
	browsers: ['last 2 version','Android 2']
},

However, as of latest Autoprefixer (5, via grunt-autoprefixer 2.2.0) this silently fails. What is the correct way to specify this browser with browserlist in Autoprefixer 5?

browsers: ['last 2 version', 'android 2.3', 'android 2.2', 'android 2.1']

Excellent. Thanks.

On 23 Jan 2015, at 12:36, Andrey Sitnik<EMAIL_ADDRESS>wrote:
browsers: ['last 2 version', 'android 2.3', 'android 2.2', 'android 2.1']
—
Reply to this email directly or view it on GitHub.


Feature/data key rotation

Coverage decreased (-0.1%) to 55.2% when pulling 83cf033cfbfdaa868139b8103baa17274dc9f2d5 on feature/data-key-rotation into e81b96b898239ebaafb19ddeb154e4678f615ade on master.


Intercepting warp_command type 3's for ungrouped players

[ ] find out how the grouping is done (smells like client_context_update)
[ ] keep record on who is in a group
[ ] only allow warps for grouped players

Closing #27, Research issue (and warping isn't required as much, as teleportation has arrived.)


feat(InfiniteScroll): use puppeteer emulating scrolls instead of window.scrollBy

This should close #1010 (but I don't know if this is the API you referred to in your issue, and it's the only other relevant example I found for scrolling). There's still a bug I need to find out why it breaks (for some reason the test case for waitForSecs: Infinity, scrollCancelCallback throws..)

Btw I came across this issue https://github.com/puppeteer/puppeteer/issues/4690, that says there might be some issues with headless mode with this approach, would be good to ensure it works fine with headless (haven't checked, maybe the tests are already using headless).

I used this script to test these changes (since jest was waay too slow for my likings), and it worked, tho I needed to increate the timeout between scrolls to make stopScrollCallback work as before
const { launchPuppeteer, utils } = require('.');

(async () => {
    const browser = await launchPuppeteer({ launchOptions: { headless: true } });

    const page = await browser.newPage();

    let count = 0;
    const content = Array(1000).fill(null).map(() => {
        return `<div style="border: 1px solid black">Div number: ${count++}</div>`;
    });
    const contentHTML = `<html><body>${content}</body></html>`;
    await page.setContent(contentHTML);

    function isAtBottom() {
        return (window.innerHeight + window.scrollY) >= document.body.offsetHeight;
    }

    const before = await page.evaluate(isAtBottom);
    console.log(before);

    await utils.puppeteer.infiniteScroll(page, { waitForSecs: Infinity, stopScrollCallback: () => true });
    // await utils.puppeteer.infiniteScroll(page, { waitForSecs: 0 });

    const after = await page.evaluate(isAtBottom);
    console.log(after);

    console.log(await page.evaluate(() => ({
        innerHeight: window.innerHeight,
        scrollY: window.scrollY,
        innerHeightPlusYOffset: window.innerHeight + window.scrollY,
        offsetHeight: document.body.offsetHeight,
    })));

    await page.close();
    await browser.close();
})();


Component Tests for ignoring Some Classes

Hi Alexi,
I am creating a pull request for ignoring a few classes in persistence but persisting children.
In the following example I am unable to omit JobStreamSteps from persistence. I would ideally persist only JobStream and JobStreamStep into the database with a join between the two of them.
Thanks,
Vamsi

See #18, solved now.


Make multiple attempts to startup rsyslog

Seems like rsyslog, after being killed, may either start up again by itself, or possibly start up in a delayed manner [1].  Making multiple attempts while also checking if rsyslog has already started up seems to make do for now.

[1] Previous observation when I ran into this issue. Might be incorrect or irrelevant.

Fair on that, it was kind of an "Oh hey, we use '[]' when we throw in variables" sort of thing. Perhaps [#1] would be better if we want to keep that sort of style?

Also, should we mention issue #163 in the commit message? Or is that a separate thing?

Fair on that, it was kind of an "Oh hey, we use '[]' when we throw in variables" sort of thing. Perhaps [#1] would be better if we want to keep that sort of style?

Sure. That works too.

Also, should we mention issue #163 in the commit message? Or is that a separate thing?

Yes. That is exactly the thing we are providing a temporary fix for.
I'm hoping the RHEL9 people or Rsyslog people provide the true solution in the near future.


Compiler OS go packages

Appears there are builds of the compiler OS go packages for OSes they shouldn't be used on. For example, go_linux-64 is not only available on Linux, but also on macOS and Windows. This is also true of go_osx-64 and go_win-64. In fact there are no Windows builds of go_win-64.

Go generates static binaries and is capable of doing so cross-platform. On Linux, I can do:
# Install the cross-compiler
$ conda install -y go_win-64

# Hello world!
$ cat <<EOF > hw.go
package main

import "fmt"

func main() {
    fmt.Printf("Hello, World!\n")
}
EOF

# Re-check target platform
$ env | grep -i GOOS=
GOOS=windows

# Build the exe
$ go build hw.go

# What did I build?
$ file hw.exe
hw.exe: PE32+ executable (console) x86-64 (stripped to external PDB), for MS Windows

I can run it too ;-)
$ wine64 hw.exe
hello world

I see. So they are for cross-compilation?

Indeed.

Windows CI run still failing :(
[WARNING] Token warning: expires in 25 days
Traceback (most recent call last):
  File "C:\Miniconda36-x64\Scripts\upload_or_check_non_existence.py", line 131, in <module>
    main()
  File "C:\Miniconda36-x64\Scripts\upload_or_check_non_existence.py", line 121, in main
    upload(cli, fname, owner, channel)
  File "C:\Miniconda36-x64\Scripts\upload_or_check_non_existence.py", line 68, in upload
    env=os.environ)
  File "C:\Miniconda36-x64\lib\contextlib.py", line 88, in __exit__
    next(self.gen)
  File "C:\Miniconda36-x64\Scripts\upload_or_check_non_existence.py", line 27, in get_temp_token
    shutil.rmtree(dn)
  File "C:\Miniconda36-x64\lib\shutil.py", line 494, in rmtree
    return _rmtree_unsafe(path, onerror)
  File "C:\Miniconda36-x64\lib\shutil.py", line 389, in _rmtree_unsafe
    onerror(os.unlink, fullname, sys.exc_info())
  File "C:\Miniconda36-x64\lib\shutil.py", line 387, in _rmtree_unsafe
    os.unlink(fullname)
PermissionError: [WinError 5] Access is denied: 'C:\\Users\\appveyor\\AppData\\Local\\Temp\\1\\tmpwkslut82\\binstar.token'

Known issue ( https://github.com/conda-forge/conda-forge-ci-setup-feedstock/issues/14 ). We have had a hard time fixing it. If you would like to take a look, we would certainly appreciate the help. Interestingly it does not block uploading.

I deprecated the cross compiler go packages. If we need this again lets open an issue.


License question

Thanks for making this app available! May I ask what license you're putting it under? Without any license, it's "all rights reserved" and thus not "truly free" :wink:

Thank you for your attention, i've updated license right now, it is Apache 2.0 :)

Thanks a lot! Will be reflected here with the next sync tomorrow around 19:00 UTC. Be welcome to pick a badge if you want to link there :smiley:
Oh: And should you want to have something adjusted (description, screenshots), or want to have that in your repo here using Fastlane structures so you can easily adjust it yourself, just let me know. I can provide you with the initial Fastlane structure via a PR, or perform updates locally at my end.


Don't show tips when history is used

I usually use the history a lot. (E.g. the up arrow key or CTRLR from fzf)
But when using the history I don't want to see the tips.
Is that already possible and if so how?

Hi @mamiu!
Currently the plugin doesn't remember how abbreviations are triggered, so it's not possible for now.
I'm also interested in this feature, I'll take a look at it when I have some time.

@gazorby Ok get it. Thanks for taking care of it.
I just played around right now and found a workaround which works, but is probably not the best solution.
In the fish_user_key_bindings.fish file add a wrapper for the history-search-backward special input function which sets the __abbr_tips_used variable to 1 before calling the history-search-backward function. Then adjust all keybindings that use the history-search-backward function so that they use the wrapper instead.
# history-search-backward wrapper for the fish-abbreviation-tips plugin
function __abbr_tips_history_backward
    set -g __abbr_tips_used 1
    commandline -f history-search-backward
end

# user defined key bindings
function fish_user_key_bindings
    bind \e\[A __abbr_tips_history_backward # arrow up key
    # If you use other key bindings that use the history-search-backward function make sure they also call the custom __abbr_tips_history_backward function
end

This also affects custom keybindings that add a command that has an abbreviation. eg. I use \co to open my editor, passing the contents of the line as arguments:
set -x EDITOR 'nvim'
# ...
abbr nv "$EDITOR"
# ...
bind \co "commandline -i ' $EDITOR '; commandline -f backward-kill-word beginning-of-line yank execute"

But __abbr_tips_used also works here:
function launch_editor
    set -g __abbr_tips_used 1
    commandline -i " $EDITOR "
    commandline -f backward-kill-word beginning-of-line yank execute
end
bind \co launch_editor


Add a way to specify what the interval between tests should be to the config file

the default interval should be 14 days, but user should have a way to specify a different interval if more or less frequent testing is needed.

added


Fix br-cep validation

Validation was failing when receiving value of type number, cause there is no property length.

Coverage remained the same at 96.852% when pulling b6d05c3e81bd88176715a37ba3a824e314d204db on b2ys:master into 7c748f6be75f610a77b7ad7e33b83873266f6cb2 on assisrafael:master.

Thank you for the pull request.

How soon will you release a new version with this fix? I need this to fix some bugs in a project.
Thanks in advance.


WEBOPS-3348 Handle bad node config

When a node in the DOCKER_NODES env var is badly formated handle any exception caused to allow the other configured nodes to continue working

Given that we are catching any exception - can we show the exception message as part of the error so we can tell what went wrong?
eg. something like:
except exception as e:
logger.exception('Failed to add node from config: {}, details: {}'.format(node, e))`
also, should the script exit at that point, rather than continuing on after catching the exception?

Isn't that what exception does in logging: https://docs.python.org/2/library/logging.html ?

not sure I understand what you mean,
You are not passing error to your logger instance, therefore it is hidden.
Maybe you mean the handler?  But in this case, you are catching an exception, not raising one.


Refractor compute

This PR fixes #90693 and makes the compute method more efficient by using a single ReceivePort instead of 3.
The code changes were inspired by @Irhn 's comment in a Dart SDK issue..
Fixes https://github.com/flutter/flutter/issues/90693
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

There is also an edge case here that also wasn't handled in the previous iteration of the code, which is that no error will be reported if the entry point fails after the sending the result back to the main Isolate.
This is because after receiving the data we close all the ports as such no additional handlers are called.
However, this is only an issue for the development team not the clients / consumers.
I've been thinking a great deal about this and there is no simple or secure way of doing this that would be 100% future-proof. Also it's also impossible to test this because it would not something the caller is responsible for but the developer.
To illustrate when this issue would occur:
// if this were to be changed
Isolate.exit(configuration.resultPort, <R>[result]);
//  to something like this
configuration.resultPort.send(<R>[result]);
configuration.resultPort.send(<R>[result]); // This send event would not be caught
// or
configuration.resultPort.send(<R>[result]);
throw Error(); // This error would not be reported

The previous implementation also ignored additional success / result events, while reported an additional error. But because close() was called on the ReceivePort it actually wasn't handled. (I tested this).
To actually force the handlers to be called one would have to delay returning and do something like await Future.delay(Duration.zero); before closing the ports. And this STILL isn't guaranteed because the failing code could be some newly added listener or delayed response. I. e.
configuration.resultPort.send(<R>[result]);
await Future.delay(Duration(seconds: 1), () => throw Error());

However, as long as we call Isolate.exit and only send one response through the SendPort we should be fine. Even if some erroneous listener was added in the user provided callback, since the entire Isolate is killed.
Am I overthinking this? For now I'll just add a comment and if anyone has a better solution in mind, please let me know.

@dnfield Would you mind reviewing this?

I also added additional tests:

calling compute from compute callback,
testing executing Isolate.exit from the compute callback, (Tests the exit branch (which wasn't tested before))
and all of the different types of Isolate.current.kill i.e. immediate / beforeNextEvent

@dnfield from the looks of it in Dart 2.17 a new method Isolate.run is added which is essentially the same as compute (in terms of functionality).
The differences I see in the implementation is:

we time the functions i.e. Timeline
we use Exception instead of RemoteError or the error that was actually thrown by the user provided function
I see there is some additional safety around closing the receive port
and they use non-growable lists

For now, I will address 3. and 4.
Because 1. and 2. would be a breaking change in compute, I will leave those as is.
How should we proceed?

deprecate compute and lose the Timeline
keep our own version

After taking a second look at the new Isolate.run implementation it does not have exactly the same functionality.
The run method accepts a no arguments function.
While we require a function with an argument and the argument to be passed to it.
Which means the transition for end users wouldn't be just replacing the call but still relatively trivial if we chose to deprecate compute.
Anyways, awaiting additional feedback.

I think it would make sense to do the following:

Deprecate compute, and point people instead to Isolate.run.
Make its functionality forward to Isolate.run. Keep the timeline functionality in compute.

@goderbauer @Piinks wdyt?

If we want to keep timing exactly intact, we need to actually implement the function ourselves. Since the implementation timed the ReceivePort constructing and closing.
If we're OK with simply timing the user callback then the new implementation is essentially:
// Copyright 2014 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

import 'dart:async';
import 'dart:developer';
import 'dart:isolate';

import 'constants.dart';
import 'isolates.dart' as isolates;

/// The dart:io implementation of [isolate.compute].
Future<R> compute<Q, R>(isolates.ComputeCallback<Q, R> callback, Q message, { String? debugLabel }) {
  debugLabel ??= kReleaseMode ? 'compute' : callback.toString();

  return Isolate.run(() => Timeline.timeSync(
    debugLabel!,
    () => callback(message),
  ));
}

Of course test expectations would need to be changed + the raised issue in the Dart SDK resolved.

My preferred way would be to keep the compute functionality, but implement it in terms of the new Dart API. The tracing that compute adds over the raw Dart API has been useful. The important bits to keep for tracing here are the flow events (going from the point the computation was kicked of to the computation to the point where the result of the computation is received) and the duration of the computation. Measuring how long it takes to instantiate and close the ports is not important, IMO. I believe that was just done in the current implementation to get the flow events inserted properly.
I don't think we should deprecate compute altogether since it does offer the timeline tracing as an additional value. We should adjust the documentation, though, to document this difference over the other API.
Is the switch from Exception to RemoteError actually breaking anything?

Is the switch from Exception to RemoteError actually breaking anything?

@goderbauer It breaks tests and if this is fine, I have no problem changing the tests.
Personally, I do prefer the approach the Isolate.run is taking which is actually forwarding the errors and exceptions from the Isolate.run function back to the main isolate.
So, for instance, I can do:
try {
  Isolate.run(() => throw MyCustomException);
} on MyCustomException {
  print("caught");
}

// Prints "caught"

With our implementation of compute you could only catch an Exception. Which isn't that helpful and probably counter-intuitive.
try {
  compute((_) => throw MyCustomException, null);
} on MyCustomException {
  print("caught");
}

// Throws Uncaught Exception

I also think, we should keep all the tests we have, even the new ones added, since they also helped me catch a bug in the implementation of Isolate.run.
I was also wondering are we constrained by a specific Dart SDK version i.e. is it fine to already use this functionality or would we release first this version of compute and later when the minimum Dart SDK version increases the new one?
I'm a new contributor so I don't know how this is done.
I already have a running and passing local changes for a patch that uses Isolate.run.  Should I open a new PR or just change the title here?

I was also wondering are we constrained by a specific Dart SDK version i.e. is it fine to already use this functionality or would we release first this version of compute and later when the minimum Dart SDK version increases the new one?

Has the version of the Dart SDK that provides this functionality already rolled into Flutter? If so, it's ok to use it.
The approach to errors that Isolate.run is taking does sound a little nicer. If it is just breaking our own tests, I think it would be fine to just switch to that.

Isolate.run comes with Dart 2.17 which hasn't even released yet. And if I understand:

Has the version of the Dart SDK that provides this functionality already rolled into Flutter?

correctly.
Currently, only features of Dart 2.12 can be used?

The dart version that's currently bundled with Flutter on master is 2.17.0-182.0.dev. So everything included in that version can be used in the framework.

Oh!!! Wonderful!
I was able to make the required changes.
Two notes:

I improved some comments. With Dart 2.15 it became possible to send closures directly across isolates as well as instance methods. I also added tests to ensure these assumptions stay true in the future.
Until the Isolate.run bug is fixed one test is marked for skipping.

I will land the patch addressing the reviews, tomorrow. It's almost midnight here.
I also want to wait for all the tests to pass and see if the difference in error handling broke anything.
I too suspect that the fix for bug with Isolate.run will land soon considering the patch fixing it is already written. I think we should wait so I also push a commit not skipping the failing test.

@goderbauer can you check if the failure is related to this patch?

OK, thank you for letting me know.
I think we should also then wait for the fix for Isolate.run bug to roll into the framework, which I think will happen by the end of the week. Then, I'll also unskip that buggy test.
Unless we are nearing a deadline in which case I case and can push the commit with addressed changes. (The reason I haven't is because I don't want to needlessly waste resources. (For a comment fix of all things))

The fix for bug in Isolate.run landed in 2.17.0-193.0.dev.
@goderbauer Any idea when that version will be rolled into Flutter?

@jellynoone the Dart roller is currently paused for branch alignment - it should be turned back on again before long (i.e. latest should be sometime early next week). Once it's back on it will roll Dart into flutter/engine, and then that needs to be rolled into framework.
I would expect that we should be able to land this sometime in the next week or two.

Great, thank you for informing me.
I'll keep checking and push when the fix rolls into Dart.

Could we do the same in compute?

This would be a pretty big breaking change - and I don't see any easy non-breaking migration path. If we wanted to do that, we'd have to deprecate the current compute and implement a new one (finding a proper name for that one will be hard).
I think, if somebody wants the simplified semantics, they can just use Isolate.run directly.

FYI: I believe Isolate.run has some usability issues because the closure provided lents itself to over-capturing stuff that cannot be send to an isolate. See https://github.com/dart-lang/sdk/issues/48566.

But isn't this also an issue with compute now, since arbitrary closures can be passed to the function and to the best of my knowledge we really have no way of knowing if the function is static / top-level.
Except, if we do a very implementation depended assert(callback.toString().contains(': static'))

Yes, you can also run into this problem with compute, but the design of Isolate.run makes it more likely that you trigger this case, I think, because the only way to pass in data is to closure it in.

I explicitly changed comments in this PR to be more inline with the current dart version features. i.e. made it explicit that it is possible to send closure as apposed to just top-level and static functions.
Should I add another comment recommending sticking to just top-level and static functions? Citing this problem or simply adding a case for easier testing?

It may be useful to include a link to the underlying issue https://github.com/dart-lang/sdk/issues/36983 and inform people that closures in dart may capture more than meets the eye.

Addressed previous comments, added note about closures and made sure the Flow.end event is called even when the computation fails. (Missed this before).

As stated in dart-lang/sdk#48566, a decision was made to NOT ship Isolate.run in the next stable release.
I re-implemented the improved compute we had before with a few notable changes to bring it more inline with how Isolate.run did things:

errors are now caught and sent back to the main Isolate and throw,
if the isolate exited prematurely a RemoteError is thrown instead of an Exception,
it now sets the Isolate.debugName

additional changes:

I took the liberty to remove one of the previous timing functions which really did nothing and was already removed in the version which used Isolate.run,
_IsolateConfiguration now also times the callback,

This still needs a second LGTM - @goderbauer?

Gold has detected about 1 new digest(s) on patchset 24.
View them at https://flutter-gold.skia.org/cl/github/99527

Still LGTM.
Thanks for sticking with this. It may not be apparent but your work here has helped improve things around the Isolate.run API and identify some key areas needed to improve that.

@dnfield  Thank you very much. It was a fun exercise.

All tests are green some broken again, and I just wanted to add one last note for documentation purposes of the changes.
User facing changes (tiny):

one (redundant) timing event was removed;
the spawned Isolate now named;

User facing changes (minor):

Exceptions and errors thrown by the computation are re-thrown in the main Isolate;
Errors thrown in the Isolate must be sendable between Isolates
RemoteError is thrown instead of an Exception when:

a user does something freaky like immediately kill or exit the current Isolate from the computation;
a user sends back a response which cannot be sent through the SendPort.send;
a user throws an error from the computation which cannot be sent through the SendPort.send; or
we made a mistake somewhere (should only happen when/if new code is add.

Internal:

use 1 RawReceivePort instead of 3 ReceivePorts,
simplified specified types,
wrapping spawned Isolate result in List to easily differentiate between different event types

@mit-mit I don't know if you're the right person to tag.
I just want to make sure users aren't forgotten to be informed about changes in my previous post (mostly exception handling).

(About the assert: Until all programs are soundly null-safe, as Foo is potentially effectively doing is Foo?.)

Aha!!! Thank you for the explanation.


Fingerprint unicode files without error

When running in Python 2, the asset fingerprinter throws an exception if given a file with unicode contents.
The only way I found to replicate this error in a test was to read a file, rather than mocking. The one file that a) can reliably expect to exist and b) makes most sense to have an arbitrary unicode character in it is the test itself.
Fixing the error meant using the codecs module from the standard library to to match Python 3's unicode-by-default file reading.

:+1:


Merge conflicts in dev/muke

Fix

Never mind, using a pull request for this conflict would merge the changes to master.


Reference error in Converter.js

I think this line:
   data = this._csvLineBuffer;
should be:
   var data = this._csvLineBuffer;
in libs/core/Converter.js line 262 https://github.com/Keyang/node-csvtojson/blob/master/libs/core/Converter.js#L262

thanks for pointing out.
~Keyang


Added yarn.lock

Executed dependency installation using $ yarn

I don't think we should add a yarn.lock.
This project does not use yarn, so we would need a new PR for the yarn.lock each time we change/update the dependencies.

Alright then. Closing this PR.


UNION ALL query return wrong type, NULL value but get ''

the detail is that:
sql:
with a as
(
select 2 as id, '1234' as user_id
union all
select 1 as id, NULL as user_id
),
b as
(
select 4 as id, '543' as user_id
union all
select 3 as id, NULL as user_id
)
select id,user_id from a
union all
select id ,user_id from b
the result is :

my value is "NULL "  ,but  use with lable ,the result is issue, now is ''

Hi，It's look like is FE query plan's problem. I will try to fix the problem


Use ScopeGuard instead of Kokkos initialize in the example

HIP and SYCL not started, GCC was killed. SNAFU, irrelevant.


[New primitive] Subtraction (X-Y)

Things that will be done in this issue that are related to addition are:

[ ] numbers that overflow into other datatypes.
[ ] code coverage bit in l_add_l that is not yet covered in the tests for addition also related to point 1.


Memory Error in SpectralCube._pix_size

This arose when computing the 0th moment of a cube.
Running cube._pix_cen() gives the following:
---------------------------------------------------------------------------
MemoryError                               Traceback (most recent call last)
<ipython-input-2-a118f0eff323> in <module>()
----> 1 cube._pix_size()

/home/eric/Dropbox/code_development/radio_astro_tools/spectral-cube/spectral_cube/spectral_cube.py in wrapper(self, *args)
     61         # The cache lives in the instance so that it gets garbage collected
     62         if func not in self._cache:
---> 63             self._cache[func] = func(self, *args)
     64         return self._cache[func]
     65

/home/eric/Dropbox/code_development/radio_astro_tools/spectral-cube/spectral_cube/spectral_cube.py in _pix_size(self)
   1345
   1346         # Take spectral units into account
-> 1347         dspectral = dspectral * self._spectral_scale
   1348
   1349         return dspectral, dy, dx

MemoryError:

It's a fairly large cube (~30 Gb). I read it in with:
cube = SpectralCube.read("M33_14B-088_HI.clean.image.fits", mode='denywrite', memmap=True)

Commenting out line 1347 does seems to fix the issue, and the units of the moment map remain correct. The cube._spectral_scale is a float, not a quantity. Setting it to a quantity (e.g., km/s) still gives the memory error.

Yikes, this is a serious issue and looks hard to test for.  However, I don't believe the memory error could possibly be coming from the highlighted line.   Is there any chance your traceback is referring to an outdated/updated version of the file?  If not, then I am not sure what's going on, but perhaps memory allocation was already exceeded before this point and this very tiny additional memory allocation pushed it over the top.  Can you find out how big dspectral is?

you were calling _pix_size, not _pix_cen?   What are the dimensions of your cube?

Yes, it should be _pix_size. The cube dimensions are (1178, 2560, 2560).
The error does appear to be coming from that line though. I think you're right that it's just pushing the memory allocation over the top since dspectral, dx, and dy are all ~61 Gb, and the error goes away when calling _pix_size with a subcube.

This is a problem, then.  _pix_size ought to be computed slicewise or raywise.

I wonder if this is a WCS memory leak.  In _pix_size, @ChrisBeaumont left a note that the broadcast arrays should not be memory intensive.  I am not entirely convinced either way yet.

Actually, I think this might be a bad interaction between caching and _pix_cen/_pix_size: caching something that is supposed to be cheap to compute can be bad.

I think I caught a few problems, including unintentional massive duplication of data because of an order of operations issue and some unnecessary code.  I think the core of this problem, though, was something like this:
# small array
x = np.arange(1000)
# small array (same values in memory)
y = np.broadcast_arrays(x[:,None,None], x[None,:,None], x[None,None,:])
# now, the full 10^9 floats must be allocated!  Huge array!
y = y - 1

which was easily avoided by moving the subtraction before the broadcasting

@e-koch I think this solves it now

:+1:


Can't return to chromebook from xfce

Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/%{ <-- HERE (.*?)}/ at /usr/bin/edit line 528.
Error: no "edit" mailcap rules found for type "cannot open `chroot-all' (No such file or directory)"
(xenial)kloughead@loc

Hi, having difficulty returning to chromebook from  xfce.  Here is what happens:
Ctrl+Alt+Shift+Back goes to a black screen (for at least 5 minutes, I haven't waited longer than that yet), Ctrl+Alt+Shift+Forward goes either to a black screen (from xfce) or back to xfce (from the aforementioned black screen).  Ctrl+Alt+Shift+Refresh returned me to xfce.   Any other suggestions?
If known, describe the steps to reproduce the issue:

@kvnloughead,
Try switching to CrOS the programmatic way and see if it's any quicker.
In a terminal session in your chroot enter:

croutoncycle cros

I like to use that since I'm usually at the keyboard in my chroot a lot of the  time.
Here's the croutoncycle usage for other options if you're interested:
croutoncycle next|prev|cros|list|#
Cycles through running graphical chroots.
    next: switch to the next display
    prev: switch to the previous display
    cros: switch directly to Chromium OS
    list: list all of the active displays and the associated chroot name
    #: switch to the nth item in the list, zero-indexed
    :#: switch directly to the chroot owning the specified display number

Hope this helps,
-DennisLfromGA

I found after upgrading my C101PA to 83.0.4103.97 (it hadn't been updated since February), I have this too. If I try to switch away (via ctrl/alt/shift or croutoncycle), the display freezes (still showing Xfce or whatever WM, but frozen). It appears that the VT support broke (probably in ChromeOS). If I switch back via ctrl/alt/shift/next, everything goes back to normal. So the only way back to ChromeOS is to log out. I'm going to try switching to the beta channel to see if it fixes.

Closing. Please re-open if this issue is still a concern.


Improve 'Unable to start worker process' Errors for Out Of Proc

It looks like we're getting a NRE in scenarios where the Java worker is unable to start (likely applies to all workers).
Possible causes for startup failure:

no JAVA_HOME env variable
no JDK installed
old Java worker has been launched and not terminated

[19/10/2017 9:15:17] Reading host configuration file 'C:\Users\maart\Desktop\azurefunctionsdemo\target\azure-functions\maarten-azure-functions\host.json'
[19/10/2017 9:15:17] Host configuration file read:
[19/10/2017 9:15:17] {
}
[19/10/2017 9:15:18] Generating 0 job function(s)
[19/10/2017 9:15:18] Starting Host (HostId=xpsmaarten-1042021596, Version=2.0.11308.0, ProcessId=20212, Debug=False, Attempt=0)
[19/10/2017 9:15:18] No job functions found. Try making your job classes and methods public. If you're using binding extensions (e.g. ServiceBus, Timers, etc.) make sure you've called the registration method for the extension(s) in your startup code (e.g. config.UseServiceBus(), config.UseTimers(), etc.).
[19/10/2017 9:15:18] Job host started
[19/10/2017 9:15:18] The following 1 functions are in error:
[19/10/2017 9:15:18] hello: Object reference not set to an instance of an object.

Just to provide some more info:
I tried with JDK 1.8.0_131, 1.8.0_144 and 1.8.0_151.
JAVA_HOME was pointing to JDK.
I also tried to kill all the java.exe process and even restarted Windows.
But this issue persists.

@mamaso Has there been any updates to this issue? I just installed the latest Azure Functions core tools, created a new Java function (via the VS Code extension), and immediately hit this exact same error.


refactor(ast_tools): remove LateCtx abstraction

LateCtx is just a wrapper around Schema. Remove it and use Schema instead.

#7083  👈
main

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

Join @overlookmotel and the rest of your teammates on  Graphite

Merge activity

Nov 1, 6:28 PM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


I wouldn't trust any of the permission logic yet.

View only, Read only users might be able to do more than they should,
Non admin user might be able to do admin type things.

Now I trust it.


Does OrientDB support subqueries?

OrientDB Version: 2.2.20
Java Version: jdk8
OS: centos7
issue
Does OrientDB support subqueries?
eg.
select * from (select * from a) b  where ...

Hi @student1555
Yes, OrientDB supports subqueries, but you cannot add aliases to them.
You can write your query as follows:
select * from (select * from a) where ...

I hope it helps
Thanks
Luigi

OK, Thank you, @luigidellaquila .


♻ 🔊 improve event store error handling

Codecov Report

Merging #200 (d56a8a4) into main (9cd9534) will decrease coverage by 0.05%.
The diff coverage is 62.50%.

:exclamation: Current head d56a8a4 differs from pull request most recent head a81eb44. Consider uploading reports for the commit a81eb44 to get more accurate results

@@            Coverage Diff             @@
##             main     #200      +/-   ##
==========================================
- Coverage   74.03%   73.98%   -0.06%
==========================================
  Files         124      125       +1
  Lines        3867     3867
==========================================
- Hits         2863     2861       -2
- Misses       1004     1006       +2

Impacted Files
Coverage Δ

marketplace-domain/src/event_store.rs
100.00% <ø> (ø)

...etplace-infrastructure/src/database/event_store.rs
92.68% <57.14%> (-2.44%)
:arrow_down:

...arketplace-domain/src/aggregate_root_repository.rs
97.77% <100.00%> (ø)

...lace-domain/src/contribution/aggregate_root/mod.rs
95.83% <0.00%> (-3.19%)
:arrow_down:

...etplace-core/src/application/contribution/apply.rs
0.00% <0.00%> (ø)

...ace-domain/src/contribution/aggregate_root/test.rs
100.00% <0.00%> (ø)

marketplace-domain/src/aggregate.rs
100.00% <0.00%> (+20.00%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Append (not Insert/Replace) text

Hello
I'm trying to add some content programmatically. The executeEdits replaces the Text at the given Ranges. How can I add/append the text and not replace the existing content?
Thanks

I don't really know the answer to your question, but I would assume that one way to handle it would be to call executeEdits with yourCurrentValue + valueToApend.

I've been digging through the docs to solve my own problem, and I found this for you:

IModel.getLineCount()
IModel.getLineMaxColumn()

So, you could do something like so:
const lineCount = editor.getModel().getLineCount();
const lastLineLength = editor.getModel().getLineMaxColumn(lineCount);

const range = new monaco.Range(
    lineCount,
    lastLineLength,
    lineCount,
    lastLineLength
);

editor.executeEdits('', [
    { range: range, text: 'your content to add' }
])

Hello
Thanks a lot for your reply. This will add text to the end of the Content and it works perfectly. I need to add the text to a specific line and not to the end of the Content. Your expample braught me to the idea to first move the entire content starting the line number I want to insert text, and the insert the text there. I will report about this as soon as I have a solution.

Thanks for the help, it pointed me to the right direction. I could solve this like this: I find the Line number and then edit only that specific line. Here is the code:
       var position = editor.getPosition(); // Get current mouse position
        var text = editor.getValue(position);
        var splitedText=text.split("\n");
        var lineContent = splitedText[position.lineNumber-1]; // Get selected line content
        var textToInsert = "<div>"; // text to be inserted
        splitedText[position.lineNumber-1] = [lineContent.slice(0, position.column-1), textToInsert , lineContent.slice(position.column-1)].join(''); // Append the text exactly at the selected position (position.column -1)
        editor.setValue(splitedText.join("\n")); // Save the value back to the Editor
        editor.setPosition(position);


Support MAD Layer Column

Checks to see whether the new layer column exists
Selects it as with_ar for easy compatibility with existing code
Backwards compatible

Need to test with MAD and RDM

Can confirm this working as intended on the latest MAD async branch. Unfortunately I don't run any main instances anymore, so not able to confirm backwards compatability.


Refactor: move all the spec-related code to one file

Issue #, if available: N/A
Description of changes: Refactor: move all the spec-related code to one file. Ideally they would be in a new class too but.. baby steps :)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

didn't think the new region documentation would get outdated this quickly 😜

This works for Python 3 but Python 2 users are out of luck.
from cfnlint.specs import RESOURCE_SPECS as _deprecated_RESOURCE_SPECS

deprecated_names = {
    'RESOURCE_SPECS': 'is refactored and deprecated. Please use cfnlint.specs.RESOURCE_SPECS'
}

def __getattr__(name):
    if name in deprecated_names:
        warn("%s %s" % (name, deprecated_names[name]), FutureWarning)
        return globals()["_deprecated_%s" % name]
    raise AttributeError("module %s has no attribute %s" % (__name__, name))

@miparnisari should we just let my feedback go?  I don't mind as I thought it was easier to do that but you are correct for Parameters its a little confusing.
Looks like we have a merge conflict that needs to get cleaned up and then we can get this in.


Fix #387: fix deluge JSON queries

Deluge now require the Content-Type header for JSON queries. Without the header deluge returns "500 Internal Server Error".
See #387

Thanks!


vala.updateScript: init

Motivation for this change
https://github.com/NixOS/nixpkgs/pull/59372 was replaced with #98304, which was merged as
74c547209048372ca10fa92660108b03363c3489, so I'm following the
instructions in the comment and enabling the updateScript. Seems to work.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[x] Fits CONTRIBUTING.md.

I guess the only remaining issue was merging the changes when running multiple update workers which should now be handled automatically by git.


Lua file is not working properly

Describe your problem here.
So I've been trying to make custom note via Lua files and... they work as they should, but the textures doesn't work and I'm sure its not a mistyping problem, nor a problem with the textures themselves because I just took the hurt notes slammed some round notes on top. The xml file is not an issue because its not mistyped.
Really don't know why that's happening because Modcharts work fine and I seem to be the only one having this issue.
Also tried to code them in and it resulted in the same problem. I don't know what to do.

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, I added some stages, some changes to the GUI and added more people to the credits

espera vc eh br? Crl q foda
Enfim, nao deu certo :)
eu compilei varias e varias vezes e o problema ainda esta la.
O que vc quiz dizer com "se vc colocar em assets/shared/images/"? Tem um lugar aonde vc coloca e n precisa compilar o jg?
Ps: crl n espera q o Shadow Mario me responde-se


Performance enhancements related to issue #772

Unfortunately I don't have the time to continue pursuing the solution to this problem, but I thought I would send the small code changes that I made that improved performance in this extreme situation.

Removed the hashCode/equals change, as it broke tests.

@juherr Thoughts on this PR?

@cbeust I never feel good perf improvments without something concrete to evaluate it.
@benlamonica Could you add a test based on your ContentionTest from #772? How many time should it take before and after the fix? We can imagine the new test should fail if it takes too many time.

@juherr Agreed.
Unfortunately, @benlamonica says that he can't work on this any more so it's up to us to follow up or close this, and I agree with you that I wouldn't feel comfortable merging this until we can run some numbers and prove that it improves performance significantly.

@cbeust I looked further and the test case is interesting. It showed me that it has many problems but I don't know how to fix them for the moment.
I suppose it will involve many deep changes.
For the current PR, I've no idea what to do. We just know it doesn't broke something (for the moment) and it helps @benlamonica. But it is clear we should keep #772 open.


TypeError: write() argument 1 must be unicode, not str

Hi,
I'm using python 2.7 and I got error like  TypeError: write() argument 1 must be unicode, not str while trying to install pandas profiling using pip.
I have also tried to install from source code. again same error getting.
Please help me to install this on top of python 2.7.

Thanks in Advance

You need python 3 to run pandas_profiling.
If you are interested why, please read https://python3statement.org/.

Thanks buddy!


add handicap support to minigui

Quick recap:  as we walk the AST, we transform it into Sgf::Node with our own Move structs, etc.
This CL changes "GetTreeImpl" to look for a HA property, and if so, it adds Nodes for black to play handicap stones and white to pass.
The resulting tree of nodes is handled as before:  the engine calls PlayMove on each.

see warnings in docstring:
https://github.com/brilee/MuGo/blob/master/sgf_wrapper.py#L5

@brilee right now, our sgf parser literally ignores any SGF property on a node that isn't B[] or W[].  the HA property requires that another property be set on the node ('AB') specifying the actual location of the handicap stones.
So yeah your warning in the docstring is understood :)  This PR doesn't add support for positions with existing stones, it just adjusts the semantics of our translation from "SGF Tree" => "Minigo Tree"

fixes #845


Add pre-commit package and config.

Runs testing and linting on commit to prevent me from pushing bad code to repo.

Coverage remained the same at 37.45% when pulling 1e93f5f7c93a2ff5caecc75a73742d0b6b741718 on rjstires:precommit-hook into 2462a24ecbc1f798133738708cc87e2172680a06 on linode:develop.

Coverage remained the same at 37.45% when pulling 971e949450676d528e77fc6b712e0448d30811ba on rjstires:precommit-hook into 2462a24ecbc1f798133738708cc87e2172680a06 on linode:develop.


[BUG] Conflict with Tasks plugin

Hello, thank you for your theme, i love the way you customed Everforest plugin to make it smoother.
Just a message to tell you that it seems that there is a bug with the Tasks plugin.
With the plugin Tasks, you can create a task, put a tag (selected on the settings of the plugin), and then a pop window appears with the auto-suggest.
The problem is that when we try to do it while using Evereforest Enchanted, the pop-up do not appear most of the case, and sometimes it is visible but not at the right time !
I tried every updates of obsidian, update the plugin tasks, update the installer of obsidian and update you theme, but impossible to fix it.
This do not happend when we use other themes.
This do not happend on the note that already as tasks where the auto-suggest already worked.
But when we create a new note and a new task on this note, the bug is there.
I Don't know if i can do something else to help you, but i show you some screenshots.
Thank you again for your work and by.
Tasks auto suggest is working

Tasks auto suggest is not working (new note)

Tasks auto suggest working (other theme)

auto suggest appears randomly on the settings

Should be fixed as of version 3.11.3, though I didn't test the random popups in settings.
https://github.com/FireIsGood/obsidian-everforest-enchanted/assets/109556932/db718245-18a6-44d8-9f88-64b344e60661
Once you have confirmed that this fixes the issue on your end, please close this issue. If the random popups still continue, try and find a consistent setup to get them to appear and I will try and fix it again.

It works !
Thank you very much for your help, so cool !


Error encountered during depth order prediction training.

Dear Authors,
Thanks for the great work, and congratulations on getting accepted by CVPR!
I tried to train the VCoder model for depth order prediction by running bash scripts/vcoder_ds_train.sh. However, I encountered the following error.
Traceback (most recent call last):
  File "/g/data/kf09/xl9783/Code/VCoder/vcoder_llava/train/vcoder_ds_train_mem.py", line 15, in <module>
    vcoder_ds_train()
  File "/g/data/kf09/xl9783/Code/VCoder/vcoder_llava/train/vcoder_ds_train.py", line 1114, in vcoder_ds_train
    trainer.train()
  File "/home/135/xl9783/miniconda3/envs/vcoder/lib/python3.10/site-packages/transformers/trainer.py", line 1539, in train
    return inner_training_loop(
  File "/home/135/xl9783/miniconda3/envs/vcoder/lib/python3.10/site-packages/transformers/trainer.py", line 1624, in _inner_training_loop
    self.optimizer, self.lr_scheduler = deepspeed_init(self, num_training_steps=max_steps)
  File "/home/135/xl9783/miniconda3/envs/vcoder/lib/python3.10/site-packages/transformers/deepspeed.py", line 361, in deepspeed_init
    optimizer, lr_scheduler = deepspeed_optim_sched(
  File "/home/135/xl9783/miniconda3/envs/vcoder/lib/python3.10/site-packages/transformers/deepspeed.py", line 298, in deepspeed_optim_sched
    optimizer = trainer.create_optimizer()
  File "/g/data/kf09/xl9783/Code/VCoder/vcoder_llava/train/vcoder_ds_llava_trainer.py", line 163, in create_optimizer
    if self.args.depth_mm_projector_lr is not None:
AttributeError: 'TrainingArguments' object has no attribute 'depth_mm_projector_lr'

It seems that the depth_mm_projector_lr attribute is not provided in the shell script. May I ask for some suggestions on how to fix it?
Best,
Xingjian

Hi @xingjianleng, Thanks for your interest and for bringing this to our attention! It seems that I forgot to remove a redundant part of the code while doing the cleanup. I have pushed a fix, and it should be working now. Feel free to ask any other questions.

Hi @praeclarumjj3, thanks for fixing it! I'm closing this issue now.


ARROW-7299: [GLib] Use Result instead of Status

This change suppress deprecated warnings related to Result and Status.
--enable-development-mode and -Ddevelopment_mode=true are added to
build with -Werror.

+1


Improve the backoffice Marketplace dataset in OC

This will update the yaml seed file that is used when initializing the repository.

The new marketplace is available on the confluence link provided in teams


Addtupleteststoportable47

Now that we have a tuple dll that supports portable47, enable the tuple tests in core unit tests for the profile47 version of fsharp.core.dll

Looks good


Some Minor Grammatical Changes

Trying to make Cachet look prettier one capital and full stop at a time!

Thanks buddy! :+1:


Always show PowerToys Run on desktop

Provide a description of the new feature / enhancement
There is option to always show the PowerToys Run on desktop

tracked in https://github.com/microsoft/PowerToys/issues/5095


Incorrect Step 6 Information

Step 6 and beyond needs to be updated for the changes that have been made when creating a search. For example, you can now select "Locations On Hold" but there's no definition article elaborating on what it means.

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

ID: edf6054e-d069-a63c-8b7a-7dbbe98f0748
Version Independent ID: e9344a15-d168-67e2-925a-004d7e7b187d
Content: Search for content in a eDiscovery (Standard) case - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/search-for-content-in-core-ediscovery.md
Service: o365-seccomp
GitHub Login: @v-tophillips
Microsoft Alias: v-tophillips

@msbemba

@msbemba Please comment. thanks

@wege4rt34 Thank you for your feedback. I was not able to find locations on hold in an eDiscovery standard case. however, it is available in premium and more information can be found here -https://docs.microsoft.com/en-us/microsoft-365/compliance/managing-holds?view=o365-worldwide
Hope this helps!
Thanks
Sri

@yogkumgit This can be closed.


Stop New Site Creation

I have migrated a solution built on Piranha CMS to a new VS install.  Now when I start it up it kicks me over to the install a new site in management area.   I remember this being an issue with not seeing the existing db.  I know my db path and credentials are correct.  I updated the connection string.  What am I wrong on?? Is there something else that will cause this scenario??  Is there another path issue???  Cant seem to find any documentation for this.  Thx

Hmm, haven't seen this before, the only problems I'm aware of from earlier issues is that Entity Framework has tried to create the database when it should in fact be created by the internal SQL scripts. What database are you using?
Regards

It is SQL and it was an existing site db.
I did get the problem resolved.
The db shows in SQL but  something got hosed in the data when I migrated the db.
I deleted and restored again and it fired up.
The issue had nothing to do with  Piranha.
Thx for the follow-up
Glenn

From: Håkan Edling<EMAIL_ADDRESS>Sent: Wednesday, April 5, 2017 5:29:30 AM
To: PiranhaCMS/Piranha
Cc: Glenn Erler; Author
Subject: Re: [PiranhaCMS/Piranha] Stop New Site Creation (#544)
Hmm, haven't seen this before, the only problems I'm aware of from earlier issues is that Entity Framework has tried to create the database when it should in fact be created by the internal SQL scripts. What database are you using?
Regards
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/PiranhaCMS/Piranha/issues/544#issuecomment-291846191, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACsXhwsSdl3tvitbICq3mdyDzXtLfIsjks5rs4kqgaJpZM4Mv9zE.


Fix build directory structure to use index.html for each route

Change the build structure to make the page URL appear as '/about' instead of '/about.html'. Structured like
├── /about/
│   ├── /index.html
├── /blog/
│   ├── /post-one/
│   │   ├── /index.html
│   ├── /post-two/
│   │   ├── /index.html
│   ├── /index.html
├── /404/
│   ├── /index.html
├── /500/
│   ├── /index.html
├── /index.html

I guess this is needed to make the files structure to be compatible with Amazon S3? I guess it doesn't yet support requesting HTML pages without .html part. If so, that might be a good fix!

More pulling on my experience with Jekyll. Seems to make sense to me.

Why add the complexity of making it configurable? This should work in GitHub Pages as well as any other webserver.
What about other static generators? I've really only used Jekyll, which is fully supported by GitHub and GitHub Pages. Jekyll goes the way of using lots of folders and index.html.

@TeeKz oh, good to know. Maybe you right and it's better to generate a folder for each index.html page to make the site work on all platforms.


Implement dynamic server endpoints (#50)

@lgrahl @sillych what do you think?
Fixes #50.

Note: I chose not to throw any exceptions in the getXxx methods. Operations that might throw should be done in the constructor or outside the class.


Welcome Message Limits

Is there a way to limit the Welcome message being sent to only new members who have a specific role in a specific channel?
The use case is new members joining a public channel who automatically get the role "Guest". I don't want to spam "Members" who also join the public channel.

Possible sure but I don't really see what the issue is. It should only be sending the message once on server connect and never again.


Check if genesis block is already in the database before inserting it.

We should check if storage already contains a genesis block, and compare it's hash with the one retrieved from the genesis.json to decide if we should create a new one, update current, or leave it untouched.

Is this still open?


The 'Application' option is always selected when switching the options on the left side of the Settings panel

Storage Explorer Version: 1.27.0-dev
Build Number: 20221111.1
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Ventura 13.0 (Apple M1 Pro)
Architecture: ia32/x64
How Found: From running test cases
Regression From: Previous release (1.26.1)
Steps to Reproduce

Launch Storage Explorer.
Open 'Settings' -> Click 'Data Explorers'.
Observe the options on the left side of the Settings panel.
Check whether the 'Data Explorers' option is selected.

Expected Experience
The 'Data Explorers' option is selected.

Actual Experience
The 'Application' option is selected.

I noticed this was happening before the search feature was added. There doesn't appear to be any code to handle the change.
@JasoneYeMSFT Can you look into it?

Verified this issue on the build main 20221113.2. Fixed. So, we are going to close it.


vaginadepth

Proposal:
Proposal written by -(•-•)-
Is it a proposal for the website or for the bot?: bot
What is the title of your proposal?: vaginadepth
Explain your proposal more accurately (It's best to give as much information as possible, so that we can implement the proposal better): A female version of ?penissize
Why should we add this feature?: To secure our GitHub project from the SJWs (Nadeko lol)
ReportID: 196

➤ LenoxBot commented:
Approve:
for all genders
Nickkel#6515

➤ LenoxBot commented:
Approve:
agree with nickkel
SaVaGeCrEePeR28 | Furkan#3532

➤ LenoxBot commented:
Deny:
why, but ok
Denarioyt#3352

➤ LenoxBot commented:
Approve:
agree with Nickkel and Furkan
Profxy#5396


fix(onyx-736): refetch pills and artworks when navigating to alerts View Artworks screen

This PR resolves ONYX-736
Description
In before video, when I add/remove pills and go back to the previous screen - neither artworks grid or pills are updated. This PR makes the View Artworks screen to forcefully refetch data to reflect changes.

Before
After

PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[x] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates
#nochangelog
Need help with something? Have a look at our docs, or get in touch with us.

Warnings

:warning:

✅ No changelog changes

  Generated by :no_entry_sign: dangerJS against d56286d30c5ee27d1b97436550cda58b4d719797


Add the tests for the Node class and apply PEP8 on minor files.

Types are now on the Visualgo-PyPi repository so I am closing this merge request, the changes should be moved to the new repo.


conditionally require wait_port

Require wait_port only when it is needed.

👍
But what's the motivation for this?

Just a code clean up.  Bring in wait_port only when it's being used.


Document API resource properties

Docs: https://www.balena.io/docs/reference/api/
For example: what does should_be_running_release on device mean?
This is the kind of information that the API documentation should include to avoid confusion and support tickets. We should document each API request with properties, examples, or if there are any caveats or edge cases customers should know about.
FD thread: https://www.flowdock.com/app/rulemotion/i-docs/threads/3uohhegEJXWp88JFasKDv-Bld-A
@dt-rush @alisondavis17 :eyes:

Will prepare a draft and share

Closing #1485 in favor of #1496


Creating your own protocols

I've looked through previous issues and saw this has been mentioned before, but even with that pull request i struggle with creating my own protocols.
How am i supposed to do this? I see there's a guide under the contributing file, but doesn't seem to have any useful information outside of what i know already. Has there been any more work towards exposing the correct stuff?

Hello. Are you referring to creating your own novel protocol, or providing a Rust wrapper for an existing UEFI protocol? If so, which protocol are you interested in implementing?

I was referring to providing a rust wrapper for an existing uefi protocol.
My goal is to implement pxe protocols from the efi crate (to get networking) which from what i'm seeing is abandoned which is why i chose to use this crate

I don't know if there's a very well documented process, since this is mostly reverse engineering the UEFI spec :sweat_smile:
The steps I'd follow are:

Pick a protocol

Define it

#[repr(C)]
#[unsafe_guid("A19832B9-...")]
#[derive(Protocol)]
pub struct SimpleNetworkProtocol {
    revision: u64,
    // ...
}

Define the function prototypes and wrap them. You can find some example functions in the SimpleTextOutputProtocol

You can define as many functions/types as required, based on what you're trying to do in your code.

This much i understood (and had already done) but i'm getting issues with defining the actual struct.
error[E0433]: failed to resolve: unresolved import
  --> src\main.rs:57:10
   |
57 | #[derive(Protocol)]
   |          ^^^^^^^^
   |          |
   |          unresolved import
   |          help: a similar path exists: `uefi::proto`

I think i'm including the right things, i've been messing around with it for a while now without any results.
This is probably something im doing wrong, so any help is appreciated.

Are you trying to define the Protocol in your binary? You might have to add the uefi-macros crate as a dependency to get the required derive.
The easier/recommended alternative is to fork the crate, add the protocols directly to uefi-rs, and then submit a PR with the changes :)

I tried adding uefi-macros without much success (same errors)
i was doing it like this for testing anyways, forking and making a PR should be easier.


chore: bdd-gh-1583239334 to 0.0.1

chore: Promote bdd-gh-1583239334 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


There are too many never used components in the default build

Original issue: https://charm.cs.illinois.edu/redmine/issues/419

This is a problem you really notice if you build on arm7, but it is generally poor practice to keep so much cruft in the default setup.
A example would be the 15 Grid*LB files, but I'm quite certain that a lot of other dead code lurks in the load balancers and elsewhere.  We should get rid of this stuff for 6.7.0

Original author: Harshitha Menon
Original date: 2014-02-17 21:09:50

The LBs that are most likely to be used and covering centralized, distributed and hierarchical schemes.

Sifting through the morass of accumulated load balancers for the few that are used regularly was only the beginning.
An intermediate version of building only a few balancers, now CommonLB, made it more awkward to build the more obscure LBs. That led to a clear desire for having a way to cleanly build only MetisLB, or ScotchLB (or xxxxLB).  Implementing that revealed a 3 year old hack.  That hack created empty scotch and metis headers for the sake of fooling make dependency checking when scotch and/or metis weren't available.  That turned out to be necessary only because our source files are using #include "metis.h" when they should be using #include <metis.h> to rely on searching include paths for headers falling outside our immediate source tree.  Using angle brackets there allows gcc -MM to do the right thing for such cases.


[golang] "The current node is already splitted" when attempting to split a multiline statement

Split stopped working for multiline statements. e.g.
func New(param1 string, param2 int,
param3 bool) { ... }

var t := Some{ fieldA: "",
fieldB: 0}

This was working before https://github.com/Wansmer/treesj/commit/ecc658432129a23abb5b58e6f59b8bcfb9a961a4
Would it be possible to restore it?
This functionality is extremely helpful when dealing with bad formatted code (multiline).

This functionality is extremely helpful when dealing with bad formatted code (multiline).

treesj is not a formatter, maybe better to use built-in lsp formatter to format code? :-)

Would it be possible to restore it?

I don't want to restore it, but maybe later I will add an option to manage this behavior.


@after-leave error in

Vue version
3.3.6
Link to minimal reproduction
https://job.denall.com/
Steps to reproduce
We are using 0.14.10 of bootstrap-vue-next.
https://github.com/bootstrap-vue-next/bootstrap-vue-next/blob/main/packages/bootstrap-vue-next/src/components/BModal/BModal.vue
BModal receives the value of visible through v-model and uses it in v-show.
HTML with v-show applied is wrapped in .
However, often when the v-show value becomes false, the function of @leave is executed in BModal, but since the event does not occur until @after-leave, the function is not executed, causing problems in our service.
In our service A BModal show -> B BModal show -> A BModal hide -> A BModal show -> B BModal hide -> B BModal show ...
If you use it repeatedly like this, you will face the above problem.
What is expected?
In the above case, you want to be guaranteed that @after-leave is called.
What is actually happening?
Sometimes @after-leave is called and sometimes it is not.
System Info
No response
Any additional comments?
No response

Both the Vue and bootstrap-vue-next versions are outdated.
The bug might have been fixed in the latest versions. So please upgrade your dependencies and see if it persists.
Besides, this is far from a minimal reproduction. It is almost impossible for us to hunt a bug in a production website. Next time, please try to create a minimal reproduction repo using the SFC Playground or StackBlitz.


Drop physical railways from transit.

Drop physical railways from transit layer. Merge geometry of remaining rail services / lines.
Connects to #501.
@rmarianski could you review, please?

:+1:


Setup configuration file for cplex.opt

With the new release of message_ix, the options for cplex specified in cplex.opt have been relocated to core.py.  Nevertheless, an issue that remains is that the standard cplex options specified may not be ideal (e.g. lpmethod 4 should be generally used for the IIASA global model as opposed to the standard lpmethod 2).  If the preferred option though needs to be either specified every time when calling solve() it may be more intuitive to have a config file for cplex.opt similar to the default_propoerties file, which is not part of the repository but is read prior to using the default options specified in core.py.  This would avoid:
a. having excess/repetitive code in the solve statement.
b. enable ensuring that tests are always executed using the defaults as opposed to the personal configuration, as lpmethod 4 results in some tests failing.
c. implement a standardized scheme across message_ix, where functions which can be called over the command line interface first take arguments, then look for a configuration file and lastly apply defaults.
d. avoid having to make changes to core.py to set the default solving options to ones personal preferences.

Closed by #557.
For those coming back here later:

similar to the default_properties file

The use of separate properties files (for JDBCBackend config) has been deprecated, and this info is now read through the single user configuration file, or set at runtime.

ensuring that tests are always executed using the defaults as opposed to the personal configuration

This is done in the test suite via the tmp_env fixture (which predates this issue; see iiasa/ixmp#137).

implement a standard scheme…

This is described at ‘Configuration’ in the ixmp docs. To paraphrase, by setting IXMP_DATA=/foo/bar message-ix command …, one can point to a directory containing a different ixmp config.json file, in which the abovementioned settings can differ.


ElasticSearch and kibana not working as expected

I have cloned the repository.  executed the commands as per the instruction given. But elasticsearch is not started in the port 5200. It leads to an error in the kibana.. Please suggest any solution.

Closing this due to inactivity, but feel free to reopen if you're still having issues.


Implement Semver Versioning

Problem
Currently, there is no consistent tagging strategy implemented. we use pipeline-based build tags for docker image tagging.
Suggestion:
Use coco-gito.
Acceptance Criteria

Use semver version for building and publishing docker images in GitHub Action Pipeline
Only publish/push images when version has been bumped and on main branch
Publish github release after all the changes are tested

Checklist

[x] Use semver version for building and publishing docker images in GitHub Action Pipeline
[x] Only publish/push images when version has been bumped on main branch with dryrun option
[ ] Publish github release after all the changes are tested

The cog bump action is not returning any value even though version has been bumped to v0.1.1
https://github.com/abhisheksr01/spring-boot-microservice-best-practices/actions/runs/12498446613/job/34872417237
check docker-build-push job

We have implemented cog based automated releases in GitHub Action with manual approval.
Hence closing this Issue as complete.
Link to releases: https://github.com/abhisheksr01/spring-boot-microservice-best-practices/releases


Integrate cookiecutter

https://github.com/cookiecutter/cookiecutter

Added script for ez setup - cookiecutte or copier may be not needed

https://github.com/copier-org/copier


Docker: Multi-arch & cross-compile build with docker buildx

Note that this PR adds functionality that currently already exists in images/
to the main Dockerfiles.
Add support for Docker BuildX multi-arch builds for arm64 and amd64 to
Cilium runtime, builder, and release images. Add Go cross-compilation
support to Cilium release images to make the arm64 builds faster on
amd64 hosts.
If both DOCKER_BUILDKIT=1 and DOCKER_BUILDX=1 are defined, the
makefiles create a cross-compilation builder instance ('cross') and
switch buildx to use it.
Images depend on each other, so the images normally should be built in
a specific order.

Export variables

$ export DOCKER_BUILDKIT=1
$ export DOCKER_BUILDX=1
$ export DOCKER_REGISTRY=docker.io
$ export DOCKER_DEV_ACCOUNT=your-account

Runtime

$ make docker-image-runtime
$ docker buildx imagetools inspect ${DOCKER_REGISTRY}/${DOCKER_DEV_ACCOUNT}/cilium-runtime:2020-11-30
Then update the runtime image references in other Dockerfiles

Builder

$ make docker-image-builder
$ docker buildx imagetools inspect ${DOCKER_REGISTRY}/${DOCKER_DEV_ACCOUNT}/cilium-builder:2020-12-01
Update the main Cilium Dockerfile with the new builder reference

Hubble

Hubble builds via buildx QEMU integration, unless you have an ARM machine added to your buildx builder.

Check out hubble branch pr/jrajahalme/docker-buildx-support

$ export IMAGE_REPOSITORY=${DOCKER_REGISTRY}/${DOCKER_DEV_ACCOUNT}
$ IMAGE_TAG=v0.7.1x CONTAINER_ENGINE="docker buildx" DOCKER_FLAGS="--push --platform=linux/arm64,linux/amd64" make image
$ docker buildx imagetools inspect ${IMAGE_REPOSITORY}/hubble:v0.7.1x
Update the main Cilium Dockerfile with the new Hubble reference

Cilium release images

Cilium Dockerfiles are modified for cross-compilation based on the multi-arch support in the Cilium builder image:
$ make docker-images-all

test-me-please

This PR includes the 3 commits from #14207, as Cilium needs the Envoy image.

docker.io/jrajahalme/ is on used for testing only, will edit out from the PR.

test-me-please

Tests passed with test builds of runtime and builder, now removed the last commit to not impose un-official builds.

test-me-please

test-me-please

Rebased, added developer docs, and made the Makefile.buildkit a bit nicer by transforming info shell hacks into a builder-info target. The cross builder is still configured via shell function.
The docs depend on this trivial Hubble PR merging: https://github.com/cilium/hubble/pull/456

test-me-please

test-me-please

retest-gke

retest-4.9

Rebased and addressed review comments.

test-me-please

But then I also noticed that this PR changes the Dockerfile.builder but those changes are not being consumed by the main docker image build yet because there's no change to the main dockerfile to use a newer version of the builder image that would be generated by these code changes. So I think we need to generate images based on these latest changes and then add another change on top to integrate the use of those new builder images into the main dockerfiles.

These changes allow multi-arch builds for the builder and runtime. After this PR is merged we should make a decision to build the builder and runtime for both arm64 and amd64. I can't say if that can be easily automated yet, though, so it needs to be a separate discussion.

test-me-please

retest-gke

retest-gke

test-me-please

test-me-please

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke

retest-gke


RC-2852-change-sitekey

Changed sitekey in turtstile.py

The url was also changed to https://2captcha.com/demo/cloudflare-turnstile


⚠ Bofrost.lu has degraded performance

In 95a920a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1369 ms

Resolved: Bofrost.lu performance has improved in 2a54142 after 6 minutes.


raspi-serial v6 is out: please update

Current raspi-io does not build on NodeJS 13 but it does on LTS 12.
The reason is that raspi-serial used serialport v7, which doesn't build on NodeJS 13:
https://github.com/nebrius/raspi-serial/issues/10
It would be nice to update raspi-serial to v6, which uses latest serialport, which builds just fine on NodeJS 13.
I might file a MR instead, but I wanted to touch base first.
The platform I am using/testing is ArchLinux ARM, either 32bit or 64bit.

D'oh, I new I was forgetting something! Thanks for the heads up. I just published v11 of raspi-io with the update.

will double check once I can verify all is good with NodeJS 13, and re-open if needed.
meanwhile ... thanks a lot 👍


CCHMapClusterAnnotation is wrapped by the unified framework and thus loose information.

When using a CCHMapClusterController and adding MKAnnotation objects, the controller creates clustered annotation which are then wrapped by the framework into MKAnnotationWrapper objects.
This causes a loss of information since only the Title and Subtitle properties of the annotation are preserved (CCHMapClusterAnnotation.Annotations set is lost).

Currently working on it, waiting for Xamarin team to respond in their forums : http://forums.xamarin.com/discussion/31625/binding-objective-c-mkannotation-with-unified-api.

Requesting for help in bugzilla : https://bugzilla.xamarin.com/show_bug.cgi?id=26416

One workaround consists of using the runtime to get the underlying wrapped object, like the following :
public override MKAnnotationView GetViewForAnnotation(MKMapView mapView, IMKAnnotation annotation)
{
    var customAnnotation = ObjCRuntime.Runtime.GetNSObject(annotation.Handle) as ACustomAnnotation;
}