Bootstrap files-set for new Projects

Create a maven archetype that extends the Adobe multi-module maven archetype but includes core organization and place holders.
Intermediary solution: a zip of the augmenting files to unzipped over a new multi-mod project.
Key elements:

skeleton component (copy down to create new components; promotes a common impl structure)
common osgi configs xmls
component organization

content/pages
global.jsp
base components
other examples XML of various common nodes. Templates, widgets, etc.

Closed via https://github.com/Adobe-Consulting-Services/lazybones-aem-templates


Add sccache

Tool name
sccache
Tool license
Apache License 2.0
Add or update?

[X] Add
[ ] Update

Desired version
v0.3.0
Approximate size
12MB
Brief description of tool
sccache is a ccache-like compiler caching tool. It is used as a compiler wrapper and avoids compilation when possible, storing cached results either on local disk or in one of several cloud storage backends.
sccache is a popular tool for caching. Given its use for caching in Rust projects it is helpful to have it preinstalled so that a GitHub Actions run can utilize the cache for all Rust components and to remove the need to install any dependencies from scratch.
URL for tool's homepage
https://github.com/mozilla/sccache
Provide a basic test case to validate the tool's functionality.
sccache rustc <(echo 'pub fn main() {}') -o main && ./main

Platforms where you need the tool

[ ] Azure DevOps
[X] GitHub Actions

Virtual environments where you need the tool

[ ] Ubuntu 18.04
[X] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[X] macOS 12
[ ] Windows Server 2019
[X] Windows Server 2022

Can this tool be installed during the build?
cargo install --locked sccache

Tool installation time in runtime
28 seconds
Are you willing to submit a PR?
Yes!

I have submitted a PR adding sccache: https://github.com/stellar/actions/pull/22.

Close as https://github.com/actions/runner-images/pull/1600

@al-cheb I note that the reasons for not including sccache was the 9 minute build time and the fact it is installed from source. In my tests install including compile takes 28 seconds, not 9 minutes. Would it be accepted if I change the PR to install the prereleased binary? This would also make it much faster.

This would be really useful, especially since the latest version of sccache now supports using the GitHub Actions cache out of the box.


Compatibility with windows ARM

Hello,
At the University of Paris 01, we discovered that geteduroam was not compatible with ARM windows. Is a solution on the way?

There's an ARM version of the application, both x86_64 and arm64 versions are available on the Releases page.


I had some problems when I used docker

docker logs <container_id>
tar: themes/casper: Cannot utime: Operation not permitted
tar: Exiting with failure status due to previous errors

and my host is win10

Looks like an incompatibility of sorts with Windows
https://github.com/docker-library/ghost/issues/69#issuecomment-319946646
https://forum.ghost.org/t/docker-containers-using-windows-lcow-not-linux-containers-on-windows/4211
LCOW has some issues with bindmounting to Linux containers
https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/linux-containers#bind-mounts
If you have further questions you could try asking the Docker Community Forums, the Docker Community Slack, or Stack Overflow. Since these repositories are for issues with the image and not necessarily for questions of usability


Delete all listings for user upon user deactivation

Also delete images and shipping options.

https://github.com/yzernik/squeakroad/pull/514


Automate deployments to Google Chrome Store

See https://circleci.com/blog/continuously-deploy-a-chrome-extension/


Document Substrate's Nonce Behaviour

Substrate is unusual from other blockchains because an account nonce can be reset if, for
example, an account's balance drops below the existential deposit for the Substrate chain
it's on.
In other blockchain ecosystems this is not the case, so an account nonce is typically
used to provide replay protection. In Substrate this is done through the use of
transaction mortality.
Since smart contract developers will be coming from different ecosystems we should
document this behaviour for them, and have some possible mitigation.
Here are some resources to help get these docs started:

Original Substrate issue
Discussion about UX improvements
Polkadot transaction mortality docs

Is this mostly addressed by https://github.com/paritytech/polkadot-sdk/pull/4034 ?


Week 5 Check-In (2/2): 1 user story per person, 1 group demo

[ ] Victor
[ ] Ashray
[ ] Brandon
[ ] Jason
[ ] Lucas
[ ] Alexi
[ ] Group demo

What kind of router does Kyle have?


Adds sciond request for segments used to construct paths

Adds ability to request detailed segment data after get_paths
succeeds.
Returns requested segments data (core, up, down).
Requested segment data can be used to calculate core ASes in paths.
Requested segment data can be used to calculate path types.
Useful for visualizations to display core and path types for every AS
routed through.
Closes #1299.

This change is

Reviewed 7 of 7 files at r1.
Review status: all files reviewed at latest revision, 9 unresolved discussions, some commit checks failed.

proto/sciond.capnp, line 23 at r1 (raw file):

        serviceInfoReply @10 :ServiceInfoReply;
        revReply @11 :RevReply;
        segmentRequest @12 :SegmentRequest;

I'm not thrilled with the naming here. To me, this name implies you tell sciond you want segments from A to B, whereas this asks sciond for all segments of a given type. segTypeReq/segTypeReply maybe?

proto/sciond.capnp, line 125 at r1 (raw file):

struct SegmentRequest {
    segmentType @0 :PSeg.PathSegType;

"type" would sufficient, as the context is already clear.

proto/sciond.capnp, line 129 at r1 (raw file):

struct SegmentReply {
    entries @0 :List(SegmentReplyEntry);

Why not simply :List(PSeg.PathSegment)?

python/lib/sciond_api/segment_req.py, line 1 at r1 (raw file):

# Copyright 2017 ETH Zurich

2018

python/lib/sciond_api/segment_req.py, line 31 at r1 (raw file):

    @classmethod
    def from_values(cls, seg_type=None):

This is not an optional argument, there's no sane default. And this will cause an exception if the arg isn't supplied.

python/lib/sciond_api/segment_req.py, line 33 at r1 (raw file):

    def from_values(cls, seg_type=None):
        p = cls.P_CLS.new_message()
        p.segmentType = seg_type

p = cls.P_CLS.new_message(segmentType=seg_type)

python/lib/sciond_api/segment_req.py, line 39 at r1 (raw file):

        desc = ["%s:" % self.NAME]
        desc.append("  segmentType: %s" % self.p.segmentType)
        return "\n".join(desc)

This is a very simple request, with no repeating fields, so this can just be
return "%s: type: %s" % (self.NAME, self.p.segmentType)

python/sciond/sciond.py, line 378 at r1 (raw file):

            db = self.up_segments
        elif segmentType == PST.DOWN:
            db = self.down_segments

This should log an error if the segmentType is anything else.

python/sciond/sciond.py, line 382 at r1 (raw file):

        total_segs = len(self.core_segments) + \
            len(self.up_segments) + len(self.down_segments)
        assert total_segs != 0, 'No segments found, did you call get_paths() first?'

This is a bad idea - if sciond had just restarted, for example, this will kill it. There's no need to check for this case. The response will just have no entries in it. That's perfectly legal.

Comments from Reviewable

Always put a blank line in the git commit after the description, otherwise git will do things like:
* pubpr/1383        7b0588e [pubup/pubpr/1383] Adds sciond request for segments used to construct paths - Adds ability to request detailed segment data after get_paths succeeds. - Returns requested segments data (core, up, down). - Requested segment data can be used to calculate core ASes in paths. - Requested segment data can be used to calculate path types. - Useful for visualizations to display core and path types for every AS routed through. - Closes #1299.

Review status: all files reviewed at latest revision, 9 unresolved discussions, some commit checks failed.

Comments from Reviewable

Updated original commit message.

Review status: 0 of 7 files reviewed at latest revision, 9 unresolved discussions, some commit checks failed.

proto/sciond.capnp, line 23 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
I'm not thrilled with the naming here. To me, this name implies you tell sciond you want segments from A to B, whereas this asks sciond for all segments of a given type. segTypeReq/segTypeReply maybe?

Good point. Better to not confuse with other messaging in our protocols. I like your suggestion. I've propagated that naming throughout.

proto/sciond.capnp, line 125 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
"type" would sufficient, as the context is already clear.

Done.

proto/sciond.capnp, line 129 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
Why not simply :List(PSeg.PathSegment)?

True. I've removed SegmentReplyEntry.

python/lib/sciond_api/segment_req.py, line 1 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
2018

Done.

python/lib/sciond_api/segment_req.py, line 31 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This is not an optional argument, there's no sane default. And this will cause an exception if the arg isn't supplied.

Yep. Removed default.

python/lib/sciond_api/segment_req.py, line 33 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
p = cls.P_CLS.new_message(segmentType=seg_type)

Done.

python/lib/sciond_api/segment_req.py, line 39 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This is a very simple request, with no repeating fields, so this can just be
return "%s: type: %s" % (self.NAME, self.p.segmentType)

Done.

python/sciond/sciond.py, line 378 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This should log an error if the segmentType is anything else.

Done.

python/sciond/sciond.py, line 382 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This is a bad idea - if sciond had just restarted, for example, this will kill it. There's no need to check for this case. The response will just have no entries in it. That's perfectly legal.

Done.

Comments from Reviewable

Reviewed 7 of 7 files at r2.
Review status: all files reviewed at latest revision, 6 unresolved discussions, some commit checks failed.

python/lib/app/sciond.py, line 205 at r2 (raw file):

        return self._resolve_dst_addr(spkt.addrs.src, spkt.addrs.dst)

    def get_segments(self, seg_type):

This should be renamed, too. get_type_segs?

python/lib/app/sciond.py, line 420 at r2 (raw file):

    :param seg_type: The type of PathSegmentType requested.
    :returns: List of SCIONDSegTypeReplyEntry objects.

This is a list of PathSegments now.

python/lib/sciond_api/segment_req.py, line 45 at r2 (raw file):

    @classmethod
    def from_values(cls, entries):
        p = cls.P_CLS.new_message(entries=entries)

I don't think this works (or if it does, what exactly the result is :). The previous code was correct (using p.init etc).

python/lib/sciond_api/segment_req.py, line 49 at r2 (raw file):

    def entry(self, idx):
        return self.p.entries[idx]

This should return PathSegments, not raw capnp objects. Same for iter_entries.

python/sciond/sciond.py, line 379 at r2 (raw file):

            db = self.down_segments
        else:
            logging.error("Requesting segment type %s unrecognized.\n%s" % segmentType)

This has a trailing \n%s, that will cause a run-time error.

python/sciond/sciond.py, line 384 at r2 (raw file):

        for segment in db(full=True):
            seg_entries.append(segment.p)
        seg_reply = SCIONDMsg(SCIONDSegTypeReply.from_values(seg_entries), pld.id)

Hmm. One thing to consider here is that you can run out of space pretty quickly. The max message size is ~65k. A sciond that has a lot of segments could easily exceed this, with segments ranging from maybe 750B to 10KB. This makes this API only really usable in a controlled/test environment, which in turn raises the question of whether it's a good idea to put this into the main codebase. I'm leaning towards no.

Comments from Reviewable

Review status: 2 of 7 files reviewed at latest revision, 6 unresolved discussions, some commit checks failed.

python/lib/app/sciond.py, line 205 at r2 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This should be renamed, too. get_type_segs?

Done.

python/lib/app/sciond.py, line 420 at r2 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This is a list of PathSegments now.

Reverted to list of SCIONDSegTypeReplyEntry

python/lib/sciond_api/segment_req.py, line 45 at r2 (raw file):
Previously, kormat (Stephen Shirley) wrote…
I don't think this works (or if it does, what exactly the result is :). The previous code was correct (using p.init etc).

Reverted to list of SCIONDSegTypeReplyEntry and restored. :-)

python/lib/sciond_api/segment_req.py, line 49 at r2 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This should return PathSegments, not raw capnp objects. Same for iter_entries.

Reverted to list of SCIONDSegTypeReplyEntry

python/sciond/sciond.py, line 379 at r2 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This has a trailing \n%s, that will cause a run-time error.

Done.

python/sciond/sciond.py, line 384 at r2 (raw file):
Previously, kormat (Stephen Shirley) wrote…
Hmm. One thing to consider here is that you can run out of space pretty quickly. The max message size is ~65k. A sciond that has a lot of segments could easily exceed this, with segments ranging from maybe 750B to 10KB. This makes this API only really usable in a controlled/test environment, which in turn raises the question of whether it's a good idea to put this into the main codebase. I'm leaning towards no.

I'd like to make this useful and at least come under the size get_paths() currently returns. So in general, I've reverted the reply from a list of PathSegment back to a list of SCIONDSegTypeReplyEntry with modifications. The return objects should contain the minimum data we need, including timestamps and all interfaces, rather than the larger PathSegment which included a number of sub-objects not currently needed.

Comments from Reviewable

Reviewed 5 of 5 files at r3.
Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

proto/sciond.capnp, line 124 at r3 (raw file):

}

struct SegTypeReq {

So, now we're back to a naming issue :) This no longer requests segments. My best suggestion right now is SegTypeHopReq - how does that sound?
Relatedly, one thing that comes to mind is that we're planning to rewrite sciond in the ~near future, in which case it will use the new sqlite3-backed pathdb (https://github.com/scionproto/scion/tree/master/go/lib/pathdb/sqlite). This means that if you want to do advanced querying such as this use-case, you could simply query the database directly for anything you like, without needing sciond protocol/code changes.
With that in mind, while i'm ok with adding this functionality to the existing python sciond, i don't plan to have the new go version support it. Just something to be aware of.

proto/sciond.capnp, line 134 at r3 (raw file):

struct SegTypeReplyEntry {
    interfaces @0 :List(PathInterface);  # List of interfaces for the segment
    timestamp @1 :UInt64;  # Creation timestamp

This should specify the unit/epoch. E.g. Creation timestamp. Seconds since Unix Epoch.

Comments from Reviewable

Review status: 0 of 7 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

proto/sciond.capnp, line 124 at r3 (raw file):
Previously, kormat (Stephen Shirley) wrote…
So, now we're back to a naming issue :) This no longer requests segments. My best suggestion right now is SegTypeHopReq - how does that sound?
Relatedly, one thing that comes to mind is that we're planning to rewrite sciond in the ~near future, in which case it will use the new sqlite3-backed pathdb (https://github.com/scionproto/scion/tree/master/go/lib/pathdb/sqlite). This means that if you want to do advanced querying such as this use-case, you could simply query the database directly for anything you like, without needing sciond protocol/code changes.
With that in mind, while i'm ok with adding this functionality to the existing python sciond, i don't plan to have the new go version support it. Just something to be aware of.

Sure! I've updated the naming across all files. I'm glad to know the work on the pathdb is forthcoming. This kind of data is quite useful.

proto/sciond.capnp, line 134 at r3 (raw file):
Previously, kormat (Stephen Shirley) wrote…
This should specify the unit/epoch. E.g. Creation timestamp. Seconds since Unix Epoch.

Done.

Comments from Reviewable

Screenshot result combined with https://github.com/netsec-ethz/scion-viz/pull/40.

Please rebase it on master, and then we can merge it.

Reviewed 7 of 7 files at r4.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Reviewed 1 of 1 files at r5.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Image and area inside wrapper not clickable

I'm facing the issue mentioned in #37 According to the issue it was fixed in november. I've tried it with a couple of versions but onClick events assigned to img and area elements are not executing.
Sandbox where it was reproduced: https://codesandbox.io/s/happy-fire-efyl8?file=/src/App.js
It seems that when I'm clicking on the image or area, then the click events target will be the TrasformComponent instead of the img/area.
You can check the behavior in the sandbox above. The first image is outside of the TrasformWrapper and both the img and area click events log to the console. However at the bottom, clicking on the img and area won't fire console.logs. The button and the div which are in the TrasformWrapper as well fire their onClick events accordingly.

@palika Hello, were you able to make the clicks inside work?

Same issue here. The culprit is in src/components/TransformComponent.module.scss
.content img {   pointer-events: none; }
This basically disables pointer events on images ... and, therefore, hover, clicks, etc. don't work on images.
To get around this, add the following style to your images:
pointer-events: auto !important;

I am still unable to handle click event on the image @prc5


[FEATURE] divide the Module into more Detail

Currently the module is at the same level. But I think it will cause conflict at some time.
Suppose that we have Redis for EmbeddingStore And Memory. How to name both of them?
I suggest that we can move current module into submodule, such as langchain4j-model(contains langchain4j-vertex-ai and langchain4j-dashscope) and langchain4j-embeddding-store(contains langchain4j-milvus, langchain4j-pinecone, langchain4j-weaviate and langchain4j-elasticsearch).
In the future we may need langchain4j-memory-store and langchain4j-agents.

One question is that if we add prefix to current module(eg. langchain4j-elasticsearch to langchain4j-embedding-store-elasticsearch). It may not be compatible. if we do not add prefix, how to avoid conflict?

demo see PR

@Martin7-1 good question. I guess at some point we will probably need to rename modules to include prefix as you suggested. Or maybe we will just put all related implemnetations (embedding store, memory store) in the same module to keep things simple. If person already uses redis to store embeddings, there is a big chance he will use redis to store memory.

@Martin7-1 good question. I guess at some point we will probably need to rename modules to include prefix as you suggested. Or maybe we will just put all related implemnetations (embedding store, memory store) in the same module to keep things simple. If person already uses redis to store embeddings, there is a big chance he will use redis to store memory.

@langchain4j You are right. Now if we don't get any feedback we probably don't need to think about that for a while.


[Feature] Alerts

Is your feature request related to a problem? Please describe.

No
Describe the solution you'd like

It would be great to have notifications (errors, task completion, etc). They could be informative and also be the basis for automations.
Describe alternatives you've considered

I've used a rest sensor for alerts but it often gives errors as the api returns empty json if there are none. I know that the api exposes notification dismissal too, but not sure how that would be implemented.
Additional context

can you give me endpoint which you used?

Of course!
The main alert endpoint is /api/v2.0/alert/list (GET). To dismiss an alert the endpoint is /api/v2.0/alert/dismiss (POST).
The rest sensor I had is below. As I said this gives errors in HA because if there are no alerts the json returned is []. I don't know if this is expected. The conditional tries to catch the exception, but I wasn't able to find a way to make the attribute loading conditional, which I guess is what fails because the Indexes don't exist if it's empty.
Hope this helps.
# Alerts. Error if response is empty.
- platform: rest
  name: tn_alert_level
  resource: http://___address___/api/v2.0/alert/list
  headers:
    Authorization: !secret tn_api_key
    Content-Type: application/json
    User-Agent: Home Assistant
  scan_interval: 300
  json_attributes:
    - level
    - formatted
  value_template: >
    {% if value_json is defined %}
      {{ value_json[0].level }}
    {% else %}
      {{ "None" }}
    {% endif %}
- platform: template
  sensors:
    ## Alert message
    tn_alert_message:
      unique_id: 6c8fd927-e198-4f0e-b67e-2d42e7c9ed04
      friendly_name: "Alert Message"
      value_template: "{{ state_attr('sensor.tn_alert_level', 'formatted') }}"

Yes, that is most likely correct behavior since you query a list.
I will have a look into what we could do with alerts.


[Bug] dictionary changed size during iteration in BaseChannel

File "/usr/local/lib/python3.11/site-packages/pypz/core/channels/base.py", line 322, in retrieve_connected_channel_unique_names
for key, val in self._status_map.items():
RuntimeError: dictionary changed size during iteration
This error is caused, because the dictionary can be updated on a different thread while iterating over it. The fix is to copy the dictionary before iterating over it.

Fixed


The /api/tags route doesn't load

Describe the bug
The model list remains empty. When I look into the network tab, I see the /api/tags route fails
http://myhost:11434/api/tags
Failed to load resource: net::ERR_CONNECTION_REFUSED
However, the error doesn't always appear:

When loading the page from localhost on Ubuntu with Chrome, it works
When loading by IP address on macbook, it fails in all 3 browsers (Chrome, FF, Edge). It even fails with VS Code port forwarding, loading as http://<IP_ADDRESS>:3000/ on Mac.

To Reproduce
Steps to reproduce the behavior:

Load thee root page
The model list is empty

Expected behavior
Model list should load from all browsers and loaded on <IP_ADDRESS> or IP
I tried
docker build --build-arg PUBLIC_API_BASE_URL='http://<IP_ADDRESS>:11434/api' --build-arg OLLAMA_API_BASE_URL='http://<IP_ADDRESS>:11434/api' -t ollama-webui .

and
docker build --build-arg OLLAMA_API_BASE_URL='http://<IP_ADDRESS>:11434/api' -t ollama-webui .

Hi, It's most likely caused by a CORS error, make sure to run the following command to serve Ollama, as mentioned here, which should solve your issue:
OLLAMA_HOST=<IP_ADDRESS> OLLAMA_ORIGINS=* ollama serve

Keep me updated, Thanks.

same thing for me. Also to even get web page to load i had to map port to 3000 inside to container instead of the 8080 in the read me.
to build image i coppied the latest release to my host. ran docker build inside the ollama folder.
image build was successful but when the page loaded the model list was empty.
I am able to interact with the model fine through the cli.

@awptechnologies Hi, the latest release isn't up to date yet, please clone the repo and build from there instead. Regarding the connection error, the environment variable must be passed to Ollama itself, not the WebUI. Thanks.

https://github.com/ollama-webui/ollama-webui#accessing-ollama-web-interface-over-lan

Kinda new to github. I know how to use git but what is the link for the repository. Where do I clone into.

figured it out. Github is the bomb. This worked perfectly. It also fixed the webpage being hosted at 8080. Love the project. Any idea when it will be able to use the internet. Awesome feeling having these resources locally. Im at the point where im done with all this big businesses.

now my question. I have it all working perfect. I use haproxy as reverse proxy and when i try and set up the web ui to use my domain and ssl certs server connection fails. Any ideas? is there a setting i need to have for this to work??

@awptechnologies  Hmm, I'm not so sure. In theory, there shouldn't be any issues caused by the Web UI. Keep us updated if you find a solution. Thanks.

@tjbck So... I have gotten it to work.. I technically don't like the way i did it though.  So the way i did it. I set up the webUI with reverse proxy set server and port and used ollama.mydomain.com to access it. This like mentioned before left the error of not being able to connect to server. i had to then set up a reverse proxy for the API as well. So again set server and port 11434 for API, and used ollamaapi.mydomain.com. Once i did this and set the ollamaapi.mydomain.com as server for webgui it works. The reason i don't like this is because i wanted to set this up with cloudflare so i can access it publicly.  with having to do it this way i had to also expose the API. Best way i can describe it is it is using the front end of the web page to contact the server instead of going through the backend. The ideal setup would be to leave the API accessible only on private network and expose only the web GUI. When setting up cloud-flare i tried to only expose the web GUI and doing this led to the error. The only way i could get it to work is expose the API publicly as well.... Any ideas?

i am running this in docker swarm and they are together in a stack so technically they are directly connected to each other. I figured they would be able to communicate regardless of how i access it on the front end...

when you go to ollama.mydomain.com it only shows ollama is running. so i don't think there is any way for bad actors to mess with it just don't like the idea of the backend being accessible from anyone that knows domain.

Maybe you could try @coolaj86's method of running the Web UI. I'm not so sure about how to fix your problem.


pip install magenta-gpu in Centos

how can i slove this problem  thank you

That looks like an issue with your Python distribution. I'd recommend going through the manual installation steps in our main README and installing a separate conda environment: https://github.com/tensorflow/magenta#manual-install

thank you i slove this problem  but there is new problem


Not detecting ipsw

Everytime I try to downgrade I have to download new ipsw because the script isnt detecting the ipsw which is in ipsw folder

Everytime I try to downgrade I have to download new ipsw because the script isnt detecting the ipsw which is in ipsw folder

please git pull and try again


Xcode 12.5 beta - Swift Compiler Error for RealmSwift module

Goals
Build Realm on Xcode 12.5 beta
Expected Results
To be able to build project
Actual Results
Got a Swift Compiler Error for the RealmSwift module in Combine.swift
with the error being that 'Identifiable' is only available in iOS 13 or newer.
Steps for others to Reproduce
Add Realm and RealmSwift modules via SPM in Xcode 12.5 beta
Build project
Version of Realm and Tooling
Realm framework version: 10.5.1
Realm Object Server version: ?
Xcode version: 12.5 beta
iOS/OSX version: macOS 11.2
Dependency manager + version: SPM (also tried with same error with Cocoapods)

Hey, this issue seems legitimate. We'll get to it shortly.

@jsflax any update?

I am having the same issue.

Same issue here. When will this be fixed and available?

I'm having this issue. XCode 12.5 Beta, application build. "Identifiable' is only available in application extensions for iOS 13 or newer" on on the following line in Combine.swift.
public protocol ObjectKeyIdentifiable: Identifiable, ObjectBase {
    /// The stable identity of the entity associated with `self`.
    var id: UInt64 { get }
}

This was fixed in 10.5.2.

Thanks, I copied the Realm Cocoapods example too literally, didn't notice it was set to '=10.1.4'

From #7098:

@jsflax the problem still exists in v5.5.0 any chance to fix this in that version? Not sure if we can update from v5.5.0 to v10.x.x at this point.
I've fixed it in this fork.

Does anyone know if there is a fix planned for v5.5.0?

I've started assembling a v5.5.1 release that'll include this.

Awesome thx 🙏

I've started assembling a v5.5.1 release that'll include this.

Any update on v5.5.1?

It was released a month ago.

It was released a month ago.

Oh, thanks for the quick reply.
I didn't see v5.5.1 in the release notes and my cocoa pods weren't finding it using ~> '5.5.1'.  I ended up using pod 'RealmSwift', '5.5.1' and it worked.  Thanks again.

Xcode 12.5 binaries has been added to the release-v10.7.4  package. pod update Realm RealmSwift will work.

I have a similar issue, when build Realm(10.10.0) on Xcode 13 BETA3, Xcode error shows 'AnyCancellable', 'Publisher', 'CAncellable' is only available in iOS 13.0 or newer, but the error only occurs on the device under iOS 12.
i'm not sure it is the same one or anything i did wrong

Hi @yves8833 are you using Cocoapods or SPM to install Realm?

Hi @dianaafanador3 i use cocoapods (v1.10.1)

It's working fine on my part on Xcode 13 (Beta 4), Realm(v10.10.0) Cocoapods (v1.10.0), Device (Simulator iOS 11.4)
Can you update to the latest Xcode beta version?, maybe it is something they fixed between versions.

Thanks i will try it.

Hi @yves8833 there are some users having a similar error, seems like an Xcode issue, you can follow the thread here https://github.com/realm/realm-cocoa/issues/7368

When I updated to Xcode 13.2.1, it started showing me Swift Compiler Error in RealmSwift/SwiftUI like

Cannot find type 'Binding' in scope
Unknown attribute 'StateObject'

@zohairhadi  was you able to solve the issue?

It seems to work for me after changing the iOS Deployment Target of RealmSwift pod to 12.0 and do a pod upgrade.

@alissone so what version did RealmSwift jump to? If it jumped to their latest version, they stated in their release that they fixed this issue. I suppose a simple pod update would work as well

Furthermore, what is support for iOS 11 is needed?

It seems like I fixed the issue by just bumping the RealmSwift to the latest version (~> 10.21) without adjusting deployment target explicitly.

Yes, updated to 10.21 works now. Thanks


gtkglext lib

I was unable to find gtkglext library on vcpkg when I did a search. I need it to be able to compi;e GTK and GDK. Thanks

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


Proposal: Live Translations during Smart Maps Pacific

In the spirit of open communication, I would like to suggest we try Zoom auto caption features for participants fluent in other languages (specifically Japanese). This is available as follows: https://support.zoom.us/hc/en-us/articles/6643133682957-Enabling-and-configuring-translated-captions
Thoughts?

I like this idea!

@albertkun Many thanks for clarifications.


DebugConsole: can't exit out of interactive console app

In the new console, when running a REPL command line tool, there is no easy way to get out. e.g. try running cat. It correctly takes input and echos it, but neither Ctrl-C, Ctrl-Break nor Ctrl-Z work to get out.
We may need to add some support for control characters.

This is not likely to happen. Kudu Console is not a true console, and things like Ctrl-C are hard to achieve. If you really need to kill a process, you can do it from Process Explorer.

I face this same issue today. It will be nice to have this feature enable.

Do you have any alternative to close procdump without killing the process?

Hi
Kudu will continue to run in Azure App Service. However, this repo will no longer be maintained.
If the problem persists and is related to running on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


Execute tests for net451 and/or dnx451

Also publishes to obj/ instead of .testpublish/
cc @JunTaoLuo @pranavkm

:shipit: as we will need it before updating test TFMs. Will need to update some repos that depend on the relative paths of the tests such as https://github.com/aspnet/ServerTests/blob/dev/test/ServerComparison.FunctionalTests/Helpers.cs#L13

The relative paths shouldn’t need updating. I’m just moving the test publish folder sideways, not up or down.

You're right, they don't have to be updated due to this change. However they still need to be updated since they have not been correct since we moved away from dnx test which launched the tests in the project directory.


case_sparql_select: End output with newline

Another patch series coming momentarily adds output modes that happen to end with newlines by default, versus the current output modes that do not.
This patch series changes the behavior of case_sparql_select to always end with a newline.

This will cause a slight conflict with #86 due to a change in the expected test output.  So, this should be reviewed to give an OK on the gist, but it should not be merged until after develop is merged back in after 86 is merged.


putObjectMultipartStreamNoLength not returning (spinning) on ErrUnexpectedEOF

Hi,
I'm having an issue when trying to feed PutObject with a reader coming from a HTTP request where the request's body is converted into a http.MaxBytesReader. If the underlying connection is suddenly interrupted the reader will return ErrUnexpectedEOF but the loop in putObjectMultipartStreamNoLength will keep iterating on totalPartsCount which in my case gets set to 8192. This in turn will make the CPU spike and a high number of requests being made by the minio client of zero length in body.
Is there a reason for ignoring ErrUnexpectedEOF?
Here's an example which should reproduce the issue:
package main

import (
	"bytes"
	"log"
	"net/http"

	"github.com/minio/minio-go/v6"
)

func main() {
	endpoint := "localhost:9000"
	accessKeyID := ""
	secretAccessKey := ""
	maxFileSize := int64(1024 * 1024 * 1024) // 1GB

	uploadHandler := func(w http.ResponseWriter, req *http.Request) {
		minioClient, err := minio.New(endpoint, accessKeyID, secretAccessKey, false)
		if err != nil {
			log.Fatalln(err)
		}
		r := http.MaxBytesReader(w, req.Body, maxFileSize+bytes.MinRead)
		written, err := minioClient.PutObject("test", "testfile", r, -1, minio.PutObjectOptions{})
		if err != nil {
			log.Fatalln(err)
		}
		log.Println(written)
	}

	http.HandleFunc("/upload", uploadHandler)
	log.Fatal(http.ListenAndServe(":8080", nil))
}

curl -X POST http://localhost:8080/upload --upload-file some_file --limit-rate 1k

Interrupting the upload before its completion triggers the problem.
Any help with this would be greatly appreciated, thanks :)

This is actually a bug in the io.ReadFull implementaion or the io.Reader passed to io.ReadFull because
ReadFull reads exactly len(buf) bytes from r into buf. It returns the number of bytes copied and an error if fewer bytes were read. The error is EOF only if no bytes were read. If an EOF happens after reading some but not all the bytes, ReadFull returns ErrUnexpectedEOF. On return, n == len(buf) if and only if err == nil. If r returns an error having read at least len(buf) bytes, the error is dropped.

Let's highlight

The error is EOF only if no bytes were read.

So here the issue is that io.ReadFull has length == 0 and err set to io.ErrUnexpectedEOF this means that

  r := http.MaxBytesReader(w, req.Body, maxFileSize+bytes.MinRead)

has an incorrect reader implementation which returns io.ErrUnexpectedEOF which an io.Reader shouldn't do,
so points to a deeper bug in the Go ecosystem.
// ReadAtLeast reads from r into buf until it has read at least min bytes.
// It returns the number of bytes copied and an error if fewer bytes were read.
// The error is EOF only if no bytes were read.
// If an EOF happens after reading fewer than min bytes,
// ReadAtLeast returns ErrUnexpectedEOF.
// If min is greater than the length of buf, ReadAtLeast returns ErrShortBuffer.
// On return, n >= min if and only if err == nil.
// If r returns an error having read at least min bytes, the error is dropped.
func ReadAtLeast(r Reader, buf []byte, min int) (n int, err error) {
	if len(buf) < min {
		return 0, ErrShortBuffer
	}
	for n < min && err == nil {
		var nn int
		nn, err = r.Read(buf[n:])
		n += nn
	}
	if n >= min {
		err = nil
	} else if n > 0 && err == EOF {
		err = ErrUnexpectedEOF
	}
	return
}

So here the implementation simply ignores the situation when nn == 0 and err == io.ErrUnexpectedEOF which should be either silently converted to err == io.EOF  or it can lead to bugs like this since the reader is consistently returning io.ErrUnexpectedEOF instead of io.EOF at EOF.
So I went ahead and added logs to io.ReadAtLeast() which is where I saw that r.Read() indeed returns io.ErrUnexpectedEOF with nn == 0 - this can lead to quite a lot of bugs from the caller who expects to believe this language
ReadFull reads exactly len(buf) bytes from r into buf. It returns the number of bytes copied and an error if fewer bytes were read. The error is EOF only if no bytes were read. If an EOF happens after reading some but not all the bytes, ReadFull returns ErrUnexpectedEOF. On return, n == len(buf) if and only if err == nil. If r returns an error having read at least len(buf) bytes, the error is dropped.

Now keeping all this in mind that io.Reader implementations can return io.ErrUnexpectedEOF this means that io.ReadFull is going to lead to bugs in subtle ways if not well understood.
https://golang.org/pkg/io/#Reader documentation either lacks this clarity or looks like MaxBytesReader is not following this because If I keep reading after the client has closed connection, then it keeps returning io.ErrUnexpectedEOF which is an implementation issue here.
Modified the code
go run ./t.go
2020/07/24 20:21:55 Read-1 65536 unexpected EOF
2020/07/24 20:21:55 Read-2 0 unexpected EOF
2020/07/24 20:21:55 Should be io.EOF false

package main

import (
        "bytes"
        "io"
        "log"
        "net/http"
)

func main() {
        maxFileSize := int64(1024 * 1024 * 1024) // 1GB

        uploadHandler := func(w http.ResponseWriter, req *http.Request) {
                r := http.MaxBytesReader(w, req.Body, maxFileSize+bytes.MinRead)
                buf := make([]byte, 100*1024*1024)

                // First read
                n, err := io.ReadFull(r, buf)
                log.Println("Read-1", n, err)

                // Second read
                n, err = io.ReadFull(r, buf)
                log.Println("Read-2", n, err)
                log.Println("Should be io.EOF", err == io.EOF)
        }

        http.HandleFunc("/upload", uploadHandler)
        log.Fatal(http.ListenAndServe(":8080", nil))
}

To dig further avoid using wrapper io.ReadFull() lets directly call r.Read
package main

import (
        "bytes"
        "io"
        "log"
        "net/http"
)

func main() {
        maxFileSize := int64(1024 * 1024 * 1024) // 1GB

        uploadHandler := func(w http.ResponseWriter, req *http.Request) {
                r := http.MaxBytesReader(w, req.Body, maxFileSize+bytes.MinRead)
                buf := make([]byte, 100*1024*1024)

                // First read
                n, err := r.Read(buf)
                log.Println("Read-1", n, err)

                // Second read
                n, err = r.Read(buf)
                log.Println("Read-2", n, err)
                log.Println("Should be io.EOF", err == io.EOF)
        }

        http.HandleFunc("/upload", uploadHandler)
        log.Fatal(http.ListenAndServe(":8080", nil))
}

go run ./t.go
2020/07/24 20:23:27 Read-1 65536 <nil>
2020/07/24 20:23:33 Read-2 0 unexpected EOF
2020/07/24 20:23:33 Should be io.EOF false

This should be io.EOF since the client has canceled the connection.

When Read encounters an error or end-of-file condition after successfully reading n > 0 bytes, it returns the number of bytes read. It may return the (non-nil) error from the same call or return the error (and n == 0) from a subsequent call. An instance of this general case is that a Reader returning a non-zero number of bytes at the end of the input stream may return either err == EOF or err == nil. The next Read should return 0, EOF.

NOTE: I used curl with 3 bytes a second

curl -X POST http://localhost:8080/upload --upload-file ~/Downloads/ubuntu-18.04-desktop-amd64.iso --limit-rate 3

@harshavardhana
thank you for the excellent analysis :+1:
So, if I understood this correctly, the main issue is that we expect EOF to be returned since Read() returned 0 but instead we get an ErrUnexpectedEOF which in theory should be returned only when at least some data was read.
Also, directly passing the HTTP request's body works fine which indicates it's indeed the http.MaxBytesReader causing the problems.
Looking at that, the problem appears to be the sticky error they use here:
https://golang.org/src/net/http/request.go?s=36920:36960#L1117
After the first failure the Read() implementation will just return 0 and whatever the original error was.
Maybe it makes sense to also raise this with the Golang's team, at least to get some clarification.

@harshavardhana
thank you for the excellent analysis :+1:
So, if I understood this correctly, the main issue is that we expect EOF to be returned since Read() returned 0 but instead we get an ErrUnexpectedEOF which in theory should be returned only when at least some data was read.
Also, directly passing the HTTP request's body works fine which indicates it's indeed the http.MaxBytesReader causing the problems.
Looking at that, the problem appears to be the sticky error they use here:
https://golang.org/src/net/http/request.go?s=36920:36960#L1117
After the first failure the Read() implementation will just return 0 and whatever the original error was.
Maybe it makes sense to also raise this with the Golang's team, at least to get some clarification.

Yes definitely that's the bug here, http.MaxBytesReader is actually making a strong assumption which is defeating io.Reader behavior.
But we do have a workaround.


Add cosmosdb example

Running into a blocking issue because the cosmosdb container does not start in github actions.
That and the other issues with the emulator made me decide not to implement a cosmosdb example. Its just not possible to create a robust test setup with the emulator as the emulator itself is too buggy.


feat(material-experimental/mdc-list):  investigate using radio buttons for single-selection mat-selection-list (primarily as a UX improvement)

Feature Description
investigate using radio buttons for single-selection mat-selection-list (primarily as a UX improvement)
Use Case
No response

This was completed in #25933


[package_info] Moved everything from package_info to package_info/package_info

Description
In this PR, I have moved everything from package_info to package_info/package_info in order to move towards platform_interface package.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

i have already done this in package_info_plus package @yash1200 .

Just remembered this, thanks @balvinderz


The Eclipse .classpath hardcodes the minor JDK version

This is minor, but annoying.  In .classpath the version of the JDK is hardcoded to
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jdk1.8.0_74"/>
Changing that to
<classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
should make it work with whatever version of the jdk is installed.

Fixed in the Git master branch.


Question: How to remove duplication of loguru logger patching in pytest (hashtag1153)

I am testing a function which calls loguru.logger.add("file.log") at the start. This causes issues during pytest execution. The file is written to a temp dir and thus is being used by another process (good ol' Windows) when clean-up happens.
PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'path/to/tmp_dir/file.log'

One solution is to patch loguru.logger.add on each test. But this results in much repeated (boilerplate?) code. For many tests, I don't need to refer to logger.add,  just need patch it so the test runs.

def test_one(mock_logger_add):
    ...
    hashtag Useful to check, but don't want to call this in EVERY test
    mock_logger_add.assert_called_once()

def test_two(mock_logger_add):
    ...
    hashtag No need to check mock_logger_add, just want my code to run

How can I reduce this duplication?
Things I've tried:

Adding an autouse=True fixture to conftest.py or in the test file/class

e.g.

def patch_logger_add(monkeypatch):
    monkeypatch.setattr("loguru.logger.add", lambda *args, **kwargs: None)
    hashtag or
    hashtag monkeypatch.setattr("loguru.logger.add", MagicMock())

or

def no_logger_add(monkeypatch):
    monkeypatch.delattr("loguru.logger.add")

These don't work. Perhaps because, in order for loguru to work with pytest, we have to [redefine caplog]( and that involves calling logger.add.
This works but only when I do not pass caplog to my tests.

def patch_logger():
    with patch("loguru.logger.add"):
        yield

Note: I do not want to turn loguru off completely because I check the logs for errors in my tests.
I posted this also on [SO]( but didn't get much response so wondered if I'd get better results here.
)

to fix your trouble check this fix, i see it in another issue,
https://github.com/Jostino/RimWorld-it/releases/tag/fix
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Collections deprecated in 3.8

Using the schedule module with my project, and testing with pytest, yields a warning about 3.8 dropping support for collections being called in the way its used.
Running python 3.7.3 with schedule 0.6.0 release.
[csabato@thor-teststand-1 unit_tests]$ python3 -V
Python 3.7.3
[csabato@thor-teststand-1 unit_tests]$ pip install -U schedule
Requirement already up-to-date: schedule in /usr/local/lib/python3.7/site-packages (0.6.0)
[csabato@thor-teststand-1 unit_tests]$
/usr/local/lib/python3.7/site-packages/schedule/init.py:357: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
if not all(isinstance(tag, collections.Hashable) for tag in tags):

has this merged version not made it's way back to pypi.org yet? I noticed this same warning from an imported module.

This will be released in the next release, which is almost ready, :tada:, see #412

This will be released in the next release, which is almost ready, :tada:, see #412


Add support for Angular 17

Desired functionality
Add support for Angular 17 release.
Now that Angular 17 has been released, are there any plans to release a new version that supports Angular 17?

Are currently any plans for this? It is currently blocking us from upgrading to Angular 17 for our project.

This needs to be upgraded because Angular 17/18 apps not using Zone.js break with "Zone is not defined" due to direct reference in ng-idle-core on line 750 for example.

@moribvndvs Hi, can we please add the support for Angular version 17 & 18. That will be great, we have our project updated to 18 recently and we are currently in build fail due to this package being unsupported :(

Hi @hey24sheep there are two active PRs for Angular 17 and Angular 18 Can you review the PR whether it works and meets the requirements?

@BhuiyanSaif18 I just reviewed they are migrations only. So, it should work but the release needs to happen through the owner so it can be published on NPM itself. This issue has been open since 2023, I think it's high time to update the packages to support 17 & 18. I request for the update, it is very much needed to upgrade our projects. I don't want to maintain the forks just for the project upgrade.

@moribvndvs do you think, we could merge these PRs mentiond by @BhuiyanSaif18? LGTM!

Closed by #200


[BUG] Inline code block doesn't work when converting Markdown to HTML (sometimes)

This is an example of that bug. Additionally, Markdown syntax for code block is showing (at the end of the file).

By seeing the RAW data on the database, the real problem was that the code blocks weren't there. It is probably an issue with the Markdown converter that I used.

It was actually a problem with the software that I was using to convert. It was not a bug on my program.


Unclear memory and bandwith on App Service

For Free App Service, the limits are unclear.
It says there's 1024MB of memory per App Service plan per hour. Does this mean the total RAM available to an App Service plan is 1024MB? What does "per hour" mean here?
It says bandwidth is 165MB. Is this a speed or cap? Is this per second, hour, day, what?

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

ID: 36f49a06-90b1-cbe1-3853-2c38277b79f8
Version Independent ID: 02ff6f6c-3ef6-b48f-060d-b290419e0aba
Content: Azure subscription limits and quotas - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/azure-subscription-service-limits.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@KTibow
Thanks for your feedback! We will investigate and update as appropriate.

@KTibow,   If the app is hosted in a Free (or Shared) plan, the limits on the resources that the app can use are defined by quotas.
The limits you are referring to is for Free App Service Plan (ASP) tier.
Memory: The total amount of memory allowed for this app.
Bandwidth: The total amount of outgoing bandwidth allowed for this app in a day. This quota resets every 24 hours at midnight UTC.
•	1024MB of memory per App Service plan per hour: This means that the total RAM available to an App Service plan is 1024MB. The "per hour" essentially means that the limit is enforced on an hourly basis. In other words, you can use up to 1024MB of memory in any given hour, but you cannot exceed that limit over the course of the hour.
•	165MB of bandwidth: This is a cap on the amount of data that can be transferred to and from your App Service plan.
Additionally, Shared compute: Free and Shared, the two base tiers, runs an app on the same Azure VM as other App Service apps, including apps of other customers. These tiers allocate CPU quotas to each app that runs on the shared resources, and the resources cannot scale out. These tiers are intended to be used only for development and testing purposes.
Reference:
Monitor apps in Azure App Service
Azure App Service plan overview
Thank for your patience and feedback!

Thanks for the clarification. I'll be making a PR to clarify this soon, but I still don't understand how exactly a fixed cap/resource (RAM) is per hour. It's not possible to exceed the amount of RAM allocated, as there would literally be no more bits to use. Is the cap implemented in another way, eg if at one point the combined RAM usage of a plan is more than 1024MB to disable it for the remainder of the hour?

Hmmm. Now I'm even more confused because the document linked doesn't reference "1 hour" at all, and the Quotas page always says Memory Usage is 0 MiB for my app on F1, even when running intensive tasks. This makes me think the "1 hour" was added because all quotas had to have a reset interval or some other technicality.

We will close this now, if you have further questions, please let us know or raise a PR, we will share your feedback to content author for further review. Much appreciate your feedback to improve Azure docs.

Thanks for the follow-up. Your feedback has been shared with the content owner for further review and to add additional clarity.

@cephalin or @msangapu-msft - do you know the answers to these questions?

#reassign:msangapu-msft
We've added this feedback to our backlog to review and update as necessary.

#please-close


[Feat] define coverage folder path

By default, this plugin creates coverage report in the project root folder.
For Nx and monorepos, the coverage folder is generally at the root of the Monorepo, so it would be convenient to have this option for Storybbok coverage as well.
Reference option in Vitest: https://vitest.dev/guide/coverage#changing-the-default-coverage-folder-location

My bad, this can be done with nycrc.

Can you post your solution please? Wondering the same thing.


pulumi-bin: 2.17.2 -> 2.18.0

Motivation for this change
Update pulumi-bin
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/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Whoops, looks like 2.18.2 has come out since!

Whoops, looks like 2.18.2 has come out since!

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110602 run on x86_64-darwin 1

1 package built:

pulumi-bin

This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 110602 run on x86_64-darwin 1

1 package built:

pulumi-bin


Question about monsters with blindsense, but effectively blind

Hello! My question is the following: I configured a monster, such as the black pudding, which has blindsense up to a certain range, but is blind beyond this range. I selected the "blindsight" vision mode and added only the "blindsense" detection mode. Then I placed the token on the canvas and realized that both hearing and light perception are automatically added to the token, and cannot be removed. Therefore, in a completely illuminated map, it is almost impossible to determine the token's vision range, since it will see infinitely because of light perception. What functional configuration does the module allow me to make, to simulate this type of sense?

I just realized that if I configure "light perception" with a range limit, for a token, when it is placed on the canvas it does not have unlimited light perception. I also realized that I was wrong: this behavior is from Foundry and not from this module. Therefore, I believe this ticket can be closed. Sorry for the inconvenience.


DollarActivity Bootstrap Tour to introJS Tour

hey @llaske i have changed bootstrap tour to introJS tour in Dollar Activity . PLS review it.
Refer to issue:https://github.com/llaske/sugarizer/issues/1090

The popup on Things in detailed view is missing

@llaske okay i am fixing it

@llaske please review it i have fixed it


Exception handling heartbeat_worker

Any time workers start up, I am now getting spammed with the following traceback:

distributed.core - ERROR - Exception while handling op heartbeat_worker
Traceback (most recent call last):
  File "/opt/conda/lib/python3.8/site-packages/distributed/core.py", line 497, in handle_comm
    result = handler(comm, **msg)
  File "/opt/conda/lib/python3.8/site-packages/distributed/scheduler.py", line 3652, in heartbeat_worker
    ws._executing = {
  File "/opt/conda/lib/python3.8/site-packages/distributed/scheduler.py", line 3653, in <dictcomp>
    parent._tasks[key]: duration for key, duration in executing.items()
KeyError: '_get_metadata-b90f52ba-c5e1-4a88-a296-5dc505b1d178-10'

I have seen this before, and it typically goes away on a restart of the kernel, but this time it's been persisting all day. Despite it, the processor seems to continue to run - there's just a lot of spam it throws out concurrently, all of which is this error with small variations.

I think this is a duplicate of https://github.com/CoffeaTeam/coffea-casa/issues/79


Add dns_enable to variables

Overview
I add a dns_enable option to variables in this PR.
Thanks to this option, it's possible to build only CloudFront and S3.
Purpose
Current Route53 setting only creates A record. This PR makes it possible to use customized Route53 module: such as using other DNS record types, setting failover, handling health check, and so on.
To do that, I add the option to create only CloudFront and S3.

@joshmyers
Would you please review again?

@aknysh Thank you for the review.
I changed to the same way as terraform-aws-rds-cluster, and deleted dns_record.
Without the following commit, it did not work, so I updated the module version.
https://github.com/cloudposse/terraform-aws-route53-alias/commit/74957ad27314622bc1d647f98216a1c8d6ee8130


flow type added for Icons.js

Added a type for various Icons used from /src/common/Icons.js from what I interpreted from the Flow documentation.

Hi @harishnandan -- thanks for taking a shot at this!
The most important thing when adding type annotations is that they accurately describe what's possible -- that's what makes them valuable when reading the code and trying to understand it.
In this case, it looks like this type doesn't quite describe what props can actually be passed to these components. For example, in src/compose/ComposeMenu.js we pass onPress to several icons, which isn't on your list. And the docs for the underlying icon components we're using say it takes a very long list of properties -- these three, plus "any Text property", linking to the Text doc. That doc lists 18 other properties, including onPress.
On the other end of things, it looks like our Flow setup doesn't check the types even on the props you've listed. For example, try changing size={24} on some icon to size={"blah"} -- that's a type error, but Flow doesn't complain. So these particular type annotations unfortunately don't do us much good right now. (I'd like to fix that, but that'll be a more complex project.)
I recommend finding some other code to cover with types. Have you tried my suggestions in #2052 for finding code that needs types?
Wherever you do end up adding types, I definitely recommend doing a bit of poking at the code to make sure the types are being checked properly -- things like changing a call site to pass the wrong type, like my size={"blah"} example above.

@gnprice Thanks a lot for the review. I will send a PR covering all the missing points soon.


Use count methods with transaction state

Use count methods with tx state instead of ones without tx state that are deprecated and being removed.

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


updating MediaWiki link syntax as mentioned in issue #24850

Why:
In relation to issue #24850. The mention was to reverse the MediaWiki link syntax
Closes: Issue #24850
What's being changed (if available, include any code snippets, screenshots, or gifs):
The MediaWiki link syntax was updated from:

[[nameofwikipage|Link Text]]

To:

[[Link Text|nameofwikipage]]

Check off the following:

[X] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[X] For content changes, I have completed the self-review checklist.

@PaoloJr90 Thanks so much for opening a PR! I'll get this triaged for review :zap:


Make scripts/patch_name.sh to be compatible with TVM 0.7 and 0.8

During the migration to black formatting in TVM 0.8, the use of double-quotes was adopted, so this script needs to be fixed to cope with both single and double-quotes, during the name patching process.

cc @icemelon9


Fix 'renderHobbies' was used before it was defined eslint error

Found by codeclimate.
I just switched the two method definitions.

Codecov Report

Merging #2750 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #2750   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          67      67
  Lines        1384    1384
======================================
  Hits         1384    1384

Continue to review full report at Codecov.

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

Thanks!


NetworkPolicy rules are not enforced correctly in some case

Describe the bug
The upstream e2e should allow egress access to server in CIDR block is failing randomly.
It looks like a race condition when enforcing 2 egress rules.
To Reproduce
The e2e test deletes the test pod and policy too fast so hard to debug.
To reproduce step by step:
kubectl run nginx --image=nginx --replicas=4

# Get one nginx pod ip, say <IP_ADDRESS>
cat <<EOF | kubectl apply -f -
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: test-network-policy
  namespace: default
spec:
  podSelector:
    matchLabels:
      run: client
  policyTypes:
  - Egress
  egress:
  - ports:
    - port: 8080
  - to:
    - ipBlock:
        cidr: <IP_ADDRESS>/32
    ports:
    - port: 80
EOF

kubectl run -it client --rm --image=qtian/toolbox bash

Now client should be able to access <IP_ADDRESS>:80 and all addresses' 8080 port.
But there's a possibility that it cannot access <IP_ADDRESS>:80.
Openflow:
 cookie=0x7e38000000000000, duration=1332.164s, table=50, n_packets=19140, n_bytes=177881957, priority=210,ct_state=-new+est,ip actions=resubmit(,70)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=3.208s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=5.483s, table=50, n_packets=0, n_bytes=0, priority=200,tcp,tp_dst=80 actions=conjunction(1,3/3)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,tcp,tp_dst=8080 actions=conjunction(2,3/3)
 cookie=0x7e38050000000000, duration=5.482s, table=50, n_packets=0, n_bytes=0, priority=200,ip actions=conjunction(2,2/3)
 cookie=0x7e38050000000000, duration=4.854s, table=50, n_packets=0, n_bytes=0, priority=200,ip,nw_src=<IP_ADDRESS> actions=conjunction(2,1/3),conjunction(1,1/3)
 cookie=0x7e38050000000000, duration=5.484s, table=50, n_packets=0, n_bytes=0, priority=190,conj_id=2,ip actions=resubmit(,70)
 cookie=0x7e38050000000000, duration=5.484s, table=50, n_packets=0, n_bytes=0, priority=190,conj_id=1,ip actions=resubmit(,70)
 cookie=0x7e38000000000000, duration=1332.167s, table=50, n_packets=679, n_bytes=53093, priority=0 actions=resubmit(,60)

The flow nw_dst=<IP_ADDRESS> actions=conjunction(2,2/3) should be conjunction(2,2/3),conjunction(1,2/3).
Expected
NetworkPolicy rules should be enforced correctly.
Actual behavior
As describe above.
Versions:
Please provide the following information:

Antrea version (Docker image tag).
v0.4.0-dev-242cf77
Kubernetes version (use kubectl version). If your Kubernetes components have different versions, please provide the version for all of them.
Container runtime: which runtime are you using (e.g. containerd, cri-o, docker) and which version are you using?
Linux kernel version on the Kubernetes Nodes (uname -r).
If you chose to compile the Open vSwitch kernel module manually instead of using the kernel module built into the Linux kernel, which version of the OVS kernel module are you using? Include the output of modinfo openvswitch for the Kubernetes Nodes.

Additional context

@wenyingd could you take a look at this? I suspect it's related to #332 .

Should we harden the upstream tests to reproduce this more reliably ?

Should we harden the upstream tests to reproduce this more reliably ?

@jayunit100 I think this might be too specific to internal implementation (might be race condition), hard to describe a generic scenario for it. It's detected by upstream test, even the steps I wrote can't reproduce it 100%.

@wenyingd could you prioritize this bug as it might affect our network policy functionality in upcoming 0.4.0?

Sure, I will look into it.


[FR] Validate desktop package version when launching desktop App

Suppose I am a civilian desktop App user of fiftyone==<IP_ADDRESS>, which I installed as follows:
pip install fiftyone==<IP_ADDRESS>
pip install 'fiftyone[desktop]'

Then I upgrade my FiftyOne package as instructed:
pip install --upgrade fiftyone

If I then try to launch the App:
fiftyone quickstart --desktop

I see an unhandled error like so:
An exception has been raised by the server. Your session has been reverted to its previous state.

Traceback (most recent call last):
  File "main.py", line 272, in wrapper
    result = await func(self, *args, **kwargs)
  File "main.py", line 516, in on_message
    event = getattr(self, "on_%s" % message.pop("type"))
AttributeError: 'StateHandler' object has no attribute 'on_page'

The solution is to upgrade my fiftyone-desktop package too, but, as a civilian, I didn't know that I needed to do that and the error message above doesn't help.
Proposals:

Should we manually verify that the desktop package has a compliant version before launching the App, and, if not, print a helpful error message telling the user what to do? And/or, is there something more automatic we can do to always keep the desktop package in sync?
And/or, add fiftyone-desktop upgrade instructions to upgrade section?

Related note:
The install guide shows pip install fiftyone-desktop, but pip install 'fiftyone[desktop]' would probably be better because the latter will install the proper desktop version for your fiftyone install, while the former seems to always install the latest version of the desktop package.

I think we could do both. At a minimum, adding fiftyone as a versioned requirement should work.

Hmm, if we add fiftyone as a requirement to the desktop package, then I believe pip install --upgrade fiftyone would result in a pip error like fiftyone-desktop XXX requires fiftyone YYY, but you have fiftyone ZZZ which is incompatible. The issue with this is that it's backwards from what one would prefer: "your version of fiftyone-desktop is now incompatible and needs upgrade" (not the other way around).
Maybe I'm missing a different variation on this which is cleaner.

And also raise an informative error when there is a mismatch.

I put together a little function for this, I guess for insertion into the launching the desktop App code:
import pkg_resources

def import_desktop():
    """Imports the `fiftyone-desktop` package and verifies that the correct
    version is installed.
    """
    try:
        import fiftyone.desktop
    except ImportError as e:
        raise ValueError(
            "You must `pip install fiftyone[desktop]` in order to launch the "
            "desktop App"
        ) from e

    # Get `fiftyone-desktop` requirement for current `fiftyone` install
    fiftyone_dist = pkg_resources.get_distribution("fiftyone")
    requirements = fiftyone_dist.requires(extras=["desktop"])
    desktop_req = [r for r in requirements if r.name == "fiftyone-desktop"][0]

    desktop_dist = pkg_resources.get_distribution("fiftyone-desktop")

    if not desktop_req.specifier.contains(desktop_dist.version):
        raise ValueError(
            "fiftyone==%s requires fiftyone-desktop%s, but you have "
            "fiftyone-desktop==%s installed.\n"
            "Run `pip install fiftyone[desktop]` to install the proper "
            "desktop package version" % (
                fiftyone_dist.version,
                desktop_req.specifier,
                desktop_dist.version
            )
        )


HOP-3776 Optimized Hop-Translator

Fix current selected row always drifts when the line number is greater than the number of visible lines

Maybe should move redraw method to inside the finally block.


Add OrderSettings transformer

Closes #59

Codecov Report

Merging #101 (880f7d3) into main (3fec199) will increase coverage by 0.12%.
The diff coverage is 98.75%.

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

@@            Coverage Diff             @@
##             main     #101      +/-   ##
==========================================
+ Coverage   96.87%   97.00%   +0.12%
==========================================
  Files          21       22       +1
  Lines         961     1035      +74
==========================================
+ Hits          931     1004      +73
- Misses         30       31       +1

Impacted Files
Coverage Δ

robotidy/cli.py
93.83% <90.00%> (-0.37%)
:arrow_down:

robotidy/app.py
88.00% <100.00%> (ø)

robotidy/transformers/OrderSettings.py
100.00% <100.00%> (ø)

robotidy/transformers/__init__.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


How to deploy? and THANKS

HI;
i hope its ready to deploy now, so will u plz add some instructions regarding how to deploy it and what features it has.
Thanks for bringing this up.

HI; i hope its ready to deploy now, so will u plz add some instructions regarding how to deploy it and what features it has. Thanks for bringing this up.

use brain.exe cuz heroku banning it

HI; i hope its ready to deploy now, so will u plz add some instructions regarding how to deploy it and what features it has. Thanks for bringing this up.

use brain.exe cuz heroku banning it

My brain.exe is not that capable thats why im asking here.
i have another bot from other repo which is working fine, so there must be a way to fix it.

Guys, my own bot got suspended on heroku. So, I'm confused ri8 now.

Guys, my own bot got suspended on heroku. So, I'm confused ri8 now.

yes all bots being banned not only yours .............................Bettter if you rebase code and use fresh docker with alpine debian arch or fedora

HI; i hope its ready to deploy now, so will u plz add some instructions regarding how to deploy it and what features it has. Thanks for bringing this up.

Fork this repo tgmb-beta-deploy. Dont make any changes to code base. Go to repository settings and add secrets in accordance with ./github/workflows/deploy-heroku.yml file. Detailed instructions will be added some time soon after fixing suspension by heroku.

HI; i hope its ready to deploy now, so will u plz add some instructions regarding how to deploy it and what features it has. Thanks for bringing this up.

Fork this repo tgmb-beta-deploy. Dont make any changes to code base. Go to repository settings and add secrets in accordance with ./github/workflows/deploy-heroku.yml file. Detailed instructions will be added some time soon after fixing suspension by heroku.

Thanks bro, will try this.

@ksssomesh12  any update?

@ksssomesh12 any update?

Added support for qbittorrent.

@ksssomesh12 any update?

Added support for qbittorrent.

Thanks bro, but readme is still missing, will u add some info there?

@ksssomesh12 any update?

Added support for qbittorrent.

Thanks bro, but readme is still missing, will u add some info there?
EDIT: there is little confusion, there is no config file there, so where to copy paste these values? i only see 'HEROKU_APP_NAME' and 'HEROKU_API_KEY' in https://github.com/ksssomesh12/tgmb-beta-deploy/blob/master/.github/workflows/deploy-heroku.yml

It's github secrets  <your_fork> -> settings -> secrets -> add new

@ksssomesh12 any update?

Added support for qbittorrent.

Thanks bro, but readme is still missing, will u add some info there?
EDIT: there is little confusion, there is no config file there, so where to copy paste these values? i only see 'HEROKU_APP_NAME' and 'HEROKU_API_KEY' in https://github.com/ksssomesh12/tgmb-beta-deploy/blob/master/.github/workflows/deploy-heroku.yml

It's github secrets <your_fork> -> settings -> secrets -> add new

yes bro but what about config.env var name, is it DYNAMIC_JSON_FILEID ?

@ksssomesh12 any update?

Added support for qbittorrent.

Thanks bro, but readme is still missing, will u add some info there?
EDIT: there is little confusion, there is no config file there, so where to copy paste these values? i only see 'HEROKU_APP_NAME' and 'HEROKU_API_KEY' in https://github.com/ksssomesh12/tgmb-beta-deploy/blob/master/.github/workflows/deploy-heroku.yml

It's github secrets <your_fork> -> settings -> secrets -> add new

yes bro but what about config.env var name, is it DYNAMIC_JSON_FILEID ?

There is a sample for every file check every repository including the main one (tgmb-beta) links
And you should upload it to googledrive and get the fileid of it as it is taken in here. links

@ksssomesh12 any update?

Added support for qbittorrent.

Thanks bro, but readme is still missing, will u add some info there?
EDIT: there is little confusion, there is no config file there, so where to copy paste these values? i only see 'HEROKU_APP_NAME' and 'HEROKU_API_KEY' in https://github.com/ksssomesh12/tgmb-beta-deploy/blob/master/.github/workflows/deploy-heroku.yml

It's github secrets <your_fork> -> settings -> secrets -> add new

yes bro but what about config.env var name, is it DYNAMIC_JSON_FILEID ?

There is a sample for every env check all the files in the repository. links
And you should upload it to googledrive and get the fileid of it, as it is taken in here. links

Thank You. And Sorry. ReadMe is in works. And U dont have to generate any json files by urself. The setup.py script will do that for you.

@ksssomesh12 any update?

Added support for qbittorrent.

Thanks bro, but readme is still missing, will u add some info there?
EDIT: there is little confusion, there is no config file there, so where to copy paste these values? i only see 'HEROKU_APP_NAME' and 'HEROKU_API_KEY' in https://github.com/ksssomesh12/tgmb-beta-deploy/blob/master/.github/workflows/deploy-heroku.yml

It's github secrets <your_fork> -> settings -> secrets -> add new

yes bro but what about config.env var name, is it DYNAMIC_JSON_FILEID ?

There is a sample for every env check all the files in the repository. links
And you should upload it to googledrive and get the fileid of it, as it is taken in here. links

Thank You. And Sorry. ReadMe is in works. And U dont have to generate any json files by urself. The setup.py script will do that for you.

Oh ok, I had a little doubt that setup.py has a automation of generating configs.

I tried deploying from cli and its deployedd but its not responding to bot messages.
I think the problem might be in the config file.
The authorised chat anf google folder section not explained correctly.
if possible, please add instruction to create the config file for the deployment.

any update bro?


Let pipe lessc output to outfile rather than providing outfile arg due to lessc bug

Makes it work with bootstrap 3. See http://stackoverflow.com/questions/28475730/compiling-bootstrap-less-shows-errors-warnings

Oh well.
Thanks :bowtie:


New release for rails 6

It looks like the update for rails 6 version constraint has been merged already. Could you make a release please so it can be used?

v0.5.0 has been released 🎉


Vector search vith VectorDBQAChain

Hello, Thank you for this framework! We are made fantastic product!
But I searched one little issue. When I search with VectorDBQAChain and define metadata, search is not good work. For example:
`async getSimilarity(text: string) {
const vectorStore = await PineconeStore.fromExistingIndex(
this.openaiEmbeddings,
{ pineconeIndex: this.index },
);
const chain = VectorDBQAChain.fromLLM(this.model, vectorStore, {
  k: 5,
  returnSourceDocuments: true,
  metadata: {
    userId: 'h35hd5-3h5d-3h5d-34td-3hdcrg5d3h53',
    id: 'h35hd5-3h5d-3h5d-3h5d-3h5d3h5d3h5d',
  },
});

const response = await chain.call({ query: text });

return response;

}`
and return if I askes "How I feel?"
{   "text": "Based on the context provided, it seems that you feel good right now.",   "sourceDocuments": [     {       "pageContent": "I feel good right now",       "metadata": {         "loc.lines.from": 1,         "loc.lines.to": 1       }     },     {       "pageContent": "I feel good right now",       "metadata": {         "id": "h35hd5-3h5d-3h5d-3h5d-3h5d3h5d3h5d",         "loc.lines.from": 1,         "loc.lines.to": 1,         "userId": "h35hd5-3h5d-3h5d-34td-3hdcrg5d3h53"       }     }   ] }
And searched two documents.
May be I don't understand how to strict search with for example "userId" and "id"
Thank you for your attention!

Thank you for help!
And what chain you could recommended me when I after searched documents and want to call chain with only this docs?

@dosu-bot Thank you for help!
And what chain you could recommended me when I after searched documents and want to call chain with only this docs?


Accessing categories

The user will interact with Bestpy using the following syntax:
best.CATEGORY

Where CATEGORY is simply the category or topic they want to find the best thing I and best is the module they import (bestpy). The issue is how we're going to implement this in the best way possible. The answers will be in a dictionary in a separate python file (check out #3).
Goals
Here are some of the things I'd like for us to achieve with this:

Don't clutter up the global namespace, if possible
Keep it dynamic, so an update in the answers file would result in an update to the available answers straight away
Respect the syntax shown above. No one would like to use best.answer["CATEGORY"] or something like that

Possible solutions
We could add the values from the answers dictionary to the globals in the main file. This would presumably work, but I'm not a huge fan of cluttering up the namespace like that.
We could maybe use an excepthook to achieve this, where AttributeErrors raised with one of the available categories simply respond like usual. This seems like overkill, though, and I'm not a fan of this solution.
If you have any ideas on how we could solve this, I'd love to hear about it.

I think using the first proposed solution with globals could be fine as a start, but it's not something I'd like to call a long term solution. Here's how simple that could be:
# __main__.py
from best import answers
globals().update(answers.answers)

We decided to go with a new implementation that's a bit out of the box. Instead of doing the following:
import best
best.CATEGORY

We now do:
from bestpy import best
best.CATEGORY

This allows us to make the logic of retrieving answers separate from the file that's being run. It also minimises namespace pollution and keeps things cleaner. I like this solution a lot better. Thanks to @fisher60 for proposing it.


Null safely support.

Please, add null safely support.

Thanks for your reminding.
I just added it.


jail: Use the right arch for a pkgbase jail

This is currently a problem for anything not amd64 when building pkgbase jails.  Strip the ARCH and use only what corresponds to TARGET_ARCH.

Test plan:
# poudriere jail -c -j generic-15 -m pkgbase=base_latest -U https://pkg.freebsd.org -v 15 -K generic
# poudriere jail -l
JAILNAME    VERSION         OSVERSION ARCH          METHOD  TIMESTAMP           PATH
generic-15  15.0-CURRENT              arm64.aarch64 pkgbase 2024-10-15 16:27:01 /usr/local/poudriere/jails/generic-15

cc/ @emaste

[!NOTE]
The OSVERSION does not show up because there is no /sys in the jail (not related to this change).

I don't use pkgbase or touch image ever, so need a review from someone else to get this in.

Rebase.
Let's wait for @bapt or @manu then. Thank you!
I'll take the rebase as an opportunity to explain the reasoning behind the changes.
This pull request contains two commits:

get_host_arch() sets ARCH as $(uname -m).$(uname -p), if both are the same (as is the case for amd64), then it just uses one. For all the other architectures, both values will differ.  pkg ABI uses FreeBSD:<version>:$(uname -p), so we must trim the uname -m part.

On some installations, make distributeworld may have not been executed (as is the case for pkgbase).  Among other things, it installs the symlink /sys ->/usr/src/sys (https://github.com/freebsd/freebsd-src/blob/c3f8900e696998c410dc16f9bd9d45c24c413e6b/Makefile.inc1#L1522).  Arguably, this symlink can be added to the pkgbase as a post-install scrpt.


New version: GlobalSensitivityAnalysis v2.0.0

Registering package: GlobalSensitivityAnalysis
Repository: https://github.com/lrennels/GlobalSensitivityAnalysis.jl
Created by: @lrennels
Version: v2.0.0
Commit: dffbbb6bee8c5e97e54f5cf3253d71093580a9eb
Reviewed by: @lrennels
Reference: https://github.com/lrennels/GlobalSensitivityAnalysis.jl/commit/dffbbb6bee8c5e97e54f5cf3253d71093580a9eb#commitcomment-45946780

Not sure what these errors are about, but I also meant to make this 1.2.0 so can close this one and retag, but would love some information on why this failed?

Not sure what these errors are about, but I also meant to make this 1.2.0 so can close this one and retag, but would love some information on why this failed?

Unfortunately we're experiencing some issues in CI today.  #27974 should alleviate them.
[noblock]

Unfortunately we're experiencing some issues in CI today.  #27974 should alleviate them.
[noblock]

Ok, closed so that you can register with a different version number :slightly_smiling_face:

Ok, closed so that you can register with a different version number :slightly_smiling_face:


Feat/341 integrate flyway migration files

Description
Completes #342 and #341. Related to #340 and
This PR converts enums in Java to Postgres table with scripts provided by @thiagosanchezenc
The following migrations scripts are added:

V16: create and seed tables for those enums
V17: add comments to all previously existing tables
V18: add triggers to automate entry_timestamp and update_timestamp in various tables

Summary of Back-end changes
Converted 7 enums to tables, each table has its own endpoint, service, entity and repository.
The list of tables introduced:

cone_collection_method_list
gametic_methodology_list
genetic_class_list
genetic_worth_list
method_of_payment_list
seedlot_source_list
seedlot_status_list

Added default_method_ind to method_of_payment_list
Added female_methodology_ind to gametic_methodology_list
Renamed test files under test/jpa to fileNameRelationalTest.java and moved them under /test/repository/seedlot
Cleaned up swagger documentation and made endpoints use plural form where they can.
Summary of Front-end changes

use the newly added isDefault flag to determine the default method of payment instead of using hardcoded option
use the newly added isFemaleMethodology to determine the sex of the methodology instead of using the first char of the code
refactored endpoints to use the updated endpoint addresses

Type of change

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
manual and unit test
Checklist

[x] I have read the CONTRIBUTING doc
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have already been accepted and merged

Thanks for the PR!
Any successful deployments (not always required) will be available below.
Backend
Frontend
Oracle-API
Once merged, code will be promoted and handed off to following workflow run.
Main Merge Workflow

Great job with the audit columns @craigyu , it is in accordance with the NRM Data and Database Development Guidelines:
https://apps.nrs.gov.bc.ca/int/confluence/display/NRMDDDG/Database+Audit+Columns

Great job with the audit columns @craigyu , it is in accordance with the NRM Data and Database Development Guidelines: https://apps.nrs.gov.bc.ca/int/confluence/display/NRMDDDG/Database+Audit+Columns

Nice, didn't know this guideline existed, I was just trying to be lazy so we don't have to pass in timestamps every time 😜

@RMCampos leaving a reminder here to discuss about doing manual migrations on openshift

@thiagosanchezenc
Do we need all four of those audit columns for each table?
btw I noticed favourite_activity and user_profile do not have any audit column

LGTM! Although, I think the the backend needs some double checking. And also, this was a huuuuuuuge PR, quite painful to review everything at once, in the future we could divide it into minor PRs.

Yes, I can see how painful it is 🙂🙂🙂, thanks for suffering through.
I didn't expect it to be this big either, next time I'll split it or at least getting you in a call to do a review together


Prepare code for performance

[x] CSS cleanup
[x] Code smells cleanup
[x] Import cleanup
[x] NPM modules and dependencies cleanup
[x] Formatting cleanup

solved in 1fa5a383ef58a6645e15aada650f313f7ccc4607


[ADAM-1795] Map -DskipTests=true to exec.skip for Python and R tests.

Fixes #1795.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2475/
Test PASSed.

Merged! Thanks @heuermh!


Fixing user cookie issue #1063

Done! @fzs

This was manually merged,
a) because the PR was created from rcaaa:master. Please use separate branches when creating pull requests, because any other push to your master branch will also show up in this pull request.
b) To improve on it by controlling the seeding of the PRNG.