Remove TTY flags from presets files

Describe the feature
We have deprecated the --disable-tty flag and the KOOL_TTY_DISABLE environment variable. but they weren't removed from the presets files. We should remove them before dropping them from kool
Backward compatibility concerns
Can be a BC if no-tty alike scripts were being used by the final users for some reason.

@danielsuguimoto I don't see it as BC because people using no-tty would still have that preset in their projects, and the flag will keep working... if they want to they can update the preset and be safe for 2.0 when the flag is removed. We should already remove them from the preset now I guess.


the tool will not monitor if the chrome where whatsapp login is minimize

Hello
when I try to minimize chrome which is used to enter WhatsApp, the tool will no longer monitor. This means that the chrome that is used to enter WhatsApp must be seen continuously and cannot be run in the background. I have a WhatsApp bot, is it possible to modify it to use it to monitor WhatsApp contacts online? https://github.com/kepangada/wo

Hello
It's the same for me, the script does not accommodate the connections and disconnections of the target...
I remain a little on my hunger, because it is very practical to follow the discreet profiles...

Hello guys @ChristianBdv @kepangada , unfortunately it's not possible to receive this information in other ways. The reason for this is that there are no underlying API calls that reveal the online status of a user: it can only be obtained through visual HTML inspection
Therefore it can work for only the currently selected profile, and the window must be open. But you can have multiple WhatsApp sessions open in different tabs if you use different phone numbers (>1 phone number: >1 automated browser sessions)

Gracias por su respuesta, retomaré la configuración porque no tengo comentarios incluso con un solo número monitoreado. Te mantendré informado !!
Saludo

@ChristianBdv que lenguaje tienes en el Sistema Operativo? Es importante que el lenguaje que utilices tenga "online" o "en línea", si está en otro idioma puede que haya problemas para detectar el código HTML en el que se extrae el online/offline status


In Assets list group by tokens instead of blockchain

Innovative blockchains have been increasingly arising, so tokens are becoming multi-blockchain, and token holders have a choice of which blockchains they want their tokens on.
Withdrawal pages on centralized exchanges often provide a list of many blockchain options:

Tether lists some of the blockchains that USDT officially exists on at Supported Protocols and Integration Guidelines.
e.g.:
Ethereum: https://etherscan.io/token/0xdac17f958d2ee523a2206206994597c13d831ec7
Avalanche: https://snowtrace.io/token/0x9702230a8ea53601f5cd2dc00fdbc13d4df4a8c7
Polygon: https://polygonscan.com/address/0x170a18b9190669cda08965562745a323c907e5ec
Kava: https://explorer.kava.io/address/0x919C1c267BC06a7039e03fcc2eF738525769109c
Tron: https://tronscan.org/#/token20/TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
EOS: https://bloks.io/account/tethertether
A wallet may hold various quantities of a token on multiple blockchains. Currently, AlphaWallet would show each in separate rows, in sections separated by blockchain.
It'd make more sense to list a token only once in the Assets list, and then show how much of the token is held on each blockchain, and then maybe a total quantity across all enabled blockchains. i.e. group by logical token instead of by blockhain.

I see, how would you propose that this is shown? Maybe under defi we can show a 'conglomerate' view that bunches together the corresponding tokens, for a start at least.
I like the idea.

Hre are some of my ideas:
Each row in the assets list can have:
On left show the logo of the logical token (as it already does, but without the small blockchain logo), then in the middle part small icons of the blockchains on which the user has some of such tokens, then on right the total quantity across all blockchains.
There could be a dropdown button near the total, that when clicked, expands a subsection under the row that shows the breakdown of how much of the token the user has on each blockchain.

Behind the scenes there'd need to be a data structure that maps a logical token to a set of addresses on blockchains.

@tab00 do you know if there's a resource or API with a list of common tokens?
I can see on (for example) the Tether Coingecko page there's a drop down that shows the address for every chain:
https://www.coingecko.com/en/coins/tether
however I couldn't find the corresponding API call to fetch this.

See https://api.coingecko.com/api/v3/coins/list?include_platform=true

In the token details panes (e.g. Token Info, Activity) you'd need to add blockchain names.

See https://api.coingecko.com/api/v3/coins/list?include_platform=true
I'm surprised to see that USDT is on 43 different blockchains. They'll need to be checked.
The Polygon address is different from the one published on Tether's official web site. I think the address in CoinGecko is the correct one based on the activity on PolygonScan. It's weird that the official web site shows an address with almost no activity.

Wow that's an epic API call! Nice find.

For individual logical tokens see https://api.coingecko.com/api/v3/coins/tether which has keys platforms and detail_platforms (which has decimal_place which could be important).

You can alternatively GET https://api.coingecko.com/api/v3/coins/ethereum/contract/0xdac17f958d2ee523a2206206994597c13d831ec7 if you have the blockchain and contract address at hand.


k8s automatic injection docs need update

https://istio.io/docs/reference/commands/istioctl.html#istioctl-kube-inject
https://github.com/istio/pilot/blob/master/doc/proxy-injection.md
incorrectly says it's not supported
https://github.com/istio/pilot/issues/335#issuecomment-341160462

https://istio.io/docs/reference/commands/istioctl.html#istioctl dcs for kube-inject have been updated to reflect that automatic injection is supported. https://github.com/istio/istio/pull/3249 removes the original stale docs for kube-inject.


🔖(ashley) bump version to 1.0.0-beta.2

Added

add dependency to bootstrap 4.4.1 and font-awesome 5.13.0
add button to insert a link in AshleyEditor component

Changed

build the forum CSS theme inside ashley instead of using the compiled CSS
file distributed with django-machina
coalesce SASS color variables between django-machina and bootstrap
use a fluid container for a better iframe integration
change SASS colors

:tada:


ProtonVPN API error on startup

vpn_http_proxy-1  | [!] There was an error with accessing the ProtonVPN API.
vpn_http_proxy-1  | [!] Please make sure your connection is working properly!
vpn_http_proxy-1  | [!] HTTP Error Code: 422
vpn_http_proxy-1  | [!] There was an error with accessing the ProtonVPN API.
vpn_http_proxy-1  | [!] Please make sure your connection is working properly!
vpn_http_proxy-1  | [!] HTTP Error Code: 422
vpn_http_proxy-1  | Device "proton0" does not exist

According to this Reddit post the CLI is no longer supported.

Seems related to this too https://github.com/Rafficer/linux-cli-community/issues/365

Same issue here. I guess pip3 install protonvpn-cli isn't going to work anymore b/c must use a more recent version of the command line client.

This diff fixed the issue for me. I think the right process is to submit a merge request but sorry I'm not a tech guy, don't know how exactly. Pretty straightforward tho
diff --git a/Dockerfile b/Dockerfile
index 92a6bcb..f49ef04 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -19,8 +19,10 @@ ENV PVPN_USERNAME= \
 COPY app /app
 COPY pvpn-cli /root/.pvpn-cli

-RUN apk --update add coreutils openvpn privoxy procps python3 runit \
+RUN apk --update add coreutils git openvpn privoxy procps python3 runit \
     && python3 -m ensurepip \
-    && pip3 install protonvpn-cli
+    && git clone https://github.com/ProtonVPN/linux-cli-community \
+    && cd linux-cli-community \
+    && pip3 install -e .

 CMD ["runsvdir", "/app"]

That's great :D I created a PR with that fix https://github.com/walterl/proton-privoxy/pull/47
Basically the process is;

Create a fork of the project (there's a button for that at the top of the repo page)
Clone the forked version, which should be named something like ab2022/proton-privoxy by default
Make a new branch
Make you changes and create a commit
Push the branch
GitHub will give you a link to create a PR in the response :)

I can confirm that worked too :)

Yeah probably it will stop working eventually. They recommend to use their app but it's UI only, no cli AFAIK.
For alpine (not one of their supported distros) they suggest wireguard. But wg each server needs it's own config which you download from your account login.
Alternative, someone could volunteer to become maintainer of the community client. That seems to be their issue with it - it's unmaintained, no updates in years.

Yeah ... WG is bad in that regard. OpenVPN though can do "country specific" endpoint pools IIRC, but that's probably another headache.  Unfortunately I am not a coder so am now seeing what my alternatives are  I saw this and 1st thought was GREAT! I can do that! Then I realized an alternative needs to be investigated on my side (no big deal it is what it is).  My internal proton-privoxy solution can probably be migrated to something else I already have running .. my guest network version may be more problemmatic. :-)

Thanks a lot for the issue and PR #47, @betterphp and @ab2022. After some adjustments, that PR was merged, and this issue should now be fixed. It's available on DockerHub: docker pull walt3rl/proton-privoxy.

Thanks for the link to that discussion, @MyVizDrake.
It's really unfortunate that ProtonVPN isn't planning on supporting any alternative to the CLI. While I've been with ProtonVPN for years, and generally hold them in high regard, this feels like a betrayal of their (perceived?) early "hacker-friendly" ethos. I'll have to start looking at alternative VPN providers, for one that supports the use case that this project requires. If it's easier to switch to a more CLI-friendly VPN service, than to implement a solution like what @betterphp is suggesting (limited in scope as it is), I don't mind voting with my wallet.

@walterl if OpenVPN is OK, one could create a OpenVPN file that has all of the possible end points someone wants. I know I can download an OpenVPN file now for say, Belgium and I would get all of the Belgian ProtonVPN OpenVPN servers and I believe it will select one at random. This would be better than a single WG endpoint and a lot simpler than the idea that @betterphp proposed.  Would be at the expense of tunnel speed being OpenVPN vs WG.
I could be a guinea-pig (i.e. tester) if need be.
I had been running your container for at least a year and really appreciate the effort you had put into it!!!

@MyVizDrake
There are a number of Docker images available on github that provide OpenVPN and Privoxy functionality.
But I suspect that the Proton CLI client is preferred because it provides some additional features that are not possible with OpenVPN (whatever they may be, I don't use them myself...)

Being able to pick the country with an environment variable was the main thing for me, not likely to be a generic solution for that since it would always require provider specific information.
Thanks for sorting all that out @walterl <3


Support rails 5 v2

This is a copy of @st0012's PR #24. It just brings back the use of .try as recommended by @dcosson.

An alternative to using heroku_rails_deflate is to enable deflate in Rack.  If you're using Rails, you're already using Rack, and Rack now has its own built-in deflate mechanism.  You just need to enable it, e.g.:

config.middleware.use Rack::Deflater

I know that Rack at one time didn't include deflate.

No kidding? That's really good to know, thanks!

Sure!  I just recently learned this myself, and it seems to work fine (when Amazon Web Services isn't having problems).  This is a newer addition to Rack - when I originally added heroku_rails_deflate I'm pretty sure Rack didn't have this capability.

To be fair: The heroku_rails_deflate README specifically notes that it enables heroku_rails_deflate to perform its functionality.  This heroku_rails_deflate gem does other (optimization) things, but since it didn't work with Rails 5, my approach was to go back-to-basics instead.  You can decide what's best for your circumstance!

I'd still really like to see this merged.  Without heroku_rails_deflate, or something similar, we end up compressing already-compressed files.


⚠ Turnos 24x7 has degraded performance

In 047d1ca, Turnos 24x7 (https://reservas.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1011 ms

Resolved: Turnos 24x7 performance has improved in 28f4b63.


PyPI release of 0.32.1 only contains Windows wheels

The PyPI release of 0.32.1 only contains Windows wheels. There are no Mac wheels, and no source tarball either.
This effectively means 0.32.1 is uninstallable through PyPI on any platform other than Windows.
Version 0.32.0 does have Mac wheels, as well as a source tarball.
See: https://pypi.org/project/shap/0.32.1/#files
and:  https://pypi.org/project/shap/0.32.0/#files

Thanks for pointing this out! I was working on getting travis to post the source and wheels automatically, it failed I forgot to then post the tarball directly. Fixed now.

Thanks for the quick fix!


Not working

This does not work for VSTS repos, or *.visualstudio.com repos.

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

ID: 0e7fcfcb-c10c-be34-4a9d-94d54245a3da
Version Independent ID: aa7b7720-7c7e-1b4f-96e8-3bf068efe9fd
Content: Clone a Git repository in a public project - Azure DevOps Services Public Project
Content Source: docs/organizations/public/clone-git-repo-public.md
Product: devops
Technology: devops-public-projects
GitHub Login: @steved0x
Microsoft Alias: sdanie

@ChrisColeTech Thank you for the feedback.
Does this apply to a specific set of instructions in the documentation, i.e. with Visual Studio or command-line and what is the specific error?
Please note that since this is the documentation forum our support options are limited.
For further support, you will need to move the issue here to get feedback from the product team.

Closing the issue now.

There is no 'Clone' button on VSTS repos -

so step 2 fails.
Also, it does not work from the command line:

Using Visual Studio is not an option because I am on a MacBook.

Assigning this to the author for review.

That's not a Git repository, it's TFVC. There is no "clone" button for TFVC.


[Website] Update info on site

Originally part of #262, all information related changes:

Update stats on the about page
Add me (MattIPv4) to the about page
Add key stats to the home page
Ensure brand name consistency
Ensure brand colour consistency
Add robots.txt with sitemap

Once this is merged I will begin work on the next subset of #262 so that I can resolve conflicts as I go instead of after (mainly due to massive file refactoring occurring).

Putting this as WIP whilst I wait for Feb stats

Latest stats added and conflicts resolved. Ready to go now @PeterDaveHello

@MattIPv4 can you please remove Merge branch 'master' into MattIPv4-update-info here? This branch should rebase on the latest master branch, without other merge commits, thanks.

@PeterDaveHello Git won't allow me to rebase due to unstaged files generated in the sri folder?

@MattIPv4 you can delete those files or use sparseCheckout to not checkout those files.

@PeterDaveHello Based on what has just been pushed, I feel rebase really isn't working due to the conflicts..?

@MattIPv4 the conflicts need to be resolved no matter using rebase or merge, because they are just there.

@MattIPv4 I thought the conflicts may come from the duplicated commits, commits from other authors than you should be removed ;)

@PeterDaveHello As before, conflicts have been resolved and merged.

@MattIPv4 I don't understand, the "merge commit" is still there...

@MattIPv4 that's not the preferred way to "resolve" the conflicts, that means this branch its own change is not clean

@PeterDaveHello yes, the issue is that we track sitemap.xml which is automatically generated. This branch makes a change to the script that generates sitemap.xml and so there is a conflict. That's why the merge commit is needed to resolve that?

@MattIPv4 if so, you can remove the commit and generate new sitemap again, or jutst regenerate it when git says there are conflcts.

@PeterDaveHello I'm not sure how it generates a new sitemap?
I'm running the update.js script which is running fine but it seems to rely on public/packages.min.json of which I must have an older version?

@MattIPv4 I think maybe you can simply drop the changes on the sitemap?

@PeterDaveHello I honestly still have no idea how to rebase this from command line?

@MattIPv4 Try git rebase -i HEAD~13 ?

@PeterDaveHello Successfully rebased and updated refs/heads/MattIPv4-update-info. Nothing to commit or push?

@MattIPv4 Maybe you didn't rebase anything in the interactive interface?

@MattIPv4 Try this one: https://hackernoon.com/beginners-guide-to-interactive-rebasing-346a3f9c3a6d

@PeterDaveHello or maybe just consider to commit everything from scratch without touching something not related, then you'll have a clean branch

@PeterDaveHello I'm not sure what the issue is as to why it can't clean merge if you look at the conflict, it's where you have updated the body, which I haven't touched?

@MattIPv4 nope, it's clear that you touched the sitemap, let me point it out in the diff for you

@PeterDaveHello looks it's cleared now!? 👍

@MattIPv4 please note that there are still conflicts in templates/layout.html

@PeterDaveHello yeah, I managed to locate all the commits that changed it. What should be done about layout?

@MattIPv4 GitHub tells me that, I haven't took a look... but I thought you can try merging locally with master and you'll see the error?

@PeterDaveHello I think by some miracle of random git commands, it is now happy! 🎉

@MattIPv4 well, I'm worried about that mirable a little bit, as we better know what cause the issues so we can prvent them in the future. Anyway, I'll take a look at the new commits, thanks.

@PeterDaveHello I'm honestly not really sure, Git seemed to think the <body> line had been modified by me and so it was conflicting with the updated line in master, however, I had only modified the line below. Rebasing onto master (manually resolving the conflict) did fix it though looking at my command history. Thank you for helping :)

BTW, CDNJS -> cdnjs seems to be kind of rebranding, any reason why about that? I thought it's not really an important task right now, but just curious about it, actually, many many users don't even know the difference between cdnjs and Cloudflare, or think it's cdn.js

@PeterDaveHello With regards to CDNJS -> cdnjs, almost everywhere but certain bits of the site we are marketed as cdnjs, so as part of updating the info on the site, I enforced consistency in the naming.

I thought b81f2e3 20e5e5f 3a8e72d should be squashed into a single commit as it's a single thing?

Sorry, don't know how to do this correctly?

@MattIPv4 https://hackernoon.com/beginners-guide-to-interactive-rebasing-346a3f9c3a6d
use rebase with squash/fixup, you can move these commits in order and merge them into single one

@PeterDaveHello I think I have fixed everything now?

@MattIPv4 Thanks, I'll take a look ;)

Commit 3d9266a8ef9da7ba4e7f72d8757a39b726894655 says: refactor about, need to be more precise with more details.

@PeterDaveHello Anything further?

As a note of the looking part(I only reviewed the commit and the codes before),
The original look:

The new look:

It suddenly makes the homepage being a little bit complex, I'm not sure if it's good ... prefer to take a while to think about it, but some code refactor or about page change could be good, that's why we should separate different changes into different pull requests, so they won't block each other with unrelated reason.

@PeterDaveHello Yeah, I'm just going to work a bit on cleaning up that design now :)

@MattIPv4 thanks

@PeterDaveHello Issues fixed, added some more padding and condensed the points on the homepage to make it cleaner. (#266 fixes the layout further in terms of responsiveness)

@PeterDaveHello Sorry, could you possibly do the clean merge with master? I'm still not very good at doing it.

@MattIPv4 you can run this command locally:
"git rebase master MattIPv4-update-info"

@PeterDaveHello Ah, thank you! As soon as the checks complete, this should be good to go?

cc @ryankirkman This involves a change to branding in that is consolidates the use of cdnjs over CDNJS, which appears to be how the brand is aligned currently in most places. It also enforces the use of a single, consistent brand colour.

New
Old

+1 for keeping home page minimal.

I personally think the few key selling points that will be added here are still keeping the page minimal but also work well to help promote what cdnjs is better to a user who may not know and has ended up on the home page? @thomasdavis

@MattIPv4 let's separate the homepage redesign into another PR and get this merged, what do you think?

@PeterDaveHello Homepage design changed moved to #293 - Also, rebased against latest master.

As @ryankirkman @thomasdavis @drewfreyling for review as branding changed.

Never mind. @MattIPv4 let's resolve the conflicts and get it merged, thanks.

@PeterDaveHello Thank you, rebased against latest master :)


LSTM for Sequence Classification into Categories

Hi,
I'm trying to use a LSTM where I provide word2vec vectors as inputs and I want to classify the this sequence into a set of categories, so, as training data, I have something like that for example:
"<text>", <category id>
"lorem ipsum dolor sit amet...", 5

So, my question is: how can I feed that into my LSTM?
Here is how I build my model:
# Create the LSTM Neural Model
model = Sequential()
model.add(
  Embedding(
    output_dim=word_vector_model.dimension,
    input_dim=number_of_words_in_dataset, # thats correct?
    mask_zero=True,
    weights=[embedding_weights], # what this should be?
    input_length=input_length, # what this should be?
    output_dim=number_of_categories # thats correct?
  )
)
model.add(LSTM(word_vector_model.dimension))
model.add(Dropout(0.5)) # try 0.3
model.add(Dense(1, activation='sigmoid'))

# Compile the model
model.compile(loss='binary_crossentropy', optimizer='adam')

What output_dim should be? The number of categories in y?
What are the embedding_weights?
What input_dim should be?

Thank you, and sorry if I don't understand the meaning of each field.

I personally use a colleague's vocabulary class (you can find his implementation here .  Basically, it maps string -> int.
You can do (and I prefer the nomenclature vocab... sorry if that's confusing):
## assuming dataset is an array of arrays of words.
vocab = Alphabet.from_iterable(word for sent in dataset for word in sent)
## if not..
vocab  = Alphabet.from_iterable(word for sent in dataset for word in sent.split(" "))

Now you have indices you can use.    Some other things to consider:

if you want to use a mask on the lstm for variable lengths, you'll not want the vocab to map a word to the 0th index
You want the indices of the vocabulary to match the indices on your embedding matrix so that the embedding layer correctly works. I preferably make a new matrix by doing (for example, and using glove which comes in a text file):

def make_embeddings(igor, vocab):
    #glove_fp = "/research/data/glove/glove.840B.300d.txt"
    vocab_togo = set(vocab._mapping.keys())
    E = igor.embedding_size
    V = len(vocab)
    embeddings = np.zeros((V, E))
    with open(igor.glove_fp) as fp:
        for line in tqdm(fp.readlines(), unit='lines'):
            line = line.replace("\n","").split(" ")
            word,nums = line[0], [float(x.strip()) for x in line[1:]]
            if word in vocab_togo:
                vocab_togo.remove(word)
                embeddings[vocab[word]] = np.array(nums)

    print("{} words not in glove".format(len(vocab_togo)))
    with open("glove_oov.txt", "w") as fp:
        fp.write("\n".join(vocab_togo))

    for word in vocab_togo:
        embeddings[vocab[word]] = GlorotUniform().sample((E,1)).reshape(E)

    utils.save_embeddings(igor, embeddings, vocab)
    return embeddings

@brunoalano , I am also working with the same task. Did you solve the problem?

Any body having character based text classification code in keras like in https://github.com/tensorflow/tensorflow/blob/master/tensorflow/examples/skflow/text_classification_character_rnn.py


Fetch Refactor: Cypress Tests

Problem statement
As a report stream developer / maintainer I want to be ensured that the new fetch system is working properly, and I'd like to do so by having the value sets editor run through end to end tests.
Create some Cypress tests for value sets.
This may not be worth doing until existing Cypress tests are fixed and running in CI?
What you need to know
[Links to documents, workflows, or list of key people and contact info]

Document 1
Document 2
...

Acceptance criteria

[ ] Common value sets workflows are covered by passing Cypress tests

To do

[ ] ...

Might need a separate ticket for figuring out Auth


Not able to load trained models

Hi,
I am trying to load the OccAnt(depth) models but to no luck. Getting the following errors :
Unexpected key(s) in state_dict: "mapper_state_dict", "local_state_dict", "global_state_dict", "config", "extra_state".

I am not doing evaluations through your code base but rather trying to replicate the test_occant.py file.
TASK_CONFIG = "OccupancyAnticipation/occant_baselines/config/ppo_exploration.yaml"
        cfg = get_config(TASK_CONFIG)
        occ_cfg = cfg.RL.ANS.OCCUPANCY_ANTICIPATOR
        OccNet = OccAntDepth(occ_cfg)
        OccNet.load_state_dict(torch.load("OccupancyAnticipation/ckpt.11.pth",map_location='cuda:0'))
        OccNet.eval()

I tried using the specific state dics like mapper_state_dict, but that also does not match with the model's state dict.

Missing whole lot of keys too
Missing key(s) in state_dict: "gp_depth_proj_encoder.inc.conv.conv.0.weight", "gp_depth_proj_encoder.inc.conv.conv.0.bias", "gp_depth_proj_encoder.inc.conv.conv.1.weight", "gp_depth_proj_encoder.inc.conv.conv.1.bias", "gp_depth_proj_encoder.inc.conv.conv.1.running_mean", "gp_depth_proj_encoder.inc.conv.conv.1.running_var", "gp_depth_proj_encoder.inc.conv.conv.3.weight", "gp_depth_proj_encoder.inc.conv.conv.3.bias", "gp_depth_proj_encoder.inc.conv.conv.4.weight", "gp_depth_proj_encoder.inc.conv.conv.4.bias", "gp_depth_proj_encoder.inc.conv.conv.4.running_mean", "gp_depth_proj_encoder.inc.conv.conv.4.running_var", "gp_depth_proj_encoder.down1.mpconv.1.conv.0.weight", "gp_depth_proj_encoder.down1.mpconv.1.conv.0.bias", "gp_depth_proj_encoder.down1.mpconv.1.conv.1.weight", "gp_depth_proj_encoder.down1.mpconv.1.conv.1.bias", "gp_depth_proj_encoder.down1.mpconv.1.conv.1.running_mean", "gp_depth_proj_encoder.down1.mpconv.1.conv.1.running_var", "gp_depth_proj_encoder.down1.mpconv.1.conv.3.weight", "gp_depth_proj_encoder.down1.mpconv.1.conv.3.bias", "gp_depth_proj_encoder.down1.mpconv.1.conv.4.weight", "gp_depth_proj_encoder.down1.mpconv.1.conv.4.bias", "gp_depth_proj_encoder.down1.mpconv.1.conv.4.running_mean", "gp_depth_proj_encoder.down1.mpconv.1.conv.4.running_var", "gp_depth_proj_encoder.down2.mpconv.1.conv.0.weight", "gp_depth_proj_encoder.down2.mpconv.1.conv.0.bias", "gp_depth_proj_encoder.down2.mpconv.1.conv.1.weight", "gp_depth_proj_encoder.down2.mpconv.1.conv.1.bias", "gp_depth_proj_encoder.down2.mpconv.1.conv.1.running_mean", "gp_depth_proj_encoder.down2.mpconv.1.conv.1.running_var", "gp_depth_proj_encoder.down2.mpconv.1.conv.3.weight", "gp_depth_proj_encoder.down2.mpconv.1.conv.3.bias", "gp_depth_proj_encoder.down2.mpconv.1.conv.4.weight", "gp_depth_proj_encoder.down2.mpconv.1.conv.4.bias", "gp_depth_proj_encoder.down2.mpconv.1.conv.4.running_mean", "gp_depth_proj_encoder.down2.mpconv.1.conv.4.running_var", "gp_depth_proj_encoder.down3.mpconv.1.conv.0.weight", "gp_depth_proj_encoder.down3.mpconv.1.conv.0.bias", "gp_depth_proj_encoder.down3.mpconv.1.conv.1.weight", "gp_depth_proj_encoder.down3.mpconv.1.conv.1.bias", "gp_depth_proj_encoder.down3.mpconv.1.conv.1.running_mean", "gp_depth_proj_encoder.down3.mpconv.1.conv.1.running_var", "gp_depth_proj_encoder.down3.mpconv.1.conv.3.weight", "gp_depth_proj_encoder.down3.mpconv.1.conv.3.bias", "gp_depth_proj_encoder.down3.mpconv.1.conv.4.weight", "gp_depth_proj_encoder.down3.mpconv.1.conv.4.bias", "gp_depth_proj_encoder.down3.mpconv.1.conv.4.running_mean", "gp_depth_proj_encoder.down3.mpconv.1.conv.4.running_var", "gp_depth_proj_encoder.down4.mpconv.1.conv.0.weight", "gp_depth_proj_encoder.down4.mpconv.1.conv.0.bias", "gp_depth_proj_encoder.down4.mpconv.1.conv.1.weight", "gp_depth_proj_encoder.down4.mpconv.1.conv.1.bias", "gp_depth_proj_encoder.down4.mpconv.1.conv.1.running_mean", "gp_depth_proj_encoder.down4.mpconv.1.conv.1.running_var", "gp_depth_proj_encoder.down4.mpconv.1.conv.3.weight", "gp_depth_proj_encoder.down4.mpconv.1.conv.3.bias", "gp_depth_proj_encoder.down4.mpconv.1.conv.4.weight", "gp_depth_proj_encoder.down4.mpconv.1.conv.4.bias", "gp_depth_proj_encoder.down4.mpconv.1.conv.4.running_mean", "gp_depth_proj_encoder.down4.mpconv.1.conv.4.running_var", "gp_decoder.up1.conv.conv.0.weight", "gp_decoder.up1.conv.conv.0.bias", "gp_decoder.up1.conv.conv.1.weight", "gp_decoder.up1.conv.conv.1.bias", "gp_decoder.up1.conv.conv.1.running_mean", "gp_decoder.up1.conv.conv.1.running_var", "gp_decoder.up1.conv.conv.3.weight", "gp_decoder.up1.conv.conv.3.bias", "gp_decoder.up1.conv.conv.4.weight", "gp_decoder.up1.conv.conv.4.bias", "gp_decoder.up1.conv.conv.4.running_mean", "gp_decoder.up1.conv.conv.4.running_var", "gp_decoder.up2.conv.conv.0.weight", "gp_decoder.up2.conv.conv.0.bias", "gp_decoder.up2.conv.conv.1.weight", "gp_decoder.up2.conv.conv.1.bias", "gp_decoder.up2.conv.conv.1.running_mean", "gp_decoder.up2.conv.conv.1.running_var", "gp_decoder.up2.conv.conv.3.weight", "gp_decoder.up2.conv.conv.3.bias", "gp_decoder.up2.conv.conv.4.weight", "gp_decoder.up2.conv.conv.4.bias", "gp_decoder.up2.conv.conv.4.running_mean", "gp_decoder.up2.conv.conv.4.running_var", "gp_decoder.up3.conv.conv.0.weight", "gp_decoder.up3.conv.conv.0.bias", "gp_decoder.up3.conv.conv.1.weight", "gp_decoder.up3.conv.conv.1.bias", "gp_decoder.up3.conv.conv.1.running_mean", "gp_decoder.up3.conv.conv.1.running_var", "gp_decoder.up3.conv.conv.3.weight", "gp_decoder.up3.conv.conv.3.bias", "gp_decoder.up3.conv.conv.4.weight", "gp_decoder.up3.conv.conv.4.bias", "gp_decoder.up3.conv.conv.4.running_mean", "gp_decoder.up3.conv.conv.4.running_var", "gp_decoder.up4.conv.conv.0.weight", "gp_decoder.up4.conv.conv.0.bias", "gp_decoder.up4.conv.conv.1.weight", "gp_decoder.up4.conv.conv.1.bias", "gp_decoder.up4.conv.conv.1.running_mean", "gp_decoder.up4.conv.conv.1.running_var", "gp_decoder.up4.conv.conv.3.weight", "gp_decoder.up4.conv.conv.3.bias", "gp_decoder.up4.conv.conv.4.weight", "gp_decoder.up4.conv.conv.4.bias", "gp_decoder.up4.conv.conv.4.running_mean", "gp_decoder.up4.conv.conv.4.running_var", "gp_decoder.outc.conv.weight", "gp_decoder.outc.conv.bias".

This is likely because of a mismatch between the model checkpoint and the config. Did you try using this config?

So I tried that and it gave me the same error. However I notice something :
Example of missing keys :
gp_depth_proj_encoder.inc.conv.conv.0.weight", "gp_depth_proj_encoder.inc.conv.conv.0.bias"

Example of unexpected keys :
 "mapper.projection_unit.main.main.gp_depth_proj_encoder.inc.conv.conv.0.weight",

Seems like mapper.project_unit.main.main. is just an additional string attached .

@Singh-sid930  - sorry for the late response. The above snippet will not work. You should be following the conventions used in the trainers for loading the defining and loading the model. Here is the relevant snippet for why those additional strings are appended to the state_dict. This is the definition of OccupancyAnticipator.

In the meantime I had got this working by doing this small hack. I could tried the above method which didn't work correctly. High chance I am doing something wrong so I will try it out later.
But just to confirm, the occAntDepth model class pertains to the this model : https://dl.fbaipublicfiles.com/OccupancyAnticipation/pretrained_models/occant_depth_ch/ckpt.13.pth
And inside this model, thee "mapper_state_dict" key is what contains the mapper weights (plus a few more)
This is my hack :
        occ_cfg = cfg.RL.ANS.OCCUPANCY_ANTICIPATOR
        OccNet = OccAntDepth(occ_cfg).cuda()
        state_dict = torch.load("OccupancyAnticipation/OccDepth.pth", map_location='cuda:0')
        state_dict = state_dict["mapper_state_dict"]

        new_state_dict = OrderedDict()

      #### hack
        for k,v in state_dict.items():
            if "mapper.projection_unit.main.main." in k:
                name = k.replace("mapper.projection_unit.main.main.","")
                new_state_dict[name] = v
        OccNet.load_state_dict(new_state_dict)

        OccNet.eval()

I just had a few questions about the inpput and output.
q1: I notice the input is a 128*128 tensor of two channels.
As I understand it :
channel 0 = occupancy probability
channel 1 = exploration probability (confidence that it has been explored)
What is the purpose of exploration? We do not have the exploration probability in our setup. Is it necessary to estimate occupancy?
What we have is a top down map of occupancy as seen by the robot and we can also accumulate that over steps.
This map was created from the habitat depth data.
Or can we provide high confidence values to the pixels, that the robot has explore(be it free or occupied)
q2: For the 128,128 map, is the robot ego-centric to the center of the map or the bottom middle of the map ?
q3 : Is the output also the same semantically as the input in terms of what the channels represent.

Yes. That checkpoint corresponds to OccAnt(depth). The method for loading the checkpoint looks good to me.
q1 - For non-anticipation models, channel 1 indicates whether that part of the space was observed or not (unobserved is 0, observed is 1). For anticipation models, channel 1 indicates the model's confidence about its prediction for that part of the map. Note that an anticipation model does not necessarily have to observe a location to predict its occupancy.
q2 - The robot starts at the center of the map facing upward. But the full map is not rotated as the agent moves.
q3, q6 - What input and output are you referring to here?

By input I mean the dict that is to be sent to the model which in the case of OccAntDepth is
input = { 'ego_map_gt' : (bs, 2, H, W) }

And output is then
y = model(input)
output = y["occ_estimate"]

q3 : for the output also channel 0 = occupancy probability , channel 1 = prediction confidence ?
q6: in the input of ego_map_gt is the map (the top down occupancy) a snapshot of the current step or the accumulation of all the past steps in the episode.
q1: quick clarification for the input then, in my ego_gt_map which I send to the OccAntDepth model, channel 1 does not necessarily need to have the any values which represent observation ? Just trying to understand what should I put in channel 1 of the ego_gt_map. We do track explored space, but not confidence of exploration.

ego_map_gt is basically the geometric projection of the depth sensor readings (non-anticipation). So the q1 response applies.
Here is a reference for how ego_map_gt is computed.

Closing this issue since the questions were addressed. Please feel free to re-open it if there are any more.


[SPARK-9753] [SQL] TungstenAggregate should also accept InternalRow instead of just UnsafeRow

https://issues.apache.org/jira/browse/SPARK-9753
This PR makes TungstenAggregate to accept InternalRow instead of just UnsafeRow. Also, it adds an getAggregationBufferFromUnsafeRow method to UnsafeFixedWidthAggregationMap. It is useful when we already have grouping keys stored in UnsafeRows. Finally, it wraps InputStream and OutputStream in UnsafeRowSerializer with BufferedInputStream and BufferedOutputStream, respectively.

cc @JoshRosen @rxin for review.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

Test build #1407 has started for   PR 8041 at commit 7753e34.

Test build #1407 has finished for   PR 8041 at commit 7753e34.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merging this -- I tried this locally also and it is definitely faster than current master.


replaced firewall_policy_attachments with firewall_policy_association…

… in example

Thanks @apichick. Test error is unrelated to your change.


⚠ Bofrost.de has degraded performance

In 9928d34, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1540 ms

Resolved: Bofrost.de performance has improved in 03dc4d3 after 13 minutes.


SiteWhere fail install

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing 😞


fix_regression_on_modify_column

I did not analyzed the code much, it's just the minimal change that fixes the #647 and it's compatible with existing code.

Thank you for the PR. I'm wondering if we have an issue here too? https://github.com/elixir-ecto/ecto_sql/blob/373845629a6a66aabbcc5db4c1a201ccbf075d35/lib/ecto/adapters/postgres/connection.ex#L1561

Here as well: https://github.com/elixir-ecto/ecto_sql/blob/373845629a6a66aabbcc5db4c1a201ccbf075d35/lib/ecto/adapters/postgres/connection.ex#L1550
if we are allowing from: {%Reference{}, opts}

Yeah, I am afraid this is a bit too tricky to the point a separate helper may be better after all. :(

Thanks @greg-rychlewski for the review. The 2 places you marked are in the same function. I think it should be good there now

if we are allowing from: {%Reference{}, opts}

I'm not sure if this one will not crash, because the reference column type is handled differently, when wrapped in tuple then instead of returning type it will return the reference struct.
  1852     defp extract_column_type({type, _}) when is_atom(type), do: type
  1853     defp extract_column_type(type) when is_atom(type), do: type
  1854     defp extract_column_type(%Reference{type: type}), do: type

Feel free to update the pr. We should test the type system on this piece of code :D

Sorry what I meant was
defp column_change(table, {:modify, name, %Reference{} = ref, opts}) do
      reference_column_type = reference_column_type(ref.type, opts)
      from_column_type = extract_column_type(opts[:from])
      from_opts = extract_opts(opts[:from])
...

If `opts` is `from: {%Reference{}, from_opts}` then `extract_opts(opts[:from])` will return `nil` here, from what i can see

defp extract_column_type({type, }) when is_atom(type), do: type
defp extract_column_type(type) when is_atom(type), do: type
defp extract_column_type(%Reference{type: type}), do: type
defp extract_column_type(), do: nil

But I also agree with Jose this is kind of getting hairy. It's also making me wonder if it people will use it wrong without realizing

If opts is from: {%Reference{}, from_opts} then extract_opts(opts[:from]) will return nil here, from what i can see

But in this case extract_column_type will also return nil because no other pattern matches, the first one will not match because {%Reference{} = reference, _} where is_atom(reference).
Maybe using something like that is cleaner?
defp extract_column_type_and_opts({type, opts}) when is_atom(type), do: {type, opts}
defp extract_column_type_and_opts({%Reference{type: type}, opts}), do: {type, opts}
defp extract_column_type_and_opts(type) when is_atom(type), do: {type, []}
defp extract_column_type_and_opts(%Reference{type: type}), do: {type, []}
defp extract_column_type_and_opts(_), do: {nil, []}

That's a good point. I think you uncovered another potential issue.
So then the question is do we want to continue trying to make it work this way or would it be simpler to take the functionality out of modify.

I updated the pr with the code from last comment. We should decide either to merge it or revert the commit because master is broken.

I am thinking a revert is saner. Thoughts @greg-rychlewski?


MMCls is called MMPreTrain now, should change the "mmcls>xxxx" in requirements to "mmpretrain>xxxx"?

requirements/mminstall.txt & requirements/runtime.txt

Any news?

Sorry for replying late. Now both mmcls and mmselfsup are moved into mmpretrain. You can use mmpretrain directly.

thx


Update environment parameters

Someone in my team have some difficulties trying to use this doc, so a suggest this change so it can help others.

@AleCo3lho : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

Thank you for the feedback.
This issue was addressed in another commit.
#please-close


Fix ModelConverter when impl is not callable

Supersedes #177

Thanks to @okapies for raising the issue and creating the initial PR.


Update list of active IBM members

Update list of IBM members that are still active in the past year.

/cc @terrytangyuan


how do training ?

Hi,
Please give me more information about training and prepare dataset, how do apply labels for this ?
please put this walk-through steps.
thanks.

Sorry. I confirmed it a little late.
I will update the training detail in the readme.
Please check.

In my opinion, I think that there will be a lot of performance difference according to learning data.
If you have a lot of real license plate images, I think it will work well.
In addition, I know that scene text recognition models such as GRCNN, RARE, and FAN as well as CRNN works well in real environment.

GRCNN is CNN + GRU?

No!
GRCNN is Gated Recurrent Convolution Neural Network for OCR
t is similar to CRNN, but there is a difference in that certain parts of the CNN layer have been replaced by Gated Recurrent Convolution Layer.
GRCNN


Upgrade core 13.14.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 89.285%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
3133

Relevant Lines:
3509

💛  - Coveralls


Enabling/disabling Components is very slow

To uncheck Enable in the Navigator when multi-selecting all muscles takes ~45s on the drop landing model (49 muscles)  to take effect, which seems excessive. Re-enabling takes about the same amount of time. This on on recent Windows Frame Editing build running on a desktop.
See at #56.

Although this specific build was using RelWithDebugInfo native libraries which exaggerated the problem, the performance is poor on Release builds as well. Every edit goes through this hammer of initSystem, swapping states in/out in case state layout changes. If this can be avoided it will speed edits massively across the board.

Every edit goes through this hammer of initSystem, swapping states in/out in case state layout changes.

This has been known for 4yrs now, ever since we asked Kevin to make the "hammer" so that property edits are handled without error and the live model is never out-of-date. On multi-select it seems quite clear what the solution is: make all the edits first on each selected Object, then call initSystem(). Why can't that be done?


[stable/traefik] backoff storeconfig job

What this PR does / why we need it:
Adds a backoff limit to storeconfig job.
If the job starts to fail for whatever reason, it will keep going... it happened here and it launched over 6k containers in a couple of days.
Which issue this PR fixes
Special notes for your reviewer:
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @ldez

/assign @emilevauge

cc/ @ldez @dtomcej can someone take a look on this?

/lgtm

The backofflimit should be in the Job spec, or am i wrong?
I get the following error:
ValidationError(Job.spec.template.spec): unknown field "backoffLimit" in io.k8s.api.core.v1.PodSpec;

you're right, my bad, fixing

@superbarne https://github.com/helm/charts/pull/17181


Docs seem to show wrong way to use built-in modules

In the sass docs, it seems to show the wrong way to use built-in modules.
One example is the docs demonstrate the alpha method like this:
https://sass-lang.com/documentation/modules/color#alpha
@debug color.alpha(#e1d7d2); // 1

That causes the following error
SassError: Invalid CSS after "color": expected expression (e.g. 1px, bold), was ".alpha(#e1d7d2)"

When I remove the color keyword and just use the method name it works:
@debug alpha(#e1d7d2); // 1

It seems like the docs should be updated to remove module name prefix when demonstrating how to use built-in modules.
If there is something I am missing, maybe docs should be updated to explain when it's appropriate to use the module name?
node-sass version: "^4.14.1"

As per the top of that page, those are only supported in dart-sass

@nschonni That is very confusing, because the methods themselves are not only supported in dart-sass. If you are looking for documentation on how to use these methods outside of dart-sass, then the docs could easily lead you astray.

@nschonni could you update so that this line is automatically present and not revealed by a dropdown?
"Only Dart Sass currently supports loading built-in modules with @use. Users of other implementations must call functions using their global names instead."

You'd need to raise that over on the website repo https://github.com/sass/sass-site/


[Editor] Fix the CSS properties of the canvas when it's used in a stampEditor (bug 1895909)

And move the page canvas properties under canvasWrapper in order to avoid future regressions.

Can we please just revert the regression patch first, see PR #18079, so that we get back to a working state before making any further changes to this code?

I added back the display: block for the page canvas in order to avoid any confusion and @nicolo-ribaudo can make a follow-up patch to fix the zoom stuff.

/botio integrationtest

/botio-windows integrationtest

/botio-windows integrationtest

/botio-windows integrationtest

/botio-windows integrationtest

/botio-windows integrationtest

/botio-linux preview

Thank you for improving the CSS here, and adding more tests to avoid future regressions!


[Bug]AttributeError: 'ErrorResponse' object has no attribute 'model_dump'

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.

Describe the bug
model: qwen-7b-chat 微调后合并的版本 直接运行没问题, kv int8后的也是这个问题，int4目前官方支持不了
step：
1.create workspace files success
python -m lmdeploy.serve.turbomind.deploy qwen-7b  /hy-tmp/quantize/qwen1009
2.run openai success
python -m lmdeploy.serve.openai.api_server /hy-tmp/workspace  <IP_ADDRESS>  8080 --instance_num 32 --tp 1
[WARNING] gemm_config.in is not found; using default GEMM algo
INFO:     Started server process [1027762]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8080 (Press CTRL+C to quit)
3.request api error
follow error is blow
INFO:     <IP_ADDRESS>:51102 - "POST /v1/chat/completions HTTP/1.1" 500 Internal Server Error
ERROR:    Exception in ASGI application
Reproduction
1.create workspace files success
python -m lmdeploy.serve.turbomind.deploy qwen-7b  /hy-tmp/quantize/qwen1009
2.run openai success
python -m lmdeploy.serve.openai.api_server /hy-tmp/workspace  <IP_ADDRESS>  8080 --instance_num 32 --tp 1
[WARNING] gemm_config.in is not found; using default GEMM algo
INFO:     Started server process [1027762]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:8080 (Press CTRL+C to quit)
3.request api error
Error traceback
Traceback (most recent call last):
  File "/usr/local/miniconda3/lib/python3.8/site-packages/uvicorn/protocols/http/httptools_impl.py", line 426, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "/usr/local/miniconda3/lib/python3.8/site-packages/uvicorn/middleware/proxy_headers.py", line 84, in __call__
    return await self.app(scope, receive, send)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/fastapi/applications.py", line 276, in __call__
    await super().__call__(scope, receive, send)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/starlette/applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/starlette/middleware/errors.py", line 184, in __call__
    raise exc
  File "/usr/local/miniconda3/lib/python3.8/site-packages/starlette/middleware/errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/starlette/middleware/exceptions.py", line 79, in __call__
    raise exc
  File "/usr/local/miniconda3/lib/python3.8/site-packages/starlette/middleware/exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
    raise e
  File "/usr/local/miniconda3/lib/python3.8/site-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
    await self.app(scope, receive, send)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/starlette/routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/starlette/routing.py", line 276, in handle
    await self.app(scope, receive, send)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/starlette/routing.py", line 66, in app
    response = await func(request)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/fastapi/routing.py", line 237, in app
    raw_response = await run_endpoint_function(
  File "/usr/local/miniconda3/lib/python3.8/site-packages/fastapi/routing.py", line 163, in run_endpoint_function
    return await dependant.call(**values)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/lmdeploy/serve/openai/api_server.py", line 110, in chat_completions_v1
    error_check_ret = await check_request(request)
  File "/usr/local/miniconda3/lib/python3.8/site-packages/lmdeploy/serve/openai/api_server.py", line 70, in check_request
    ret = create_error_response(
  File "/usr/local/miniconda3/lib/python3.8/site-packages/lmdeploy/serve/openai/api_server.py", line 61, in create_error_response
    ErrorResponse(message=message,
AttributeError: 'ErrorResponse' object has no attribute 'model_dump'

Please update fastpi and pydantic package.

It is works!
thanks very much!


Adds option for the exposed ingress routes

The Legend Studio application typically serves on /studio, however it can serve / as well, so a 404 Error is not encountered while accessing the root URI.
However, for the Public instance we would like to route the / route to the github pages, which means that we need to be able to tune what the Legend Studio charm exposes as an ingress route.
Adds use-root-path config option (True by default). Setting it to False will result in the charm exposing the /studio ingress route instead of /.

Tested, needed to update the ingress route for Legend Studio to allow other application use the / route (e.g.: docs page).


Mounting component with props passed with spread operator doesn't work right

Current behavior
I'm trying to mount a component to make a snapshot test. When I pass component props with normal syntax, i. e.: mount(<Component randomProp={randomValue}/>) the mount work as expected and I see the full component tree in the snapshot.
However, if I'm trying to pass props with object spread operator, i. e. mount(<Component {...props}/>), instead of a full component tree in the snapshot I see only the Component with passed props: <Component randomProp={randomValue} />
Expected behavior
See the full component tree while mounting component with props passed with the spread syntax
Your environment
OS: macOS High Sierra
Node: v8.3.0
API

[ ] shallow
[X] mount
[ ] render

Version

library
version

Enzyme
3.3.0

enzyme-adapter-react-16
1.1.1

enzyme-to-json
3.3.1

React
16.2.0

Jest
22.4.2

Adapter

[X] enzyme-adapter-react-16
[ ] enzyme-adapter-react-15
[ ] enzyme-adapter-react-15.4
[ ] enzyme-adapter-react-14
[ ] enzyme-adapter-react-13
[ ] enzyme-adapter-react-helper
[ ] others ( )

enzyme doesn't have snapshot support, so I'm not sure how to interpret that part.
What is the output of mount(<Component randomProp={randomValue}/>).debug() vs mount(<Component {...{randomProp: randomValue }} />).debug()?

I'm sorry. I figure out it was totally my fault


Incorrect link to Google Cast iOS Sender Overview

Link to Google Cast iOS Sender Overview in the README file is not correct or does not exist. Please fix it.
Wrong Link: https://developers.google.com/cast/docs/ios_sender

Thanks for reporting. The link has been fixed.


Compliance Report | Adjustments to the Part 2 calculation in the summary section |3|

Task:
This card is to make some fundamental changes to the Part 2 Summary section as it relates to Schedule C.
Schedule C Part 2 requirement:
Currently, if a fuel supplier reports Petroleum-based diesel with an expected use of heating oil it is included in the appropriate cells of the Part 2 summary section. We need to expand this section by including all Part 2 fuels reported in Schedule C regardless of expected use.
Line 1 - Volume of petroleum-based gasoline supplied:

This line currently displays the total volume of petroleum-based gasoline reported in Schedule B.
Schedule B: Fuel Type = Petroleum-based gasoline
This line needs to display the total volume of petroleum-based gasoline reported in Schedule B and Schedule C.
Schedule B and C: Fuel Type = Petroleum-based gasoline

Line 2 - Volume of gasoline class renewable fuel supplied:

This line currently displays the total volume of Part 2 renewable fuel supplied within the gasoline class, as reported in Schedule B.
This line needs to display the total volume of Part 2 renewable fuel supplied within the gasoline class as reported in Schedule B and Schedule C.
Renewable fuel supplied within the gasoline class includes ethanol and renewable gasoline. Schedule B and C: Fuel Type = Ethanol or Renewable gasoline.

Line 12 - Volume of petroleum-based diesel supplied:

This line currently displays the total volume of petroleum-based diesel reported in Schedule B and reported in Schedule C with the expected use of Heating Oil.
Formula is Schedule B: Fuel Type = Petroleum-based diesel + Schedule C: Fuel Type = Petroleum-based diesel and expected use of "Heating Oil".
This line needs to display the total volume of petroleum-based diesel reported in Schedule B and Schedule C, regardless of expected use.
Formula is Schedule B and C: Fuel Type = Petroleum-based diesel.

Line 13 - Volume of diesel class renewable fuel supplied:

This line currently displays the total volume of Part 2 renewable fuel supplied within the diesel class, as reported in Schedule B. It also includes diesel class renewable fuel supplied for Heating Oil, as reported in Schedule C.
For Schedule B, renewable fuel supplied within the diesel class includes biodiesel, HDRD, and Renewable Diesel. Fuel Type = Biodiesel or HDRD or Renewable Diesel.
For Schedule C, renewable fuel supplied within the diesel class includes biodiesel, HDRD, and Renewable Diesel regardless of expected use. Fuel Type = Biodiesel or HDRD or Renewable Diesel.

https://trello.com/c/XLkQ0wHt/2031-compliance-report-adjustments-to-the-part-2-calculation-in-the-summary-section-3

 Compliance Report | Adjustments to the Part 2 calculation in the summary section |3|


Arguments are validated if help or version is used and exitProcess=false

Fixed and explained in PR 271.

As a workaround, I'm currently overriding showHelp and throws an exception after printing the help.
try

    origShowHelp = yargs.showHelp
    yargs.showHelp = () ->
        origShowHelp.apply(yargs, arguments)
        throw new Error('showed help')

    argv = yargs.argv

    # other stuff here

catch err
    if err.message == 'showed help'
        # not really an error, so do nothing
        return

    # really errors handling

@tepez Thanks again for your contributions! Would you mind giving 3.27.0 a test drive to verify this issue has been fixed? Then we can safely close this out.

@nexdrew my pleasure, and thank you for maintaining this great package.
I've just updated to 3.27.0 and all my units tests are passing.


need a new release..

you have a very important fix merged at february 2014, however 0.0.2 - your latest release was on january 2014..
you should have a new version released. it is a crucial bug regarding -- completion.
I just spent 2 hours from my life hacking through it until I noticed someone fixed it.
BTW - cool library! why did you stop deveoping it? there's more potential - like integration with commander library..
thanks.

Hi @GuyMograbi
Sorry for that. I just published a new version.


Bundle development

resolution_fixed   |    by<EMAIL_ADDRESS>
Ben called to tell me that Chris was having issues with his 'bundle' development, where changes we're making are conflicting with changes he's making.
In the first instance I think this will be helped by more communication about what we're doing, I'll add Chris to the trac mailing list so he has an idea of where our development is going

Issue migrated from trac:65 at 2024-01-31 17:14:35 +1100

<EMAIL_ADDRESS>commented

The changes relating to bundles were from setting up vnc and openbox. I copyed the nci desktop bundle (as it was in december last year) and a few other necessary packages ( vnc, xterm, yum_groupinstall ) from the nci puppet repository, then adding the openbox-desktop as a project bundle.
See changesets:
changeset:bc69effe8e98ffd2fc53ead2cdc78ecf34a01f28/puppet
changeset:b86686a4343c0c61f3ddc98a3e5ff1b86ee4b45e/puppet
Let me know if I can do anything to help resolve these conflicts.

<EMAIL_ADDRESS>commented

I've added Chris to the trac CC list so he's able to see what we're working on.
Chris would you be able to outline the current conflicts with your bundle system?

<EMAIL_ADDRESS>changed _comment0 which not transferred by tractive

<EMAIL_ADDRESS>commented

You can add /puppet to the revision to get changesets to link properly in trac, e.g. changeset:bc69effe8e98ffd2fc53ead2cdc78ecf34a01f28/puppet

<EMAIL_ADDRESS>commented

Thanks Scott, I've done that now

<EMAIL_ADDRESS>changed _comment1 which not transferred by tractive

<EMAIL_ADDRESS>changed status from new to assigned

<EMAIL_ADDRESS>changed priority from major to blocker

<EMAIL_ADDRESS>commented

My point was simply that "accessdev" is not currently using our baseline Puppet framework which means we have to spend time backporting and testing any fixes that are requested.  I guess at some point we'll have to migrate "accessdev" onto that framework since it will become infeasible (if not already) to continue backporting stuff, but there will definitely be conflicts where you've implemented OS level configurations that the framework already provides; eg. firewall configuration just to name a simple example.

<EMAIL_ADDRESS>changed milestone from Future to accessdev v1.0

<EMAIL_ADDRESS>commented

Accessdev forked from the NCI puppet over a year ago, the problems in moving modules between them are undoubtedly unavoidable at this stage.
I see two main issues if we were to combining the forks - there's no clear boundary between accessdev and NCI development, and there's a lack of communication on what both sides are doing.
This would probably be better off left to a meeting, a couple questions I'd like us to have (documented!) answers to are:

How do the NCI and accessdev repos relate?

Is NCI an upstream of accessdev?
Is accessdev a module that gets plugged in to the NCI repo, only setting up rose, umui, etc?
Is NCI a module that gets plugged in to the accessdev repo to set up LDAP, mail relay, etc?

How do changes from NCI get into accessdev?

Are there documented releases from NCI that we can pull from?

How do we request & keep track of changes in the NCI repo?

This trac site is becoming very useful for our development, should there be a similar setup for NCI's side?

<EMAIL_ADDRESS>commented

Putting what we discussed on 4/2 in writing (at least what I recall from it, feel free to correct) -
The NCI repository will be an upstream of accessdev - NCI will tag stable versions in their repository and ask us to pull from those.
NCI intend to put up some form of developer site to host documentation for the cloud systems
ETA for a stable v1.0 of the NCI bundles is 3-4 weeks (i.e. early march)
The NCI repository will handle low-level infrastructure common to anyone running at the NCI cloud site such as:

LDAP
Firewall
Mail
/g/data1 mounts
Logging to shared infrastructure
etc.

I'd assume that our expectations of the NCI repository are (again I'd welcome input from others):

NCI releases are stable & tested
Releases will be documented (change logs, user guides etc.)
NCI are responsible for any issues related to their modules & will provide an issue tracker (e.g. RT, trac.nci, etc) where we can submit bugs & feature requests
Documented ways will be provided for us to hook into the NCI module's functionality so we can create our services (e.g. functions to open a firewall port, Puppet variables containing LDAP details for hooking up services etc.)

I understand that Chris will be doing the initial integration of accessdev with the NCI repository, I'd expect that after that the integration work will be minimal & can be left to the accessdev group. Updates would hopefully be backwards compatible & follow semantic versioning (i.e. updating from NCI 1.0 to 1.1 shouldn't require changes on our end unless we want to make use of new functionality)

<EMAIL_ADDRESS>changed owner from `` to cma900

<EMAIL_ADDRESS>commented

Yep, that pretty much sums it up I think.
We will be testing the core framework in itself, however while we'll obviously take as much care as we can to keep things stable (at least during minor releases), it probably won't be practical for us to test integration into every downstream project especially since we aren't experts in each project's specialised applications.  Also, due to the nature of Puppet's design, there's always the risk that namespace conflicts may inadvertently occur as well.  For these reasons and as general best practice, we'll be advising that new versions should be pulled into a test branch first and thoroughly tested in the project before deploying into production.  We will also be staging changes that haven't been published yet in a separate branch which you will of course be more than welcome to pull from for pre-release testing and feedback.

<EMAIL_ADDRESS>commented

Milestone accessdev v1.0 deleted

<EMAIL_ADDRESS>changed status from assigned to closed

<EMAIL_ADDRESS>removed milestone (was accessdev v1.0)

<EMAIL_ADDRESS>changed component from accessdev server to NCI Puppet

<EMAIL_ADDRESS>changed resolution from `` to fixed


The menu

~I don't think that this is ready to merge, but I wanted to get feedback on where I am to see if you all like the direction I'm taking.~ This branch has been updated with early feedback and is stable and ready for review. I've updated the test below to indicate changes made.
The program displays a menu allowing the user to select the program that they'd like. Upon selection, the menu's handlers are cleared and new handlers are added to detect the exit command. Then the selected program is imported. ~The menu thread hangs around waiting for the exit command. Its impact should be minimal as it's using an ``Asyncio.Event`~ Asyncio is no longer used. No thread is created. A normal button handler is used to detect the exit request.

~This approach forces script authors to use some asyncio code in their scripts. I believe that the impact is minimal and I've documented the requirements thoroughly.~ In addition I've provided an example hello_world.py  which can serve as a reference as well as a starting point for new scripts.
I've updated all of the scripts except consequencer to support the menu. The changes were minimal, despite what the diffs look like. I'm happy to put each of the script's changes in their own PR if you think it make more sense to discuss them individually.
The 'copy all the code to the pico' problem isn't really solved, but I'm hoping that issue #71 makes it much easier. (it has)
~The classes LongPressAndTapButton and Menu are written to be abstract enough to be used elsewhere. If we find another place to use them they should be moved to europi.py~ LongPressAndTapButton has been removed and Menu has been put into the new ui.py module in firmware.

Known remaining work:

~save state so that the menu automatically loads the last running program~
~update the consequencer~
~a couple small TODOs~
~document that reset_state() shouldn't be called in scripts~

Made the following changes:

remove asyncio
renamed menu.py to bootloader.py and put it in with the firmware
moved the Menu class to a new ui.py module in firmware
removed the LongPressAndTapButton class, added long both button support to europi.py
added the EuroPiScript base class to firmware and updated all scripts to use it

Open work:

update all docs with the above changes
make sure it all works with the new packaging

Excellent work here! I'm excited for the improvements this change will bring.


some chromosomes were grouped together, or the maximum number of clusters is even less than the expected number of chromosomes.

RuntimeError: Pipeline Abortion: Inflation recommendation failed. It seems that some chromosomes were grouped together, or the maximum number of clusters is even less than the expected number of chromosomes. For more details, please check out the logs.

Please see our document, FAQ and this issue before asking questions.

Sorry, I just noticed, thank you so much for your quick reply!


Child Nodes are not placing inside Parent Node.

while trying to draw Parent and child nodes, some of the child nodes are not placing inside the Parent node. Please check the attached screenshot and sample html code to reproduce the issue.

Is this a Netron issue or are you trying to write custom code using dagre?
Can you share the model file?

I have modified the Netron code and trying to implement Clusters concept. In Netron code it has been already implemented partially, and same code I have modified. I Think the issue is with Dagre. I have created issue in Dagre repo also.
Thank you


Reexport flate2's rust_backend and zlib features

Why is this needed? Is it not sufficient to run with --features flate2/zlib? Or are there other cases where such a flag is not possible?

The flag works for zip-rs but not for a crate that depends on zip-rs.
In other words, a crate cannot set the features of a dependency of a dependency (unless the dependency re-exports its dependency's features).

I have choosen to merge #73 instead, but thank you for the contribution!


[Bug] Make sure cache is properly loaded in the GitHub Workflow

Env job is properly working but when using the other jobs like test and build, cache is "loaded" but is not reflected in pip environment.
Make sure pip is properly using the cache so the jobs take less time overall.

Test to do with following solution :
https://adamj.eu/tech/2023/11/02/github-actions-faster-python-virtual-environments/
# ...

jobs:
  example:
    # ...

    steps:
      # ...

      - uses: actions/setup-python@v5
        id: setup_python
        with:
          python-version: '3.12'

      - name: Restore cached virtualenv
        uses: actions/cache/restore@v4
        with:
          key: venv-${{ runner.os }}-${{ steps.setup_python.outputs.python-version }}-${{ hashFiles('requirements.txt') }}
          path: .venv

      - name: Install dependencies
        run: |
          python -m venv .venv
          source .venv/bin/activate
          python -m pip install -r requirements.txt
          echo "$VIRTUAL_ENV/bin" >> $GITHUB_PATH
          echo "VIRTUAL_ENV=$VIRTUAL_ENV" >> $GITHUB_ENV

      - name: Saved cached virtualenv
        uses: actions/cache/save@v4
        with:
          key: venv-${{ runner.os }}-${{ steps.setup_python.outputs.python-version }}-${{ hashFiles('requirements.txt') }}
          path: .venv

      # ...


Added /hw-transport-ios-ble

📝 Description
This is the Transport extension which makes it possible for the Swift Native Module to interact with the app bindings.
❓ Context

Impacted projects: Connect
Linked resource(s): Trello ticket

✅ Checklist

[ ] Test coverage
[X] Atomic delivery
[X] No breaking changes

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

@gre letting you handle this one as you may have more context.


[AgriFood] Adding 2021-07-31-preview API version

Data Plane API - Pull Request
Adding new 2021-07-31-preview API version
API Info: The Basics
Private repo PR - https://github.com/Azure/azure-rest-api-specs-pr/pull/8244

Link to engagement record issue:

Is this review for (select one):

[x] a private preview
[ ] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous Open API document (swagger) if applicable, and the root paths that have been updated.

Design Document:
Previous Open API Doc:
Updated paths:

❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Azure DevTools Wiki

@bhargav-kansagara I believe this PR is simply establishing the basis for a public preview in the near future, and that the changes requested in the internal repo PR #8244 will be addressed in the PR for the public preview. Can you please confirm?
If this understanding is correct I am fine with merging this PR and deferring a full review for the PR for public preview.

@mikekistler Yes that is correct, we will address all the comments as part of the next API version (Nov 2022) and schedule a new review as well.

Breaking change: Expected and already communicated to customers
LintDiff: Model is dependent on partner services' request & response and not controlled by us
SemanticValidation: Getting errors for form-data type, only getting reported in older version of oav, link to issue raised - https://github.com/Azure/azure-rest-api-specs-pr/issues/8678


chore: Remove arbitary comments from examples files

Those comments are outdated

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Ant sacrifice visible without r5x24

Whoops, submitted without content.
At least on the Kongregate version, on Chrome or Firefox on Ubuntu, the automatic ant sacrifice UI is visible but nonfunctional without the relevant research.

Hello,
Is this a persistent bug in the testing version?

By testing version do you mean a recent commit here that maybe hasn't been deployed to Kongregate? No idea; if you can give me the commit hash most recently deployed to Kongregate I can both test the current repo head and, if it happens to have been resolved incidentally, I can git bisect.

To determine if it is a bug on the test version:

Come to this game link: https://pseudo-corp.github.io/SynergismOfficial/
Import the savefile that has this bug

Visually, it should not display ant sacrifice before it is unlocked.

Yup, it's bugged at that link as well. Savefile attached.
Synergism-v2.1.2-2021-04-04 23_13_13.txt

I proposed a fix for this bug in the live version some time ago: https://github.com/Pseudonian/SynergismOfficial/pull/249
The check to display or not the auto sacrifice buttons was accidentally removed when the checks for the display of the talisman auto enhance / fortify buttons were introduced.
To patch v2.5, pasting the same 3 lines of code in UpdateHTML.ts around line 246 should be good:

I proposed a fix for this bug in the live version some time ago: Pseudonian/SynergismOfficial#249
The check to display or not the auto sacrifice buttons was accidentally removed when the checks for the display of the talisman auto enhance / fortify buttons were introduced.
To patch v2.5, pasting the same 3 lines of code in UpdateHTML.ts around line 246 should be good:

Fixed, thanks.
Live version probably won't be getting any updates until v2.5.0 is ready, unless @Pseudonian is up to it.


feat: check handle step.

Make it possible to interrupt the handleStep to navigate to next step.

Is there a release date also for this by chance?
Thanks

Are there any plans to support such functionality?  @devrnt

Throwing error within handler just for the sake of stopping nextStep() feels counter intuitive.

Indeed, this feels a bit off at the moment

Actual handling of such error that has been thrown from handleStep() is not documented at all. Yes, it is easy to make the connection between handleStep() and nextStep(), however, it would help a lot if it were to be documented.

You're right, there is only one mention in the docs at the moment, are you willing to pick this up?

You're right, there is only one mention in the docs at the moment, are you willing to pick this up?

I am willing to pick this up.

I am also looking at this feature.

I've noticed this pr only after leaving the following comment (which is weirdly not linked): https://github.com/devrnt/react-use-wizard/issues/74#issuecomment-1731210574
I gotta say that throwing is perfectly fine, it just needs a mention on the docs.

Closing because already possible with the current API


Update vue-loader to 13.x for postcss-cssnext support

The feature postcss-nesting which is included in cssnext needs at least version 6.x of postcss to be installed. Vue-loader in the current vue-cli is on version 12 which uses postcss 5.x.

Please open the issue on the relevant template, I think you're looking for https://github.com/vuejs-templates/webpack/


Adding url as property to query, test

Addresses issue #225

Not sure whether it should be merged to official master.

Does this cause issues?  May I ask why it wouldn't make sense in the master?

I don't think it is so evital for everyone, and as it is private it can be changeabl in future. You can patch in your folk.


SIGSEV on reconciling temporal worker process

Hi,
I am getting following error on reconciling Temporal worker process resource.
1.6692205965847738e+09  INFO    Observed a panic in reconciler: runtime error: invalid memory address or nil pointer dereference        {"controller": "temporalworkerprocess", "controllerGroup": "temporal.io", "controllerKind": "TemporalWorkerProcess", "TemporalWorkerProcess": {"name":"test","namespace":"dev-stage"}, "namespace": "dev-stage", "name": "test", "reconcileID": "49490e44-9277-4f1d-972c-5c2288ffb791"}
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1c0a7e6]

Please see full log and my manifests in the attachment.
Thanks,
Premek
temporallogs.tar.gz

Hi @remeq!
Thanks for the report!
According to the log, there is a bug on the operator side. I know how to fix it and I'll do it ASAP.
This bug can be mitigated by settting the spec.builder.attempt field, like that:
apiVersion: temporal.io/v1beta1
kind: TemporalWorkerProcess
metadata:
  name: test
spec:
  # [...]
  clusterRef:
    name: prod
    namespace: demo
  temporalNamespace: default
  # [...]
  builder:
    attempt: 1 # <-- This is the fix

cc @ktenzer

@alexandrevilain
would you have an example of full, working  spec.builder spec ? With provided fix it started crashing somewhere else in the code:
1.669302070867436e+09   INFO    Observed a panic in reconciler: runtime error: invalid memory address or nil pointer dereference        {"controller": "temporalworkerprocess", "controllerGroup": "temporal.io", "controllerKind": "TemporalWorkerProcess", "TemporalWorkerProcess": {"name":"test","namespace":"dev-stage"}, "namespace": "dev-stage", "name": "test", "reconcileID": "352594d7-71ae-4858-99d0-053d246858c3"}
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x1c1b2f2]

goroutine 1214 [running]:
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile.func1()
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:118 +0x1f4
panic({0x1dea040, 0x362f4e0})
        /usr/local/go/src/runtime/panic.go:838 +0x207
github.com/alexandrevilain/temporal-operator/controllers.(*TemporalWorkerProcessReconciler).reconcileDefaults(0x0?, {0x0?, 0x0?}, 0xc0009f0540)
        /workspace/controllers/temporalworkerprocess_controller.go:228 +0x92
github.com/alexandrevilain/temporal-operator/controllers.(*TemporalWorkerProcessReconciler).Reconcile(0xc0009722a0, {0x25cffd8, 0xc000e61ec0}, {{{0xc000841da0?, 0x10?}, {0xc000841d98?, 0x40d7a7?}}})
        /workspace/controllers/temporalworkerprocess_controller.go:79 +0x1bb
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile(0x25cff30?, {0x25cffd8?, 0xc000e61ec0?}, {{{0xc000841da0?, 0x1fa0460?}, {0xc000841d98?, 0x4041f4?}}})
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:121 +0xc8

Wow so much bugs ... I'm sorry about that.
It's because it's missing a gitRepository.
apiVersion: temporal.io/v1beta1
kind: TemporalWorkerProcess
metadata:
  name: test
spec:
  # [...]
  clusterRef:
    name: prod
    namespace: demo
  temporalNamespace: default
  # [...]
  builder:
    attempt: 1 # <-- This is the fix
    gitRepository:
      url: https://my-repo.com

FYI I'm starting to work on a better workerprocess builder implementation.

Oh ... Are you just trying to use the WorkerProcess and not the builder ?

Yep sorry for these bugs this was my bad.
First there are two ways to use temporalworkerprocess 1) you can just point it at an image and it will deploy that image. In this case you would change the version which is the version of your docker image and it would deploy new image. 2) you can point it at a git repo and it will build the provided Dockerfile, push it to your repo and then deploy it. If you change the version or buildAttempt it will force a new build, push, deploy.
The idea is you would have some CI upon checking into your git repo (git actions or something) and then operator would manage CD part. We have plans to integrate with some webhooks but today you need to change either version or buildAttempt to redeploy.
This is example of a spec which would be option 1:
spec:
  clusterRef:
    name: prod
    namespace: temporal
  image: ktenzer/helloworld-worker
  jobTtlSecondsAfterFinished: 300
  pullPolicy: Always
  replicas: 3
  temporalNamespace: default
  version: v1.0

This is example of a spec which would be option 2:
spec:
  builder:
    attempt: 3
    buildDir: samples-go/helloworld
    buildRegistry:
      passwordSecretRef:
        key: PASSWORD
        name: docker-password
      repository: docker.io
      username: ktenzer
    enabled: true
    gitRepository:
      reference:
        branch: main
      url: https://github.com/ktenzer/samples-go.git
    image: quay.io/podman/stable
    version: latest
  clusterRef:
    name: prod
    namespace: temporal
  image: ktenzer/helloworld-worker
  jobTtlSecondsAfterFinished: 300
  pullPolicy: Always
  replicas: 3
  temporalNamespace: default
  version: v1.0

Let me know if this helps?

@alexandrevilain No problem at all, I understand this is WIP.
I am just trying to set up some basic "hello world" -  I want to deploy Temporal Worker Process from the example shown here: https://github.com/alexandrevilain/temporal-operator/tree/main/examples/cluster-postgres
I haven seen the "builder" part nowhere in the examples so I am not sure if I generally need  it (at least for some basic hello world)

@ktenzer no problem thanks. Is there any workaround if I want to get option 1 running before fix will be available?

@remeq You should be able to just set enable: false under builder. Then it will deploy the image, in example below it would be ktenzer/helloworld-worker:v1.0. Let me know if that works?
spec:
builder:
attempt: 3
buildDir: samples-go/helloworld
buildRegistry:
passwordSecretRef:
key: PASSWORD
name: docker-password
repository: docker.io
username: ktenzer
enabled: false
gitRepository:
reference:
branch: main
url: https://github.com/ktenzer/samples-go.git
image: quay.io/podman/stable
version: latest
clusterRef:
name: prod
namespace: temporal
image: ktenzer/helloworld-worker
jobTtlSecondsAfterFinished: 300
pullPolicy: Always
replicas: 3
temporalNamespace: default
version: v1.0

@ktenzer yes, thanks, it seems to work now - the operator now started provisioning workers

@remeq awesome yeah we will fix this its just a minor thing with the optional parameters not being optional

@remeq maybe there was issue with the image. I repushed it and tested and it works using latest. Can you try below spec?
kind: TemporalWorkerProcess
metadata:
  name: test
spec:
  builder:
    attempt: 3
    buildDir: samples-go/helloworld
    buildRegistry:
      passwordSecretRef:
        key: PASSWORD
        name: docker-password
      repository: docker.io
      username: ktenzer
    enabled: false
    gitRepository:
      reference:
        branch: main
      url: https://github.com/ktenzer/samples-go.git
    image: quay.io/podman/stable
    version: latest
  clusterRef:
    name: prod
    namespace: temporal
  image: ktenzer/helloworld-worker
  jobTtlSecondsAfterFinished: 300
  pullPolicy: Always
  replicas: 3
  temporalNamespace: default
  version: latest```

@ktenzer yes, thanks this seems to be working if I set following on the TemporalCluster:
  mTLS:
    provider: cert-manager
    internode:
      enabled: false
    frontend:
      enabled: false

It doesn't work when I enable mTLS, so I am supposing your example works only with mTLS disabled, correct?

@remeq The temporalworkerprocess does not yet support mtls so you need to have it disabled,

Hi @remeq, @ktenzer, @rawcode
The PR fixing this issue is now merged, I'll release v0.10.0 during the day. I'll ping you once available.
Please note that v0.10.0 now requires cert-manager on the cluster.

Hi all,
Release v0.10.0 is now available 🎉.
If some of you find time to check if everything is fixed, that would be nice :)

Hi @remeq, @ktenzer, @RawCode The PR fixing this issue is now merged, I'll release v0.10.0 during the day. I'll ping you once available. Please note that v0.10.0 now requires cert-manager on the cluster.

Awesome, thank you very much, will check it out once we will be doing redeployment and will report back

@alexandrevilain This works when we create a new Temporal cluster, but the upgrade from the old release to the new breaks.
I don't have the exact error message any more, I failed to keep it during debugging. But it said something like "Cluster information was duplicated"

Oh, I need to check that.
Could you please give me more context ?

To reproduce, deploy the Operator (0.9) and add a cluster. My Cluster resource was:
new kubernetes.apiextensions.CustomResource("temporal-cluster", {
	apiVersion: "temporal.io/v1beta1",
	kind: "TemporalCluster",
	metadata: {
		// We call this temporalio to avoid conflicts during the UI config rendering.
		// The temporalio/ui container uses `TEMPORAL_UI_PORT` to configure the listening
		// port, which causes a collision with any service called temporal-ui.
		// Let's avoid that
		name: "temporalio",
	},
	spec: {
		version: "1.18.5",
		numHistoryShards: 1,
		jobTtlSecondsAfterFinished: 300,
		persistence: {
			defaultStore: {
				sql: {
					user: postgreSQLUsername,
					databaseName: postgreSQLUsername,
					pluginName: "postgres",
					connectAddr: `${postgreSQLClusterName}-rw:5432`,
					connectProtocol: "tcp",
				},
				passwordSecretRef: {
					name: secret.metadata.name,
					key: "password",
				},
			},
			visibilityStore: {
				sql: {
					user: postgreSQLUsername,
					databaseName: `${postgreSQLUsername}_visibility`,
					pluginName: "postgres",
					connectAddr: `${postgreSQLClusterName}-rw:5432`,
					connectProtocol: "tcp",
				},
				passwordSecretRef: {
					name: secret.metadata.name,
					key: "password",
				},
			},
		},
		mTLS: {
			provider: "cert-manager",
			internode: {
				enabled: true,
			},
			frontend: {
				enabled: true,
			},
			certificatesDuration: {
				rootCACertificate: "2h",
				intermediateCAsCertificates: "1h30m",
				clientCertificates: "1h",
				frontendCertificate: "1h",
				internodeCertificate: "1h",
			},
			refreshInterval: "5m",
		},
		ui: {
			enabled: true,
		},
		admintools: {
			enabled: true,
		},
		metrics: {
			enabled: true,
			prometheusConfig: {
				listenPort: 9090,
			},
		},
	},
});

I then upgraded to the latest release of the operator and the error was present.
I'll see if I can find some time today to downgrade and try the upgrade again.

Thanks! Do you have the error message ?

Hi @rawkode !
I created a brand new kubernetes cluster, with cert-manager.
Then I installed temporal-operator v0.9.1 using:
k apply -f https://github.com/alexandrevilain/temporal-operator/releases/download/v0.9.1/temporal-operator.crds.yaml
k apply -f https://github.com/alexandrevilain/temporal-operator/releases/download/v0.9.1/temporal-operator.yaml

Then I created the exact same cluster than you (using mTLS). I had an issue with the following part:
metrics: {
	enabled: true,
	prometheusConfig: {
		listenPort: 9090,
	},
},

I had to replace with:
metrics: {
	enabled: true,
	prometheus: {
		listenPort: 9090,
	},
},

Then I upgraded temporal-operator to v0.10.0 :
k apply -f https://github.com/alexandrevilain/temporal-operator/releases/download/v0.10.0/temporal-operator.crds.yaml
k apply -f https://github.com/alexandrevilain/temporal-operator/releases/download/v0.10.0/temporal-operator.yaml

Everything worked well.
Did you remember to update CRDs ?

I close the issue for now.
Don't hesitate to create a new one with steps to reproduce the issue.


RC v2.20.6 | Payments v2

Description
A couple of commits has been cherry-picked from master to update the target sdk version to 28 as per Google Play enforcement for App Updation.

Closing in favor of https://github.com/edx/edx-app-android/pull/1378


chore: bump google.golang.org/protobuf from 1.30.0 to 1.33.0

Fixes https://github.com/Azure/gpu-provisioner/security/dependabot/5

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.38%. Comparing base (db934fe) to head (257b8e8).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #103   +/-   ##
=======================================
  Coverage   77.38%   77.38%
=======================================
  Files           3        3
  Lines         252      252
=======================================
  Hits          195      195
  Misses         56       56
  Partials        1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Scroll position is shared between feeds

Steps to Reproduce

Identify two feeds with a sufficient number of articles to fill past the screen
Open the articles list for the first feed, and scroll somewhere down the list
Switch to the other feed; the scroll position will be the same as in the previous feed

Expected behavior
Two possible intuitive implementations for the user:

Each feed has an individually-saved scroll position, which isn't based on the previous one
The scroll position is reset every time you switch feeds

Screenshots or screen recording
The following screen recording uses "Unread" feeds sorted with oldest articles first as example, but the same occurs in the "All" feeds section.
https://github.com/user-attachments/assets/28c60f57-f0ec-41b4-ae05-3f34ec5f76b5
Device, Operating system, and app version
REDMAGIC 9 Pro, Android 14, Capy Reader 2024.11.1078-dev (latest from GitHub)

Thanks @Philippe-Choquette. This has been a bug since Capy started. It's caused by the fact that, behind the scenes, the list is shared between all pages and the filter changes between each.
I remember running into issues trying to solve it several months ago, but I want to fix it since it is very unexpected.

Hi @jocmp - the latest update is much better now. On unread though it jumps the feed around when you have 'mark as read on scroll' enabled. I would have expected it not to change what's on screen when I've paused scrolling.

https://github.com/user-attachments/assets/656c61de-a3bd-412a-b133-b72cc8a5758a

@jstride sorry for that. I pulled the latest release and I'll push up a fix asap, hopefully tomorrow.

A fix is live in 2024.12.1080-dev for the unread mark-as-read bug. This retains the initial fix for reseting the scroll position. @jstride or @PhilC813 feel free to reopen this or start a new issue if you see anything wrong. Thanks!


Excludes for variable-name

I have a variable in my app that comes from a third party and needs to be named a certain way. Would it be possible to add the ability to exclude a certain variable name? Like,
"variable-name": [true,
    "TheVarName",
],

Or something like that?

You can insert rule exclusions in your code using comments
/* tslint:disable: name-of-rule-to-disable */
yourCodeHere
/* tslint:enable */

Yes but in my case it's a service I import in multiple controllers and I don't want to litter my codes with comments like that, it would be way easier to ignore it globally. If the syntax is the issue then maybe an object (which would be clearer anyway than the array thing used currently):
"variable-name": {
  enabled: true,
  ignore: ['TheVarName'],
},

What's the exact code this rule is failing on? Are you re-declaring the variable? If it's provided by a third party library, shouldn't it be declared outside of the code you're linting?

It's an Angular service I'm injecting so the variable name has to match the service name registered on the container by the third party

ah, ok. This is similar to #457. Do you have use cases where the injected variable is used as something other than a constructor? Meaning, if we resolve #457, would that satisfy your use case completely?

Hm I think it might, not sure, it's a factory. Here's my code dumbed down:
class MyClass {
  constructor(public Flash: Flash) {}

  someMethod() {
    this.Flash.create('success', 'The message');
  }

Even with #577 implemented, that still doesn't address variables from third party libs which are declared as interfaces instead of classes. So I agree we should implement excludes for the variable-name rule.

Another example of when this comes up is using stateless functional components in react.
export const Example: React.SFC<{}> = () => <div />;

With the current rule, this variable name doesn't pass the lint check, but React requires that custom components including SFCs be capitalized.

The SFC is what hits us at the moment. I think that maybe only classnames should be PascalCase and one should explicitely do it like this:
const example = ...
export {example as Example}
Any more thoughts on this?

We have also run into this issue at my work place, we do not use snake_case variables but have multiple data base columns that are snake_case and therefore violate the rules. The solution outlined in the original post (or something similar) would solve this for us because we know exactly what we want to allow.

☠ TSLint's time has come! ☠
TSLint is no longer accepting most feature requests per #4534. See typescript-eslint.io for the new, shiny way to lint your TypeScript code with ESLint. ✨
It was a pleasure open sourcing with you all!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋


WIP: initial install for containerized proxy

Signed-off-by: Ricardo Mateus<EMAIL_ADDRESS>What does this PR change?
install needed packages for containerized proxy

As initial PR, looks good.
But I guess we will need to also support the possibility to have the services enabled and started, not only have the packages installed.
And for that, I think better we handle with two parameters.

So we have the possibility in our tests to have all necessary packages installed, but the service stopped.
We have the possibility in demos or developments to have the containerized proxy service enabled and started, and for that we need to also change the default ssh port of the VM, as I do in the tests:sed -i.bak -Ee 's/^#?Port\s+[0-9]*$/Port #{port}/g;' /etc/ssh/sshd_config
systemctl restart sshd

end

I need to think about the auto configuration, since we need to get the server up and running, to get the configuration zip file. I would let it automate for latter, when we have a clear picture for it


Running here, the process is killed

DEBU[2021-06-03T16:50:46+08:00] kademlia pruned peer from address book "5ff37907e4eace8f1e89d17819a5093bef99406b2276536e5c0d399200520d8c"
DEBU[2021-06-03T16:50:46+08:00] kademlia: peer not reachable from kademlia "[Underlay: /ip4/<IP_ADDRESS>/tcp/1634/p2p/16Uiu2HAmRvFC2vKsnVHWLDZJzhMP19W4eRnwimsmq7qyjq65KXFo, Overlay 5ff37907e4eace8f1e89d17819a5093bef99406b2276536e5c0d399200520d8c, Signature 35cf2ccd8aa442d293455db7b93760d909f38d7190089353d5f0f180332deb8f1acd095802c73f4dc5cdc0c59c71c93ac0e84852c8c82591e87c151f4c49bc421c]": context deadline exceeded
WARN[2021-06-03T16:50:46+08:00] peer not reachable when attempting to connect
TRAC[2021-06-03T16:50:46+08:00] kademlia: connector took 5.489756778s to finish: old depth 0; new depth 0
DEBU[2021-06-03T16:50:46+08:00] kademlia manage loop exited
WARN[2021-06-03T16:50:51+08:00] puller shutting down with running goroutines
INFO[2021-06-03T16:50:51+08:00] kademlia shutting down
INFO[2021-06-03T16:50:51+08:00] kademlia persisting peer metrics
Running here, the process is killed

same as #1947

there's not enough information here. If the problem persists please open a new issue and kindly follow our issue template


docker machine 0.2.0 amazonec2 driver cannot run in AWS China(cn-north-1)

is there something wrong with cn-north-1 region URL?
hi. I execute the command and return an error:
docker-machine create --driver amazonec2 --amazonec2-region=cn-north-1 --amazonec2-root-size=5 --amazonec2-vpc-id=vpcxxxx --amazonec2-subnet-id=subnetxxxxx --amazonec2-access-key= --amazonec2-secret-key= --amazonec2-ami=ami-fe7ae8c7 --amazonec2-zone=a --amazonec2-security-group=docker-machine --swarm --swarm-master --swarm-discovery token://d270bd78882e04e1ee987de3f7270db6 swarm master
client encountered error while doing the request: Get https://ec2.cn-north-1.amazonaws.com/?Action=DescribeKeyPairs&Version=2014-06-15: dial tcp: lookup ec2.cn-north-1.amazonaws.com: no such hostERRO[0000] Error creating machine: Problem with AWS API call: client encountered error while doing the request: Get https://ec2.cn-north-1.amazonaws.com/?Action=DescribeKeyPairs&Version=2014-06-15: dial tcp: lookup ec2.cn-north-1.amazonaws.com: no such host
WARN[0000] You will want to check the provider to make sure the machine and associated resources were properly removed.
FATA[0000] Error creating machine
Thanks.

That doesn't look like a valid endpoint.  http://docs.aws.amazon.com/general/latest/gr/rande.html#ec2_region
Please re-open if this isn't correct.  Thanks!

Hi, BOSS~
cn-north-1 (a or b) is a Isolated Region, so URL may be different.
http://docs.aws.amazon.com/general/latest/gr/isolated_regions.html
Thanks.

The correct endpoint is ec2.cn-north-1.amazonaws.com.cn
Reference: http://docs.amazonaws.cn/en_us/general/latest/gr/rande.html#cnnorth_region


[Event Parameter Change] Codeunit 5751 - Get Source Doc. Inbound - procedure OpenWarehouseReceiptPage - event OnOpenWarehouseReceiptPage

We would like the parameter GetSourceDocuments added to the following events.
Codeunit 5751 - Get Source Doc. Inbound - procedure OpenWarehouseReceiptPage - event OnOpenWarehouseReceiptPage
Original:
OnOpenWarehouseReceiptPage(WarehouseReceiptHeader, ServVendDocNo, IsHandled);

[IntegrationEvent(false, false)]
local procedure OnOpenWarehouseReceiptPage(WarehouseReceiptHeader: Record "Warehouse Receipt Header"; ServVendDocNo: Code[20]; var IsHandled: Boolean)
begin
end;

Change
OnOpenWarehouseReceiptPage(WarehouseReceiptHeader, ServVendDocNo, IsHandled, GetSourceDocuments); // <-- ADDED

[IntegrationEvent(false, false)]
local procedure OnOpenWarehouseReceiptPage(WarehouseReceiptHeader: Record "Warehouse Receipt Header"; ServVendDocNo: Code[20]; var IsHandled: Boolean; var GetSourceDocuments: Report "Get Source Documents") // <-- ADDED
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 44246.