URL not found

I am getting:
huggingface_hub.utils._errors.HfHubHTTPError: 404 Client Error: Not Found for url: https://huggingface.co/api/models/mosaicml/mpt-7b-chat

Could you provide some more details here? Where was this? What were you trying to do?

Hi @dariocazzani , I think this is a transient HF Hub error, their API occasionally goes down. Could you try it once more? I am seeing success when I visit that URL:
{"_id":"64544621ce1cc3ed5fe64629","id":"mosaicml/mpt-7b-chat","modelId":"mosaicml/mpt-7b-chat","author":"mosaicml","sha":"fa9345560420e2111498f87799ea7dd31cbd647e","lastModified":"2023-05-06T13:46:24.000Z","private":false,"disabled":false,"gated":false,"pipeline_tag":"text-generation","tags":["pytorch","mpt","text-generation","dataset:jeffwan/sharegpt_vicuna","dataset:Hello-SimpleAI/HC3","dataset:tatsu-lab/alpaca","dataset:Anthropic/hh-rlhf","dataset:victor123/evol_instruct_70k","arxiv:2205.14135","arxiv:2108.12409","arxiv:2010.04245","transformers","Composer","MosaicML","llm-foundry","license:cc-by-nc-sa-4.0","has_space"],"downloads":11793,"library_name":"transformers","widgetData":[{"text":"My name is Julien and I like to"},{"text":"My name is Thomas and my main"},{"text":"My name is Mariama, my favorite"},{"text":"My name is Clara and I am"},{"text":"My name is Lewis and I like to"},{"text":"My name is Merve and my favorite"},{"text":"My name is Teven and I am"},{"text":"Once upon a time,"}],"likes":219,"model-index":null,"config":{"architectures":["MPTForCausalLM"],"model_type":"mpt"},"cardData":{"license":"cc-by-nc-sa-4.0","datasets":["jeffwan/sharegpt_vicuna","Hello-SimpleAI/HC3","tatsu-lab/alpaca","Anthropic/hh-rlhf","victor123/evol_instruct_70k"],"tags":["Composer","MosaicML","llm-foundry"],"inference":false},"transformersInfo":{"auto_model":"AutoModelForCausalLM","pipeline_tag":"text-generation"},"spaces":["mosaicml/mpt-7b-chat","h2oai/h2ogpt-chatbot","h2oai/h2ogpt-chatbot2","lukesteuber/textual","AlekseyKorshuk/model-evaluation","wsvn53/mpt-7b-chat"],"siblings":[{"rfilename":".gitattributes"},{"rfilename":"README.md"},{"rfilename":"adapt_tokenizer.py"},{"rfilename":"attention.py"},{"rfilename":"blocks.py"},{"rfilename":"config.json"},{"rfilename":"configuration_mpt.py"},{"rfilename":"generation_config.json"},{"rfilename":"hf_prefixlm_converter.py"},{"rfilename":"meta_init_context.py"},{"rfilename":"modeling_mpt.py"},{"rfilename":"norm.py"},{"rfilename":"param_init_fns.py"},{"rfilename":"pytorch_model-00001-of-00002.bin"},{"rfilename":"pytorch_model-00002-of-00002.bin"},{"rfilename":"pytorch_model.bin.index.json"},{"rfilename":"special_tokens_map.json"},{"rfilename":"tokenizer.json"},{"rfilename":"tokenizer_config.json"}]}

@abhi-mosaic
Thank you, it seems like it was the case :)


Load modules from nearest tailwindcss instance

This PR updates the tailwindcss module resolution so that it won't look further up the tree after finding the first instance of tailwindcss

I think this is breaking my setup. I have a project that pulls in a tailwind config from a separate package. Prior tov0.2.6 this was working, but now I'm getting an error that one of my plugin packages cannot be found, even though it's in the deps of my package that has the source tailwind config.
Let me know if that doesn't make sense...


Fix: Allow closing the commit view if prompt_on_abort_commit=false

Fixes #1055
Regardless of what #1016 does or eventually will do, this needs a hotfix bc right now, the user can't close the commit view using ctrl+w if prompt_on_abort_commit is false.

Thanks


Stop "snapshot"messages being written to the log

Is there a way to stop the Homebridge log getting clogged up with endless camera snapshot messages? "debug": false doesn't help, unfortunately.

Anybody?

@soulcook I manually commented out line 178 in ffmpeg.js to temporarily resolved but would obvisouly need to repeat after each update.

Thank you!
Could it maybe be a configuration option in future?
On Fri, 24 Apr 2020 at 15:50, Adam Dempsey<EMAIL_ADDRESS>wrote:

@soulcook https://github.com/soulcook I manually commented out line 178
https://github.com/KhaosT/homebridge-camera-ffmpeg/blob/master/ffmpeg.js#L178
in ffmpeg.js to temporarily resolved but would obvisouly need to repeat
after each update.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/KhaosT/homebridge-camera-ffmpeg/issues/447#issuecomment-619058027,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOF7QMJ35KOKKO4B3P44BIDROGRLFANCNFSM4LY6HHUA
.


login using email

Hi,
I'm trying to register using the email address as username and I get a validation error "validationErrors: { username: [ 'Username Invalid username' ] },"
I assume SuperLogin is preventing me from either using special characters in the username or to set username and password with different values.
How can I change that?

I just found the answer, there is a config option here: https://github.com/colinskow/superlogin/blob/master/config.example.js


Component gallery should include uploads and downloads?

Perhaps as it's own section?
Also, keep in mind that downloads aren't currently possible in Express mode, but should be soon https://github.com/posit-dev/py-shiny/pull/967
@gregswinehart @garrettgman @gadenbuie

@cpsievert what would you call that section? I know it's a stretch, but I could be convinced they belong in "inputs."

ui.input_file() would definitely work in the inputs sections. Downloads don't have as much as an obvious home, but it kind of fits in the outputs section?


Replacing Cloud Portal for Launchpad

SAP Cloud Portal is no longer a service offered, the service that replaces it (in a way) is SAP Launchpad.

Hi @ajmaradiaga !
Thank you for the valuable feedback!
Because the SAP Cloud Portal is still available for customers that already purchased a license for it, we want to change the text to:
Finally, to consume the applications, you can create a site using SAP Cloud Portal service or SAP Launchpad service, build the URL, and define custom domains.
Kind regards!

That's a good idea as it is still available to customers. Thanks for pointing that out.


added load_data(), config, updated tests

Added:

scripts folder to store the CAMELS download script for simple runoff / precip vars
updated .gitignore
Added a pyproj.toml file in case we decide to be fancy
Added a config object to keep track of variables using Pydantic

updated the model, and tests to reflect the config

added a test for load_data

Doors project.toml need something in it to be useful?

Not really. Some people use it in their repos for linting and pytest configurations. I can delete it until we need it

Will probably end up getting it populated at some point.  Will likely end up refactoring things into a package structure in the near future and we can add it then with the package metadata.


Fix for potential race condition

Suggestion comes from https://mobilegrowth.org/discussions/thread/unity-branch-initsession-callback-never-fires-when-deep-linking/
Original notes:

In my [Unity] app, probably due to how scenes are loaded, the Branch.initSession callback never fires when the app is launched from a branch link (handleDeepLink). After lengthy debugging, I found the following patch fixes the issue for me. Is this a legit fix that others might encounter?

I think there is probably a better solution.  If handleDeepLink tries to call the callback before it is setup by the app (via initSession), it should remember that (eg, callbackAttempted flag?) and then when initSession is called, it can check that flag and do the callback immediately.

@dave-mcclurg Just so I understand, the broken time sequence is as follows:

handleDeepLink or continueUserActivity receives the deep link URL
/v1/open is called with that deep link URL
parameters are returned to the app and stored in the ns user defaults
you then call initSession with an options dictionary filled with the URL and register your deep link handler
callback block doesn't trigger because initSession falls through

This is an edge case we've never supported as the normal iOS lifecycle never has initSession being called before continueUserActivity or openUrl.
If this is happening 100% of the time, can you just fetch the deep link parameters in your scene using our local nsuserdefaults method shown here? https://github.com/BranchMetrics/unity-branch-deep-linking#retrieve-session-install-or-open-parameters
I hesitate to open up support for this lifecycle flow since it's so unnatural, but let me think a bit more about this.

@dave-mcclurg Please read and comment on the above, but also note that I've changed the logic here. Would love to see if this new fix would work for you.

@aaustin - The patch works great. I’ll go with that.

Making against staging in this PR. Closing this out https://github.com/BranchMetrics/ios-branch-deep-linking/pull/535


acknowledge use of Bjoern Hoehrmann code

https://github.com/apache/incubator-pekko-http/blob/5e82a0bc168644d5219b77877cbd337233aa3915/http-core/src/main/scala/org/apache/pekko/http/impl/engine/ws/Utf8Decoder.scala#L23-L48

argument we should move the license bit to the file header as opposed to a Javadoc in middle of file
need to mention in Pekko LICENSE (and pekko-http-core license)
part of #35

#198 merged


C++: Incorrect Assciidoc title for structs with :: in their name

Hi,
when converting a struct compound, the generated .adoc file only contains the part of the compound name after the last ::.
eg. <compoundname>is_container< std::array< T, N > ></compoundname> results in the Asciidoc section title array< T, N > >.
I suspect that the compound names are being parsed in a way where everything before the :: is considered to be a namespace.

I have reproduced the issue in a unit test. The parser that removes the namespace from the full name is indeed too simple. I will switch to using the full type parser for the name.


Created outer functionality in dummyDataMain file

Co-author: @JustinD-A
Types of changes

[ ] Bugfix (change which fixes an issue)
[x] New feature (change which adds functionality)
[ ] Refactor (change which changes the codebase without affecting its external behavior)
[x] Non-breaking change (fix or feature that would causes existing functionality to work as expected)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Purpose
Added a file with partial functionality for creating dummy data. This is the first modular step in creating functionality to fully write dummy data values into the existing sql instances.
Approach
Wrote an algorithm to generate table matrices that populate with dummy data. This piece of the function is missing two helper functions: one to generate the a value with the correct data type (using Faker.js), and one to create the query strings and write them to a generated sql file.
Learning
Nested/chained promises:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/resolve

looks groovy


Consider rewriting to es6

Have you considered rewriting the plugin from scratch (maybe using es6)? At the current state it is difficult to contribute with a pull request. I would to be happy to help if there is enough interest in this.
I am planning to open a repository containing es6 rewrites of popular plugins and would like to start with slick slider with your permission and help.

They've started writing a jquery-free version of it, I believe:
https://github.com/kenwheeler/slick/issues/494
https://github.com/kenwheeler/slick/tree/2.0

By the looks of it, there isn't much activity in the branch. We will be doing our own fork and rewriting it from scratch.
We will try to do as much individually possible, but any help from the community would be great.
@bonzzy will paste the link to the repo once he finds time to set it up (sometime next week).

PRs to the 2.0 branch welcome!


Help with Nodemethods and arguments

Using Ua expert as client, I've successfully created the node tree with a node method and a nodemethod with argument.
But I can't browse correctly the InputArguement node.
I've noticed that ExpandedObject is not really used, I already added it in "GetVariantTypeFromType"
I think the Argument object is missing, and I don't know how to encode it correctly.

Please capture the traffic with Wireshark and upload it here. I can take a look and tell you what is missing. Most likely you'd have to serialize into an ExtensionObject. I don't have any samples of doing this and the UA specification is unclear.

Yes, i saw in other projects, Argument object is set into a ExtensionObject.
The extension object serialization had an issue. Now it's OK.
Last thing is then encoding mask :
In wireshark expected value is : "EncodingMask: 0x01, has binary body"
What i have is : "EncodingMask: 0x01, EncodingMask: Four byte encoded Numeric"
In ua expert, tree values are correct, but when i call the method, ua plugin says that method has no arguments
Sorry if i'm unclear

Yes, I checked on other projects.
So I created a Argument object and encoded it correctly in an ExtensionObject.
My mistake was on the string encoder.
Now it's OK on ua expert but only in the tree view, I can see all nodes and arguments.
The last thing is to be able to call the method with arguments in UA expert.
I continue to check.
Thanks for the help !

Ok found.
There is an issue in HandleTranslateBrowsePathRequest
Line if (target.BrowseName.Equals(rp.TargetName))
should be
if (target.BrowseName.Name.Equals(rp.TargetName.Name))
as ua expert doesn't send the good namespace identifier in the request .

Just took a look at the source, both BrowseName and TargetName are QualifiedNames. This means that equality includes a test for namespace and value. This is likely a bug in uaexpert, namespaces are independent and comparing values across namespaces shouldn't match.


Off topic: tips for building computer?

Any thoughts about building hardware to build Chrome/Thorium?  How long does it take for you to build?  Think more than 32Gb RAM is useful?
TIA

@tomByrer I am using a fairly old system. A FX-8370 overclocked to 4.6Ghz, 24GB DDR3 1866Mhz, and a 1TB SSD. For me, compiling thorium takes 4-6 hours. @gz83 Is using a server with a 11th gen core i7, and 16GB ram, and SSD, and it takes him 2-3 hours.
You will need at a minimum: 2 core processor, 8GB ram, and 75 GB free space. Having 16 or more gb ram is better. 32 is overkill and wont make it faster. The newer/more cores/larger cache/higher frequency your CPU is, the better. This is the main limiting factor.
Someone used a Ryzen Threadripper 3990X overclocked to 4.2GHz on all cores, and compiled Chromium in 20 minutes lol

@tomByrer Also, this isnt off topic at all. Stuff like this is welcome, and I like when people post issues asking about building Thorium, it makes me happy that people want to build my project. I am also open to having a one on one with anyone on any social media platform, to guide them through anything they need help on. I am usually free.

I just picked up an Core i5-12600K, 64Gb of DDR4 3600 cl16 RAM... Maybe I'll make a RAM-disk since I will use old SSD?

@tomByrer That should be more than enough to build Thorium/Chromium in 4 hours or less. And no need to make a ram disk, an SSD, even an old one, will perform superbly for building. IDK if you got the idea for making a ram disk from the official linux building instructions, but that section in the doc is out of date, and was intended for people building with a regular HDD.

@tomByrer Are you intending to build thorium? if so, for what platform?
If you have any issues or questions regarding the building process for either thorium or chromium, dont hesitate to make an issue. I also can have a one on one with you on pretty much anything. I have facebook, instagram, snapchat, phone number, telegram, there is the new Thorium IIRC chat, etc. Only thing i dont have is microsoft teams or discord

@tomByrer Hi. Checking back in. Hows it going. Have you made any chromium or thorium builds. If you made a chromium build, did you use some or all of thoriums args.gn?


[DOC] Add new documentation for date index name processor

Description
Content gap; add new documentation for date index name processor
Issues Resolved
Checklist

[X] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@heemin32 Please review the new date_index_name processor documentation includes the necessary info and technically accurate. Thank you, Melissa

@heemin32 Please review this new processor doc at your availability. Thank you, Melissa

@heemin32 @kolchfa-aws I expanded the intro at line 10 to include more info about the date math index expression. I also corrected the response in step 3 and index name in step 4. Please review and approve at your availability. Thank you for your time and examples.

@vagimeli Could you please fix links?


Channel callbacks not called during BufEnter after window close

Describe the bug
v8.2.1948, which prevents handling messages during a window close, also prevents handling messages in subsequent autocommand events like BufEnter. This patch appears to remedy the problem while still preserving the intended behavior of the original change:
diff --git i/src/window.c w/src/window.c
index 8e5d3de26..df98d5d93 100644
--- i/src/window.c
+++ w/src/window.c
@@ -2651,6 +2651,9 @@ win_close(win_T *win, int free_buf)
 	win_equal(curwin, curwin->w_frame->fr_parent == win_frame, dir);
     else
 	win_comp_pos();
+#ifdef MESSAGE_QUEUE
+    --dont_parse_messages;
+#endif
     if (close_curwin)
     {
 	win_enter_ext(wp, FALSE, TRUE, FALSE, TRUE, TRUE);
@@ -2660,9 +2663,6 @@ win_close(win_T *win, int free_buf)
     }

     --split_disallowed;
-#ifdef MESSAGE_QUEUE
-    --dont_parse_messages;
-#endif

     /*
      * If last window has a status line now and we don't want one,

To Reproduce
Save this to a .vim file and :source it:
augroup bufenterjob
  autocmd!
  autocmd BufEnter /tmp/bufenterjob call s:Trigger()
augroup END

function s:Trigger() abort
  let queue = []
  let job = job_start(['date'], {'callback': { j, d -> add(queue, d) }})
  while empty(queue)
    sleep! 10m
  endwhile
endfunction

only
split /tmp/bufenterjob
wincmd p
redraw
close

Expected behavior
The file /tmp/bufenterjob is opened, and the previously opened window is closed without hanging and requiring CTRL-C.
Environment (please complete the following information):

Vim version 8.2.3281
OS: Ubuntu 21.04
Terminal: GUI, rxvt-unicode

Hmm, but I think the decrement should be after win_enter_ext(), otherwise some state might be wrong.
But autocommands are also triggered in that function.
Thus we would have to do it halfway that function.  Let's first refactor to pass flags instead of a bunch of boolean, so that it's easier to understand.


Adding tox env for building with READTHEDOCS theme.

LGTM.  I'm assuming this is primarily to allow debugging the RTD rendering?

Yep. And just if people want to view it.


Added PMTiles #17

OL STAC implementation: https://github.com/m-mohr/ol-stac/pull/4

Any thoughts @bdon?


[arm64] mclient crashes when changing display resolution the first time

Steps to repro:

Boot arm64 jessie container on bullhead
Cast to chromecast
Use Settings > Display to change the resolution from the default 1920x1080 to 1280x720

Screen will go black and logs show:
BadValue (integer paramater out of range for operation): request code 130
error calling XShmGetImage
error calling XShmGetImage
...

The timeout on the resolution change triggers and screen switches back to default 1920x1080, then mclient segfaults and restarts. Then you can change the display resolution just fine! Weird.
I can't reproduce this on armhf.

The one thing I noticed is that the pointer value of ximg changes to a different memory location right before this issue. But when the resolution change is succesful, the ximg pointer stays constant.

This is still an issue with Maru 0.6 and Debian Stretch.
One difference is that mclient does not segfault this time so the screen stays blank and we keep getting the X errors:
Mar 04 21:40:36 stretch64 mclient[62]: [t=46367039] screen size changed to 1920x1080 508mmx286mm in main evloop
Mar 04 21:40:36 stretch64 mclient[62]: invalid mdisplay size, using current mode
Mar 04 21:40:36 stretch64 mclient[62]: failed to sync X with mdisplay, re-configuring to match new size
Mar 04 21:40:36 stretch64 mclient[62]: [t=46420197] screen size changed to 1280x720 508mmx286mm in main evloop
Mar 04 21:40:36 stretch64 mclient[62]: invalid mdisplay size, using current mode
Mar 04 21:40:36 stretch64 mclient[62]: failed to sync X with mdisplay, re-configuring to match new size
Mar 04 21:40:36 stretch64 mclient[62]: BadValue (integer parameter out of range for operation): request code 130
Mar 04 21:40:36 stretch64 mclient[62]: error calling XShmGetImage
Mar 04 21:40:36 stretch64 mclient[62]: BadValue (integer parameter out of range for operation): request code 130
Mar 04 21:40:36 stretch64 mclient[62]: error calling XShmGetImage
... (keeps repeating BadValue)

The desktop must be rebooted to fix this issue. After the reboot, you can change resolution back and forth with no issues, which is very strange.

@pdsouza Now I use adb shell wm size to change display size, the maruos works fine. Maybe you have  fixed this problem.


Jenkinsfile: Abort previous builds

If a new build starts, abort already running builds to save
resources.

Won't this cancel any build of this job? We probably only want to cancel builds of the same PR/branch.

I'm not sure what it is doing exactly. This PR is here to find out :)

Also I'm not sure if Jenkins already does this, or if it waits for a previous build to finish if one is already running against the branch (therefore we won't get a chance to cancel it).

I think it does not. That's why we have this long waiting queue in jenkins.
But currently it does anyway not work because we don't have the permissions on jenkins to run the groovy script (I talked to Daniel to change this. let's see if we get the perms). See https://jenkins.io/doc/book/managing/script-approval/

Lets close this for now, it can be restored later if needed.


[tests] global-add should not fail if shellenv-not-in-path and add testscript unit tests for add and global-add

Summary
Makes a couple of fixes:

devbox global add should avoid returning an error status code if devbox-global-bin-path is not in PATH. We should instead print a warning, and return a 0 code.
devbox global shellenv should call ensureNixInstalled to find nix if not in PATH.

Adds basic test cases for multiple packages for devbox add and devbox global add
How was it tested?
go test -v -run TestScripts/add ./testscripts/...
go test -v -run TestScripts/global_add ./testscripts/...

Current dependencies on/for this PR:

main

PR #958   👈

This comment was auto-generated by Graphite.


Please remove the color from this article.

"Git has many benefits"
It has more negatives than benefits when compared to TFVC, unless you live/work in a fourth/fifth world country and have to be disconnected most of the time. Even then there are local workspaces.
Rather than start a pointless holy war (that git would lose =D) please leave articles like this without the fervor, zealotry, excitement, and evangelizing. Stick to the topic without editorializing or creating or serving bias.

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

ID: d24126ce-abfc-07d0-ceea-51534f745e55
Version Independent ID: 60861ae7-4b6d-e360-8ab7-28b276326569
Content: Import repositories from TFVC to Git - Azure Repos
Content Source: docs/repos/git/import-from-TFVC.md
Product: devops
Technology: devops-code-git
GitHub Login: @apawast
Microsoft Alias: atinb

I'll update that sentence to say "Migrating to Git is an involved process for large TFVC repositories and teams." - should be live later today.


Re-basin and Stable Diffusion Tensor Flow weights

Hi Samuel. Thank you for being willing to look at this. Basically, i'm trying to see if it is possible to merge stable diffusion models i've finetuned with dreambooth with your method.
The first hurdle of course is that your implementation is not yet compatible with pytorch as far as i know. But the pytorch weights can be successfully converted to Tensorflow weights. This has been done before as well. I don't mind doing this if i have to.
The second hurdle will be successfully using your implementation on the TF models. I'm not sure how feasible this all is or how i would use your code on the SD TensorFlow weights.

Hi @ogkalu2! The exact framework that the model runs in is not super important. For example, we have used our JAX code to align the weights of two PyTorch models in the past. The only important part is that you can load the weights into Python/JAX and that you have a correct PermutationSpec for your model.
In general writing down the PermutationSpec will be the more challenging step. We are currently working on a pure-PyTorch version, including a "tracer" that can automatically generate the PermutationSpec for you but this is not ready for release just yet.
Would be very cool to see if this works on StableDiffusion models! Do let me know if you get it working!

Hi @samuela Thanks for responding. Quite a bit's happened since the last comment.
I found a repo that had converted the code to pytorch. I also actually got down to writing the permutation spec for stable diffusion today. I think i'm on the right track but i'm not too sure. For instance, i'm not quite sure what the correct p_in and p_out values should be. Running it right now gives a couple different errors each time.
Sometimes i get something like
File "/content/drive/MyDrive/SD_rebasin/weight_matching.py", line 487, in weight_matching
A += w_a @ w_b.T
RuntimeError: mat1 and mat2 shapes cannot be multiplied (1280x11520 and 5760x1280)
or
"addmm_impl_cpu_" not implemented for 'Half'
Can you take a quick look here and see what you think I might be doing wrong ?
https://imgur.com/a/DMnb7P8

This looks to be an error in your permutation spec, I would try debugging what weight arrays that's occurring on.

This looks to be an error in your permutation spec, I would try debugging what weight arrays that's occurring on.

I'll try that thanks.
I also get "Indices out of bounds" too

This looks to be an error in your permutation spec, I would try debugging what weight arrays that's occurring on.

I've tried a couple different tests now removing everything besides a few lines of layers that were explicitly labelled in the state dict to see if that was the issue and i could build from that.
Example here https://imgur.com/a/IbAEfdP and https://imgur.com/a/o6SgMk8
But i still get those weird errors.

I've just taken a look at the flatten_params function for the pytorch code here. https://github.com/themrzmaster/git-re-basin-pytorch. Doesn't seem to be defined correctly and i think that's part of what was causing the issue. I've just switched the actual code for it as well as using your weight matching, get perm params etc code since like you said, it doesn't really matter.
I'm getting
TypeError: weight_matching() missing 1 required positional argument: 'params_b'
Any idea what that's about ?

@samuela
I finally got it to run the final permutation function for the few explicit blocks/layers (i'll build from there once i see everything else works) !
I feel so close but i've hit another wall on the apply permutation line. It's giving me "Key Erorr: Betas"
The good news is that i'm pretty sure i know what's happening here. Betas is the first key in Stable Diffusion's State Dict. It seems to be stuck trying to apply the permutation to Betas but betas wasn't defined in the permutation_spec list of layers or blocks to alter. More importantly, it's not the only key in the state dict i thought best left undisturbed.
Is there any way i can get the apply permutation function to skip keys that it doesn't have altered values for ?

Hmm, I'm not familiar with the stable diffusion architecture... is there a reason not to model permutations on the betas?
You could always add them to you PermutationSpec and just specify None for all the axes. That should make apply_permutation ignore them.
(Btw, since you're using the 3rd-party pytorch implementation some things may be different! That's a different codebase.)

You can skip betas, it's not a layer of the actual architecture but a stored parameter used for sampling and generating timestep embeddings. Same goes for alphas_cumprod, sqrt_alphas, and a dozen others.
Anything that isn't either in diffusionmodel, first_stage_model or cond_stage_model is such a parameter.
Actually you can probably skip first_stage_model (VAE) and cond_stage_model (CLIP) as well as those will probably be the same between two models. If not it would still make more sense to spec them separately as they are indeed separate models that only interact with each other manually, e.g. they have no connection in the model graph.
UNet is the interesting part, and this resides in diffusionmodel.model.*

Hmm, I'm not familiar with the stable diffusion architecture... is there a reason not to model permutations on the betas?
You could always add them to you PermutationSpec and just specify None for all the axes. That should make apply_permutation ignore them.
(Btw, since you're using the 3rd-party pytorch implementation some things may be different! That's a different codebase.)

Mostly 3 reasons

I can't tell the layer type of all the layers in the state_dict, only most of them. So i have to skip some to test it out first
A few correctly identified layers don't work well for some reason. I get an error like

File "/content/drive/MyDrive/SD_rebasin/weight_matching.py", line 293, in weight_matching
w_a = torch.moveaxis(w_a, axis, 0).reshape((n, -1))
RuntimeError: shape '[512, -1]' is invalid for input of size 768

Strictly speaking, the Unet architecture begins with "model.diffusion_model.time_embed.0.weight" not betas so i thought i might skip it

For axes you mean the P_bgx and P_bgy values right ?. So None and None then ?
I have a question on that too. There are a lot of layers. I'm unsure how to correctly label them all. For the layers with 2 P values, do i just keep going sequentially ? I reach P_bg50 or so that way.
For the layers with only one , how would that work exactly ? It's a bit hard to tell when i need to go from say P_bg1 to P_bg2 and to P_bg3 and so on. The architecture is divided in 3 parts - The input blocks, the middle blocks and the output blocks. So I'm wondering, is it P_bg1, _bg2, P_bg3 for those set of blocks or something else ?

You can skip betas, it's not a layer of the actual architecture but a stored parameter used for sampling and generating timestep embeddings. Same goes for alphas_cumprod, sqrt_alphas, and a dozen others. Anything that isn't either in diffusionmodel, first_stage_model or cond_stage_model is such a parameter. Actually you can probably skip first_stage_model (VAE) and cond_stage_model (CLIP) as well as those will probably be the same between two models. If not it would still make more sense to spec them separately as they are indeed separate models that only interact with each other manually, e.g. they have no connection in the model graph.
UNet is the interesting part, and this resides in diffusionmodel.model.*
EDIT: to clarify, these are the keys you can skip
betas
alphas_cumprod
alphas_cumprod_prev
sqrt_alphas_cumprod
sqrt_one_minus_alphas_cumprod
log_one_minus_alphas_cumprod
sqrt_recip_alphas_cumprod
sqrt_recipm1_alphas_cumprod
posterior_variance
posterior_log_variance_clipped
posterior_mean_coef1
posterior_mean_coef2
model_ema.decay
model_ema.num_updates

and these are the ones you can skip if you retain the same VAE and text encoder
cond_stage_model.*
first_stage_model.*

Thanks. Lots of dreambooth repos train the text encoder also now so i won't skip them.
I have some uncertainty on the type of certain layers.
The layers that have
emb_layers
proj_in
ptoj_out
transformer_blocks
skip_connection
self_attn
mid.attn
Do you have any idea ? Are they norm, conv, dense or neither ?

emb_layers is SiLU + linear -> dense
proj_in is Conv2d
proj_out is Conv2d
transformer_blocks is BasicTransformerBlock -> CrossAttention, LayerNorm, FeedForward

CrossAttention: all linear layers -> dense
FeedForward: GEGLU + linear -> dense

GEGLU: linear + gelu -> dense

skip_connection: is either Identity or Conv2d (Identity has no weights, so going by key, its always Conv2d)
self_attn: CLIPAttention -> dense
mid.attn: AttnBlock -> Conv2d

Keep in mind that the different Attention layer types might be either all conv or dense, but they are not just sequentially chained.
Rather they do qkv queries and batch matrix mult on results. I'm not sure if that has any impact on the results of the permutations.

emb_layers is SiLU + linear -> dense

proj_in is Conv2d

proj_out is Conv2d

transformer_blocks is BasicTransformerBlock -> CrossAttention, LayerNorm, FeedForward

CrossAttention: all linear layers -> dense

FeedForward: GEGLU + linear -> dense

GEGLU: linear + gelu -> dense

skip_connection: is either Identity or Conv2d (Identity has no weights, so going by key, its always Conv2d)

self_attn: CLIPAttention -> dense

mid.attn: AttnBlock -> Conv2d

Keep in mind that the different Attention layer types might be either all conv or dense, but they are not just sequentially chained. Rather they do qkv queries and batch matrix mult on results. I'm not sure if that has any impact on the results of the permutations.

Thanks for the response. It's helped a lot. Yes i think i'm going to skip the attention layers, at least for the first go around.
As samuel suggested, Labeling the axes as none for betas worked on skipping it so i just have to do them all now.
Forgot to ask, what are the time_embed (i'm assuming dense now), model.out.0 and out.2 (norm and conv i think) and .op (i think conv ) ?

Just an update. At first I had trouble building up. Some layers would work, most wouldn't. But most irritatingly, it felt inconsistent on what would work without error and what wouldn't. Today I figured out the issue was the axis and the torch size of the layers. Not all layers can or should be connected by axis and the torch size which ones can/should be. Anyway, I can get pretty much every later to permutate now. So I'll finish that and fight test this.

@ogkalu2 So the idea is to go pytorch -> TF -> rebasin -> pytorch? This sounds huge btw, thanks for doing it.

also, you probably saw this, but there's a PyTorch version, but I think you need to come up with a PermutationSpec: https://github.com/themrzmaster/git-re-basin-pytorch

@ogkalu2 So the idea is to go pytorch -> TF -> rebasin -> pytorch? This sounds huge btw, thanks for doing it.

I'm pretty just using the pytorch implementation now. The one you linked, I already knew about it. Ended up using Jax for flattening and unflattening the parmeters but that's about it.
No problem. It's my pleasure. Done with the unet. Working on the text encoder. There's no doubt it'll run now. Just if it merges as hoped. Fingers crossed for that.

@ogkalu2 Do you have a repository for this where I could take a look?

@lopho No. I wanted to finish things and see the results of a merged model before i uploaded anything to a repo.

@ogkalu2 Do you have a repository for this where I could take a look?

Although i did upload my first attempt here. A few things have changed to make it work, mostly the axes
https://imgur.com/a/DMnb7P8
But i added a bias option for the conv and added the dense emb layers in the easyblock

Hi @samuela would this run faster on a gpu ?

Yes, it should run quite a bit faster on a GPU since that will speed up the matrix multiples but the linear assignment problem solve still happens on the CPU, so I don't think the speedup you'd get would be anything too crazy... I've never tried running on CPU only

Yes, it should run quite a bit faster on a GPU since that will speed up the matrix multiples but the linear assignment problem solve still happens on the CPU, so I don't think the speedup you'd get would be anything too crazy... I've never tried running on CPU only

Ah I see. If I don't specify device as cpu, i get
File "/notebooks/weight_matching.py", line 798, in weight_matching
A += w_a @ w_b.T
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu! (when checking argument for argument mat2 in method wrapper_mm)

@lopho @affableroots @samuela
I'm done with the spec. I've not tested a merge yet but that will take time so i've uploaded it here for anyone to test as well.
https://github.com/ogkalu2/Merge-Stable-Diffusion-models-without-distortion

Hi @samuela How many iterations does the weight matching typically run ? I know max iterations is 100 but it doesn't usually go that high, i don't think ?

It totally depends on the model and initialization. I've seen it take as few as 3 and as many as 50. It is guaranteed to terminate though, so don't worry it can't run forever!

I keep OOMing on 32GB RAM, any tips on what I can delete when, or maybe running the merge in parts?

I keep OOMing on 32GB RAM, any tips on what I can delete when, or maybe running the merge in parts?

Really ? Huh. I'm just running on vast right now.  You can't really run in parts right now. As for what to delete, it's possible to skip some layers but i honestly don't know exactly what i can skip yet. The vae layers would be the first thing i'd remove but i don't know besides that. I'll look into that.
The OOM errors seem odd though. Do you actually get those errors on your console/terminal or does your system freeze up or something ?

 The test i have running has 2 dreambooth models pruned to 2GB. The bigger the size of the models, the higher the RAM usage. I didn't realize 4gb models were too much for 32 GB ram systems currently. The problem is the linear sum assignment. It can only run on the CPU

@samuela
Have someone here who's running through this in minutes lol
https://github.com/ogkalu2/Merge-Stable-Diffusion-models-without-distortion/issues/1#issuecomment-1319102078
Anyway i have a new problem now. So the perm spec runs fine and the parameters get updated fine. The previous line i wrote to save the model won't work. After defining the state dict(s) as state_a = model_a["state_dict"], i tried to save the model with
torch.save({
"state_dict": state_b(updated_params)
}, output_file)
but get hit with
"state_dict": state_b(updated_params)
TypeError: 'dict' object is not callable

Hi @samuela
Something seems to be up with the get_permuted_params function. applying the permutation with it just seems to bias whatever the selected model parameters are.
So a merge with apply_permutation(permutation_spec, final_permutation, mode_a state dict) just produces a model that is basically model a and a merge with apply_permutation(permutation_spec, final_permutation, mode_b state dict) just produces a model that is basically model b.
Any idea what the issue might be ?

So a merge with apply_permutation(permutation_spec, final_permutation, mode_a state dict) just produces a model that is basically model a and a merge with apply_permutation(permutation_spec, final_permutation, mode_b state dict) just produces a model that is basically model b.

Hi @ogkalu2, how are you measuring the difference between the permuted model and the original? Have you inspected the final_permutations to see if they are close to identity? Depending on the kind of fine-tuning you're doing, it could be reasonably expected that the optimal permutation is already close to identity. This is a convenient property of fine-tuning that you generally don't leave the pre-training basin, esp. with large models and small learning rates, see eg https://arxiv.org/abs/2109.01903, https://twitter.com/moyix/status/1581390268368302080, and so forth.

Hi @ogkalu2! The exact framework that the model runs in is not super important. For example, we have used our JAX code to align the weights of two PyTorch models in the past. The only important part is that you can load the weights into Python/JAX and that you have a correct PermutationSpec for your model.
In general writing down the PermutationSpec will be the more challenging step. We are currently working on a pure-PyTorch version, including a "tracer" that can automatically generate the PermutationSpec for you but this is not ready for release just yet.
Would be very cool to see if this works on StableDiffusion models! Do let me know if you get it working!

Hello, I wonder if there is an update on the automatic tracer in pytorch for the permutation spec? Thanks!


chore(main): release 0.38.0

:robot: I have created a release beep boop
0.38.0 (2024-05-10)
Features

TopicClient follow-up revisions" (#287) (66e190d)

Miscellaneous

allow IntoBytesIterable on statically allocated arrays (#288) (82c556c)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/momentohq/client-sdk-rust/releases/tag/v0.38.0 :sunflower:


Fix german translations - administration Part 1

1. Why is this change necessary?
Currently, there are some errors in German translations.
2. What does this change do, exactly?
Fixes German translations in the first 7 admin-modules.

misleading context to English source, including punctuation mark
grammar
spelling
add missing translations

3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hi @tinect, you still need to accept the "Contributor License Agreement" before we can go on with this PR

@pantrtxp Now it's rebased onto master

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-7792
Please use this issue to track the state of your pull request.

Fixed one misleading comma :-)

@GitEvil Sorry, so much lines. Now ready ;-)

Thank you for your contribution :blue_heart: :tada:


envoy crd / ingress controller support

3 commits:

add ciliumegressnatpolicy and ciliumenvoyconfig to cluster role.
update cluster role for ingress controller
create cilium ingress class.

aks failed to pull quay.io/cilium/cilium-cli-ci:313536d43e475cac9bcabd155e26f67d2d3dfd20. i can pull it now, so i think it's a transient failure. restarting.

https://github.com/cilium/cilium-cli/runs/4451759861?check_suite_focus=true
failed to download eksctl. restarting!


Frontend orientation

Current implementation still requires login. Landing page now uses Vue. CSS and forms have been un-broken.

Thanks for all your work on this @Ry-Dowd. I'll try to review this first thing tomorrow

@exbinary per our convo, I'm going to go ahead and merge (so I can test deployment to Heroku), and maybe if you add any comments when you're able, that'd be cool?


Installation Doc

Hi, Can you provide a installation document on knot-server?

@knkrth Hi! Sorry I haven't put up any instructions yet. I'll try and give you a quick rundown:
You'll need to have composer and PHP 7.1 or greater.

Clone the repo: git clone git@github.com:knotworks/knot-server.git
cd knot-server && composer install
php artisan migrate && php artisan passport:keys
php artisan passport:client --password. Name it whatever you like.
php artisan storage:link

The migrations include a table for queues, so if you'd like to use the database driver for queues be sure to set QUEUE_DRIVER=database in your .env file. If not, just leave it as sync.
As of right now, photo posts are defaulted to use Amazon S3 for uploading. If you don't want to use S3 locally you should be safely able to set FILESYSTEM_CLOUD=local in your .env file. I haven't personally confirmed this works, but it should.
Finally you'll need to run php artisan queue:work when testing any image uploads (profile photos or photo posts).
That should get you up and running! If something isn't working feel free to let me know. I'll try and fine tune local installation a little better in the future (including not using S3 by default).

I got this errors while running composer install
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for aws/aws-sdk-php 3.65.2 -> satisfiable by aws/aws-sdk-php[3.65.2].
    - aws/aws-sdk-php 3.65.2 requires ext-simplexml * -> the requested PHP extension simplexml is missing from your system.
  Problem 2
    - Installation request for phar-io/manifest 1.0.3 -> satisfiable by phar-io/manifest[1.0.3].
    - phar-io/manifest 1.0.3 requires ext-dom * -> the requested PHP extension dom is missing from your system.
  Problem 3
    - Installation request for phpunit/php-code-coverage 6.0.7 -> satisfiable by phpunit/php-code-coverage[6.0.7].
    - phpunit/php-code-coverage 6.0.7 requires ext-dom * -> the requested PHP extension dom is missing from your system.
  Problem 4
    - Installation request for phpunit/phpunit 7.3.2 -> satisfiable by phpunit/phpunit[7.3.2].
    - phpunit/phpunit 7.3.2 requires ext-dom * -> the requested PHP extension dom is missing from your system.
  Problem 5
    - Installation request for theseer/tokenizer 1.1.0 -> satisfiable by theseer/tokenizer[1.1.0].
    - theseer/tokenizer 1.1.0 requires ext-dom * -> the requested PHP extension dom is missing from your system.
  Problem 6
    - aws/aws-sdk-php 3.65.2 requires ext-simplexml * -> the requested PHP extension simplexml is missing from your system.
    - league/flysystem-aws-s3-v3 1.0.19 requires aws/aws-sdk-php ^3.0.0 -> satisfiable by aws/aws-sdk-php[3.65.2].
    - Installation request for league/flysystem-aws-s3-v3 1.0.19 -> satisfiable by league/flysystem-aws-s3-v3[1.0.19].

  To enable extensions, verify that they are enabled in those .ini files:
    - /etc/php/7.1/cli/php.ini
    - /etc/php/7.1/cli/conf.d/10-mysqlnd.ini
    - /etc/php/7.1/cli/conf.d/10-opcache.ini
    - /etc/php/7.1/cli/conf.d/10-pdo.ini
    - /etc/php/7.1/cli/conf.d/20-calendar.ini
    - /etc/php/7.1/cli/conf.d/20-ctype.ini
    - /etc/php/7.1/cli/conf.d/20-exif.ini
    - /etc/php/7.1/cli/conf.d/20-fileinfo.ini
    - /etc/php/7.1/cli/conf.d/20-ftp.ini
    - /etc/php/7.1/cli/conf.d/20-gettext.ini
    - /etc/php/7.1/cli/conf.d/20-iconv.ini
    - /etc/php/7.1/cli/conf.d/20-json.ini
    - /etc/php/7.1/cli/conf.d/20-mbstring.ini
    - /etc/php/7.1/cli/conf.d/20-mcrypt.ini
    - /etc/php/7.1/cli/conf.d/20-mysqli.ini
    - /etc/php/7.1/cli/conf.d/20-pdo_mysql.ini
    - /etc/php/7.1/cli/conf.d/20-phar.ini
    - /etc/php/7.1/cli/conf.d/20-posix.ini
    - /etc/php/7.1/cli/conf.d/20-readline.ini
    - /etc/php/7.1/cli/conf.d/20-shmop.ini
    - /etc/php/7.1/cli/conf.d/20-sockets.ini
    - /etc/php/7.1/cli/conf.d/20-sysvmsg.ini
    - /etc/php/7.1/cli/conf.d/20-sysvsem.ini
    - /etc/php/7.1/cli/conf.d/20-sysvshm.ini
    - /etc/php/7.1/cli/conf.d/20-tokenizer.ini
    - /etc/php/7.1/cli/conf.d/20-zip.ini
  You can also run `php --ini` inside terminal to see which files are used by PHP in CLI mode.```

It looks like your server doesn't have the ext-simplexml and ext-dom extensions. You'll want to make sure you have those, as the AWS package depends on them. I generally provision my servers with Laravel Forge, so they come prebuilt with all this stuff.

After installing
sudo apt-get install php-xml

It works.

Closing this issue, but note to others, the above instructions are not quite relevant anymore. Newer installation instructions will be coming soon!

Closing this issue, but note to others, the above instructions are not quite relevant anymore. Newer installation instructions will be coming soon!


Feature/hibernate query cache

Checklist

[ ] I tested the changes and all related features on the test server https://artemistest.ase.in.tum.de.
[ ] I documented my source code using the JavaDoc / JSDoc style.
[ ] I added integration test cases for the server (Spring) related to the features
[ ] I added integration test cases for the client (Jest) related to the features
[ ] I added screenshots/screencast of my UI changes
[ ] I translated all the newly inserted strings

Motivation and Context

Description

Steps for Testing

Log in to ArTEMiS
Navigate to Course Administration
...

Screenshots

There is not much going here, so I'll close this to keep the open pull requests small.
Feel free to reopen it, when there is additional progress


Custom formula options can't be parsed

Please note we will close your issue without comment if you delete, do not read or do not fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
I was trying to install a custom formula with custom options. Actually, I found this issue on a formula with decent amount of options, but it can be reproduced with much smaller formula (basically, took it from the cookbook).
class Foo < Formula
  desc ""
  homepage ""
  url "https://example.com/foo-0.1.tar.gz"
  sha256 "85cc828a96735bdafcf29eb6291ca91bac846579bcef7308536e0c875d6c81d7"

  # depends_on "cmake" => :build

  option "with-ham", "Description of the option"
  option "without-spam", "Another description"

  def install
    # ENV.deparallelize
    system "./configure", "--disable-debug",
                          "--disable-dependency-tracking",
                          "--disable-silent-rules",
                          "--prefix=#{prefix}"
    # system "cmake", ".", *std_cmake_args
    system "make", "install"
  end

  test do
    system "false"
  end
end

What happened (include command output)
$ brew install Foo.rb --with-ham

Command output

Updating Homebrew...
==> Auto-updated Homebrew!
Updated Homebrew from 3b78b1aa9 to ef3b14814.
No changes to formulae.
Usage: brew install [options] formula
Install formula. Additional options specific to formula may be appended to
the command.
Unless HOMEBREW_NO_INSTALL_CLEANUP is set, brew cleanup will then be run for
the installed formulae or, every 30 days, for all formulae.
-d, --debug                      If brewing fails, open an interactive
                                 debugging session with access to IRB or a
                                 shell inside the temporary build directory.
    --env                        If std is passed, use the standard build
                                 environment instead of superenv. If super
                                 is passed, use superenv even if the formula
                                 specifies the standard build environment.
    --ignore-dependencies        An unsupported Homebrew development flag to
                                 skip installing any dependencies of any
                                 kind. If the dependencies are not already
                                 present, the formula will have issues. If
                                 you're not developing Homebrew, consider
                                 adjusting your PATH rather than using this
                                 flag.
    --only-dependencies          Install the dependencies with specified
                                 options but do not install the formula
                                 itself.
    --cc                         Attempt to compile using the specified
                                 compiler, which should be the name of the
                                 compiler's executable, e.g. gcc-7 for GCC
                                 7. In order to use LLVM's clang, specify
                                 llvm_clang. To use the Apple-provided
                                 clang, specify clang. This option will
                                 only accept compilers that are provided by
                                 Homebrew or bundled with macOS. Please do
                                 not file issues if you encounter errors
                                 while using this option.
-s, --build-from-source          Compile formula from source even if a
                                 bottle is provided. Dependencies will still
                                 be installed from bottles if they are
                                 available.
    --force-bottle               Install from a bottle if it exists for the
                                 current or newest version of macOS, even if
                                 it would not normally be used for
                                 installation.
    --include-test               Install testing dependencies required to
                                 run brew test formula.
    --devel                      If formula defines it, install the
                                 development version.
    --HEAD                       If formula defines it, install the HEAD
                                 version, aka. master, trunk, unstable.
    --fetch-HEAD                 Fetch the upstream repository to detect if
                                 the HEAD installation of the formula is
                                 outdated. Otherwise, the repository's HEAD
                                 will only be checked for updates when a new
                                 stable or development version has been
                                 released.
    --keep-tmp                   Retain the temporary files created during
                                 installation.
    --build-bottle               Prepare the formula for eventual bottling
                                 during installation, skipping any
                                 post-install steps.
    --bottle-arch                Optimise bottles for the specified
                                 architecture rather than the oldest
                                 architecture supported by the version of
                                 macOS the bottles are built on.
-f, --force                      Install without checking for previously
                                 installed keg-only or non-migrated
                                 versions.
-v, --verbose                    Print the verification and postinstall
                                 steps.
    --display-times              Print install times for each formula at the
                                 end of the run.
-i, --interactive                Download and patch formula, then open a
                                 shell. This allows the user to run
                                 ./configure --help and otherwise
                                 determine how to turn the software package
                                 into a Homebrew package.
-g, --git                        Create a Git repository, useful for
                                 creating patches to the software.
-h, --help                       Show this message.

Error: invalid option: --with-ham

What you expected to happen
Custom option to be parsed.
Step-by-step reproduction instructions (by running brew commands)

save provided formula somewhere
brew install Foo.rb --with-ham
Notice the error.

Interestingly, if I disable the homebrew autoupdate and revert https://github.com/Homebrew/brew/pull/7333, then everything works.

set -x HOMEBREW_NO_AUTO_UPDATE false (I am using fish, hence the syntax)
cd /usr/local/Homebrew/
git revert 8d868b739
cd back to formula location
brew install Foo.rb --with-ham - option is parsed, it just says that URL is invalid, which is expected.

Output of brew config and brew doctor commands

$ brew config
HOMEBREW_VERSION: 2.2.13-84-gef3b148
ORIGIN: https://github.com/Homebrew/brew
HEAD: ef3b148147717e0f317d6e51f9b56e50558e6d5f
Last commit: 15 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 0a27529d1d443cec9237ccce19168aac9d6de8e1
Core tap last commit: 4 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.LWJk7M9QjH/org.macosforge.xquartz:0
HOMEBREW_EDITOR: emacsclient
HOMEBREW_MAKE_JOBS: 8
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
Clang: 11.0 build 1103
Git: 2.26.1 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
Java: 13.0.1, 1.8.0_192
macOS: 10.15.4-x86_64
CLT: N/A
Xcode: 11.4.1
XQuartz: 2.7.11 => /opt/X11

$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: Putting non-prefixed coreutils in your path can cause gmp builds to fail.

Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  docker
  emacs
  gnupg

Confirm that it is fixed. Thank you very much!


empty window

somebody experienced an empty window when opening the gui?
(using linux mint 64 , tried both cinnamom and xfce)

the project is abandoned?

I think I can look into it, but it will be a while(days) before I can even start.
Are you using the latest Linux Mint version 22 codename Wilma from here https://linuxmint.com/?

21.3 Virginia with Xfce and Cinnamom

I setup a 21.3 cinnamon virtual machine and it ran without any white screen issue. Then I realized I never published the binaries here on github so I added a release. I did some research and found a potential fix for the white screen. I can make the change but there's no way for me to test it.
Did you build this from source or did you use the installer from the web page, https://clintons3d.com/plugins/other/micmacgui/index.html ? If you built it yourself try the deb installer instead. I should have the change in place this weekend.

I installed from deb, i also tried the source code but had this error,

I also tried <yarn install --ignore-engines>, if finish the process but after it looks like nothing is installed.

I updated the package to work with newer Node versions, added instructions to the README for building it and using it in development and altered a react router command that I hope might help with the white screen issue. The installer for the new v1.1.1 is here: http://clintons3d.com/plugins/downloads/micmac_gui_1.1.1_amd64.deb


Add support for simple subroutines (EIP-2315, scheduled for Berlin)

What is wrong?
EIP 2315 introduces three opcodes to support subroutines: BEGINSUB, JUMPSUB and RETURNSUB which Py-EVM currently does not yet support.
How can it be fixed

Read the EIP
Add support for the three opcodes
Add tests for all official test cases

I'm going to look into this.

Can I take a shot at this? seems an interesting job

@Peppece I started with this today. I have a rough implementation and are now trying to work myself through the test cases that are specified in the EIP.
I also believe that some familiarity with the code base would be good to work on this issue. That said, if you think this would make a great code challenge for you then I'm happy to throw my code away and take yours!
I propose to put my code away for some days and wait for you to create a PR to show some progress on the issue. I would recommend to base your work on #1933 which has the basic boilerplate code to support the upcoming Berlin fork.
You may also want to look into test_opcodes to get a sense for how the other opcode tests are written.
Please let me know if you want to take a stab on that or find something else. For instance, there's also #1927 that needs to be tackled for the upcoming Berlin fork.

Awesome, thank you soo much! I’ll dig this and get back asap.

@Peppece We'll save this for you until all the other EIPs are done. Can't save it too long though, because the mainnet date approaches.


Remove unrequired variables

I cannot see where these are used in this defined type. In the main ::duplicity defined type (init.pp) these are used to create a cron job, but in the specific job defined type they are simply not referenced again.
I believe they were inadvertently moved across in 4eb6a7009b3eeb84a02e81d8bb765dff2d8a2c37

Hmm, tests for ruby 1.9.3 are failing because:
Gem::InstallError: json_pure requires Ruby version ~> 2.0.

Added a commit specifying the version of json_pure.

This is good.  The thing we would need to keep is the $weekday param which is used here.  As discussed with @alexmuller, I'll submit a PR to upstream.


wasm is enabled by default in Edge 16

https://twitter.com/MSEdgeDev/status/894607665334177792

Thanks!


feat(theme): show unlisted/draft banners in dev mode

Motivation
Fix #8285
Test Plan
ci & unit test & argos
Test links
Deploy preview: https://deploy-preview-10376--docusaurus-2.netlify.app/

LGTM thanks
Did some refactoring to cleanup but this works well

FYI this broke our builds since we were using overrides for DocItem/Layout that had import to @theme/Unlisted. Not sure if you consider that breaking or not, just wanted to let you know, we'll change the import on our end.

@B4nan it's not marked as a safe component to swizzle so we keep the right to do refactors like this one in minor versions.
I'll see how we could make it easier for those like you who swizzle unsafe components. Maybe listing changes in our release notes would be helpful?


App crashes when server is unavailable.

When the server is unavailable (like blocked in my country) the app will crash rather than displaying an error message.

Can you post a stacktrace?

Will try to reproduce and post a stack trace if possible.

If you have a stacktrace we can fix it, I'll also try to reproduce.

Here's a logcat from when I launched the application.
http://pastebin.com/0zvWx7pU
I tried launching the app without having an internet connection, and it crashes instantly. That should be much easier to reproduce.

Can confirm - mine says about the same.

Working on it right now, should have it fixed shortly here, thanks for the stacktrace guys!


Dapr-1.0.0-rc3 (and newer) breaks CloudEvent.deserialize for data-types other then String

In what area(s)?
/area runtime
Ask your question here
when updating from dapr 0.10.0 to the release candidates (first introduced in 1.0.0-rc3) we first noticed that many of our unit test were failing. Having a deeper look shows that this is also a runtime problem: the CloudEvent.deserialize method does not work as before. It deserialized the payload as "LinkedHashMap".
The reason is obviously that the type for "data" was changed from String to Object. With that, the deserializer cannot write the json-string into the correct object class.
Up to rc3 there was the code-snippet
if (node.has("data") && !node.get("data").isNull()) {
JsonNode dataNode = node.get("data");
if (dataNode.isTextual()) {
data = dataNode.textValue();
} else {
data = node.get("data").toString();
}
}
Hence data contained a valid json-String after deserialisation. With that, we were able to invoke a second MAPPER.deserialize() on the data-field.
We were able to implement a workaround: We simply do not use dapr's CloudEvent class at all. Instead we provide an own version of this class (which is basically a copy of the previous version of dapr's CloudEvent class).
But is that the intended usage? I think dapr should provide a mean to correctly deserialize into the client's data-class

I am looking into how to make this easier for apps to handle their own deserialization.

@yaron2 : thanks for you suggestion. I just compared the rc-version sources in github: The breaking change in CloudEvent was introduced in rc-2. So falling back to rc-3 makes no sense.

I have found a way to deserialize correctly from LinkedHashMap. Just use ObjectMapper.convertValue(). See in the test code below:
public class CloudEventTest {

  private static final ObjectMapper OBJECT_MAPPER = new ObjectMapper();

  public static class MyClass {
    public int id;
    public String name;
  }

  @Test
  public void deserializeObjectClass() throws Exception {
    String content = "{\n" +
        "    \"specversion\" : \"1.0\",\n" +
        "    \"type\" : \"com.github.pull_request.opened\",\n" +
        "    \"source\" : \"https://github.com/cloudevents/spec/pull\",\n" +
        "    \"subject\" : \"123\",\n" +
        "    \"id\" : \"A234-1234-1234\",\n" +
        "    \"time\" : \"2018-04-05T17:31:00Z\",\n" +
        "    \"comexampleextension1\" : \"value\",\n" +
        "    \"comexampleothervalue\" : 5,\n" +
        "    \"datacontenttype\" : \"application/json\",\n" +
        "    \"data\" : {\"id\": 1, \"name\": \"hello world\"}\n" +
        "}";

    MyClass expected = new MyClass() {{
      this.id = 1;
      this.name = "hello world";
    }};

    CloudEvent cloudEvent = CloudEvent.deserialize(content.getBytes());
    assertEquals("application/json", cloudEvent.getDatacontenttype());

    MyClass myObject = OBJECT_MAPPER.convertValue(cloudEvent.getData(), MyClass.class);
    assertEquals(expected.name, myObject.name);
  }
}

Closing this issue. See solution above.

Hi @artursouza ,
sorry for reacting so late. We were very busy changing the dapr-runtime ...
I can confirm that the the suggested ObjectMapper.convertValue() solution works (at least for the examples I tested so far).
Nevertheless we don't think it is a good solution. As you know, convertValue would first serialize the data, before calling readValue again. Overall it is just superfluous work. First you deserialize in CloudEvent deserialize, then you serialize again, before finally deserialize.
What we would prefer is an additional CloudEvent.deserialize method which lets users specify the desired target-class of the data. Don't know whether that is feasable.
Additionally, it turned out that it makes sense to have the used ObjectMapper configurable. E.g. we typically need to set
.findAndRegisterModules()
.registerModule(new ParameterNamesModule())
.registerModule(new Jdk8Module())
.registerModule(new JavaTimeModule())
.disable(DeserializationFeature.ADJUST_DATES_TO_CONTEXT_TIME_ZONE)
.configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false)
.setSerializationInclusion(JsonInclude.Include.NON_NULL);
on it. That means, CloudEvent.deserialize() would also (optionally) need a parameter to pass the ObjectMapper.
As I already said: We currently implemented a private version of the CloudEvent class which works. However, it would be nice to make use of CloudEvent directly in order to be future-proof to changes in this area.


WebJobs deploy from Visual Studio Community Mac OS

Hey,
Working on a Mac with VS Community 7.5.1 and I'm trying to following this guide to add a WebJob to my .net core Web App.
Added a Console App project and "linked" it with the Web App through the json files as described, but a "Publish" on the Web App doesn't create the WebJob on Azure...
Also on the Console App I can't see a "Publish as WebJob" anywhere, nor any mention of "WebJobs".. :(
Is this not implemented on Mac ? any alternatives ?
Thx for the help, bye

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

ID: 7c1407af-81a5-52e7-a800-79d57704a876
Version Independent ID: 5ec30406-731f-6198-99a1-9d4ee5c67475
Content: Develop and deploy WebJobs using Visual Studio - Azure
Content Source: articles/app-service/websites-dotnet-deploy-webjobs.md
Service: app-service
Product: unspecified
GitHub Login: @tdykstra
Microsoft Alias: glenga;david.ebbo;suwatch;pbatum;naren.soni

@paulceli Could you check if the following NuGet package is installed:
https://www.nuget.org/packages/Microsoft.Web.WebJobs.Publish/
Also, pls ensure you have installed the required Workloads for your VS for Mac (not all workloads are supported for mac yet).

@paulceli We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

i've installed https://www.nuget.org/packages/Microsoft.Web.WebJobs.Publish/ but there is no workload option for VS for mac to publish this, I believe? https://docs.microsoft.com/en-us/visualstudio/mac/workloads

Yes workloads is not a thing on Mac. But Microsoft very recently added the possibility to publish Functions from VS Mac on the "beta" updates channel.
I've bailed on WebJobs, has I get the feeling that Microsoft is pushing Durable Functions instead.


Duplicated paragraph

I found a duplicated text on that page, suggesting to remove it.
That means when designing experiences in Bedrock Edition, you should be aware of the different types of input players will be using. Also, keep in mind how your players are playing. While spam clicking might be OK with a mouse or even a controller, it would provide a poor experience for touch players. Keyboard players with a bow might have perfect aim, but it's a lot more difficult when using a controller or touch controls. Complex parkour might even be game-breaking for a mobile player.

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

ID: 8293cbae-4896-4d03-9764-09e23027db99
Version Independent ID: 6ada8e59-a330-e8ca-5967-8c5dc67db846
Content: Differences Between Minecraft Bedrock Edition and Minecraft Java Edition
Content Source: creator/Documents/DifferencesBetweenBedrockAndJava.md
Product: gaming
GitHub Login: @docsbryce
Microsoft Alias: v-bbortree

Hey, I was just about to raise the same issue. I've made a quick edit and submitted pull request.
https://github.com/MicrosoftDocs/minecraft-creator/pull/502

Great catch! This will be updated with the next release.


How to bring back pulsating fade in fade out effect?

I am trying multiple ways , but cant do.
also the background color of cursor is opque , is that happened due to tiled rendering? Because before update to 0.13 , it is fine.

I think my conf is screwed , i can't configure blink interval or pulse duration at all. Here it is:
  "block-cursor":
    preview: "The quick brown fox jumps over the lazy dog"
    global:
      blinkOff:
        borderColor:
          red: 8
          green: 200
          blue: 230
          alpha: 1
        backgroundColor:
          red: 255
          green: 0
          blue: 0
          alpha: 0
        borderStyle: "bordered-box"
      blinkOn:
        borderColor:
          red: 255
          green: 0
          blue: 0
          alpha: 0.15
        backgroundColor:
          red: 0
          green: 0
          blue: 0
          alpha: 0
        borderStyle: "bordered-box"
      pulseDuration: 3000
    primaryColor: {}
    secondaryColor: {}
    blinkInterval: 3000

Hey, thanks for reporting the issue. Turns out it was pretty easy to fix the pulseDuration setting.
I've removed the blinkInterval setting in v0.13.0, and created its own package: cursor-blink-interval. It was quite complicated to implement it in this package after the rewrite...

Thanks gonna try!

So it seems that Blink Interval no longer works? Got it .

But i still see it inside setting dialog , is that due to leftover at config.cson ? Should i delete it?

Yeah, leftovers at config.cson from the previous version. You can safely delete the value.


Update tips.md

Changes:

smart-enter.yazi: add support for zoxide
2 panes borders

Thank you!

Closing as full-border has been moved to https://github.com/yazi-rs/plugins/tree/main/full-border.yazi as a separate plugin from the tips page


Documented EOF in ATTACH_CONTAINER_INPUT

This documents how to indicate when EOF is reached on STDIN.
See https://github.com/dcos/dcos-core-cli/blob/009999e1d8f4eddca5d961152f32669e02ed81d5/python/lib/dcos/dcos/mesos.py#L1657-L1658

@vinodkone PTAL

Yes, I think this makes sense to include.
On Tue, Jul 2, 2019 at 2:32 PM Vinod Kone<EMAIL_ADDRESS>wrote:

@vinodkone commented on this pull request.
LGTM. Should we add the extra bit about the expectation when TTY is
enabled? See comment here:
https://github.com/apache/mesos/blob/master/src/slave/containerizer/mesos/io/switchboard.cpp#L1727
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/mesos/pull/340?email_source=notifications&email_token=AAR5KLCWPPLENB32KV7KPSTP5ONNVA5CNFSM4H426542YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB5JKNXQ#pullrequestreview-257074910,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAR5KLCXS5QC7MHPSD6YDZDP5ONNVANCNFSM4H42654Q
.

--
James DeFelice
585.241.9488 (voice)
650.649.6071 (fax)

Updated it, I've used launched with an associated IOSwitchboard instead of tty as it's what's being used elsewhere on the page.

@vinodkone PTAL, feedback has been addressed

IOSwitchboard is used by containers with or without TTY.
s/launched with an associated IOSwitchboard/launched with TTYInfo in their ContainerInfo/

@vinodkone : is this sentence a few lines above accurate then?

This call can only be made against containers that have been launched with an associated IOSwitchboard (i.e. nested containers launched via a LAUNCH_NESTED_CONTAINER_SESSION call or normal containers launched with a TTYInfo in their ContainerInfo)

See also https://github.com/dcos/dcos-core-cli/blob/1.14-patch.x/python/lib/dcos/dcos/mesos.py#L1425-L1428, where the code treats a missing I/O Switchboard as missing TTY.

@bamarni For a regular container launched by a framework, IOSwitchboard is only enabled when TTY is requested. But an operator can launch a debug container without TTY and IOSwitchboard is still enabled AFAIK. In other words, TTY => IOSwitchboard but not the other way around. @abudnik @Gilbert88 can you confirm?

@bamarni For a regular container launched by a framework, IOSwitchboard is only enabled when TTY is requested. But an operator can launch a debug container without TTY and IOSwitchboard is still enabled AFAIK. In other words, TTY => IOSwitchboard but not the other way around. @abudnik @Gilbert88 can you confirm?

Yes, correct.
Also, a debug container can be launched only by LAUNCH_NESTED_CONTAINER_SESSION call.

Thanks for the clarification @abudnik @vinodkone , I've updated the PR


navigation between languages

Some pages have a more nested file path than others (i.e. examples) which makes it difficult to have the non-default language as simply another folder because the links on the sidebar would have to be different on the english site vs the spanish (or other languages) site.
Currently, I think the best solution is to create a completely new domain with either a specific extension or a subdomain to represent the site in another language, so the sidebar partial stays the same for all languages.
I must figure out how exactly this should be implemented if this is how we decide to structure the site. Also, I am open to other suggestions/feedback on the issue if anyone has any!

woohoo we figured this out!


Waypoint: Return a Value from a Function with Return

Challenge Waypoint: Return a Value from a Function with Return has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.106 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
// Example
function minusSeven(num) {
  return num - 7;
}

// Only change code below this line
function timesFive(numb) {
  return numb * 5;
}

/* problem in this waypoint is that it is not complete yet i can pass it , it should be more like this
function plusThree(num) {
return num + 3;
}
var answer = plusThree(5); // 8
but var answer = plusThree(5); is missing
*/

You're suggesting that we also have the user invoke the function?

yes i think that is what it means , it took me long time to realize that timesfive had a background of 5.
or explain it in a comment , thanks.

I'm not sure that there is anything to fix here. This is pretty much operating as designed.


(PDB-1925) PQL Prototype

Consider this a preview/prototype, until we clean up.
Still a few things that need working on, either for this patch or later on:

Extraction can be after the filter, so far people prefer this to the current placement
Currently I have the PQL hook in a global place, this needs changing
Documentation
I'd like to be able to express JSON error messages, but I think this might involve more work
~> support doesn't exist
IN  supported doesn't exist
No pagination
No functions or aggregation (group by et al)

And a couple of other minor syntactical things.

Finalising this work is mainly part of: https://tickets.puppetlabs.com/browse/PDB-1927

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/334/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/346/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/349/
Test PASSed.

A few minor comments, but looks good to me generally with respect to code and functional testing aside from AJ's comment on throwing a PQL error on invalid json. I suspect there may be more stuff that comes to light when we document it. Nice work.

Fwiw also functionally tested this and looks nice to me as well.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/364/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/365/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/366/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/367/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/368/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/369/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/370/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/371/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/377/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/382/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/383/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/384/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/385/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/386/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/391/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/392/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/401/
Test PASSed.

@wkalt re: the integer E notation problem, I'm tempted to bump it for now, since it can be added later if we want ... that is, if you think its important to add E notation for integers I might just create a small ticket for its support for later. What do you think? My feeling at the moment is that we have real E notation working properly, that covers most cases, integer support is additive and well - I'm tempted to wait for people to ask explicitly for it.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/402/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/405/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/423/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/425/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/426/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/427/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/428/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/429/
Test PASSed.

I've tested this manually and the functionality looks good. I'll take a look at the code in the morning

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/453/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/467/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/477/
Test PASSed.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/478/
Test FAILed.

That was me cancelling a broken job ^^. Another job is coming through soon.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/479/
Test FAILed.

@puppetlabs-jenkins retest this please

Last failure due to cancelled an old job ^^

Refer to this link for build results (access rights to CI server needed):
http://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_puppetdb_init-multijob_githubpr-master/480/
Test PASSed.

+1


[LayoutAnimation] Opacity doesn't animate on update

See: https://rnplay.org/apps/1gl8Uw
Should be fading out to 0.1, but changes suddenly instead. cc @nicklockwood

Thanks for creating the example. It looks like you've slightly misunderstood how the layout animations are supposed to be used. They don't let you animate arbitrary property changes, but instead specifically support the following:

when updating a component, you can animate the frame only, meaning that the frame will animate from its previous value to its new value.

when creating a component, you can animate the scaleXY and/or opacity. If you animate scaleXY then the view will be scaled from a scale of {0,0} to whatever scale was set ({1,1} by default). If you animate opacity then the opacity will fade from 0 to whatever opacity was set (1.0 by default).

In your example, you are updating the opacity of a component that is already on screen, to trigger a re-render. This will invoke the update animation, but since the frame has not changed, nothing will animate.
To recap: LayoutAnimations only support animating opacity from 0 to n (where n is the current opacity style value of your component), and only when a component is mounted, not when an existing component is being updated.
To animate opacity in the way you want, you'll need to use the Animated API instead.
(@sahrens the LayoutAnimations API does seem a bit clunky and confusing. Is this how it was intended to work? And if so, do you think it's worth revisiting it? We could relatively easily support animating other properties besides the frame, and maybe there's a better way to specify the scaleXY/opacity constants so that they won't be confused with component properties?)

cc @vjeux for thoughts on the API

Instead of
property: LayoutAnimation.Properties.opacity/scaleXY
Maybe we could use something like
transition: LayoutAnimation.Transitions.fadeIn/zoomIn ?
Also, it seems odd that you can only fade in or zoom in - why not allow both?

Thanks for clarifying that @nicklockwood! I suppose that makes sense given that it is called LayoutAnimation :P It would be very useful to be able to animate opacity with this as well -- I imagine the idea was to include that in the delete phase of LayoutAnimation but since that seems like it will be a tricky thing to implement, opacity in update might be a good solution for now at least.

awesome work here, I'd totally support renaming Properties to Transitions and opacity/scaleXY to fadeIn/zoomIn. It got me really confused when I first started using it.

Question, is there a way to specifically opt-ou an element for transitions?

LayoutAnimation is primarily intended simply to do the things that are common and cumbersome with the Animated API, which is the creation and cascading layout updates of views, especially when involving Text which requires asynchronous/native text measurement.
The idea was that everything else should be handled by Animated so as to reduce overlapping functionality.
That said, the animation paradigm of LayoutAnimtion has proven very powerful, easy to use, and performant, so we might want to reconsider expanding the functionality into something with more controls (e.g. subtree scoping rather than global via props and/or react context or something, more curve specifications, etc) and more animatable attributes (basically any prop/keypath that is natively animatable, like opacity, rotation and 3D transforms, etc).
I'm kinda leaning towards the beefing up LayoutAnimation.

On Dec 15, 2015, at 11:06 AM, Gaston Morixe<EMAIL_ADDRESS>wrote:
Question, is there a way to specifically opt-out an element for transitions?
—
Reply to this email directly or view it on GitHub.

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/layoutanimation-opacity-doesnt-animate-on-update
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix.
We're a small team and rely on the community for bug fixes of issues that don't affect fb apps.


fix(button): give the button default theme,reset missing scripts

I don't know why the previously committed code was removed.

It seems that there are some build errors , it's strage too for me🤣, when I just debug, I found that the type prompt did not work

It seems that there are some build errors , it's strage too for me🤣, when I just debug, I found that the type prompt did not work

Maybe some dependencies improved caught it.

https://github.com/qmhc/vite-plugin-dts/issues/129


Adding working slate macros to ATITD9 repo

Oh, wait I need to test with interface small according to:
https://github.com/DashingStrike/Automato-ATITD/issues/89
I'll reopen later


Add help text and example for setting the timezone

Don't ask how many tries it took me to find out about the caveat regarding the quotation marks :wink:

Ah, nice, thanks!


Update "Latest Release"?

Currently v1.0.2 is set as the "Latest Release" under the Releases Tab. Maybe change the tag to point to the v1.1.0 release?

Yes that would be useful. I saw you had tags, but a release creates a zip and tar.gz people can easily download and then build.
Having the tags it shouldn't be too long. Thanks in advance!
ping @orangemug

Apologies for taking so long to get to this. v1.2.0 is now released see

https://github.com/maputnik/editor/releases
https://maputnik.github.io/blog/2018/05/08/release-v1.2.0


Enhancement: Functionality to adjust the degree (Temperature/Entropy) of the trained dataset when generating final midi files

A functionality to allow some variability in Magenta's ability to snap to a remembered song. As the loss becomes closer to zero Magenta tends to remember a trained song instead of merging the components of several songs.
See discussion on google groups tensorflow magenta discuss at
https://groups.google.com/a/tensorflow.org/forum/#!topic/magenta-discuss/SCZR9qrQUGM
I have setup a magenta fork at
https://github.com/hpssjellis/magenta
PR's are welcome.

I think the pull request in #103 will fix this for you.


fix: remove gofrs-uuid

Signed-off-by: Anthony Casagrande<EMAIL_ADDRESS>github.com/gofrs/uuid is still an indirect dependency due to onvif library.
See: https://github.com/IOTechSystems/onvif/pull/12

@cloudxxx8 no worries. Done.


Join table

Create vets, specialisations and visits tables
Insert data to these tables
Doing some queries from these tables

There are screenshots of those queries:

These are screenshots of last changes:


Android:Make MessageQueueThreadImpl startNewBackgroundThread more eff…

Notes
By adding thread synchronization,creating background threads is more efficient.
Thanks for @javache
TianXia
XiaoMi Corp.

Thanks for the PR! Can you explain why this is more efficient? I can also import this and run some internal perf tests on this.

Can  you please sign the CLA so I can import this?

Looking forward to import. :)
Thank you for your reviews. @javache

I've run some internal tests on this and there's no obvious performance win here. Do you have some numbers from benchmarks yourself on this?

I've also run some internal tests after removing the code MessageQueueThreadRegistry.register(mqtFuture.getOrThrow()),seems no obvious performance win too.
To ensure that a return with a secure Looper for MessageQueueThreadImpl,I think MessageQueueHandlerThread is more clear.