Setup problems with tokenize native app?

Describe the bug
Following the setup steps for the tokenization example doesn't seem to work as documented? Reported by Priyanta, being handled by @samsternberg.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Fixed by https://github.com/SkyflowFoundry/snowflake_functions/pull/10


Add babel-plugin-transform-object-assign.

It would be helpful for those runtime don't have Object.assign natively.

this polyfill should be in the client code

You can do that in your own project by transpiling react-loadable/lib/index.js using your own .babelrc.
I would rather have ES2017 exported from react-loadable. Otherwise it's punishing (no matter how close this lib is) those who make effort to serve modern JS to modern browsers and legacy JS to legacy browsers.
👎

Yes transpiling or use polyfill are options, but shouldn't Object.assign be listed on the dependencies if react-loadable didn't do that? IMO, as a lib, it could either add this object assign transform plugin or update the README.md that developers should take care transpiling themselves.

Adding to README is a better option IMO.

Adding into README.md seems more reasonable as client might use different approach to polyfill Object.assign, which might causes duplication or unnecessary client side bundle increase.


[Bug]: "Strange" characters appear when running Tinker

Short bug description
When I run Tinker, "weird" characters appear in the output
Extended bug description
Strange characters always appear instead of the results. Even if we do a simple "echo", the same characters always appear.

Your project is not the problem

[X] I tried using a fresh laravel install - I'm fairly certain it has nothing to do with my project.

How to reproduce?
When I run anything.
Expected behavior
The expected result should appear
Screenshots

IDE & Version
PHPStorm 2024.1
PHP Version
8.0
OS and version
Windows 11
Laravel Tinker plugin version
2.7.0
Interpreter type
Local
Laravel Version
8.32
Tinker version
2.7.0
Psysh version
0.11.9
Additional Context
No response

When I install the @dev version of psysh, everything works normally.

Hey, thanks for posting this issue. It's related to https://github.com/Roboroads/laravel-tinker/issues/320 tho, so I'm going to close this one and focus it all there :)

Ok, perfect! ;)


Bug: CDN contents cannot be installed with FBI as a .3dsx

Under the new Homebrew Menu and Rosalina, which provides .3dsx applications the same permissions as .cia applications, FBI can install local CIAs and direct links to CIAs correctly, but attempting to install CDN contents will yield this error:

This occurs right after the "installing ticket" screen, and afterwards FBI will report "Install finished." as if it completely properly.
Here's some more information about the 0xD963F805 error code:
Module: Application (254) | Description: String too big? This error is returned when service name length is greater than 8. (srv) (5) | Summary: Internal (11) | Level: Permanent (27)
Additionally, the latest release does not return to the Homebrew Menu cleanly when exiting; it kills the HB Menu and returns to the Home Menu. This is because a new homebrew runflag was necessary for returning cleanly to the Homebrew Menu under Rosalina; this can be fixed by updating to a recent ctrulib commit and recompiling FBI; no code changes necessary.

This looks more like an issue with the environment (possibly the app you're running under?) than FBI. It's unable to create the thread it needs to execute the task.

Got it. To resolve the issue with not exiting cleanly, do you think you could make a point release or recompile and modify 2.4.8's attachments?

I suppose I could simply reupload the last release compiled against the latest ctrulib. I'll get around to it sometime fairly soon.

Thanks!

Can you confirm that this build fixes the 3DSX exiting issue?
https://www.dropbox.com/s/1qmjowxpqdo8jmn/FBI.zip?dl=1

It does; it returns to the Homebrew Menu cleanly. Thanks!

Thanks for testing. I've updated the official 2.4.8 release build.

@Steveice10 Just letting you know, this issue was indeed an environment issue, and was fixed here.


Trident Install Fails if GlusterFS is installed on K8s node

Installing Trident on a new server fails if GlusterFS is enabled.
Trident Logs:
ERRO Trident REST interface was not available after 180.00 seconds.
FATA Install failed; exit status 1; Error: Get http://<IP_ADDRESS>:8000/trident/v1/version: dial tcp <IP_ADDRESS>:8000: connect: connection refused
command terminated with exit code 1; use 'tridentctl logs' to learn more.  Resolve the issue; use 'tridentctl uninstall' to clean up; and try again.
root@:/root/bin/NAS/trident-installer
Error Logs
2018-09-10 17:37:04.829170 W | etcdserver: another etcd process is using "/var/etcd/data/member/snap/db" and holds the file lock.
2018-09-10 17:37:04.829196 W | etcdserver: waiting for it to exit before starting...
2018-09-10 17:37:09.846095 C | mvcc/backend: cannot open database at /var/etcd/data/member/snap/db (no locks available)
panic: cannot open database at /var/etcd/data/member/snap/db (no locks available)
Workaround: disable GlusterFS before running the install.

@rileynjohnson Please share what version of GlusterFS is deployed and whether GlusterFS is deployed in a container or not.

It would also be good to know if they're running gNFS or Ganesha with GlusterFS. GlusterFS itself doesn't use the NFS lock manager, so the issue here might be that the NFS lock manager cannot start because GlusterFS is running or NFS on top of GlusterFS is causing problems.
Please share the output of rpcinfo -p run on the Kubernetes hosts.
Since NFSv4 locking doesn't require the lock manager, it might be worthwhile to run the flock tests (https://github.com/NetApp/trident/issues/175#issuecomment-422448765) with NFSv4 and GlusterFS. This configuration would take the lock manager out of the equation.

rpcinfo –p works fine on the node with GlusterFS turned OFF (see below).

The GlusterFS version is 3.12.11 and it is deployed in a container

Thanks for the details. Please have your customer open the issue with GlusterFS. This isn't a Trident issue or even a NetApp one.


Create database from init flow when it doesn't exists

Right now if the database doesn't exist in the database server, we are unable to proceed through the init flow and we need to manually create the database. What I would like is an option similar to that in lift(screenshot below) that will allow us to create this database within the init flow.

This option now exists @pantharshit00. Unfortunately it is always triggered as the database/schemas you entered is ignored, so we will have to retest this after the other bug is fixed to see if the behavior is as expected/wanted.


Pylance syntax highlighting overrides user-defined color

Hi,
Pylance semantic highlighting messes up the default theme syntax highlighting defined by the user, which is very annoying.
Adding
{
    "[python]": {
        "editor.semanticHighlighting.enabled": false
    }
}

to the settings.json file does not solve my problem.
Environment data

Language Server version: 2021.2.4
OS and version: Mac OS Mojave 10.14.6
Python version (& distribution if applicable, e.g. Anaconda): 3.7.10

Expected behaviour
Still have the user-defined colouring of selected text highlighting applied ("editor.selectionHighlightBackground": "#000000").
Screenshot with IntelliSense (every corr_type instance is highlighted in black):

Actual behaviour
When setting Pylance as language server ("python.languageServer": "Pylance"), Pylance colouring scheme takes over, overriding the user preferences.
Screenshot with Pylance (only some instances of corr_type are highlighted, in a faint hard to see light grey):

This isn't an override problem with semantic highlighting; the issue here is that Pylance provides an "occurrence highlighter" implementation to VS Code, which it uses to identify that one symbol is the same as another. In your first screenshot, corr_type is highlighted everywhere as it is using VS Code's "selection" highlighter. In the latter, VS Code calls Pylance to ask "give me the locations of all variables that are the same as this location", so it highlights those instead.
If you don't like Pylance's semantic occurrence highlighter, you can disable it with:
"editor.occurrencesHighlight": false

Can you try adding this setting to see if your color setting then works?
But I would argue that it's likely a bug that VS Code isn't respecting your configuration (even if the setting says "selection" rather than "occurrence"). The semantic occurrence provider is much more useful than the selection method, so I'd rather not recommend disabling this feature to work around a VS Code quirk.

This issue hasn't been updated in over a month; closing. If you can try with that above setting we can revisit this (but I'm fairly certain that we need to be filing this on VS Code itself instead).


chore: upgrade phoenix_live_view to v0.18.18

Fixes #683

An important note: Because the new TagEngine is now used, tag attributes are no longer dasherized. This means that the form attributes like :phx_submit are converted to "phx_submit". So the event handling doesn't work anymore.
see here the latest LiveVIew change
  def attributes_escape(attrs) do
    # We don't want to dasherize keys, which Phoenix.HTML does for atoms,
    # so we convert those to strings

    attrs
    |> Enum.map(fn
      {key, value} when is_atom(key) -> {Atom.to_string(key), value}
      other -> other
    end)
    |> Phoenix.HTML.attributes_escape()
  end

Surface form options
    # form.ex
    event_opts =
      event_to_opts(assigns.change, :phx_change) ++
        event_to_opts(assigns.submit, :phx_submit) ++
        event_to_opts(assigns.auto_recover, :phx_auto_recover)

@frankdugan3 thank you for the PR!
I merged it into update-lv-to-0.18.18 so I can fix the tests and work on other compatibility issues.
@Menkir thank you for reporting this. I'll take a look at it.

An important note: Because the new TagEngine is now used, tag attributes are no longer dasherized. This means that the form attributes like :phx_submit are converted to "phx_submit" which is not the same as "phx-submit". So the event handling doesn't work anymore.

@Menkir are you sure about this? I'm running the tests using LV 0.18.18 and Phoenix 1.7.2 and according to the following test, the changes don't seem to affect the generated code:
https://github.com/surface-ui/surface/blob/3adc9c544e49ca29b4225f9f4718037731ca572e/test/surface/components/form_test.exs#L124-L135


InvalidArgumentError in semantic_similarity_with_bert example

Hello,
I'm having a trouble while running "semantic_similarity_with_bert". Anyone having the same error? Do you have any solution? Thank you.
InvalidArgumentError:  Incompatible shapes: [32,53,768] vs. [1,128,768]
[[node model/tf_bert_model/bert/embeddings/add (defined at /local/lib/python3.6/dist-packages/transformers/modeling_tf_bert.py:192) ]] [Op:__inference_train_function_31438]
Errors may have originated from an input operation.
Input Source operations connected to node model/tf_bert_model/bert/embeddings/add:
model/tf_bert_model/bert/embeddings/GatherV2 (defined at /local/lib/python3.6/dist-packages/transformers/modeling_tf_bert.py:188)
model/tf_bert_model/bert/embeddings/position_embeddings/embedding_lookup/Identity (defined at /local/lib/python3.6/dist-packages/transformers/modeling_tf_bert.py:189)
Function call stack:
train_function

it seems there is a problem when you feed the bert model. maybe you should check the shape of the tensors you give to the model. it should be = (None, 256) or (None, 128) if max_length = 128
print(input_ids.shape)
print(attention_masks.shape)
print(token_type_ids.shape)

it seems there is a problem when you feed the bert model. maybe you should check the shape of the tensors you give to the model. it should be = (None, 256) or (None, 128) if max_length = 128
print(input_ids.shape)
print(attention_masks.shape)
print(token_type_ids.shape)

Better idea : add truncation = True in the tokenizer (def_getitem...)
encoded = self.tokenizer.batch_encode_plus(
sentence_pairs.tolist(),
add_special_tokens=True,
max_length=max_length,
truncation = True,
return_attention_mask=True,
return_token_type_ids=True,
pad_to_max_length=True,
return_tensors="tf",

Better idea : add truncation = True in the tokenizer (def_getitem...)
encoded = self.tokenizer.batch_encode_plus(
sentence_pairs.tolist(),
add_special_tokens=True,
max_length=max_length,
truncation = True,
return_attention_mask=True,
return_token_type_ids=True,
pad_to_max_length=True,
return_tensors="tf",

I tried your suggestions. Now I am waiting. Thank a lot!

I tried your suggestions. Now I am waiting. Thank a lot!

Hi again. I just wanted to say thank you again. Your suggestions worked for me. You made my day!

Hi again. I just wanted to say thank you again. Your suggestions worked for me. You made my day!

Thank you for your feedback, I'm happy it works :-)

Thank you for your feedback, I'm happy it works :-)


Do not say 'no significant change' if the reason we did nothing was, it's a branch

I don't know what to do instead

Fixed


Fedora package outdated.

Hugo is quite outdated in the Fedora package repository. Is there anybody who might be willing to contact the maintainer and take over responsibility?

@c-edw While this doesn't address your original question, since you want to use a package manager to install/manage hugo, is using snap an option for you? Snap also includes latest hugo dev versions.
https://snapcraft.io/hugo

Personally I don't use Snaps, but thank you for making me aware that it's available. I have installed Hugo manually for now. Though, the Hugo installation is so simple that maybe it's not worth chasing after package maintainers. An autoupdate or update notice functionality in Hugo would make it acceptable to not provide distribution packages, in my opinion.

I think, given the manpower we got, I will close this. Opening up a thread on https://discourse.gohugo.io/ may be a better road to take.


Dark theme

@matteocargnelutti
I think the dark mode color scheme looks great!
I have two questions in this section!

Why did the icon for the archiving change from the lock to this arrow (with files?)
Wondering if we should do an accessibility check for the slight color change in the making the link public button? I think the contrast in the colors could be a little low. I would be happy to do this and suggest some colors!  https://coolors.co/contrast-checker/112a46-acc8e5

@shljessie
Thank you very much for having a look 😄 , much appreciated.

Why did the icon for the archiving change from the lock to this arrow (with files?)

(Missing context discussed on Slack)

Wondering if we should do an accessibility check for the slight color change in the making the link public button? I think the contrast in the colors could be a little low. I would be happy to do this and suggest some colors! https://coolors.co/contrast-checker/112a46-acc8e5

That's always a good idea 😄 .
I did check contrast ratios as I edited the colors for the dark theme, but suggestions are more than welcome!
For the "white on blue" buttons, I get a score of 4.59 in its default state, 4.77 on :hover. It probably can be improved!

You'll find the color schemes I use here:

https://github.com/harvard-lil/perma-extension/blob/develop/src/popup/index.css#L11
https://github.com/harvard-lil/perma-extension/blob/develop/src/popup/index.css#L34

Thanks again,

Cool! I was talking more about the button background color change from a lighter blue to a darker blue when clicked!
But if the function for the button is now a copy link instead of an archive/public, I think the current color change from a lighter blue to a darker blue is good enough to let the user know it has been clicked!

@shljessie I see, cool! Thanks again for having a look 👍 !


Fix height in yooinputgroup::before

Fix height in yooinputgroup::before

This still relevant @inando85? Can we proceed with the merge?

This still relevant @inando85? Can we proceed with the merge?

Yes, this was necessary because the height alignment of the base line of the form was broken when the form entered another state, active or error type. But as this MR has been around for so long, I don't know if someone had already corrected it in another one.


Logging of true

For some reason I'm getting a "true" printed out from the code below:
js2coffee.build(scriptStr, {indent: '  ', single_quotes: true})

This is usually harmless, but for a script that generates output it means I've had to hack into console.log to prevent this appearing in the output.

https://github.com/js2coffee/js2coffee/blob/master/src/documents/lib/js2coffee.js.coffee#L41
if opts.single_quotes? and opts.single_quotes is true
  console.log opts.single_quotes
  strEscape = strEscapeSingleQuotes
else
  strEscape = strEscapeDoubleQuotes


Update instructions to provide implicit information in Accessing Nested Objects Challenge

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #36080

Congrats @NoobyScoob on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝

Thank you @RandellDawson I really like to contribute. Love Freecodecamp!
BTW how can I add emote here?


Remove reference to testing infrastructure to prevent warnings from javascript packagers

Not sure how you will want to move the other stuff around to continue getting coverage, but having this set up makes WebPack throw errors while bundling.

Thanks.  I'll look into better ways to run the test coverage.  That logic is over 2 years old, and I'm sure there is a better way.


fixed layout issue with long urls

Codecov Report

Merging #107 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master   #107      +/-   ##
========================================
+ Coverage   90.92%    91%   +0.08%
========================================
  Files          57     57
  Lines        1201   1201
  Branches      120    120
========================================
+ Hits         1092   1093       +1
+ Misses         63     62       -1
  Partials       46     46

Impacted Files
Coverage Δ

...trivago/cluecumber/properties/PropertyManager.java
82.35% <0%> (+2.94%)
:arrow_up:

Continue to review full report at Codecov.

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


Add some logging regarding command palette usage

Summary of the Pull Request
Pretty straightforward. Logs three scenarios:

The user opened the command palette (and which mode it was opened in)
The user ran a command from the palette
The user dismissed the palette without running an action.

We discussed this in team sync yesterday.
PR Checklist

[x] I work here
[n/a] Requires documentation to be updated

@msftbot merge this in 1 minute


CI cross-compilation improvements

It seems like cross-compilation using Nix is kind of clunky so here comes a github action based building, including cross-compilation to some desirable targets:

wasm
macos
aarch64 android

Codecov Report

Merging #455 (22cde32) into master (2cd4cb8) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #455      +/-   ##
==========================================
- Coverage   74.54%   74.54%   -0.01%
==========================================
  Files          83       83
  Lines       10550    10550
==========================================
- Hits         7865     7864       -1
- Misses       2685     2686       +1

Impacted Files
Coverage Δ

client/client-lib/src/lib.rs
89.06% <ø> (ø)

client/client-lib/src/api.rs
81.38% <0.00%> (-1.10%)
:arrow_down:

fedimint/src/net/connect.rs
95.20% <0.00%> (+0.25%)
:arrow_up:

fedimint/src/net/peers.rs
93.43% <0.00%> (+0.26%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

LGTM. Should build ios eventually, too.


Add http/https support to socketio url valid

Allow http/https protocols for Socket.io endpoints.
Next step i will append event listener(because of socketio looks like cant get all message, must be specify eventName).

Hey @moonrailgun,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: 58478620-5e92-11ea-924a-074a1bb7e6b1


<EMAIL_ADDRESS>download via aria2 failed

When I ran scoop install source-code-pro, I received the error log like follow line:
TTF-source-code-pro-2.038R-ro-1.058R-it.zip (918.6 KB) [======================================================] 100%
Checking hash of TTF-source-code-pro-2.038R-ro-1.058R-it.zip ... ERROR Hash check failed!
App:         anderlli0053_DEV-tools/source-code-pro
URL:         https://github.com/adobe-fonts/source-code-pro/releases/download/2.038R-ro%2F1.058R-it%2F1.018R-VAR/TTF-source-code-pro-2.038R-ro-1.058R-it.zip
First bytes: 50 4B 03 04 14 00 08 00
Expected:    478028ec70adc1ff73848a546c3ad266716a0096cd1f1a1ef18aeff0199d5996
Actual:      5d53213eb7a4e1749daef33749fef8301bda4d302059054e2bbe88a9906d0a16

I have tried to close the aria2 and ran again, but still have this problem. What can I do?
Scoop Configuration
{
  "last_update": "2022-12-12T13:53:31.3010049+08:00",
  "aria2-enable": true,
  "aria2-enabled": true,
  "alias": {
    "remove": "scoop-remove"
  },
  "scoop_repo": "https://github.com/ScoopInstaller/Scoop",
  "scoop_branch": "master"
}

sourcecodepro also has  problem like this.

I will look into this when I get back from the work in the evening to confirm it, and to see what is going on.

@god464  Run whatever console you are using as an admin, then update the bucket and install it using scoop update && scoop install source-code-pro
I'll close this now as resolved, as i fixed the hash and i do not experience any problem with it. It the problem persists for you please comment on here


feat: integrate external model editor and handle message events for model updates

https://github.com/user-attachments/assets/a417f823-8051-46ff-8d5a-881619bacdd2


Tutorial 6: How to fit in pre-trained embedding matrix as the embedding layer in the transformer model?

Thanks Ben for your wonderful tutorial on the attention mechanism.
We are trying to build a conversational model based on transformer principle.
One of our main objectives for the conversational model is to maximise the coverage of our training vocabulary by word vectors from pre-trained word embeddings.
Thus we are planning to use multiple pre-trained word embeddings like : glove, gensim, fasttext to serve our purpose of ensuring maximum coverage.
But, there remains this gap in understanding : how to implement this/fit this in to the transformer model you taught to build in the 6th tutorial?
I am attaching here with a jupyter notebook which contains blocks of codes to give an idea of the requirement we are struggling to meet.
It will be really helpful if you could shed some light on how to achieve our goal.
Thanks in adance!
Approach.zip

Is there any chance you could upload the notebook to a GitHub gist?

I have detailed one way to add pre-trained embeddings to a Torchtext vocabulary here.
So as long as you can write the embeddings to a file, they should be easy to load with Torchtext. I have not seen of many people doing work in combining pre-trained embeddings using multiple sources though, would be interesting to see how it works.

Thanks Ben!
I will try this out and will keep you posted on how it goes.
We might require your help along the way to complete this activity.
For the time being thus keeping this issue open

Hi Ben,
I have preprocessed my data today and created a custom_embedding dictionary.
The dictionary contains a word and corresponding word vector and it has been constructed following this logic:
I have referred two pretrained embeddings and for each unique word in my dataset I looked up in both the pre-trained embeddings for word vector and if neither of the embeddings has that word I have filled in the value part with a vector of same embedding size containing random values.
However, I would like to ask for your help to convert this dictionary to the following format (which you suggested):
"The format of your custom_embeddings.txt file needs to be the token followed by the values of each of the dimensions for
the embedding, all separated by a single space, e.g. here's three tokens with 20 dimensional embeddings (all just ones as an example):
good 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0
great 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0
awesome 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0"
I have uploaded my code so far in this git repo for your review.
https://github.com/Ninja16180/Rough_Transformer/blob/master/Rough_Transformer2.ipynb
It will be really helpful if you could guide how to save the dictionary in the very format you suggested?
Thanks in advance!

All you need to do with your cust_embedding is write it to a .txt file which Torchtext can then read and turn into a Vectors object.
This can be done with:
with open('custom_embeddings.txt', 'w+') as f:
    for token, vector in cust_embedding.items():
        vector_str = ' '.join([str(v) for v in vector])
        f.write(f'{token} {vector_str}\n')

The rest of the steps linked in the issue can then be followed:
import torchtext.vocab as vocab
custom_embeddings = vocab.Vectors(name = 'custom_embeddings.txt')
TEXT.build_vocab(train_data, vectors = custom_embeddings)
model.embedding.weight.data.copy_(TEXT.vocab.vectors)

Let me know if that works for you.

Thanks a lot Ben!
Let me try this.
I will keep you posted on the progress.

Hi Ben,
I have created custom embedding as suggested by you.
Also add the following line to both the Encoder and Decoder classes:
self.tok_embedding = nn.Embedding(input_dim, hid_dim)
    # step added for custom embedding
    self.tok_embedding.weight.data.copy_(custom_embeddings)

    self.pos_embedding = nn.Embedding(max_length, hid_dim)

However, while building the encoder object the following error was thrown.
TypeError                                 Traceback (most recent call last)
 in ()
18               ENC_PF_DIM,
19               ENC_DROPOUT,
---> 20               device)
21
22 dec = Decoder(OUTPUT_DIM,
 in init(self, input_dim, hid_dim, n_layers, n_heads, pf_dim, dropout, device, max_length)
16
17         # step added for custom embedding
---> 18         self.tok_embedding.weight.data.copy_(custom_embeddings)
19
20         self.pos_embedding = nn.Embedding(max_length, hid_dim)
TypeError: copy_(): argument 'other' (position 1) must be Tensor, not Vectors
The git repo is updated with the latest file with error description for your reference:
https://github.com/Ninja16180/Rough_Transformer/blob/master/Rough_Transformer_v.03.ipynb
Could you please advice, what went wrong ang and how to fix the issue?
Thanks in advance!

As mentioned in my previous code snippet, you cannot .copy_ from the custom_embeddings as it is a Vectors object and not a tensor.
Assuming you are using sent1 as the source and sent2 as the target, then encoder you should have:
self.tok_embedding.weight.data.copy_(sent1.vocab.vectors)

The decoder should also be changed to:
self.tok_embedding.weight.data.copy_(sent2.vocab.vectors)

Thanks Ben! It did resolved the issue.
My bad, I missed to understand the implication of using TEXT.vocab.vectors with copy_.
I am now able to proceed till training the model; I will keep you posted.
I am really grateful for your help along the way whenever I got stuck with any issue.
Thanks again!

Also I am closing this issue as I am now able to suceessfully use pre-trained embedding matrix in my model.

Also I am closing this issue as I am now able to suceessfully use pre-trained embedding matrix in my model.
For any other query (if I come across) I will open a new issue.
Thanks!


which version to download?

@ircmaxell For latest 'stable' version for product environment, should I download 'dev-master' or v1.0.4 as of today?

Fyi, the only functional difference in master is from https://github.com/ircmaxell/password_compat/pull/79.

I'd say always go for a stable tag.

I left my comment under #79 to keep consistency between dev-master and stable tag.

Master and stable are by definition not consistent. One is stable, and one is not.
I intentionally did not push a new release after merging #79. It would be fine to now (and I likely will), but there's a reason for the delay. I will explain in #79.
You should always use a production tag when you are using the code in production. Never use dev-master in production. It's as simple as that.


[docs] Add IntelliSense for each class in the classes prop

We can't add JSDOC to literals (https://github.com/microsoft/TypeScript/issues/25499) so we create an interface instead.
Before:

After:

class keys are now automatically generated (no more missing class keys)
deprecate StandardProps
It was only really useful as an internal helper but libraries such as notistack started using it so we can't make internal adjustments without disrupting the wider ecosystem.
fixes various issues where props used StandardProps even if they weren't decorated with withStyles
~remove implicit className and styles~
~It was used as a convenience helper but not necessarily correct. Whether className or styles is implemented depends on each component.~
We do this another time. Too many components rely on it.

TODO:

[x] CI green
[x] go over implicit className and style again

🔥 🔥 🔥 🔥 🔥 🔥 🔥 🔥 🔥


ImageMobjects are not properly hashed

Description of bug / unexpected behavior
I found that certain operations on ImageMobjects do not invalidate the animation cache, that is, they don't change the mobject's hash value.
In consequence, in a typical workflow of repeated renders, Manim sometimes generates videos that do not match the code they were generated with.
This is because the pixel_array is explicitly filtered out of the hashing operation:
https://github.com/ManimCommunity/manim/blob/b26137e9b62666e3f0bba0d18a72399077d3dbb6/manim/utils/hashing.py#L21-L26
Expected behavior
All (visible) modifications to an ImageMobject should result in its hash being different.
How to reproduce the issue
Code for reproducing the problem

Run the provided code (manim filename.py without a manim.cfg)
Change the alpha value
Run it again
Manim inappropriately re-uses the cached animation.

from manim import *

class TestImageCaching(Scene):
    def construct(self):
        im = ImageMobject('example.png')

        # change here           ↓↓↓
        im.set_color(RED, alpha=0.2)

        self.add(im)
        self.wait()

Additional comments
The most obvious “fix” would be to remove "pixel_array" from the exclude list – which, considering that #2923 works, doesn't break Manim – but I assume it's there for a reason.

@huguesdevimeux As you are the caching expert, do you have an idea why pixel_array is in the exclude list ?

If im not mistaken, it may have something to do with the fact that numpy arrays are not hashable.
>>> from functools import cache
>>> cache(lambda i:i)(np.array([1,2,3]))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: unhashable type: 'numpy.ndarray'

For reference, here's what happens to ndarrays that aren't filtered out:
https://github.com/ManimCommunity/manim/blob/b26137e9b62666e3f0bba0d18a72399077d3dbb6/manim/utils/hashing.py#L210-L215

@huguesdevimeux As you are the caching expert, do you have an idea why pixel_array is in the exclude list ?

I think the issue what they were too large, so there is a workaround.
Hope it's clear.

Hello and sorry, this went off my mind.
I think the most straightforward and logical thing would be to exclude ImageMobject from being cached. The main reason is that such mobject is really computationally expensive to hash, and there is no really workaround around it.

My proposal would be to generate a short random sequence as an, hash for every pixel_array, in order to invalidate the cache systematically. That's the most straightforward and simple solution I can think.


Allow harvesting of association tables

In addition to being able to harvest a single value that's associated with a given entity permanently, or on a per-year basis, we also need to be able to harvest association tables -- all the observed combinations of several columns (e.g. report_date, balancing_authority_id_eia, utility_id_eia, and state).

Hey @ezwelty did this end up getting integrated into the big PR #806?

Yes, if you mean all combinations of several columns, where all those columns are present. See "Harvest process" section of my top post in #806.

Resource.harvest_dfs() harvests from multiple named input dataframes. Only dataframes with all the primary key fields are included. If Resource.harvest.harvest=True, all such dataframes are harvested and, by default, also aggregated.

Note the "Only dataframes with all the primary key fields are included." So in your example, if you wanted to include combinations of report_date and balancing_authority_id_eia from a table without utility_id_eia and state, that would not work. Adding that functionality would be simple enough, by making Resource.format_df() insert empty columns for the missing primary key columns in the case of a partial match.


User instructions

AS A user I AM presented with three step instructions SO THAT I can find recipes depandant on my input

Removed Issue. Made updates to issues. Christine


What's the point of using context?

Hi,
I notice that in the latest version of reapp-routes, we need to use this.context.router.transitionTo instead of this.transitionTo. I'm wondering why we should do this. What's the cons of using the old way to access the react-router's transitionTo?
Thanks.

You'd need to create a mixin to simplify that and mix it into your routes like previously. I think the only difference is now react-router won't be supplying that mixin.
I'm thinking about it. Reapp is in alpha, but this release especially is shaky because both react-router and our theme engine moved to React 0.13 and new ways of using context.
It almost feels like React is asking for Decorators now. I use reapp-component for this. The hacker-news-app uses them if you want a demo. Basically you could mixin the router mixin everywhere.
I'm thinking about better ways to handle all this. I want to make reapp simpler than it is now, but still flexible. I think it's almost to the point where we can just say "react-router has won" and commit to it and that would open up some stuff to be easier.

I will say personally, I don't mind the this.context.router syntax. It's more verbose, but it's also less magical than before. But I understand where you're coming from.

Got it. Thanks for explanation.

I will say personally, I don't mind the this.context.router syntax. It's more verbose, but it's also less magical than before.

I definitely agree with you on this! Honestly, this.transitionTo made me confused for a while that I don't know where it comes from until I trace the source code.
Now I understand your designation, and I totally agree with your direction.
Good work! Thanks! :+1:


notify electron app when realm icon, profile is changed

Notify electron app about changed realm icon, org profile through electron_bridge. Also, send unread count data to electron app.
Testing Plan:

Add this to the console of devtools:

electron_bridge = {
  send_event: console.log
}

Open up a new tab and edit the realm name and icon, you should see the event name and data in your console.

For the first two commits, you want to make the changes in server_events_dispatch.js, not the success handler.  Otherwise, it'll only update that for the browser window that makes the change, not those of any of the other users in the organization.
This is a general rule in how Zulip settings work -- you never want to do anything in the success handler for the change-setting request; always in the server_events code path.  Read http://zulip.readthedocs.io/en/latest/tutorials/new-feature-tutorial.html (and similar docs) to learn more about how this works.

Ah okay, i will look through the docs and update this PR accordingly in server_events_dispatch.js.

I implemented first two commits in server_dispatch_events.js, should be good to go now.

I fixed the node test and merged the first two commits, after changing the names of the properties to have some consistency with the one we already have.  Can you please test the app-side code against this?  It'd be unfortunate to have the wrong interface end up in Zulip 1.8, since we'd end up stuck with the mistakes for a long time.  I'm test-deploying on chat.zulip.org so it's easy to verify.
I'm a bit concerned about passing through the unread.get_counts() structure; I don't think I'm confident enough in the stability of that structure to expose it as an API that we can't break later.  What data do you actually need there?
Closing, feel free to submit a new PR for the rest.

I tested this on a dev server it works as expected using the app, the unread counts work as expected after it was deployed in chat.zulip.org.

I'm a bit concerned about passing through the unread.get_counts() structure; I don't think I'm confident enough in the stability of that structure to expose it as an API that we can't break later. What data do you actually need there?

Makes sense, the data we wanted was pm_counts, but we can get them by reading the HTML which we can access on app's side.

Makes sense, the data we wanted was pm_counts, but we can get them by reading the HTML which we can access on app's side.

For pm_counts, if we just want the total, what we should do is add an event that just passes that through.


Feature/stac 1.1.0

WIP to support STAC 1.1.0

[x] Added some missing fields required in STAC 1.1.0. Changed srs variable to String for wider compatibility.

@clausmichele : unit tests are ok, I integrated the changes to keep the coherence of the model objects, and did an actual rebase, so beware that you need to freshly reset to the new HEAD of the branch in case you need to continue developing here.
Regarding the nama of the PR: I see that the reference_system element of a Dimension has been "flexible" (int, String, or Object) eversince the definition of the STAC datacube extension:
https://github.com/stac-extensions/datacube/tree/v1.0.0?tab=readme-ov-file#dimension-object
Do we want to actually upgrade to STAC 1.1.0 for other reasons?

Here's the changes that need to be applied to comply with STAC 1.1.0:
https://github.com/radiantearth/stac-spec/blob/v1.1.0/CHANGELOG.md

NOTE: also beware that the STAC version that is implemented in the Spring Driver is still 0.9.0, so for those collections not imported as-is from STAC backends, that is the version currently adopted.

Also note that in addition to STAC 1.1.0, there were important updates in the extensions projection, bands and raster.

Thanks Matthias. We could include these to the PR.
Handy changelogs:

eo
projection
raster


The requested model 'schism' is an invalid choice!

The requested model 'schism' is an invalid choice! despite compilation with sCHISM enabled.
$> ./build.sh -component SCHISM
$> ./NEMS-schism.x
$> cat PET0*

20210701 135056.070 ERROR            PET0 module_EARTH_GRID_COMP.F90:3995 Not valid  -  The requested model 'schism' is an invalid choice!

@pvelissariou1 @josephzhang8

OK, this seems to be a problem with recursively checking out the feature/schism branch (also of NEMS)


In general I like the largely functional approach that you have taken, but I do wonder if a class might be helpful to wrap these processes together. Particularly the 'iterate over samples' loop in all of the notebooks does somehow feel like it should be contained in a class rather than a user having to copy it over each time. Edit: whether a class, or maybe some kind of configuration file.

Thanks for the recommendation @ekblad!  I believe we will make this alteration in a future version.  I would first like to get a better understanding of how folks will use the package since it is now in production and then I will make these types of modifications after we field usage feedback.


panpawn made this news system, not u Lord Haji

Ty for Introducing the feature,But shldnt we forgot panpawn for the code!

Use correct English
And this is my code . Compare the diff properly

While it does bear some similarities to golds news system, its very different in many ways.

Um...you should give proper credits

I don't feel there are enough simalaraties, if @Lord-Haji says its copied from gold and modified ill add credits to panpawn, otherwise its fine as is.

@DarkNightSkies always say something before checking it properly


alarm: if network unreachable,media.start may hang more than 7s,shoul…

…d trust multimedia will report media.error or media.prepared event,and then decide what to do next

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added

The lint failed, @lanyuqingri please run npm run lint-js locally before submitting :)

@ynliSonia May I ask you to have a review?


add a callback for setting data in middleware from request

Any chance of merging this or #97?

or #93 :)

Closing in favor of #93.


Enable inference for arbitrary number of instructions

Inferring shapes of operations within a function can be performed in one pass. Switch to a data structure that does not limit the number of operations that we can shape inference on.

op_worklist has been removed since the operations can have their shape inferred as the sequence of operations is traversed.


Titania decomp - 4 non-matching, 2 non-equiv (possibly equivalent)

A lot more of a slog than I expected from this one

Outstanding work, you got one of the hardest files from this game my friend. Thank you for this contribution!


SqlServerDriver.acceptUrl works wrong

Driver version

7.2.0.jre8
8.1.0.jre11-preview
SQL Server version

MsSql16
Client Operating System

MacOs
JAVA/JVM version

Java12
Table schema

My connection string looks like

jdbc:sqlserver://myIp:1433;database=master;password=pass**;**sdfsdf%;user=my_user;

As you see my password contains ;. I use Hikari CP and this pool uses acceptUrl method. I don't want change my password and I want to use Hikari CP. Can you help me with it?

Hi @Pryanic ,
The behavior is not wrong, you need to escape semicolons, see Using SQL escape sequences. Try jdbc:sqlserver://myIp:1433;database=master;password={pass**;**sdfsdf%};user=my_user;.

How I should handle such password pasS};word={qq?

pasS};word={qq should be escaped as {pasS}};word={qq}, but looks like driver does not handle this case. I will work on a PR for this scenario.

@ulvii Did you fix the bug?


Eslint prettier config

This adds a lint configuration so that the theme scripts will keep ES5 syntax, but the rest of the testing scripts can be ES6.  Fixes https://github.com/Shopify/theme-scripts/issues/39
Example:
Ran yarn eslint packages/theme-a11y/theme-a11y.js on a file using const.
Screenshot of it in action

Some things to note:
I'm using overrides to target the actual theme scripts. In the overrides, I pull in the eslint-plugin-es5.  Because I cannot uses extends as a property of ovrrides, I copy-pasted all the rules for the no-es2015 preset.  This doesn't look cool, but it works.
While poking around the repo for this plugin, I noticed that there was an issue about the plugin potentially clashing with frameworks. Like if you use .find from jQuery or lodash.  I think this is fine for this repo as we don't want these helper scripts to have dependencies on other frameworks.
I'v added this to travis.yml so it's part of the CI process. Once merged, there are going to be a lot of errors as we're now enforcing prettier styling.  Once this is approved, I can do a PR (or two) that does a clean up of all the files which branches off this PR.

I saw your PR while following a reference from eslint-plugin-es5, and FYI the rule blocks ALL objects that might have same name as any ES6 method, regardless of the object type, not just external frameworks. Example: The rule should be blocking Array.fill, but it will also block articleRepository.find(id) if your method happens to be named so.

Thanks for the heads up @8shashank . I'll see if I can switch some of those rules to throw warnings instead of errors, as suggested here: https://github.com/nkt/eslint-plugin-es5/issues/12#issuecomment-370850480

Thinking about it since more, I'll the all as errors instead of warnings as I mused on on my last comment.
As I wrote in my first comment

I think this is fine for this repo as we don't want these helper scripts to have dependencies on other frameworks.

We won't be using other frameworks in the scripts, so we don't need to worry about other framework's method names. And it's easy enough to not use an of this "not allowed" method Nantes if we are writing our own.
I'm assigning this over to you now @t-kelly as I'm out for the next little while

Happy to see this working! However I'm not convinced this is the best approach. Managing all these individual rules is bound to end up in frustration...
What about taking advantage of Eslint's config scoping, and have the root config handle all ES5 files, and configs in test/ directories which handle tests?
Will open an alternative PR soon!

Woops didn't realize I was pushing to Nathan's branch 😅

What about taking advantage of Eslint's config scoping, and have the root config handle all ES5 files, and configs in test/ directories which handle tests?

Nice! Much simpler.  Thanks for taking over this and improving it 😄


Update reference-machine-learning-cloud-parity.md

need to update GA features in Mooncake

Microsoft authors of articles need to make updates through the private repository, so the updates can be staged and validated by current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.
It's easy to access the private repo version of your articles in GitHub. Just add -pr to the URL, as follows:
 Public repo URL: https://github.com/MicrosoftDocs/{docs-repo}
 Private repo URL: https://github.com/MicrosoftDocs/{docs-repo-pr}
We have closed this pull request. Please resubmit the updates through the private repo. For more information, see the contributor guide.


Results not repeatable?

Results not repeatable?
I installed all the necessary files and started it with the default values. Training worked fine I assume (trained for 3 hours), final training batch looks like this:

But when I open an image for inference, in this case image number 201739 from the celeb a dataset, the result of the inference (which should be male to female) is:

Can you tell me what is going wrong?

Based on the last training batch it definitely looks like the model has not
converged yet. Notice that the right image in each image pair looks bad.
What kind of hardware are you using for training? To train in 3 hours you
need a high-end GPU.
On Jul 16, 2017 12:54, "Rainbow Unicorn"<EMAIL_ADDRESS>wrote:

Results not repeatable?
I installed all the necessary files and started it with the default
values. Training worked fine I assume (trained for 3 hours), final training
batch looks like this:
[image: batch000140_out]
https://user-images.githubusercontent.com/25714601/28249543-05403f84-6a58-11e7-9f52-5c2d41f4dab0.png
But when I open an image for inference, in this case image number 201739
from the celeb a dataset, the result of the inference (which should be male
to female) is:
[image: inference_out]
https://user-images.githubusercontent.com/25714601/28249551-2bc3b23a-6a58-11e7-8b24-c9417901a947.png
Can you tell me what is going wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/david-gpu/deep-makeover/issues/10, or mute the thread
https://github.com/notifications/unsubscribe-auth/ATYzmJuwyD55TOkCG0sqq8RDGzaLVfZFks5sOkBSgaJpZM4OZWaB
.

I had the same hunch, so I trained it on my lab computer, again for 3 hours, this time with better results:

and the inference of:

resulted in:

which could possibly already be the start of a male->female translation, I guess I will just let it train for a day now and see if it works then

after having it train for 1440 hours still no luck, the latest training batch (20k+) looks like this:

and when I try to inference, it says Operation 'None' not supported
But even without the error, I guess, since it always starts training fresh from the start, it seems like this code is unusable for me =/

I don't know why your model isn't converging. In the readme I suggested training for "40,000 to 50,000 batches", perhaps that's the reason? As for training from the start, you could easily add some code to load the existing checkpoints.
These toy projects are provided as-is. I don't have the bandwidth to maintain them. Sorry.


Final Updates to Github Actions

Overview

Created new daily_transform GitHub Action workflow
Scheduled daily transformation job at 9:00 AM EST
Configured workflow to run on-demand and automatically

Config and Secrets

Added Github secrets for AWS config and Postgres params

GitHub Actions Workflows

Added new daily_transform.yml workflow

Runs daily transformation in production environment
Supports manual triggering via workflow_dispatch

Updated existing workflow files to use GitHub secrets consistently
Added AWS_DEFAULT_REGION to environment variables
Ensured daily transform job always uses "Prod" target

SQLMesh Configuration

Fixed port configuration by explicitly converting POSTGRES_PORT to an integer
Resolved validation error in state connection configuration

Entrypoint Script

Removed S3 upload disabling for transform_dry_run command
Ensured consistent S3 upload behavior across different run modes

Readme

Removed unnecessary section about profiles

Key Improvements

Added automated daily production transformation
Enhanced configuration flexibility
Improved GitHub Actions workflow consistency
Resolved potential configuration validation issues

@db-tycoon-stephen  Alright, postgres config added as run time params for github actions. Please make sure the references from github secrets are correct as I don't seem to be able to see those secrets


Create a Viewable GUI item

Class Viewable is the base class for all entities which get attribute .content which is a numpy ndarray.
Let's then make any such class inherit from it.

Completed, tested.


generate_small_primes doesn't test division by 3

Running the code shows that some non-primes, such as 9 or 15, get included in the output.

I think correct implementation for trial_division method is code bellow (check out https://en.wikipedia.org/wiki/Primality_test#Simple_methods)
fn trial_division(n: u64, start: u64) -> PrimeResult {
    if n == 2 || n == 3 {
       return PrimeResult::Prime;
    }

    if n <= 1 || n % 2 == 0 || n % 3 == 0 {
       return PrimeResult::Composite;
    }
    // assumption: n > 3 and start > 3
    let root_n = (n as f64).sqrt() as u64;
    for x in (start..(root_n + 1)).step_by(6) {
        if n % x == 0 || n % (x + 2) == 0 {
            return PrimeResult::Composite;
        }
    }
    PrimeResult::Prime
}

Hey @meithecatte and @igorcrevar, Thanks for noticing this!
An earlier version of this test used to have a check for n % 3 == 0 which somehow got removed in later cleanup. generate_small_primes() iterates with +=2, and I set the last bit of all random numbers to 1 so this test will not receive even numbers, but I should probably mention that in the assumptions.
Fortunately this does not affect the primality testing in the final version of the code as it's only used for an early exit, and fixing this would make it run very slightly faster as the few false positives that were reaching miller-rabin would now get removed in the early exit.
I will update the article and code with this fix.


notifyException creates Segmentation fault on Lumen 5.2

Hi,
I've noticed that the package segfaults with combination of Lumen 5.2 and PHP 7.0.x. Lumen 5.1 does not seem to be affected. Here are steps to reproduce:
composer create-project laravel/lumen bugsnag-lumen-test
cd bugsnag-lumen-test/
composer require bugsnag/bugsnag-laravel:1.*

Then add these two lines to app/bootstrap.php after line 83 + set the config for API key.
$app->register('Bugsnag\BugsnagLaravel\BugsnagLumenServiceProvider');
app('bugsnag')->notifyException(new Exception("Something bad happened"));

If I remove the second line, it works just fine. The backtrace from gdb looks something like this and it just repeats the same three lines.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000774e58 in _zval_copy_ctor_func ()
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", line 63, in <module>
    from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named 'libstdcxx'
(gdb) bt
#0  0x0000000000774e58 in _zval_copy_ctor_func ()
#1  0x00000000007ec447 in ?? ()
#2  0x00000000007b1d2b in execute_ex ()
#3  0x0000000000767109 in dtrace_execute_ex ()
#4  0x00000000007eea40 in ?? ()
#5  0x00000000007b1d2b in execute_ex ()
#6  0x0000000000767109 in dtrace_execute_ex ()
#7  0x00000000007689fc in zend_call_function ()
#8  0x0000000000791df4 in zend_call_method ()
#9  0x00000000007aa300 in zend_std_read_dimension ()
#10 0x00000000007b2c9b in ?? ()
#11 0x00000000007b35aa in ?? ()
#12 0x00000000007b1d2b in execute_ex ()
#13 0x0000000000767109 in dtrace_execute_ex ()
#14 0x00000000007eea40 in ?? ()
#15 0x00000000007b1d2b in execute_ex ()
#16 0x0000000000767109 in dtrace_execute_ex ()
#17 0x00000000007eea40 in ?? ()
#18 0x00000000007b1d2b in execute_ex ()
#19 0x0000000000767109 in dtrace_execute_ex ()
#20 0x00000000007f3cfd in ?? ()
#21 0x00000000007b1d2b in execute_ex ()
#22 0x0000000000767109 in dtrace_execute_ex ()
#23 0x00000000007eea40 in ?? ()
#24 0x00000000007b1d2b in execute_ex ()
#25 0x0000000000767109 in dtrace_execute_ex ()
#26 0x00000000007eea40 in ?? ()
#27 0x00000000007b1d2b in execute_ex ()
#28 0x0000000000767109 in dtrace_execute_ex ()

Thank you for the report, @lasselehtinen. I'm taking a look.

Same problem +1. Does it work with an older version of bugsnag?

@kattrali Any updates on this one? I might have to go live with one Lumen application and I considering if I should downgrade to Lumen 5.1 so I can get the nice Bugsnag reports.

@kattrali I guess I found out the problem. I tested this again on PHP 7.0.3 and now instead of segmentation fault I get the following error:
PHP Fatal error:  Maximum function nesting level of '256' reached, aborting! in /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/container/Container.php on line 700
PHP Stack trace:
PHP   1. {main}() /home/vagrant/Code/bugsnag-lumen-test/public/index.php:0
PHP   2. require() /home/vagrant/Code/bugsnag-lumen-test/public/index.php:14
PHP   3. app() /home/vagrant/Code/bugsnag-lumen-test/bootstrap/app.php:85
PHP   4. Laravel\Lumen\Application->make() /home/vagrant/Code/bugsnag-lumen-test/vendor/laravel/lumen-framework/src/helpers.php:39
PHP   5. Illuminate\Container\Container->make() /home/vagrant/Code/bugsnag-lumen-test/vendor/laravel/lumen-framework/src/Application.php:205
PHP   6. Illuminate\Container\Container->build() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/container/Container.php:631
PHP   7. Bugsnag\BugsnagLaravel\BugsnagLumenServiceProvider->Bugsnag\BugsnagLaravel\{closure}() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/container/Container.php:733
PHP   8. Illuminate\Auth\AuthManager->check() /home/vagrant/Code/bugsnag-lumen-test/vendor/bugsnag/bugsnag-laravel/src/Bugsnag/BugsnagLaravel/BugsnagLumenServiceProvider.php:67
PHP   9. Illuminate\Auth\AuthManager->__call() /home/vagrant/Code/bugsnag-lumen-test/vendor/bugsnag/bugsnag-laravel/src/Bugsnag/BugsnagLaravel/BugsnagLumenServiceProvider.php:67
PHP  10. Illuminate\Auth\AuthManager->guard() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/auth/AuthManager.php:244
PHP  11. Illuminate\Auth\AuthManager->resolve() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/auth/AuthManager.php:57
PHP  12. Illuminate\Auth\AuthManager->createApiDriver() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/auth/AuthManager.php:77
PHP  13. Illuminate\Auth\AuthManager->__call() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/auth/AuthManager.php:77
PHP  14. Illuminate\Auth\AuthManager->guard() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/auth/AuthManager.php:244
PHP  15. Illuminate\Auth\AuthManager->resolve() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/auth/AuthManager.php:57
PHP  16. Illuminate\Auth\AuthManager->createApiDriver() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/auth/AuthManager.php:77
...
PHP 253. Illuminate\Container\Container->offsetGet() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/auth/AuthManager.php:154
PHP 254. Laravel\Lumen\Application->make() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/container/Container.php:1174
PHP 255. Illuminate\Container\Container->make() /home/vagrant/Code/bugsnag-lumen-test/vendor/laravel/lumen-framework/src/Application.php:205
PHP 256. Illuminate\Container\Container->normalize() /home/vagrant/Code/bugsnag-lumen-test/vendor/illuminate/container/Container.php:616

Fatal error: Maximum function nesting level of '256' reached, aborting! in /home/vagrant/Code/bugsnag-lumen-test/vendor/laravel/lumen-framework/src/Concerns/RegistersExceptionHandlers.php on line 54

Seems like the culprit is here. The auth check causes a nested loop in Lumen that never gets resolved. Commenting this try block resolves the issue but naturally I won't get the User ID attached.
https://github.com/bugsnag/bugsnag-laravel/blob/master/src/Bugsnag/BugsnagLaravel/BugsnagLumenServiceProvider.php#L67

Here is a work-around for now. In bootstrap/app.php uncomment the following lines:
$app->withFacades();
$app->register(App\Providers\AuthServiceProvider::class);

@kattrali Any updates?

It looks like we have an infinite loop resolving the current user here.

I guess this is happening because the authentication stuff hasn't been bootstrapped. I'm not quite sure how we can detect this. It looks like a bug in Lumen itself that the manager can go into a loop like this, but we definitely need to look into us avoiding it.

I'm going to have a chat with Taylor about this.

This was fixed by https://github.com/laravel/framework/commit/511e7ab0e5c9f3f84608fb5431cccb8d7ebdbe08. Please let me know if you're still experiencing any issues. :)

I have the same problem with Lumen when I use

        $this->app->alias('bugsnag.multi', \Illuminate\Contracts\Logging\Log::class);
        $this->app->alias('bugsnag.logger', \Psr\Log\LoggerInterface::class);

From docs:

If you’d like to keep logging to your original logger as well as Bugsnag, you can bind 'bugsnag.multi' rather than 'bugsnag.logger

Thanks for getting in touch. It looks like you're using the Laravel way rather than the Lumen way.
You can read about the Lumen way on our Lumen specific docs:

https://docs.bugsnag.com/platforms/php/lumen/#reporting-unhandled-exceptions.

We're also planning to update our Laravel docs to make it clearer that we have Lumen docs too.

@GrahamCampbell you are right. My fault


README.md should be updated

The README file contains a lot of obsolete information. It's not easy to get started when the information provided is misleading.
1. Install prerequisites
Need to install extra packages to make install with pip work.
sudo apt-get install python-pip mysql-server libmysqlclient-dev libpython2.7-dev

missing in requirements
gdata and flask should be install too:
pip install gdata flask

Add a new sql file to create database and user.
createuser.sql:
CREATE DATABASE seocrawler;
CREATE USER 'seo'@'localhost' IDENTIFIED BY 'oes';
GRANT ALL PRIVILEGES ON seocrawler . * TO 'seo'@'localhost';
FLUSH PRIVILEGES;

Then I ran the following command line to create the database and the user with right permissions.
cat createuser.sql | mysql -uroot -p

Run crawler
To run crawler, you need to execute with:
./run_seocrawler.py --database config.yaml --base_url http://fashionista.com
Run repporter
./run_seoreporter.py --database config.yaml

Thanks for reviewing the README. If you'd like to send a PR, I'd be happy to merge it. Otherwise, we're in no rush to update this tool since we're not using it at the moment. I'll try to get to it though. Thanks! :)

I've fork the project and made a lot of changes like for my own need.

Glad you're getting value from this project! If there's anything you'd like to contribute back, I'll be more than happy to merge it in! :)


Brewing Stand + Hopper Exploit = EZ money not much effort

How to reproduce:
Place a row of hopper pointing to a chest and ontop the hoppers brewing stands
Fill the brewing stands with materialsa and fuel  ie: blaze powder and nethe wart
Start filling all the brewing stands nonstop with water bottles and wait
et voilà, you get paid without using any of the materials you just put on the stands, rinse and repeat and get ez money on any server, the bottles get sucked by the hopper and mantain their original state, so you can use it again and keep earning money indefinetely.
Edit: Found a easier method to test
Build this

And when you put the bottle inside, move the lever so the potion gets sucked by the hopper.
The issue is i bet, the plugin doesnt check if a hopper takes the item out of the brewing stand and marks it as still brewing, and pays the player.
Tested on 1.12.2 and 1.13.2
Jobs 4.10.3

It's june, is there an update on this exploit?

This working correctly with the latest version and has built the brewing, hopper, and what you said. Firstly, make sure you have enabled the ExploitProtections.BrewingStands.Reassign and ExploitProtections.Brew.PreventBrewingStandFillUps options in generalConfig.

I have  those options set to true, using jobs 4.12.0 and I can still do this.
https://streamable.com/xovhs

Apparently, after a good long month, this is no longer detectable, so close.

This bug still exists, is not about filling the  brewing stand is about removing the water bottle with a hopper after the brewing started, jobs starts to count after that even if the potion is not brewing anymore and pays.


CI for docs

This CI is to catch failures when building the docs.

@landreman
Updated as per the comments raised


'Banach' initialization in oscillators

Oscillators must be initialized by a (smooth) stochastic process. See Leon 2015 appendix C.

A good starting point should be this, but it's not clear what a "squared-exponential process" is (or how to generate that).
Another option is to use a mollifier.
Other solutions may be to filter an OU process (red-shifting it) or to apply a differential operator (heat-equation-like) and relaxing for a fixed amount of time.


Not working properly

Logs:
[ INFO - 5:27:38 PM] vscode.workspace.onWillSaveTextDocument start
[ INFO - 5:27:38 PM] formatXml start
[ WARNING - 5:27:38 PM] docText is null. Fetching from DocumentHelper
[ INFO - 5:27:38 PM] formatWithCommandLine start
[ INFO - 5:27:38 PM] converted input to json {"xmlString":"\r\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\r\n<!-- sdf-->\r\n<company>\r\n    <employee name=\"Employee1\"              job_title=\"Job1\"              department=\"Department1\"              salary='1' >\r\n</company>","actionKind":"Format","formattingOptions":{"IndentLength":4,"UseSingleQuotes":false,"UseSelfClosingTags":true,"FormatOnSave":true,"AllowSingleQuoteInAttributeValue":true,"AddSpaceBeforeSelfClosingTag":true,"WrapCommentTextWithSpaces":true,"AllowWhiteSpaceUnicodesInAttributeValues":true,"PositionFirstAttributeOnSameLine":true,"PositionAllAttributesOnFirstLine":true,"PreserveWhiteSpacesInComment":false,"EnableLogs":true}}
[ INFO - 5:27:38 PM] Starting dotnet childProcess at c:\Users\KIIT\.vscode\extensions\prateekmahendrakar.prettyxml-3.5.0\lib\XmlFormatter.CommandLine.dll
[ INFO - 5:27:38 PM] replaceDocumentTextWithProgressForCallback start
[ INFO - 5:27:38 PM] replaceDocumentTextWithProgressForCallback end
[ INFO - 5:27:38 PM] vscode.workspace.onWillSaveTextDocument end
[ WARNING - 5:27:39 PM] childProcess errored with exitCode<PHONE_NUMBER>
[ ERROR - 5:27:39 PM] undefined : undefined
[ INFO - 5:27:39 PM] provideDocumentFormattingEdits start
[ INFO - 5:27:39 PM] getDocumentRange start
[ INFO - 5:27:39 PM] getDocumentRange end
[ INFO - 5:27:39 PM] formatXml start
[ INFO - 5:27:39 PM] formatWithCommandLine start
[ INFO - 5:27:39 PM] converted input to json {"xmlString":"\r\n<?xml version=\"1.0\" encoding=\"utf-8\"?>\r\n<!-- sdf-->\r\n<company>\r\n    <employee name=\"Employee1\"              job_title=\"Job1\"              department=\"Department1\"              salary='1' >\r\n</company>","actionKind":"Format","formattingOptions":{"IndentLength":4,"UseSingleQuotes":false,"UseSelfClosingTags":true,"FormatOnSave":true,"AllowSingleQuoteInAttributeValue":true,"AddSpaceBeforeSelfClosingTag":true,"WrapCommentTextWithSpaces":true,"AllowWhiteSpaceUnicodesInAttributeValues":true,"PositionFirstAttributeOnSameLine":true,"PositionAllAttributesOnFirstLine":true,"PreserveWhiteSpacesInComment":false,"EnableLogs":true}}
[ INFO - 5:27:39 PM] Starting dotnet childProcess at c:\Users\KIIT\.vscode\extensions\prateekmahendrakar.prettyxml-3.5.0\lib\XmlFormatter.CommandLine.dll
[ WARNING - 5:27:39 PM] childProcess errored with exitCode<PHONE_NUMBER>
[ ERROR - 5:27:39 PM] undefined : undefined
[ ERROR - 5:27:39 PM] undefined : undefined
[ INFO - 5:27:39 PM] provideDocumentFormattingEdits start

Document:

<?xml version="1.0" encoding="utf-8"?>
<!-- sdf-->
<company>
    <employee name="Employee1"              job_title="Job1"              department="Department1"              salary='1' >
</company>

A few minutes earlier it was only working on vanilla settings. And, now nothing seems to work.

There are few issues with your XML.

First line is blank. Delete it empty first line.
<employee> is not closed.

After fixing this XML errors this should work.
Working XML
<?xml version="1.0" encoding="utf-8"?>
<!-- sdf-->
<company>
    <employee name="Employee1"              job_title="Job1"              department="Department1"              salary='1' />
</company>

As mentioned in ReadMe this extension works for valid XML files.


Change authentication method in postgres - Fix bug connect to postgres in Kubernetes

Thanks, but we're gonna fix the app so it properly auths.

Thanks, but we're gonna fix the app so it properly auths.


eureka 1.3.1 failed parse JSON register

With eureka 1.3.1, JSON doesn't work anymore. It is rejected:
HTTP returned 400 registering Instance ... Body="{"error": "cannot parse request body"}"
The problem seems come from DataCenterInfo where:

"@ class": "com.netflix.appinfo.MyDataCenterInfo" is mandatory (see https://groups.google.com/forum/m/#!topic/eureka_netflix/7BoNPyPNSXo)
and AmazonMetadataType has to be removed (or be modified?)

Hrm, so I've started working on this, but it turns out there's more to it than just the DataCenterInfo class. It looks like there are some inconsistencies with how Ports are represented introduced in 1.3.1.
I see, for example, some ports as {"$": 9090, "enabled": "true"} and others as {"$": "9090", "enabled": "true"} so somewhere along the way Eureka stopped forcing all port numbers to strings, and instead mixes them. This is a recipe for :cry: time.
Also, it looks like they require incoming ports in JSON to be represented as integers, which is incompatible with the 1.1.X series of APIs. Given this, I'm thinking about dropping the JSON API altogether and using only XML since it seems to be the "first class" way to interact with Eureka.
It shouldn't need to affect the public API since the UseJSON bool would become a noop, and hopefully the XML-only interface would let us keep compatibility with the 1.1.X APIs.
What do the rest of the contributors think about that? @tysonstewart @Camtendo @jcox92

I have to use JSON API, since the InstanceMetadata with XML API seems not to work.
Do you have some tips about how to use InstanceMetadata with XML API ?
thx in adv.

@ryansb That seems reasonable to me. I'm not at all familiar with the differences (if any) between the JSON and XML APIs so I'll defer to your judgement on that. All of our internal tools that use Fargo only use the XML API so we should be good on that front!

I haven't contributed actual code to this (just the OSS badges) so I'll also defer my opinion. That proposition makes sense to me though.

@jcox92 what version of Eureka are you going to be using going forward? Will you be migrating to 1.3.x, or will you stay on the 1.1.x series?

@ryansb We're planning on staying on 1.1.x going forward. As of right now we don't have any plans to upgrade that I'm aware of.

I'm using Eureka 1.3  Any chance you would consider modifying fargo.Instance so that we can pass in our own JSON, and it is just stored as json, and then that json is passed to Eureka during registration?  That would put the burden on the user if they choose/need to use JSON, but you wouldn't have to keep modifying your code.
By the way, I can't get the xml to work either for Eureka 1.3, so this issue really unfortunately means I can't use your awesome package.

I stand corrected  XML does work with Eureka 1.3  I've included the XML output, in case anyone else is having difficulty.
2016/09/29 15:47:12 Registering instance with url http://localhost:8761/eureka/apps/ES-Search
2016/09/29 15:47:12 Got eureka response from url=http://localhost:8761/eureka/apps/ES-Search/i-123456
2016/09/29 15:47:12 Instance=i-123456 not yet registered with App=ES-Search, registering.
2016/09/29 15:47:12 postBody: POST http://localhost:8761/eureka/apps/ES-Search : i-123456ES-SearchlocalhostUP600000MyOwn000000testValue
2016/09/29 15:47:12 Got eureka response from url=http://localhost:8761/eureka/apps/ES-Search
2016/09/29 15:47:12 Getting instance with url http://localhost:8761/eureka/apps/ES-Search/i-123456
2016/09/29 15:47:12 Got eureka response from url=http://localhost:8761/eureka/apps/ES-Search/i-123456

What isn't working correctly with the JSON that fargo is sending to Eureka? Is it the same problem noted above?
Do you have a server log file available?

Yes, it is the same problem as noted above - there isn't a way to add the "@ class": "com.netflix.appinfo.MyDataCenterInfo" to the Instance struct.  Here was the output
2016/09/29 15:03:24 Registering instance with url http://localhost:8761/eureka/apps/ES-Search
2016/09/29 15:03:24 Got eureka response from url=http://localhost:8761/eureka/apps/ES-Search/i-123456
2016/09/29 15:03:24 Instance=i-123456 not yet registered with App=ES-Search, registering.
2016/09/29 15:03:24 postBody: POST http://localhost:8761/eureka/apps/ES-Search : {"instance":{"hostName":"i-123456","app":"ES-Search","ipAddr":"localhost","vipAddress":"","secureVipAddress":"","status":"UP","overriddenstatus":"","port":{"$":"6000","@enabled":""},"securePort":{"$":"0","@enabled":""},"homePageUrl":"","statusPageUrl":"","healthCheckUrl":"","countryId":0,"dataCenterInfo":{"name":"MyOwn","metadata":null},"leaseInfo":{"renewalIntervalInSecs":0,"durationInSecs":0,"registrationTimestamp":0,"lastRenewalTimestamp":0,"evictionTimestamp":0,"serviceUpTimestamp":0},"metadata":{"testkey":"testValue"}}}
2016/09/29 15:03:24 Got eureka response from url=http://localhost:8761/eureka/apps/ES-Search
2016/09/29 15:03:24 HTTP returned 400 registering Instance=i-123456 App=ES-Search Body="{"error": "cannot parse request body"}"
When I manually POSTed via poster the same json but with the "@ class": "com.netflix.appinfo.MyDataCenterInfo" added to the DataCenterInfo block, it worked.

That's odd; the Eureka server doesn't demand that that field be present for the XML document. After I've registered an instance and I ask Eureka to send it back, that field is present—populated by Eureka on its own.
I take it the proposal is that we send that field when registering an instance. Before doing that, I'd like to study the Eureka server code to see why it's complaining about this lack.

Eureka release 1.2.2 introduced the Jackson codec, which brings along encoding the ports as integers. I was about to go try to handle this when I read @ryansb's earlier comment about the rest of the changes.
What a mess.

As I've been working on resolving this problem, here's what I've learned:

Eureka post-1.2.2 will accept ports as strings, though it emits them as integers.
Eureka post-1.2.2 will not accept a "dataCenterInfo" object without a "@class" field.
Eureka post-1.2.2 will accept a "dataCenterInfo" object with a "@class" field with a corresponding value of any of the following:

com.netflix.appinfo.MyDataCenterInfo
The sibling "name" field must be present with the value "MyOwn".
The sibling "metadata" field can be absent, but must not be present but null.
com.netflix.appinfo.InstanceInfo$DefaultDataCenterInfo
Alias for "com.netflix.appinfo.MyDataCenterInfo", subject to the same constraints.
com.netflix.appinfo.AmazonInfo
The sibling "metadata" field must be present and nonnull.

See pull request #59 for a proposed solution to this problem.


Unable to upgrade from 3.1.0 to <IP_ADDRESS>

Hi Team,
My existing Kong installation is done using the helm chart kong/kong v2.16.5, along with the docker-kong-oidc:3.1.1 image.
I tried to do a helm upgrade with the new 3.2.1 image and I found out that the base image for docker-kong-oidc has been upgraded from kong/kong:3.1.1-alpine to kong/kong-gateway:<IP_ADDRESS>-alpine. This has led to my existing Kong deployment to fail. I tried to connect to the admin endpoint and I get the following error:
Error: reading Kong version: making HTTP request: Get "https://kong-kong-admin.<namespace>:8444/": connection error: COMPRESSION_ERROR
Any reason behind this change of base image from kong/kong to kong/kong-gateway?
Thanks!

Sorry about that. Yes, it was an unexpected (and I hope temporary) change because of the CVE-2023-0286 that some don't deem that bad and the official docker image did not yet go to 3.2.x
As soon as it's there will update it back.

But your error should have nothing to do with the change of image, I expect you will get the same with the "official" docker one.

Understood, thanks for the quick update on this issue.

Just to update that kong/kong:3.2.2-alpine is available now, although it's not shown on the Dockerhub page.

Note the two different repositories in in Dockerhub.

kong: Official images, part of Docker library
kong/kong: Nightly images

I have not investigated to say how near these images are of each other in terms of actual code, but definitely the images are not the same. At least packaging is different and some environment variables are set differently. Example from a past version:
$ docker run --entrypoint="" --rm -it kong/kong:3.1.1 env|grep KONG_
KONG_VERSION=2.8.1
$ docker run --entrypoint="" --rm -it kong:3.1.1 env|grep KONG_
KONG_VERSION=3.1.1
$ docker images|grep 3.1.1
kong                                             3.1.1         b76469f8b580   5 weeks ago     164MB
kong/kong                                        3.1.1         43f44aed3170   3 months ago    169MB

The official library image for 3.2.2 appears to be in PR review phase at the moment.

Bumped kong to 3.2.2 and also pushed to my personal repo as free org repos on docker hub will be gone starting with 14th of April.

If you own a legacy Free Team organization, access to paid features — including private repositories — will be suspended on April 14, 2023 (11:59 pm UTC). Upgrade your subscription before April 14, 2023 to continue accessing your organization.

Thanks for following up on this closely. Would like to highlight that I'm facing a different error, where Kong throws a HTTP 500 error after authenticating with Keycloak:
[lua] openidc.lua:1475: authenticate(): request to the redirect_uri path but there's no session state found, client: <redacted>, server: kong, request: "GET /cb?state=<redacted>&session_state=<redacted>&code=<redacted> HTTP/2.0"

Yep, that is an ugly (e.g. not immediately visible) error. It is because you need to set up x_session_secret to a base64 encoded value. See README.md#notes

We did provide a x_session_secret env variable via values.yaml when performing a helm installation:
env:
    X_SESSION_SECRET:
        valueFrom:
            secretKeyRef:
                name: <redacted>
                key: <redacted>

Could the bump in version for lua-resty-session from 3.10 to 4.0.2 be a factor in this scenario? I read that the session library was basically rewritten.

If you refer to the readme or see my comment above, you have to prefix  env vars with KONG_, so KONG_X_SESSION_SECRET

Appreciate the prompt response.
Yes I checked that the KONG_X_SESSION_SECRET env variable exists even though I used X_SESSION_SECRET in values.yaml. Perhaps let me try by using KONG_X_SESSION_SECRET in values.yaml instead. Thanks for your help.

Bumped kong to 3.2.2 and also pushed to my personal repo as free org repos on docker hub will be gone starting with 14th of April.

If you own a legacy Free Team organization, access to paid features — including private repositories — will be suspended on April 14, 2023 (11:59 pm UTC). Upgrade your subscription before April 14, 2023 to continue accessing your organization.

The official release image (https://hub.docker.com/_/kong, kong:3.2.2) is available now.

Already updated :)

@IvanTanJunWen you were right, was because of kong using lua-resty-session 4: https://github.com/zmartzone/lua-resty-openidc/issues/463.
Updated plugins (https://github.com/revomatico/docker-kong-oidc/commit/4f6e449b2cfd885e068950477c9412b917bebc45), tested the oidc plugin and seems to work as expected now.


[Bug] NoClassDefFoundError at startup

Description
Hello
We are experiencing an issue with the last Firebase Unity SDK 12.1.0.
We are building aab with multidex and split application binary enabled, Unity 2022.3.13f1
The build seems to crash at startup with this error:
07-18 18:38:35.765  7452  7452 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/android/gms/common/internal/Preconditions;
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at com.google.firebase.provider.FirebaseInitProvider.checkContentProviderAuthority(FirebaseInitProvider.java:85)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at com.google.firebase.provider.FirebaseInitProvider.attachInfo(FirebaseInitProvider.java:60)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at android.app.ActivityThread.installProvider(ActivityThread.java:7940)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at android.app.ActivityThread.installContentProviders(ActivityThread.java:7451)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7209)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2284)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:106)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at android.os.Looper.loopOnce(Looper.java:240)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:351)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:8377)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:584)
07-18 18:38:35.765  7452  7452 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1013)
We have tried almost everything, so we are running out of ideas. Some things that we are seeing:

After updating to the new firebase we were using the 10.4.0, where if we disable the custom main gradle we were able to build and it was working correctly.
We have updated the Firebase SDK so we could compile with target sdk 34 (that will be required by google in one month), and just with that we weren't able to build, so we activated the custom main gradle template and use the resolver to patch it. That fixed the build, but it crashed at startup with the error mentioned
We tried a lot of solutions, adding some configurations and implementations to the gradle, try removing and putting multidex, remove other plugins...but with no luck, we always end up with that error.

Any suggestions?
Reproducing the issue
No response
Firebase Unity SDK Version
12.1.0
Unity editor version
2022.3.13f1
Installation Method
.unitypackage
Problematic Firebase Component(s)
No response
Other Firebase Component(s) in use
No response
Additional SDKs you are using
Helpshift, Appsflyer, Playfab
Targeted Platform(s)
Android
Unity editor platform
Mac, Windows
Scripting Runtime
IL2CPP
Release Distribution Type
Pre-built SDK from https://firebase.google.com/download/unity
Relevant Log Output
No response
If using CocoaPods for Apple platforms, the project's Podfile.lock

Expand Podfile.lock snippet

👀 Replace this line with the contents of your Podfile.lock!

Hey @marcoseverguild, thanks for reaching out. Could you share which Firebase products are you using? Thanks!

Yes, we are using Analytics, Messaging and Database

Thanks for the extra details, @marcoseverguild. There's an issue with Firebase SDK version 12.1.0. For context, there are breaking changes in Firebase Android SDK which requires compileSdkVersion 34.

Breaking change: Changed the required minimum compileSdkVersion to be 34 or higher.
Breaking change: Updated minSdkVersion to API level 21 or higher.

Now according to the Unity forums, Unity Editors currently do not support compileSdkVersion 34, and is currently being worked on by their engineers. There are workarounds, by the Unity engineer, however I haven't tried it myself.
Another mitigation would be to downgrade Firebase SDK version 11.9.0 while waiting for Unity to update the compileSdkVersion on their side.
That said, please continue your report in the linked Unity thread.
Thanks!

Hey @marcoseverguild, could you try the solution provided by one of the developers:

Export the Unity project to Android Studio, change Gradle and AGP version to 8+. (This page says Android 34 requires AGP 8.1.1+).
Change min SDK from 23 to 24.

Let me know if that makes any difference. Thanks!


V2 Testing

Sponsor: Tyler Peterson / Jakob Anderson / Maybe Logan?
Topic Outline:

Unit Testing
Component Testing
Integration Testing
Acceptance Testing
Testing in the Build Pipeline
TDD
BDD
Automation
Refactoring (red/green)
Cross-Browser Testing
Testing Mobile Browsers
Smoke Testing
Linting
Testing Modules
Visual Regression Testing

Resources
Unit Testing

How to Get Your Team to do Unit Testing
Udacity Free course, "JavaScript Testing": https://www.udacity.com/course/javascript-testing--ud549
Udacity Videos from course on YouTube: https://www.youtube.com/playlist?list=PLAwxTw4SYaPkv4LG-0UHNfhPkKPfYacOg

TDD vs BDD

https://www.youtube.com/watch?v=mT8QDNNhExg
https://codeutopia.net/blog/2015/03/01/unit-testing-tdd-and-bdd/
Hanging a Shelf Using TDD and BDD

Visual Regression

The Secret of Safe Continuous Deployment: Perceptual Diffs - YouTube
Automating CSS Regression Testing

Tools
Testing runners

Karma
Mocha

Assertion libraries

Chai

{unsorted}

Protractor
Web Component Tester
AVA

Visual Regression

PhantomCSS
Image-diff
BackstopJS

https://medium.com/javascript-scene/what-every-unit-test-needs-f6cd34d9836d


"Arcane Focus" Bug on mage sim

The Talent "Arcane Focus" doesn't apply the extra 3% hit when the arcane spec is chosen.
It's only on the arcane spec.
The spell hit from talents should be 6% for the arcane spec.
Screenshots:

This was tested on Chrome Desktop.

This is just a visual bug. The hit in the display doesn't show spell type specific hit increase like arcane focus. I could overwrite it to show though and have been considering doing so.


fix(package.json): Adding missing required dependencies less and and babel-plugin-import

Less version is kept on v3.x.x because of the required parens on mixins introduced by less v4.0.0.

I assume this can be installed in the package.json inside your project?

I assume this can be installed in the package.json inside your project?


Feature, sample of data visualization

Description
This PR fixes #
I add a new api only for test purpose, it return html with Bokeh data sample. The return looks like below

We can implement chats in repository/data_visualization.py  and then use dataview to return the scripts
Notes for Reviewers
Signed commits

[x] Yes, I signed my commits.

As we discussed at the meeting 19 May, https://docs.google.com/document/d/1gsNNkQ5hFLBttZ4pSf01VHpF5K89Usl1yscr1J0afcc/edit?usp=sharing
Let's hold on the PR.

As we discussed, we want to make it more easier. We will implement this at frontend.


METAMODEL-172: Adding Date parsing to ES module

When working with ElasticSearch indexes that contains Date types the API is returning Strings instead of proper Date objects. We found out this problem querying an index with a time-zone format field.
Changes made in this PR:

Added time-zone format dates support in the TimeComparator class
Added a string to date direct conversion through the TimeComparator class in the ElasticSearchUtils class that will convert the string from ES into a proper Date (when the format will be supported by Metamodel)
Added a new unit test for the ElasticSearchUtils class

@kaspersorensen as per your suggestion I moved the date parsing to the ES module instead of using the TypeComparator class

+1 from me then :)

@LosD is this also ok with you?

Yep! I'm no fan of allowing stuff the schema doesn't, but if we can't get ES to help us out, we don't really have a choice.

Yes I agree. I guess this is the best worst option. I'll merge this into master tomorrow morning then.
Thank you @kaspersorensen @LosD for your comments!


Add readme - example included

Note these were tested on Ubuntu, but should work on Mac too, windows will need to tweak the paths slightly
Install instructions
1.) Clone the C3 LSP repo: https://github.com/pherrymason/c3-lsp
2.) Build the C3 LSP with the instructions giving a binary at: c3_lsp_repo_path/server/bin/c3-lsp
3.) Set the following options in the vscode settings.json
"c3.lsp.enable": true,
"c3.lsp.path": "c3_lsp_repo_path/server/bin/c3-lsp"

4.) Clone this repo: https://github.com/c3lang/vscode-c3
5.) Starting this extension by opening extension.js and run by pressing F5
6.) A new window will appear, you can now open a C3 file or project folder

I followed the instruction and they work, however I never worked with js or vscode extensions so it took me some time to understand
5.1) Open vscode-c3 repo with code .
5.2) Open extension.js, press F5 and run with the vscode extension debugger
but I don't think it's ready for use


fix misspell find file logic

@avaid96 noticed that misspell changed up its recursive directory finding-logic (see: https://github.com/client9/misspell#how-do-you-check-an-entire-folder-recursively)
Signed-off-by: Riyaz Faizullabhoy<EMAIL_ADDRESS>

LGTM pending CI :octocat:

LGTM!


flag provided but not defined: -high-availability

I upgraded promscale from 0.7.1 to 0.8 version.
it occured "flag provided but not defined: -high-availability" error..
The document(docs/high-availability/prometheus-HA.md) say

After Prometheus instances are configured to send the correct labels, Promscale simply needs to be started with the -high-availability CLI flag. Internally, Promscale will elect a single replica per cluster to be the current leader. Only data sent from that replica will be ingested. If that leader-replica stops sending data, then a new replica will be elected as the leader.

But I saw the history of code. I found changes.
If I use v0.8 of promscale, I have to change command from "-high-availability" to "-metrics.high-availability".
if i wasn't wrong, plz update the doc.

Hi there. Thank you for letting us know!
I've updated the doc and add an alias for the old flag (which is deprecated but should have still been supported until removal).
Thanks again!


POC: Api docs

Current coverage is 92.51%

Merging #348 into master will not affect coverage as of 23e5465

@@            master    #348   diff @@
======================================
  Files            9       9
  Stmts          187     187
  Branches        36      36
  Methods         88      88
======================================
  Hit            173     173
  Partial          4       4
  Missed          10      10

Review entire Coverage Diff as of 23e5465

Powered by Codecov. Updated on successful CI builds.

Looks like some good stuff.  As a side note, I'm not sure we should document the API of internal components, e.g. Day.  If we document it then we need to support it, and having the freedom to change it would be great.

What about just documenting the datepicker.jsx? Or do you see any other files that could be useful to document?

@martijnrusschen, probably just DatePicker right now, but we'll add more when we start making other components as public API, like Calendar and DateInput

Sounds good, wrapping up this initial PR with just Datepicker.jsx


Occasional tunnel startup error: tcpip-forward request denied by peer

Describe the bug
Occasionally when starting loophole it stops with this error below. This has been happening for at least a few months. Not sure if it's this version or something else, but I didn't see any reports about this.
Registering your domain... Success!
Starting local proxy server...  Success!
Initializing secure tunnel...  Success!
11:13AM ERR Listening on remote endpoint for HTTPS failed
11:13AM FTL Tunnel startup error error="ssh: tcpip-forward request denied by peer" tunnelId=56e0cd6b-90e0-43d7-bce1-3914cd3798f4

Running the command again often gets it working. I'd say this happens to me about 25-50% of the time. I've tried on both OSX and Linux and some of my co-workers also have this same issue.
To Reproduce
Steps to reproduce the behavior:

Startup loophole
Notice the error

Expected behavior
Loophole should always connect or return a better error message for why it can't connect.
Screenshots
OSX

Windows 11

Environment

OS: OSX 12.5.1 (M1 and x86), Windows 11
Version loophole version 1.0.0-beta.15 (5cecf33)

Additional context
None

I get the same thing on Windows, running v1.0.0-beta.15 (5cecf33) (also had it on beta.14), again for a few months now.

Starting local TLS proxy server
9:00AM DBG Proxy via http to http://<IP_ADDRESS>:8000 created
Starting local proxy server...
9:00AM DBG Server for proxy created

9:00AM DBG Proxy listener for HTTPS started on port 54254

9:00AM DBG Started server TLS server
Initializing secure tunnel...
9:00AM DBG Dialing SSH Gateway for HTTPS succeeded
9:00AM ERR Listening on remote endpoint for HTTPS failed
9:00AM FTL Tunnel startup error error="ssh: tcpip-forward request denied by peer" tunnelId=3e802671-6f02-4b81-8ebc-ed7f0d59c64c
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.```

Hi folks, not sure if there are any updates on this but I'm unable to use Loophole completely because of this issue. It's failing to start for me entirely even if i use the sample port 3000
L:\loophole-cli_1.0.0-beta.15_windows_64bit\loophole-cli_1.0.0-beta.15_windows_64bit
λ loophole http 3000
Loophole - End to end TLS encrypted TCP communication between you and your clients
Registering your domain... Success!
Starting local proxy server...  Success!
Initializing secure tunnel...  Success!
12:05PM ERR Listening on remote endpoint for HTTPS failed
12:05PM FTL Tunnel startup error error="ssh: tcpip-forward request denied by peer" tunnelId=58dcbf1c-6197-4494-9246-d0057cbd83ad

This has changed now from "occasional" to every other time now. had to resort to other tools, bore, ngrok etc

I've done the same. Now using Cloudflare tunnel. It's a shame, but given loophole was free, without the resources of Cloudflare, it was inevitale, I guess.

Hello, sorry for the lack of responses from our side. My notification settings were messed up and I didn't even receive any info about this issue 🙈
We are aware of this problem and we know the steps to mitigate it, but we lack a correct detection still. As given above, loophole is free and only maintained during some breaks at our regular jobs. Recently there is a lot of work outside loophole so the time dedicated to it is much smaller than at the beginning, but we will try to solve this once and for good soon.
Best regards and thank you for trying out loophole. I hope you'll be able to get back to it and use it again :)

Exact same problem on the WSL.
What steps can be taken?

Hey, sorry for the inconvenience. The backend system was stuck. Restarted it and it works again. We did not find time to fix this yet, as we are busy with other projects and have very little time for improving loophole at the moment. We will look into this as soon as possible, promised :)


Support pat keys

I am using 1.5.2 and pat keys do indeed not work. Here you say pat keys are supported, but they aren't.
Bearer Auth must be used for pat keys.
    public HubSpotBaseClient(string apiKey)
    {
      _apiKey = apiKey;
      _mode = HubSpotAuthenticationMode.HAPIKEY;
      Initialise();
    }

You've quoted lines 35 - 40
Look at the next constructor on lines 42 - 50 - that is the constructor to use with PATs

    /// <summary>
   /// Creates a HubSpot client with the authentication scheme OAUTH.
   /// </summary>
   public HubSpotBaseClient(HubSpotToken token)
   {
       _token = token;
       _mode = HubSpotAuthenticationMode.OAUTH;
       Initialise();
   }

That's OAUTH. PAT is a private App Key that starts with pat-. HubSpotClient is handling it correctly
https://github.com/skarpdev/dotnetcore-hubspot-client/blob/c4b826ce5b72bcd182802221c3572d5ad5b0a914/src/Core/HubSpotBaseClient.cs#L269
Gesendet von Outlook für Androidhttps://aka.ms/AAb9ysg

From: cdmdotnet @.>
Sent: Thursday, November 16, 2023 8:53:52 PM
To: Chinchilla-Software-Com/HubSpot.NET @.>
Cc: Thomas Pöchtrager @.>; Author @.>
Subject: Re: [Chinchilla-Software-Com/HubSpot.NET] Support pat keys (Issue #29)
Closed #29https://github.com/Chinchilla-Software-Com/HubSpot.NET/issues/29 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/Chinchilla-Software-Com/HubSpot.NET/issues/29#event-10985608265, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVRT6OKBBK5LPF2ZWKDE7K3YEZVNBAVCNFSM6AAAAAA7OFKMS2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJQHE4DKNRQHAZDMNI.
You are receiving this because you authored the thread.Message ID: @.***>

Enter your PAT as the AccessToken in the token.

While that may indeed work I dont think thats a proper implementation for simple PATs as HubSpotToken is meant for OAUTH. I'd call it a hack that luckily works.
Gesendet von Outlook für Androidhttps://aka.ms/AAb9ysg

From: cdmdotnet @.>
Sent: Thursday, November 16, 2023 11:39:21 PM
To: Chinchilla-Software-Com/HubSpot.NET @.>
Cc: Thomas Pöchtrager @.>; Author @.>
Subject: Re: [Chinchilla-Software-Com/HubSpot.NET] Support pat keys (Issue #29)
Enter your PAT as the AccessToken in the token.
—
Reply to this email directly, view it on GitHubhttps://github.com/Chinchilla-Software-Com/HubSpot.NET/issues/29#issuecomment-1815426953, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVRT6OJQGW5LTOSAYKUUF7DYE2IZTAVCNFSM6AAAAAA7OFKMS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJVGQZDMOJVGM.
You are receiving this because you authored the thread.Message ID: @.***>

Your opinions have been noted


[ConnectedK8s] Added update command (#3)

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

ConnectedK8s

@arrownj

hi @fengzhou-msft could you pls review this PR? thanks

@fengzhou-msft , @arrownj , Everything is set from our side. Could you review as well? If possible could we get this merged today? We wanted to release this feature next week for customers.

@Anumita version 0.2.3 is released.