Unescaping f# method names

Fancy f# method names with `` `` are escaping according to some rules, and to make managed name full compatible we need to fully unescape.   #4969 fixes the most painful problem that prevents discovering completely. But in ideal case the CIL name should be fully unescaped so it can be found through reflection.

I have run a few manual tests and here are the characters that gets transformed (not exhaustive list):

\ escaped as \\
' escaped as \'
" escaped as \"
@ escaped as @5

I will look at more cases now.
Originally posted by @Evangelink in https://github.com/microsoft/vstest/issues/4969#issuecomment-2045021220
AB#2020980

Spec says:
3.4 Identifiers and Keywords
Any sequence of characters that is enclosed in double-backtick marks ( ), excluding newlines,
tabs, and double-backtick pairs themselves, is treated as an identifier. Note that when an identifier is
used for the name of a types, union type case, module, or namespace, the following characters are
not allowed even inside double-backtick marks:
‘.', '+', '$', '&', '[', ']', '/', '\', '*', '"', '`'
All input files are currently assumed to be encoded as UTF-8. See the C# specification for a list of the
Unicode characters that are accepted for the Unicode character classes \Lu, \Li, \Lt, \Lm, \Lo, \Nl,
\Pc, \Mn, \Mc, and \Cf.
https://fsharp.org/specs/language-spec/4.1/[FSharpSpec-4.1-latest.pdf](https://fsharp.org/specs/language-spec/4.1/FSharpSpec-4.1-latest.pdf)
member this.`` . + - = $ & [ ] \ / * @ ' ` " % ( ) ^ `` () =
Experimenting with the chars above and few more only ` ' " \ look to be escaped for methods:

@amaury how did you get @ to become @5?

This is not an issue, I misinterpreted what the parser is doing. We only need to handle ' correctly, which we do in  https://github.com/microsoft/vstest/pull/4969


Documentation should be updated about outdated options

The hdiutils internet enable option has been removed in macOS 10.15. When you don't use --no-internet-enable, this creates the warning "hdiutil does not support internet-enable. Note it was removed in macOS 10.15.". This should probably at least be mentioned in the documentation or be marked as deprecated. And on systems higher than 10.15 the option should probably not be passed to hdiutils.
Also, it probably should be mentioned in the documentation that --hide-extension isn't necessary for .app files on newer macOS systems as this is automatically enabled for all .app files.

Thanks @Korne127!
PRs are welcome 👍🏼


Error sending form with array

I have a small problem when submitting a form that has an array. First I sent the form without being filled, then I filled it out and tried to send it again. The values service_id and currency are filled in correctly, however resending is not allowed due to the array.
This is my form:
form: Form.create({
    service_id: null,
    currency: null,
    costs: [
		{
			value: null,
			starting_track: null,
			final_track: null
		},
		...
	]
})

These are the errors returned from my API:
{
   "message":"The given data was invalid.",
   "errors":{
      "service_id":[
         "The service id field is required."
      ],
      "currency":[
         "The currency field is required."
      ],
      "costs.0.value":[
         "The costs.0.value field is required."
      ],
      "costs.0.starting_track":[
         "The costs.0.starting_track field is required."
      ],
      "costs.0.final_track":[
         "The costs.0.final_track field is required."
      ]
   }
}

This is the error returned by the package:

Somehow, he doesn't recognize that the inputs costs.0.final_track, costs.0.starting_track and costs.0.value have been filled.
How can I get around this situation?

Hey, based on your form it seems like there is no validation in it.

I'm not validating in front-end just in the back-end, for some reason form-wrapper is not removing errors from array...

Sorry man there is no support for array inputs.

Any plans for it? I could try to implement, but I'm not familiar with TS.

Tried it before, and it make a mess for simple forms, sorry man.


Linux Notification Issue

Error when notification button is pressed on FreeDesktop
Unhandled exception. Tmds.DBus.DisconnectedException: Signal handler for org.freedesktop.Notifications.NotificationClosed threw an exception
 ---> System.InvalidOperationException: Signal handler for org.freedesktop.Notifications.NotificationClosed threw an exception
 ---> System.Collections.Generic.KeyNotFoundException: The given key '16' was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at DesktopNotifications.FreeDesktop.FreeDesktopNotificationManager.OnNotificationClosed(ValueTuple`2 event) in /home/ryoumiya/Documents/DesktopNotifications/DesktopNotifications.FreeDesktop/FreeDesktopNotificationManager.cs:line 138
   at Tmds.DBus.WrappedDisposable.Call[T](Action`1 action, T value, Boolean disposes)
   at Tmds.DBus.CodeGen.DBusObjectProxy.<>c__DisplayClass7_0`1.<WatchNonVoidSignalAsync>b__0(Message msg, Exception ex)
   at Tmds.DBus.DBusConnection.HandleSignal(Message msg)
   --- End of inner exception stack trace ---
   at Tmds.DBus.DBusConnection.HandleSignal(Message msg)
   at Tmds.DBus.DBusConnection.HandleMessage(Message msg, IMessageStream peer)
   at Tmds.DBus.DBusConnection.ReceiveMessages(IMessageStream peer, Action`2 disconnectAction)
   --- End of inner exception stack trace ---
   at DesktopNotifications.FreeDesktop.FreeDesktopNotificationManager.OnNotificationActionInvokedError(Exception obj) in /home/ryoumiya/Documents/DesktopNotifications/DesktopNotifications.FreeDesktop/FreeDesktopNotificationManager.cs:line 157
   at Tmds.DBus.WrappedDisposable.Call[T](Action`1 action, T value, Boolean disposes)
   at Tmds.DBus.CodeGen.DBusObjectProxy.<>c__DisplayClass7_0`1.<WatchNonVoidSignalAsync>b__0(Message msg, Exception ex)
   at Tmds.DBus.DBusConnection.Disconnect(Boolean dispose, Exception exception)
   at Tmds.DBus.Connection.Disconnect(Boolean dispose, Exception exception)
   at Tmds.DBus.Connection.OnDisconnect(Exception e)
   at Tmds.DBus.DBusConnection.EmitDisconnected(IMessageStream peer, Exception e)
   at Tmds.DBus.DBusConnection.ReceiveMessages(IMessageStream peer, Action`2 disconnectAction)
   at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__128_1(Object state)
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()

OS: OpenSuse Leap 15.5
.net: 7.0

Same. I also get a crash when I click on the notification itself (not a button) or the close button. Maybe because it tries to get the value from a key without checking if the key exists or the dict get modified by another thread?


chore: move React error parsing to a dedicated extension of FPJSError

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Check if the user has clipboard api permissions, if they don't, request it

https://web.dev/async-clipboard/#security-and-permissions
Relevant lines of code would be anywhere await navigator.clipboard is called.

I'd like to pick this up. 🙂

Go for it @sonylomo. Assigned to you. Thank you! 🎉


restoring the states when returning to earlier scene

Right now when I go from scene A to scene B and then back to scene A, scene A is completely re-initiated. Is there anyway for me to go back to the states scene A was in when I last left it?

It used to be you have to explicitly call a
reload("scene");
go("scene");

to reinitiate and switch scene, then changed go() to call reload() by default cuz it looks like that's a more often use case, we can either

go back to having to explicitly call reload("scene")
come up with a name for go() to a scene but not reinitiate

You could also have go(name, reload=True, ...args) although that introduces a breaking change.
Meanwhile, I tried commenting out the reload function and found a bug.
In the level example, if you have a level like this below, where you go to a different scene when you overlap with door "|". When you come back (without reloading), the coins would all fall down and off the screen.
 const map = addLevel(
          [
            "                                                                                ",
            "                                                                                ",
            "          ooo                  ooo                     ooo                 ooo             ooo                                                        ",
            "     ^+++====+=                ====+=                  ====+=              ====            ====                                                       ",
            "                                                                                ",
            "                                                                                ",
            "                                                                                ",
            "                   |                                                                                ",
            "               =++===                                                                                ",
            "                                                                                ",
            "                    oo                                                                                ",
            "        =====      +++ **                                                                                ",
            "==========++===+=^====+++==========++===+=^====+++==========++===+=^====+++==========++===+=^====+++==========++===+=^====+++==========++===+=^====+++",
          ],
          {
            width: 11,
            height: 11,
            pos: vec2(0, 0),
            "+": [sprite("steel"), solid()],
            "=": [sprite("grass"), solid()],
            "^": [sprite("jumpy"), solid(), "jumpy"],
            "|": [sprite("door"), "door"],
            "*": [
              sprite("spike"),
              body(),
              area(vec2(0, 6), vec2(11, 11)),
              "hurt",
            ],
            o: [sprite("coin"), body(), "coin"],
          }
        );

Before going to the door

After coming back. You can see the coins falling down (sorry for the bad cropping - had to take it very quickly since the coins would fall off the screen completely)

hmm, do you have the full code that I can try?

hmm, do you have the full code that I can try?

sorry I can't find it anymore, but you should be able to reproduce it just from what I have above. Either way, this bug doesn't affect me personally anymore for now - I suppose it's just something to keep in the back of the head as the project moves forward.
Btw, I loooove Kaboom. I really feel like I can get building within 5 min of playing with the APIs (I have no game dev experience, only web dev). Great work!

Closed.
For send data trough scenes you can use: `` and scene("game", (data) => debug.log())
kaboom()

scene("1", () => {
    let data = {
        life: 300,
    }

    go("2", data)
})

scene("2", (data) => {
    debug.log(data.life)
})

go("1")

And stay() for mantain objects in scene changes


pachctl enterprise activate --expires formatting

pachctl enterprise activate's  --expires flag claims to accept either iso-8601 or rfc-3339 formatted strings, but it actually seems to reject both.
$ pachctl enterprise activate $(cat "customerTokens/valid-activation-code.txt") --expires "$(date --rfc-3339=seconds)"
could not parse the timestamp "2017-09-11 14:51:02-07:00": parsing time "2017-09-11 14:51:02-07:00" as "2006-01-02T15:04:05Z07:00": cannot parse " 14:51:02-07:00" as "T"

seems to imply it may not like the space (although it does seem to have interpreted it properly). ISO uses the T, but that doesn't work either because of timezone format:
$ pachctl enterprise activate $(cat "customerTokens/valid-activation-code.txt") --expires "$(date --iso-8601=seconds)"
could not parse the timestamp "2017-09-11T14:51:02-0700": parsing time "2017-09-11T14:51:02-0700" as "2006-01-02T15:04:05Z07:00": cannot parse "-0700" as "Z07:00"

It does seem to take a string with no TZ set (ie UTC):
pachctl enterprise activate $(cat "customerTokens/valid-activation-code.txt") --expires "2017-09-11T12:31:15.000Z"

But using the date util's --utc flag still doesn't work:
$ pachctl enterprise activate $(cat "customerTokens/valid-activation-code.txt") --expires "$(date --iso-8601=seconds --utc)"
could not parse the timestamp "2017-09-11T21:51:02+0000": parsing time "2017-09-11T21:51:02+0000" as "2006-01-02T15:04:05Z07:00": cannot parse "+0000" as "Z07:00"
$
$ pachctl enterprise activate $(cat "customerTokens/valid-activation-code.txt") --expires "$(date --rfc-3339=seconds --utc)"
could not parse the timestamp "2017-09-11 21:51:04+00:00": parsing time "2017-09-11 21:51:04+00:00" as "2006-01-02T15:04:05Z07:00": cannot parse " 21:51:04+00:00" as "T"

Per slack, date -Iseconds works:
$ pc enterprise activate $(cat activation-code.txt) --expires $(date -Iseconds)
Activation succeeded. Your Pachyderm Enterprise token expires 2017-09-11 22:06:58 +0000 UTC

Are you using date for tests? If so, does the fact that -Iseconds seems to work fix the issue?
(For future reference: the go docs for date parsing (https://golang.org/pkg/time/) indicate that when Go tries to parse RFC 3339 timestamps, it expects dates of the form 2006-01-02T15:04:05Z07:00. I gather that in the examples above, the error was that the time zone was denoted with +/- instead of Z. AFAICT, that notation actually is RFC 3339 compliant, but not ISO 8601 compliant. Go also seems to err in that direction in requiring T as the date/time separator, when RFC 3339 explicitly allows a space while ISO 8601 doesn't. In general, strict ISO 8601 compliance seems to be necessary here, which is kind of annoying, but fortunately date supports that)

I'm closing the issue because my impression is that date -Iseconds will work, but we should re-open it if not

Re-opening because I didn't read your comment carefully. Your second command, which used --iso-8601=seconds totally should've worked

Interestingly, our date tools appear to be different. When you set --iso-8601=seconds, it emits 2017-09-11T14:51:02-0700 (which doesn't have a colon in the time zone, which breaks the parser) whereas mine emits 2017-09-11T14:51:02-07:00. Both seem to be 8601-compliant.
I'll update pachd to accept both

Weird that our date tools would be producing different formats, but it's also weird that Go clearly does recognize the format and translates it into what it seems to want: parsing time "2017-09-11T14:51:02-0700" as "2006-01-02T15:04:05Z07:00"
...but then still for some reason refuses to accept it -_-

This is actually an interesting feature of Go—either totally brilliant or totally stupid depending on who you ask. The way Go handles date formats is by using example dates, rather than %Y %M %m etc tokens (what's the code for two-digit year again?).
Basically, you format the date "January 2, at 3:04 PM and 5 seconds, 2006, in GMT +7 in the format you want, and then Go will render/parse dates in that format. So the date format string "2006-01-02T15:04:05Z07:00" corresponds to YYYY-MM-DD"T"HH:MM:SS[timezone]. Because the timezone component of the string is "Z07:00" rather than "Z0700" it expects a colon, which date doesn't always seem to print.

@msteffen Status?

stale


Fix CI

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@97eba8c). Click here to learn what that means.
Patch has no changes to coverable lines.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage        ?   31.08%
=======================================
  Files           ?        4
  Lines           ?      296
  Branches        ?        0
=======================================
  Hits            ?       92
  Misses          ?      204
  Partials        ?        0

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


Publish all metadata after artifacts

Fixes #28153

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

good job

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

Devam ediyor musunuz

   def expectedPublishedLog = ["Uploading snapshotPublish-${initialVersion}.jar", "Uploading snapshotPublish-${initialVersion}.pom", "Uploading snapshotPublish-${initialVersion}.module", 'Uploading maven-metadata.xml', 'Uploading maven-metadata.xml']

   int outputIndex = 0, matchIndex = 0;

   while (outputIndex < publishTaskOutputLines.size() && matchIndex < expectedPublishedLog.size()) {

       if (publishTaskOutputLines[outputIndex].startsWith(expectedPublishedLog.get(matchIndex))) {

           matchIndex++

       }

       outputIndex++

   }

   matchIndex == expectedPublishedLog.size();

   publishTaskOutputLines.collect { it =~ ~/Uploading (\S*).*/ }.findAll().collect { it.group(1) } == [

       "snapshotPublish-${initialVersion}.jar",

       "snapshotPublish-${initialVersion}.pom",

       "snapshotPublish-${initialVersion}.module",

       'maven-metadata.xml',

       'maven-metadata.xml'

   ]

—

@bot-gradle merge

The merge queue build has started. Click here to see all failures if any.


#112 - Removes duplicate method from SchemaUtils

Fix included to resolve #112

@mbarlowvt , Thanks for your contribution. I agree with the changes. I have just one suggestion - To comply with our branching policy, can you please apply these changes to the engine_integrator branch? Once the changes pass our integration tests, they will be merged to the master branch.
We should have done a better job documenting the branching policy and I am on it. For now, it would be great if you can create this PR on the engine_integrator branch.


Photos are not displayed

Currently there are no photos displayed, however there are photos in the DB.

There was an image stored in the database (and linked), but was not present on the filesystem (gui-screwed.jpg). I uploaded a couple of other images and everything worked fine. Maybe there was something wrong with this particular image? @eScienceCenter/spacialists

Still not working - no pics visible.
After uploading a picture from folder-path I get kicked and have to sign in again and still the pic is not there...

in some very few cases uploading works but editing of the properties is impossible - the are tagged by some random information from the very beginning stage of spacialist...

Closing this in favor of #74


Make force-public runnable

Is it an API key/secret issue?

Yep it's an API issue. Closing.

There is a known OSS API/Key you can include : https://github.com/artsy/eigen/blob/master/Makefile#L41-L42

Oh nice! Will definitely use that!


A faster and more memory-efficient implementation of zero_to_fp32

It is a faster and more memory-efficient implementation of zero_to_fp32.
The previous version double the memory usage, which cause cpu OOM for very large models (e.g. llama 405B).
https://github.com/microsoft/DeepSpeed/blob/b647fb2470f8f6fefe5cab0ea84a2d89696eb898/deepspeed/utils/zero_to_fp32.py#L438-L441
How does it work?

Lazy loading: Load checkpoint with mmap=True, thus the weights are mmaped rather than loading all the storages into memory.
Lazy merge: GatheredTensor contains the mmaped weights and tensor offset. It is a memory-efficient pseudo tensor. Only when .contiguous() is called, it starts to load related weights to memory and merge into a single tensor.
Free memory in time: Release the memory once a shard is saved.

Throughout the process, only one shard of tensors are keeped in memory.

@xylian86, FYI

@xu-song, just to clarify, we greatly appreciate this PR. The memory and speed benefits are very useful. My only concern are the HF_Hub related changes, so hopefully those can be clarified.
Can you please add the observed speed and memory benefits of this optimizations? Such details are generally useful for readers to better appreciate the value. Thanks!

@xu-song, just to clarify, we greatly appreciate this PR. The memory and speed benefits are very useful. My only concern are the HF_Hub related changes, so hopefully those can be clarified.
Can you please add the observed speed and memory benefits of this optimizations? Such details are generally useful for readers to better appreciate the value. Thanks!

Is there any alternative approach of sharding checkpoint in deepspeed?

@tjruwase Is there any alternative approach to sharding torch state_dict?
If any, the compatible feature to huggingface_hub.split_torch_state_dict_into_shards can be discarded.

Sorry, but I am a bit confused about the objective of this PR. The goal of zero_to_fp32 is to create a consolidated checkpoint state from the sharded checkpoints of ZeRO-* training, so I don't understand why state_dict sharding is a consideration here.
It seems that there are two parts of this PR.

Speed and memory optimizations
HF_hub compatibility involving state_dict sharding

Am I correct?

@tjruwase Is there any alternative approach to sharding torch state_dict?
If any, the compatible feature to huggingface_hub.split_torch_state_dict_into_shards can be discarded.

Sorry, but I am a bit confused about the objective of this PR. The goal of zero_to_fp32 is to create a consolidated checkpoint state from the sharded checkpoints of ZeRO-* training, so I don't understand why state_dict sharding is a consideration here.
It seems that there are two parts of this PR.

Speed and memory optimizations
HF_hub compatibility involving state_dict sharding

Am I correct?

https://github.com/microsoft/DeepSpeed/blob/54903e09eb131bb7b69bfc154e3970d4958131b9/deepspeed/utils/zero_to_fp32.py#L565-L567
To save memory, the tensors in state_dict is pesudo tensor instead of torch tensor.

@tjruwase Is there any alternative approach to sharding torch state_dict?
If any, the compatible feature to huggingface_hub.split_torch_state_dict_into_shards can be discarded.

Sorry, but I am a bit confused about the objective of this PR. The goal of zero_to_fp32 is to create a consolidated checkpoint state from the sharded checkpoints of ZeRO-* training, so I don't understand why state_dict sharding is a consideration here.
It seems that there are two parts of this PR.

Speed and memory optimizations
HF_hub compatibility involving state_dict sharding

Am I correct?

https://github.com/microsoft/DeepSpeed/blob/54903e09eb131bb7b69bfc154e3970d4958131b9/deepspeed/utils/zero_to_fp32.py#L565-L567
To save memory, the tensors in state_dict is pesudo tensor instead of torch tensor.

@tjruwase Is there any alternative approach to sharding torch state_dict?
If any, the compatible feature to huggingface_hub.split_torch_state_dict_into_shards can be discarded.

Sorry, but I am a bit confused about the objective of this PR. The goal of zero_to_fp32 is to create a consolidated checkpoint state from the sharded checkpoints of ZeRO-* training, so I don't understand why state_dict sharding is a consideration here.
It seems that there are two parts of this PR.

Speed and memory optimizations
HF_hub compatibility involving state_dict sharding

Am I correct?

Besides, our implementation exactly follows the the goal of zero_to_fp32. As the document says

Apologies for not being clear. The reason that I referred to that doc was to show that zero_to_fp32 designed to generate a consolidated checkpoint and not a sharded one. Does this clarify the intention of zero_to_fp32?

Besides, our implementation exactly follows the the goal of zero_to_fp32. As the document says

Apologies for not being clear. The reason that I referred to that doc was to show that zero_to_fp32 is meant to generate a consolidated checkpoint and not a sharded one. Does this clarify the intention of zero_to_fp32?

You may confused the intension of zero_to_fp32.py and get_fp32_state_dict_from_zero_checkpoint

If your point is no-sharding is allowed, then ignore and close this pr.

No, my point is not no-sharding is allowed. Like I said earlier, this PR is very useful, and we are appreciative. I notice that new PR does not contain HF_hub compatibility logic, and so my concern is addressed. Thanks for that.

a unit test has been added

formatting and unit test issue have been resolved.

formatting and unit test issue have been resolved.
@xu-song, apologies that our CI issues is delayed merge. Thanks for your patience.

I have a question that's a bit off-topic. Why is it necessary to convert zero to fp32 instead of directly converting it to fp16 or bf16? I don't understand this. Is there a zero_to_bf16.py script available?


DnD placeholder flashes when dragging table rows in Chrome

I'm trying to use the module to add drag-and-drop support to rows of an HTML table.
The problem I'm seeing is that whenever the DnD placeholder takes up vertical space, it sometimes starts flashing on and off while dragging in Chrome / Chromium.
Steps to reproduce:

Open the example JSFiddle in Chrome:  http://jsfiddle.net/0yua4f15/2/
Slowly drag e.g. "five" to a higher position, and keep the mouse button pressed
Once you hit a magic position, even though you don't move the mouse, the placeholder flashes on and off at about 0.5s interval.  (This seems to occur when the mouse is in a position where it would hover over the placeholder when it is present, though not necessarily always.)  Dropping works only if you release the mouse button while the placeholder is present.

There are two variants in the JSFiddle which can be enabled by removing the comment marks, neither of which fix the issue:

Style the generated
 element as a table row by CSS
Define a custom
 element as the placeholder in HTML

Tested to be buggy on Chrome 49 and Chromium 49 running on Linux Mint.  On Firefox 46 it works correctly as long as one of the options is uncommented.

After re-testing, it works in Chrome after all, as long as:

There is a custom
 implemented; and
The placeholder row contains the same amount of s (or equivalent using colspan) as the rest of the table.

I'm not sure how I missed this.  Hopefully this will help out other people struggling with the same issue.

Did you place the custom tr element inside the dnd-list or outside of it ?

Hi,
Is there an implementation available for dndPlaceholder for tr ?

Also curious - how did you get this to work?

What @plaa did is adding

 inside the
 tag, as following:

        {{$index}}
        {{number}}

```


Mysql Backup

We need a backup mechanism for storing a backup of the mysql database, in case due to any issue the database gets corrupted. The backup can happen weekly using a cronjob.

created a cronjob to backup db every week , backups are stored in ~/dump/dumps folder


fix session in cookie GH

fix session in cookie to not do all the time the auth clode flow and save some data in cookie that might be interesting to the backend
fix: #57
fix: #45
Signed-off-by: Sandor Szücs<EMAIL_ADDRESS>

:+1:

:+1:


Wemos D1 mini / Serial-Pins

Installation specifics

**Heating type: Vitodens 200
**Protocol: P300
**Board: ESP8266 Wemos D1 mini

Using self-made optolink with softwareserial and looks good. It doesn't work with RX/TX (1/3 ports), but with D7/D6.
VitoWifi for 8266 is not providing possibility to change RX/TX-Pin instead of ESP32 code.
Any hint to run VitoWifi with customized Pins or why it is not working with RX/TX of Wemos D1 mini?
Cheers,
Lutz

@lsrs7 Hi, maybe this helps. I tried to use VitoWifi with D1 Mini an changed the file "OptolinkP300.cpp":
Change line 52+ to the following:
void OptolinkP300::begin(HardwareSerial* serial) {
serial->begin(4800, SERIAL_8E2);
delay(1000);
serial->swap();
delay(1000);
_stream = serial;
// serial->flush();
}
The RX/TX is then swapped to Pins 13 an 15. I had no time to complete the project, but testing with some leds shows communications seems to use the Pins 13/15 now...

@lsrs7
Hi, I changed OptolinkP300.cpp and OptolinkKW.cpp and made VitoWifi SoftwareSerial compatible. Then I used SoftwareSerial with other pins instead of RX / TX.
Check my project
Best regards

@lsrs7 Hi, will this also work with the Vitocal 242s heat pump? Anyway, I flashed your code using VSC and platformia, just changed the port. In the available Wifi I found optolink_config, which I connected to both from computer and mobile, but I can't connect to ip <IP_ADDRESS>, it refuses the connection "ERR_CONNECTION_REFUSED".
Any advice? I have tried both Wemos D1 mini and NodeMCU, only the LED lights up but nothing happens.
Thank you
Translated with www.DeepL.com/Translator (free version)

@Bojkas1985
Hi,
to be honest I have no idea why you get the connection refused error. I have never had issues like this.
Maybe you can check if the serial logging output gives a hint.
Best regards

@empty88 Hi, I finally solved it by opening it in edge. The problem is that after entering the WLAN and the mqtt broker, I cannot connect to the administration. When I turn it off and on, it won't connect to the network again. the last message from the terminal is start webserver. In that administration, I can then set the codes under which I want Wemos to communicate with Viessmann, or do I have to do it in the code?

@Bojkas1985 hm, strange behavior...
maybe the WLAN connection infos are not correct, So it tries to connect about 200 times and then starts the optilink_config AP again, the complete serial log output would be interesting, e.g. which IP address it is assigned to? Did it start in configmode or not?
The codes have to be set in the code.

Is this issue still valid?


In 792 security issues

Bump version for almost all packages used
Added requests in the requirements
Bump python version used in Dockerfile to 3.12
Changed serialiser to JSON rather than Pickle

Changed date types to pass the serialisation by JSON serialiser: datetime objects are not serialisable so convert to str to pass serialisation and convert back when needed

Use datetime timezone rather than django timezone
Use allowed_methods for urllib3.Retry
Fix unittests

This change is

Hello @Yu-jinKim! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file trendyqc/trend_monitoring/tests/test_plotting.py:

Line 132:80: E501 line too long (105 > 79 characters)


Ported the "Add Custom Link" feature to Frontend using JavaScript

I wrote all of the JavaScript code in an index.js file.
First, I removed the backend dependency of the Add Custom Link button.
Then, I added a data-index attribute to get the number of link fields when the page first loads, using the variables: lastsite_index and num_clinks. I stored this value inside a global variable called index, which I assumed to be beginning from 0. It was just to make sure if any changes were made to the number of link fields in the future.
After this, I created an event listener for the Add Custom Link button with code that allows it to add an extra custom field. And, I used a little arithmetic with the index variable to calculate the Custom Link number.
Finally, at the end, I used a little math again to calculate the position of the last custom link component and place the new custom link component after it.
I tested the whole thing locally on my laptop, and the PHP backend was able to handle these extra fields created entirely in the frontend. The resulting output had all the extra links I gave it. Here's the preview output:

(I didn't provide any icons)

This looks good. I just have to made an edit on the github action to copy the js file.

Thanks! It's already up. Great work!


Make path optional in GraphQL errors

Signed-off-by: Igor Pashev<EMAIL_ADDRESS>

This change is

Why?

Why?

it's not present on errors (at least occasionally, need to investigate if the field was removed.)


Issues with Workforce Data Elements

All data elements are showing the NWDS ID and NWDS Field Name as National Codes, e.g.
https://www.datadictionary.nhs.uk/data_elements/employment_contract_nature_code.html

All extrafieldhead items will be supressed for october release.


FastNoiseLite for NoiseTexture3D always returns zero

Tested versions
v4.2.2.stable.official [15073afe3]
System information
Godot v4.2.2.stable - Windows 10.0.19045 - GLES3 (Compatibility) - ANGLE (AMD, AMD Radeon (TM) R9 M360 (0x0000682B) Direct3D11 vs_5_0 ps_5_0, D3D11-27.20.1034.6) () - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 Threads)
Issue description
I set up a mesh with a ShaderMaterial. The shader takes a sampler3D, to which I'm feeding a Simplex Smooth noise texture generated with the built-in FastNoiseLite.
For a simple test I have this
vec4 tex = texture(landmass_texture, VERTEX);
VERTEX += (NORMAL * tex.xyz);

But it's always zero. No error is ever thrown, but it's always zero. 2D textures work, but 3D doesn't.
Steps to reproduce

Start project
add CSGMesh3D root node
In the inspector, add a new ShereMesh and a new ShaderMaterial
In the Material properties, add a new Spatial Shader
Write the shader

shader_type spatial;
uniform sampler3D noise_texture;

void vertex() {
	vec4 tex = texture(noise_texture, VERTEX);
	VERTEX += (NORMAL * tex.xyz);
}

In the inspector, in Shader Parameters create a new NoiseTexture3D
In the NoiseTexture3D properties, for noise, create a new FastNoiseLite
There should be visible changes to the mesh, but NORMAL * tex.xyz is always zero.

Minimal reproduction project (MRP)
Noise3D.zip

Please explain what the issue is, what is expected and what are your results?
For me (in 4.3 [88f3b5f9d52f740b24fabfb8bc01b8b7026ba279]) it renders with a noisy lumpy shape, with a 3D noise texture

Also unable to reproduce on 4.3-rc3; it renders in a noisy 3D shape.

I see the default sphere, unchanged, with a 1 unit diameter.
This problem seems to only appear in version 4.2.2 and only when Compatibility is chosen for the renderer. Fixed in 4.3-rc3.

Would need to identify what fixed it in 4.3 to consider for cherry picking for a future 4.2.x, otherwise this can be closed as it's fixed


Property testing

Mostly found from rg expect src | rg -v 'self.expect' | rg -v expected:

expr.rval() should always be the same as expr.rval().rval()
t.is_assignment_operator() implies t.without_assignment() is an Ok variant
Expr::Member should always have Struct or Union type
Type::sizeof and Type::alignof should always return the same Result variant
Expr::Compare should only hold comparison tokens
last_saw_loop == false <==> !self.switches.is_empty()
current_function should be Some whenever parsing a statement
peek_token() == next_token()
peek_next_token() == { next_token(); next_token() }
unput(token.clone()) => token == next_token()

Various others I haven't bothered to write up.
https://github.com/AltSysrq/proptest (or maybe https://github.com/BurntSushi/quickcheck) seems like a good library to use.

Some of these can be solved completely with newtypes, like Comparison can very easily be an enum. Others sound to me like typestate (e.g. current_function) but I'd have to read up on typestate more since I haven't actually implemented it before. Others I really don't think can be part of the type system, like peek_next_token.


compatibility  with python 3

There is problem with the application. It misbehaves with python 3 on this line
prefix, label =message['path'].strip('/').split('/')

in consumer.py  throwing the following error a bytes like object is required, not str

In python 3 You should decode message before strip and split:
prefix, label =message['path'].decode().strip('/').split('/')


Add Testing

Add testing to the module

As you may or may not now, we have some modules published of our own and we almost always fully test our modules.
You can check these out: Mollie-ES6 and obj-denied.
Is that the kind of testing you'd like? Because I can make a start like that if you'd like.

@Geex-Renzo  Testing Branch . I have to wipe my computer tonight so i pushed what i had started on and so far its really bare bones . But the idea is to test our that our emails are comming out as expected and then to test that were getting back good data back when we look at the hosts domain.

Have you looked at the way I make the tests?
Because for starters, I have no idea why you have added "ical-toolkit" to the testing script.
I think the following should be done:
The main file should be refactored.
Functions declared in the main export should be placed in some sort of library folder (lib) and the individual functions should be tested as well.
This way, you're always sure it works the way you think you do, even if you add something new.

I added "icall toolkit" to test creating appointments and sending them through send mail
you make some good points. I think i will actually merge your code in and rewrite from there for testing.

Nice, thanks for the merge!
I think it's a good call to first start with writing the tests, before adding something new, to make sure the project works as is. This way, we can also make sure it works like it did, after adding "icall toolkit".
Would you like it if I made a start with writing tests, the way I'm used to doing it?

Yea i think that would be a huge help cause this holiday season has really just taken my time. Hope you had a merry christmas @Geex-Renzo  and a have a happy new year
Talk soon

No problem, I'll make a start this week ;)
And yes, thank you, I had a merry Christmas, I hope you did as well!
Happy new year @GreenPioneer!

No problem, I'll make a start this week ;)
And yes, thank you, I had a merry Christmas, I hope you did as well!
Happy new year @GreenPioneer!

@GreenPioneer I've started to work on the tests on a fork of this repo, since I don't have access to this repo.
You can see my progress here: https://github.com/Geexteam/node-sendmail/tree/tests

It looks like a good start. Keep up the good work @Geex-Renzo

@GreenPioneer @Geex-Renzo I could help with tests

@geofmureithi Sounds good, I'll add a PR for my current status of the testing branch tomorrow, maybe you can work from there.

Sure will be glad to.
On Jul 11, 2017 5:16 PM, "Renzo"<EMAIL_ADDRESS>wrote:

@geofmureithi https://github.com/geofmureithi Sounds good, I'll add a
PR for my current status of the testing branch tomorrow, maybe you can work
from there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/guileen/node-sendmail/issues/28#issuecomment-314458015,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGnizlQX4ieDUxYC1VbXpBkMzx6rcVlPks5sM4O_gaJpZM4LFDRj
.

@Geex-Renzo Not yet??

@geofmureithi  @Geex-Renzo  I'm looking at picking this back up to get this done because it's becoming apparent we need testing now more than ever

Renzo never got back.
How do you plan to do them? I can help
On Mar 14, 2018 10:49 AM, "jason humphrey"<EMAIL_ADDRESS>wrote:

@geofmureithi https://github.com/geofmureithi @Geex-Renzo
https://github.com/geex-renzo I'm looking at picking this back up to
get this done because it's becoming apparent we need testing now more than
ever
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/guileen/node-sendmail/issues/28#issuecomment-372932740,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGnizvrtFdL-yu4ASfkR1f4cvtiu26Vmks5teMuEgaJpZM4LFDRj
.

Sorry @GreenPioneer I've been busy with my internship so I don't have a lot of time atm...
I can look at them tonight, as my new project needs this package (again) as well :)
I'll get back to you within 48 hours, okay? :)

@geofmureithi  @Geex-Renzo
Sounds like testing happen
Maybe we should about 2.x features as well and bundle in testing?
do you guys have any thoughts towards 2.x ?

@GreenPioneer I will just work on unit testing using mocha. Let me see if we can do some integration tests.
On 2.x, inbuilt promises would be good for a start.
Allocate me some tasks btw :wink:

@GreenPioneer
Also is it possible we can modularize the internal functions such as getHost to allow better unit testing?


Add Pagella Font family to Blank

Description
Add Pagella face to Blank Template.

Pagella is a TeX update of the URW Palladio L face that is a good substitute for the commonly used Book Antiqua and Palatino faces.

https://en.wikipedia.org/wiki/Palatino#:~:text=The%20first%20legal%20free%20version,on%20URW%20Palladio%20L%20font.

Reviewer Checklist
*Reviewers, refer to this list when testing features, or suggest new items *

[ ] Font family works

[ ] Regular
[ ] Bold
[ ] Italic
[ ] Bold Italic

[ ] Snippet Works

Could you add a sample of the font to the PR?

Woff2 just has better compression, so we should prefer woff2 here

Also as I am looking at the theme I am working on now, I can likely swap out the base text font I was going to use ("de Aetna") for Pagella if that means fewer fonts are added to the repo.  I don't see much reason to have many different serif fonts for the standard base text, and Pagella seems like a good choice due to the variety of glyphs.
I know we have Booksanity already, but I think for original themes not based on some other source we can move towards more 'open' fonts.

Everything works, tested and reviewed, merging!


Alioguzhan/account valuation report

I merging this without waiting the review. I need this. If something is wrong or broken or missing, we can fix it later @vst


Failed screenshots not getting attached to html report

Environment
- OS: Mac
- Node: v18.16.1
- cypress-mochawesome-reporter: "^3.6.1"
- cypress: "^12.16.0"

What happened?
According to the documentation if a test fails , cypress-mochawesome-reporter it should take screenshot and attach it to html report. But actual behaviour is , its taking screenshot and saving it inside a folder.
Config file
const { defineConfig } = require("cypress");

// Create a timestamp
const currentDate = new Date().toLocaleString('en-US', {
  year: 'numeric',
  month: '2-digit',
  day: '2-digit',
  hour: '2-digit',
  minute: '2-digit',
  second: '2-digit',
  hour12: false,
  timeZoneName: 'short',
}).replace(/[,/:]/g, '-');

module.exports = defineConfig({
  pageLoadTimeout: 300000,
  modifyObstructiveCode: false,
  responseTimeout: 10000,
  requestTimeout: 10000,
  defaultCommandTimeout: 20000,
  failOnStatusCode: false,
  experimentalSourceRewriting: true,
  experimentalCspAllowList: true,
  reporter: 'cypress-mochawesome-reporter',
  e2e: {
    setupNodeEvents(on, config) {
      // implement node event listeners here
      require('cypress-mochawesome-reporter/plugin')(on);

    },
    supportFile: "cypress/support/B2B_Common_Intercepts.js",
    baseUrl: "http://<IP_ADDRESS>", //We can't use "http://tf101webappstg" failed DNS lookup
  },
  video: false,
});

Relevant log output
No error as such

Anything else?
No response

Please create a repo with the problem and steps to reproduce the issue so I can have a look.
Thanks.

I was having the same issue.
Have you added import 'cypress-mochawesome-reporter/register';  to the cypress/support/e2e.js file?

You can run with flag debug: true and then check the generated .log file.
In my case, it's not getting attached because context: null. Do I need to do something for context having a value?


Initial provision status is red instead of blue

Rancher versions: 2.0 master 1/21
Steps to Reproduce:

Create a cluster

Results:  Sometimes the provisioning status is red instead of blue making me thing it's in error.  It happens a lot with the first initial status

I no longer see this as an issue with RKE, but instead only see this issue: https://github.com/rancher/rancher/issues/11443.
@tfiduccia can you try provisioning some nodes with node pools to confirm that during provisioning, it no longer gets red? I had only done 1 test case.

Version - 2.0 master 3/19
Verified fixed


initial map extent

recenter initial extent and constrain so that its not so obvious we dont have world wrap

closed via d6aabb0


There's no step  to associate NAT gateway with subnet

I didn't find the command in this doc.

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

ID: a2bbaaa6-eae8-49b3-bb2b-4efcf2da30e4
Version Independent ID: 047b57e3-47c4-99be-abd4-c82574860604
Content: Tutorial: Create and test a NAT gateway - Azure CLI
Content Source: articles/virtual-network/tutorial-create-validate-nat-gateway-cli.md
Service: virtual-network
GitHub Login: @asudbring
Microsoft Alias: allensu

Its in this section:
https://docs.microsoft.com/en-us/azure/virtual-network/tutorial-create-validate-nat-gateway-cli#configure-nat-service-for-source-subnet
Thanks!

#please-close

@asudbring Thanks for the quick response. :+1:


bank asgi deployment

Hi @buckyroberts sorry, probably that's not the optimal way of making docs different for bank and validator, but if you'll give me an idea on how to do it, i'm ready to fix.


Tsx refactor clean

.jsx to .tsx refactor

@0xdavinchee do we close these now?

Not yet, this will be used as reference for the TSX refactor parts 🙂

Going to start new branches to continue ts conversion work (cc @wenfix)


Handle/Organize Large Archive Files

Checklist

[x] I'm reporting a feature request
[x] I've verified that I'm running youtube-dl version 2019.05.20
[x] I've searched the bugtracker for similar feature requests including closed ones

Description

I'm currently working with a large archive file (almost 2 million entries spanned across close to 300 channels). I've noticed that my update script seems to scan through a channel's videos quicker when the entries are close to each other in the archive file. I think it'd be helpful to have a way to scan through the archive file and group the entries together by channel.
Possibly this could be done by extracting the entries to a separate text file for each channel and then merging them together, or maybe even implementing the output templates to the archive parameter so that you can use multiple archive files for the same script.
I'm not a very good coder so I don't know the easiest way to do this, but I'm sure it's possible somehow. If it's already possible, feel free to close the topic. Thanks!

Putting entries close to each other (whatever this means) won't have any effect in general assuming random video.
Also managing archive files' granularity is your responsibility as user.
Output templates will not be allowed for download archive file paths due to obvious reasons.

By "close to eachother" I meant when video IDs from the same channel are near eachother in the archive file (so video 1 is on line 1000, video 2 is on line 1001, etc).
This has to be relevant to some degree, because my connection is steady because some channels run through quickly and some very slow. The only thing that's different is some of the ids are grouped together (due to downloading a whole channel at once) vs others are spread apart because they are updated over time and the IDs get spread out due to other channels also being updated

I mean you are the expert so I could be wrong, but if scanning the archive file is anything like the "find" feature on Notepad++, it's faster to find a string of text that's 10 lines down from the current one vs finding one that's 1,000,000 lines down. It might only be a half of a second, but that half second adds up if you are doing it hundreds of times.
Maybe I'm fundamentally misunderstanding how checking for video ID's works in the archive file, but it seems like it'd be obvious that ID's that are spread apart by thousands of lines would take longer to find than ones that are grouped together


codechecker store fails with ModuleNotFoundError: No module named 'store'

Describe the bug
codechecker store test_out -n test --verbose debug
[INFO][2021-04-16 16:19:29] {system} [75925] <4567567872> - store.py:840 main() - Storing analysis results for run 'test'
[DEBUG][2021-04-16 16:19:29] {system} [75925] <4567567872> - product.py:143 split_product_url() - Parsing product url 'localhost:8001/Default'
[DEBUG][2021-04-16 16:19:29] {system} [75925] <4567567872> - product.py:178 split_product_url() - Result: With 'http' on server 'localhost:8001', product 'Default'
[DEBUG][2021-04-16 16:19:29] {system} [75925] <4567567872> - credential_manager.py:61 init() - Loading clientside session config.
[INFO][2021-04-16 16:19:29] {system} [75925] <4567567872> - credential_manager.py:65 init() - Checking local passwords or tokens in /Users/vahag/.codechecker.passwords.json
[INFO][2021-04-16 16:19:29] {system} [75925] <4567567872> - credential_manager.py:90 init() - Password file not found.
[INFO][2021-04-16 16:19:29] {system} [75925] <4567567872> - credential_manager.py:99 init() - Checking for local valid sessions.
[DEBUG][2021-04-16 16:19:29] {system} [75925] <4567567872> - credential_manager.py:113 init() - Found session information for these hosts:
[DEBUG][2021-04-16 16:19:29] {system} [75925] <4567567872> - client.py:240 setup_client() - Initializing client connecting to localhost:8001/Default done.
[DEBUG][2021-04-16 16:19:29] {system} [75925] <4567567872> - store.py:850 main() - Will write mass store ZIP to '/var/folders/j_/2f9w6ybx35d2t067pl_91nn80000gn/T/tmpvfvu1bvy.zip'...
[DEBUG][2021-04-16 16:19:29] {system} [75925] <4567567872> - store.py:853 main() - Assembling zip file.
[DEBUG][2021-04-16 16:19:29] {system} [75925] <4567567872> - store.py:580 assemble_zip() - Processing report files ...
Process SpawnProcess-1:
Traceback (most recent call last):
File<EMAIL_ADDRESS>line 315, in _bootstrap
self.run()
File<EMAIL_ADDRESS>line 108, in run
self._target(*self._args, **self._kwargs)
File<EMAIL_ADDRESS>line 237, in _process_worker
call_item = call_queue.get(block=True)
File<EMAIL_ADDRESS>line 122, in get
return _ForkingPickler.loads(res)
ModuleNotFoundError: No module named 'store'
A process in the process pool was terminated abruptly while the future was running or pending.
File "/Users/vahag/codechecker/build/CodeChecker/cc_bin/CodeChecker.py", line 174, in
main(commands)
File "/Users/vahag/codechecker/build/CodeChecker/cc_bin/CodeChecker.py", line 141, in main
sys.exit(args.func(args))
File "/Users/vahag/codechecker/build/CodeChecker/cc_bin/../lib/python3/codechecker_client/cmd/store.py", line 859, in main
traceback.print_stack()
[ERROR][2021-04-16 16:19:29] {system} [75925] <4567567872> - store.py:860 main() - Failed to assemble zip file.
(CodeChecker venv)
CodeChecker version
Y6.16.0
To Reproduce
Steps to reproduce the behaviour:

run local server (localhost::8001)-> codechecker server

unzip attached archive
test_out.zip

run -> codechecker store   test_out   -n test  --verbose debug

See error

Expected behaviour
Report stored to database
Desktop (please complete the following information)

OS: [macos]
Browser: [Chrome]
Version: [latest]

Additional context
Add any other context about the problem.

@vahagnv What happens if you analyze a simple file and store the results to your server. Do you still get this error?
Example code:
// main.cpp
int main()
{
  sizeof(42);
  return 1 / 0;
}

Log your project: CodeChecker log -b "g++ main.cpp" -o ./compilation_database.json
Analyze your project: CodeChecker analyze ./compilation_database.json -o ./reports
Store the results: CodeChecker store -n myrun ./reports

Got the same error.

@vahagnv Do you get the same error with older version of CodeChecker (e.g.: 6.15.0)?

Got some error on 6.15.2

I think the problem comes from here:
https://github.com/Ericsson/codechecker/blob/472a7e8cd4f2c287acf8aeec566aa22504912983/web/client/codechecker_client/cmd/store.py#L545
Can you please try to debug it? Try to insert some print statement before and after this with statement to make sure that the problem comes from here. Also you can try to insert some try/except code blocks here and print the traceback.
Unfortunately we don't have an osx machine to reproduce this problem.

I've change with concurrent.futures.ProcessPoolExecutor() as executor part with sequential code and it worked.

I just googled on this problem and I found this: https://stackoverflow.com/questions/64501481/python-concurrent-futures-processpoolexecutor-and-global-variables-works-on-lin

Changed in version 3.8: On macOS, the spawn start method is now the default. The fork start method should be considered unsafe as it can lead to crashes of the subprocess. See bpo-33725.

What happens if you configure the context explicitly and set it to fork?
import multiprocessing as mp
...

with concurrent.futures.ProcessPoolExecutor(mp_context=mp.get_context('fork')) as executor:
    ...

Thank you. That's fixed the issue.

Hi All,
Any updates on fixing this on macOS (python > 3.8)?


x/pkgsite: package removal request for [https://github.com/yunacatw/bitgin]

What is the path of the package that you would like to have removed?
github.com/yunacatw/bitgin
Are you the owner of this package?
YES
What is the reason that you could not retract this package instead?
Already set module retraction, but it still exists in https://pkg.go.dev/github.com/yunacatw/bitgin
Please help me to remove this package, thanks.

retraction requires tagging a new higher version


Thaumcraft Inventory Scanning Causing Odd Crash with Draconic Evolution

crash-2018-04-07_22.23.00-client.txt
I was told by people over on the DE project page that something within Thaumcraft Inventory Scanning was causing a crash (despite the crash only happening after I installed Draconic Evolution). Above is the crash report.
If someone could tell me how to fix this (assuming it actually is Thaumcraft causing the problem) that would be helpful, as I really would like to have DE installed in my custom pack.

If Thaumcraft is not the culprit, please let me know what is I and shall head that direction.

nvmd wrong spot to report this


Does not work with eslint-import-resolver-webpack

// webpack.config.js
module.exports = {
  ...
  resolve: {
    root: [
      path.resolve(__dirname, './src')
    ],
    modulesDirectories: ['node_modules']
  }
  ...
}

// .eslintrc.js
module.exports = {
  ...
  'plugins': [ 'import' ],
  'settings': {
    'import/resolver': 'webpack'
  }
}

It seems that the config settings that is used by eslint-import-resolver-webpack is not a config in the eslint CLIEngine.
If i ran eslint from the terminal it works, but doesn't work if it's going through eslint-loader

It seems that the config settings that is used by eslint-import-resolver-webpack is not a config in the eslint CLIEngine.

Any other idea on what to use then?

It seems that the config settings that is used by eslint-import-resolver-webpack is not a config in the eslint CLIEngine.

This is true, but the keys of the config file are not being passed directly as keys to CLIEngine.  I think you're having a different problem.  I found that I needed to turn off the cache option when setting things up, or else it seemed that changes to the .eslintrc had no effect, which might have been what you were seeing.

I have the same problem, and the cache is off. Any ideas?

Seems to work then.


CLI: allow hooking into SST deployment cycle

Use cases

Run scripts after sst start is started up

Requests

rubythulhu https://discordapp.com/channels/983865673656705025/1024842578778132520
@cmaycumber https://github.com/serverless-stack/sst/issues/527

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


Restore url attribute for organizations api serializer

Codecov Report

Merging #1039 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1039      +/-   ##
==========================================
+ Coverage   90.54%   90.55%   +0.01%
==========================================
  Files         114      114
  Lines        2677     2680       +3
  Branches       31       31
==========================================
+ Hits         2424     2427       +3
  Misses        249      249
  Partials        4        4

Impacted Files
Coverage Δ

backend/apps/volontulo/views/api.py
79% <ø> (ø)
:arrow_up:

.../apps/volontulo/tests/views/api/test_login_view.py
100% <100%> (ø)
:arrow_up:

backend/apps/volontulo/serializers.py
92.51% <100%> (ø)
:arrow_up:

...pps/volontulo/tests/views/api/test_current_user.py
100% <100%> (ø)
:arrow_up:

...lontulo/tests/views/api/organizations/test_list.py
100% <100%> (ø)
:arrow_up:

backend/apps/volontulo/tests/common.py
100% <100%> (ø)
:arrow_up:

...lontulo/tests/views/api/organizations/test_read.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


TRY not used?

Why ist HDK_ROOT_DIRECTORY defined, but mostly not use inside the cmake modules?
bash-5.2$ grep -rw '\.hadouken' *.cmake cmake/
hadouken.cmake:set(HDK_ROOT_DIRECTORY     ${HDK_ROOT_PROJECT_SOURCE_DIR}/.hadouken)
hadouken.cmake:set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} ${PROJECT_SOURCE_DIR}/.hadouken/cmake/modules/)
hadouken.cmake:set(CMAKE_MODULE_PATH ${CMAKE_MODULE_PATH} ${PROJECT_SOURCE_DIR}/.hadouken/cmake/modules/find)
hadouken.cmake:file(GLOB CORE_MODULES "${PROJECT_SOURCE_DIR}/.hadouken/cmake/modules/core/*.cmake")
hadouken.cmake:file(GLOB TOOLCONF_MODULES "${PROJECT_SOURCE_DIR}/.hadouken/cmake/modules/toolconf/*.cmake")
hadouken.cmake:file(GLOB WRAPPER_MODULES "${PROJECT_SOURCE_DIR}/.hadouken/cmake/modules/wrappers/*.cmake")
cmake//modules/core/MakeComponent.cmake:include(.hadouken/cmake/modules/core/MakeTarget.cmake)
cmake//modules/core/MakeTarget.cmake:include(.hadouken/cmake/modules/core/detail/helper_functions.cmake)
cmake//modules/toolconf/CCache.cmake:include(.hadouken/cmake/modules/toolconf/detail/helper_functions.cmake)
cmake//modules/toolconf/GCov.cmake:include(.hadouken/cmake/modules/toolconf/detail/helper_functions.cmake)
cmake//modules/toolconf/LCov.cmake:include(.hadouken/cmake/modules/toolconf/detail/helper_functions.cmake)
cmake//modules/toolconf/IncludeWhatYouUse.cmake:include(.hadouken/cmake/modules/toolconf/detail/helper_functions.cmake)
cmake//modules/toolconf/ClangFormat.cmake:include(.hadouken/cmake/modules/toolconf/detail/helper_functions.cmake)
cmake//modules/toolconf/GCovR.cmake:include(.hadouken/cmake/modules/toolconf/detail/helper_functions.cmake)
cmake//modules/toolconf/GoogleTest.cmake:        TYPE STATIC SOURCES ${HDK_ROOT_PROJECT_SOURCE_DIR}/.hadouken/cmake/modules/toolconf/GoogleTest.cpp
cmake//modules/toolconf/CppCheck.cmake:include(.hadouken/cmake/modules/toolconf/detail/helper_functions.cmake)
cmake//modules/toolconf/GoogleBenchmark.cmake:        TYPE STATIC SOURCES ${HDK_ROOT_PROJECT_SOURCE_DIR}/.hadouken/cmake/modules/toolconf/GoogleBenchmark.cpp
cmake//modules/toolconf/ClangTidy.cmake:include(.hadouken/cmake/modules/toolconf/detail/helper_functions.cmake)
cmake//modules/toolconf/LLVMCov.cmake:include(.hadouken/cmake/modules/toolconf/detail/helper_functions.cmake)
cmake//modules/FeatureCheck.cmake:        if(NOT EXISTS "${HDK_ROOT_PROJECT_SOURCE_DIR}/.hadouken/cmake/modules/check/Check${arg}.cmake")
bash-5.2$

CMake Warning (dev) at chapter13/ex02_envfile_utility/CMakeLists.txt:17 (set):
  uninitialized variable 'CMAKE_MODULE_PATH'
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at chapter13/ex03_external_cmake_module/.hadouken/cmake/modules/core/MakeTarget.cmake:73 (if):
  uninitialized variable 'HDK_ROOT_PROJECT_NAME_UPPER'
Call Stack (most recent call first):
  chapter13/ex03_external_cmake_module/CMakeLists.txt:39 (make_target)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at chapter13/ex03_external_cmake_module/.hadouken/cmake/modules/core/MakeTarget.cmake:78 (if):
  uninitialized variable 'HDK_ROOT_PROJECT_NAME_UPPER'
Call Stack (most recent call first):
  chapter13/ex03_external_cmake_module/CMakeLists.txt:39 (make_target)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at chapter13/ex03_external_cmake_module/.hadouken/cmake/modules/core/MakeTarget.cmake:83 (if):
  uninitialized variable 'HDK_ROOT_PROJECT_NAME_UPPER'
Call Stack (most recent call first):
  chapter13/ex03_external_cmake_module/CMakeLists.txt:39 (make_target)
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at chapter13/ex03_external_cmake_module/.hadouken/cmake/modules/core/MakeTarget.cmake:270 (if):
  uninitialized variable 'HDK_ROOT_PROJECT_NAME_UPPER'
Call Stack (most recent call first):
  chapter13/ex03_external_cmake_module/CMakeLists.txt:39 (make_target)
This warning is for project developers.  Use -Wno-dev to suppress it.


node-sass package is missing

Hello,
The build crashes in local dev without the node-sass npm package.
I added "node-sass": "^4.14.1" to the list of dependencies in the package.json and it works.
Did it worked without this package before ?
Thanks

Can confirm this. Also deps need updating.
found 1753 vulnerabilities (1181 low, 78 moderate, 492 high, 2 critical)

Can confirm this. Also deps need updating.
found 1753 vulnerabilities (1181 low, 78 moderate, 492 high, 2 critical)


[FLINK-24017] Setup Kryo to be usable without flink-scala

With this PR Kryo works in a backwards-compatible fashion even if flink-scala is not on the classpath.
To that end the java-related serializers were moved to flink-java to remain accessible in that scenario, and the registration IDs of the java serializers and custom user-defined serializers were pinned such that they remain identical.

Also it would be great if we could have a test case, that this is fully compatible with the 1.14 KryoSerializer, but this would be quite tricky to do. Only simple approach I can think of would be writing some binary file with 1.14 version that we'd distribute with 1.15+ test suite, which is quite ugly :/

We already have plenty of such test-cases.

We already have plenty of such test-cases. Like the KryoSerializerCompatibilityTest or KryoSerializerRegistrationsTest.

Great, the KryoSerializerRegistrationsTest seems to be covering this well. 👍 Maybe we could extend it a bit by registering a custom type and checking it starts at index 85, but no hard feelings if we don't.


ng-e2e add force Flag to continue protractor test even if spec fails

🚀 Feature request
Command (mark with an x)
ng e2e --force
Description
ng e2e --force should continue protractor tests even if a spec fails.
Describe the solution you'd like
Add --force flag to ng e2e, the same way it was done or ng update:  #10149
Describe alternatives you've considered
 Have you considered any alternative solutions or workarounds?

Hi, I have looked into this and this is seems that specs continue to run after a failure.

  workspace-project App
    × should display message
      - Expected 'Welcome to app-layout-new-next!' to equal 'Welcome to app-layout2-new-next!'.
          at UserContext.<anonymous> (C:\git\cli-repos\app-layout-new-next\e2e\src\app.e2e-spec.ts:13:33)
          at new ManagedPromise (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:1077:7)
          at ControlFlow.promise (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:2505:12)
          at TaskQueue.execute_ (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:3084:14)
          at TaskQueue.executeNext_ (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:3067:27)
          at asyncRun (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:2974:25)
          at C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:668:7
    × should display any message
      - Expected 'Welcome to app-layout-new-next!' to equal 'Welcome to app-layout2-new-next!'.
          at UserContext.<anonymous> (C:\git\cli-repos\app-layout-new-next\e2e\src\app.e2e-spec.ts:18:33)
          at new ManagedPromise (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:1077:7)
          at ControlFlow.promise (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:2505:12)
          at TaskQueue.execute_ (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:3084:14)
          at TaskQueue.executeNext_ (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:3067:27)
          at asyncRun (C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:2974:25)
          at C:\git\cli-repos\app-layout-new-next\node_modules\selenium-webdriver\lib\promise.js:668:7
    √ should display welcome message

We have multiple protractor configs that we run. Let's say: 'web', 'ios', 'android'
If any test fails in 'web' config the other configs are not run anymore.
protractor run --force would solve this issue, but this does not work with 'angular e2e'.
The following ipmlementation would solve our problem: #13648

Hi, I think this is quite a specific use case were you want to treat specs failure as non fatal error and for this case I think you can use an npm script you can achieve this,
Example:
ng e2e --configuration web & ng e2e --configuration ios

If the first one exits with a non zero error code, it should still continue to execute the other part of the script.
I suggest that for the moment, we leave this outside of the scope of the CLI as adding more code require more maintenance and only implement this if we see that more CLI consumers need this behaviour.
Thank you for your understanding.


Can not stream the thermal video to v4l2 device ?

I executed this command:
./seek_viewer --camtype=seekpro --colormap=11 --mode=v4l2 --output=/dev/video0
And I got this error:
Error: control transfer failed: LIBUSB_ERROR_PIPE
Error: LIBUSB_ERROR_TIMEOUT
VIDIOC_G_FMT error: Invalid argument

How can I fix this ?
/dev/video0 is my webcam.
/dev/video2 is not listed on /dev/
I also tried with them but it's not working. I understand that after execute this command, and assume that it's working good. So I can use opencv with python to view the stream video from thermal camera. Did I understand right ?

First you need to have the v4l2 loopback module installed. This should generate a virtual device which what you should specify in the seek_viewer arguments. It sounds like you are trying to stream to an existing physical webcam which isn't the way v4l2 works. When you have v4l2loopback working you will be able to receive that stream in opencv yes.

Thank you so much for your support. It's working like a charm now. Have a nice weekend.


Support for ESLint v8+ ?

I just did a weekend hack and published fast-eslint-8
It works for me and hopefully does the same for you.
Please note, that I'm no experienced atom plugin provider, so there might be a few issues and atom might need to be restarted after installation.
I did not intend to create a competing project ... so I hope Arnaud will incorporate the code changes into the original fast-eslint.


Update README.md file with info about CSG

McThings is a procedural constructive solid geometry (CSG) framework. For the people in the indsutry this will help to understand it.

Done!


[Metal] Hoist vertex attributes.

Given
struct AssembledVertex
{
	float3	position;
	float3	color;
        float2  uv;
};

struct CoarseVertex
{
	float3	color;
        float2  uv;
};

struct VertexStageInput
{
	AssembledVertex assembledVertex	: A;
};

float4 vertexMain(VertexStageInput input) : SV_Position
{
	VertexStageOutput output;
	return output;
}

We generate this:
struct AssembledVertex_0
{
    float3 position_0;
    float3 color_1;
    float2 uv_1;
};

struct vertexInput_0
{
    AssembledVertex_0 assembledVertex_0 [[attribute(0)]]; // metal does not allow [[attribute]] here
};

#line 49
[[vertex]] VertexStageOutput_0 vertexMain(vertexInput_0 _S1 [[stage_in]], SLANG_ParameterGroup_Uniforms_0 constant* Uniforms_0 [[buffer(1)]])
{
}

Metal does not allow defining [[attribute]] on composite types. We need to hoist all vertex attributes out to the top level of the vertex input struct.

We should be able to reuse the EntryPointVaryingParamLegalizeContext pass to first hoist, flatten and SOA-ize all the nested attributes and fragment stage_in inputs into individual top level parameters, and then pack these parameters into a struct decorated with `[[stage_in``.
We can first translate vertexMain into something like
[attribute(0)] in float3 position;
[attribute(1)] in float3 color;
[attribute(2)] in float2 uv;
float4 vertexMain() : SV_Position
{
}

The EntryPointVaryingParamLegalizeContext should have everything we need to do this transform.
Then we pack them all into a struct, and pass that struct as [stage_in] parameter:
struct StageIn_vertexMain
{
[attribute(0)] float3 position;
[attribute(1)] float3 color;
[attribute(2)] float2 uv;
};
float4 vertexMain(StageIn_vertexMain stageIn [[stage_in]]) : SV_Position
{
...
}

I see. That make sense.

Note for implementing:
from legalizeEntryPointForMetal:
        hoistEntryPointParameterFromStruct(entryPoint);
        packStageInParameters(entryPoint);
        legalizeSystemValueParameters(entryPoint, sink);
        wrapReturnValueInStruct(sink, entryPoint);

require to be integrated (and reimplemented in some cases) into EntryPointVaryingParamLegalizeContext of slang-ir-legalize-varying-params.cpp

Update:
Reuse of EntryPointVaryingParamLegalizeContext likely needs to be a separate "clean up" PR since the current state of EntryPointVaryingParamLegalizeContext is quite underdeveloped and will require reworks to work with the Metal backend.
Limitations of EntryPointVaryingParamLegalizeContext:

Output legalization needs to be adapted to use the Metal legalization to legalize types.
Output legalization currently does not modify variable semantic layouts.
Output legalization of a returned variable is currently very basic and won't work with Metal.
Function params are fundamentally handled differently (much simpler than Metal legalization).

Fixing the Metal code-gen issues first and then cleanup is likely the easiest course of action.

We should be able to reuse the EntryPointVaryingParamLegalizeContext pass to first hoist, flatten and SOA-ize all the nested attributes and fragment stage_in inputs into individual top level parameters, and then pack these parameters into a struct decorated with `[[stage_in``.
We can first translate vertexMain into something like
[attribute(0)] in float3 position;
[attribute(1)] in float3 color;
[attribute(2)] in float2 uv;
float4 vertexMain() : SV_Position
{
}

The EntryPointVaryingParamLegalizeContext should have everything we need to do this transform.
Then we pack them all into a struct, and pass that struct as [stage_in] parameter:
struct StageIn_vertexMain
{
[attribute(0)] float3 position;
[attribute(1)] float3 color;
[attribute(2)] float2 uv;
};
float4 vertexMain(StageIn_vertexMain stageIn [[stage_in]]) : SV_Position
{
...
}

There are 3 suggested steps:

hoist
flatten
SOA-ize

Since legalization of varying outputs currently requires flattening a struct [1], step 1 can be skipped for now (start at step 2).

Closing issue, #4657 resolves the remaining desired changes


Version listed on IntelliJ repository prevents downloading in EAP

currently only 0.4 is installable.

Interesting, I'll see about fixing that.


Add section linking for the search result

This is a WIP.

Yea, I think we likely need to have an approach where sections take the place of the existing content -- we don't want to index the same data twice. I believe ES has the ability to do this reasonably well.

Yea, I think we likely need to have an approach where sections take the place of the existing content -- we don't want to index the same data twice

That means we will be modifying/upgrading to removing the headers field completely and indexing each section as a separate document... right?

I believe ES has the ability to do this reasonably well.

Which feature of ES are you talking about?

I would like to continue work on this PR only.. if that's okay?

That means we will be modifying/upgrading to removing the headers field completely and indexing each section as a separate document... right?

Perhaps. We still need to know what the headers are, but could group them with the section. I have reached out to my friend at Elastic to ask his opinion on this. I will update here with the approach he suggests.

@ericholscher

We still need to know what the headers are

I went ahead and try to index each section as a separate document in the ES. I think headers are mostly titles of the page ... right?
So I was having documents with -- project, version, title, section_title, section_id, section_content and other required fields. And it works well with the full page search UI. I haven't tested that with the search results page but I think it will work.

@dojutsu-user Great. That is how we used to do it, and it worked ok. So that might be a path forward :+1:

@dojutsu-user if you could push up the code here or somewhere else, I can try and take a look.

@ericholscher
Pushing the code... just 1 min.

@ericholscher
Pushed the code.
Many tests are going to fail for this.

Makes sense. I think this is a good way to test at least. If we can provide good results with this, we can definitely move to this approach in the short term. I want to think a bit more about how to combine this, along with the SphinxDomain objects that I want to return in search as well.

@ericholscher
I think results from sphinx domain are not shown to the user right now...??

SphinxDomain objects that I want to return in search as well.

Where do we want to show these results?

Full page search ui
In the search results page
Both
Assuming that we want to show sphinx domain results at both of these places -- we need to make an api endpoint which return results from both indexes -- something like AllSearch but with only two indexes.

One other thing that we need to discuss is how we will be showing this to the users..?

Either we give choice to the user to select one of the search results (facets)

In this case, for the full page search UI, we can have a dropdown or something like this with the input field and it will look good. But I can't think of how we will be giving choice to the user in the search result page.

Or we show results from both indexes.

We don't have to think much about the ui/ux in this case -- as we will be showing results from both indexes, everything will remain same with the inclusion of extra results.

In both cases -- I haven't given the thought that we will be showing results from Sphinx Domain in the full page search UI... so the extension is not prepared for that now. But it will.

Yea, I'd love to return SphinxDomain results to users in the same API results. I believe the approach we've discussed with Nested queries can work for both sections and sphinx_domains on the Page document. We should test this and see how it works.

Did this work in testing?

@ericholscher
No, we need to discuss it a little more.

Turns out that I was wrong earlier and it is working nicely.
Here is the sample result for query sponsors (ignore the value of link)
{
    "count": 31,
    "next": null,
    "previous": null,
    "results": [
        {
            "project": "rtd-test",
            "version": "latest",
            "title": "Sponsors of Read the Docs",
            "path": "sponsors",
            "link": "http://localhost:8000/docs/template/projects/rtd-test/en/latest/sponsors",
            "highlight": {
                "title": [
                    "Sponsors of Read the Docs"
                ]
            },
            "inner_hits": [
                {
                    "_source": {
                        "id": "current-sponsors",
                        "title": "Current sponsors",
                        "content": "Microsoft Azure - They cover all of our hosting expenses every month. This is a pretty large sum of money, averaging around $3,000/mo, and we are really grateful to have them as a sponsor.\nCloudflare - Cloudflare is providing us with an enterprise plan of their SSL for SaaS Providers product that enables us to provide SSL certificates for custom domains.\nYou? (Email us at<EMAIL_ADDRESS>for more info)"
                    },
                    "highlight": {
                        "sections.title": [
                            "Current sponsors"
                        ]
                    }
                },
                {
                    "_source": {
                        "id": "past-sponsors",
                        "title": "Past sponsors",
                        "content": "Python Software Foundation\nRevsys\nMozilla Web Dev\nDjango Software Foundation\nLab305\nTwilio\nRackspace\nMozilla"
                    },
                    "highlight": {
                        "sections.title": [
                            "Past sponsors"
                        ]
                    }
                },
                {
                    "_source": {
                        "id": "sponsors-of-read-the-docs",
                        "title": "Sponsors of Read the Docs",
                        "content": "Running Read the Docs isn’t free, and the site wouldn’t be where it is today without generous support of our sponsors. Below is a list of all the folks who have helped the site financially, in order of the date they first started supporting us.\n"
                    },
                    "highlight": {
                        "sections.content": [
                            "Read the Docs isn’t free, and the site wouldn’t be where it is today without generous support of our sponsors"
                        ],
                        "sections.title": [
                            "Sponsors of Read the Docs"
                        ]
                    }
                }
            ]
        },
        {
            "project": "rtd-test",
            "version": "latest",
            "title": "Changelog",
            "path": "changelog",
            "link": "http://localhost:8000/docs/template/projects/rtd-test/en/latest/changelog",
            "highlight": null,
            "inner_hits": [
                {
                    "_source": {
                        "id": "version-2-6-3",
                        "title": "Version 2.6.3",
                        "content": "Date:\nAugust 18, 2018\nRelease to Azure!\n@davidfischer: Add Sponsors list to footer (#4424)\n@stsewd: Cache node_modules to speed up CI (#4484)\n@xrmx: templates: mark missing string for translation on project edit (#4518)\n@ericholscher: Performance improvement: cache version listing on the homepage (#4526)\n@agjohnson: Remove mailgun from our dependencies (#4531)\n@davidfischer: Improved ad block detection (#4532)\n@agjohnson: Revert “Remove SelectiveFileSystemFolder finder workaround” (#4533)\n@davidfischer: Slight clarification on turning off ads for a project (#4534)\n@davidfischer: Fix the sponsor image paths (#4535)\n@agjohnson: Update build assets (#4537)"
                    },
                    "highlight": {
                        "sections.content": [
                            "@davidfischer: Add Sponsors list to footer (#4424)\n@stsewd: Cache node_modules to speed up CI (#4484)"
                        ]
                    }
                },
                {
                    "_source": {
                        "id": "version-2-6-6",
                        "title": "Version 2.6.6",
                        "content": "Date:\nSeptember 25, 2018\n@davidfischer: Fix a markdown test error (#4663)\n@davidfischer: Ad customization docs (#4659)\n@davidfischer: Fix a typo in the privacy policy (#4658)\n@agjohnson: Put search step back into project build task (#4655)\n@davidfischer: Create an explicit ad placement (#4647)\n@stsewd: Fix some typos in docs and code (#4646)\n@stsewd: Downgrade celery (#4644)\n@stsewd: Downgrade django-taggit (#4639)\n@safwanrahman: [Fix #4247] deleting old search code (#4635)\n@stsewd: Add change versions slug to faq (#4633)\n@stsewd: Pin sphinx to a compatible version (#4631)\n@davidfischer: Make ads more obvious that they are ads (#4628)\n@agjohnson: Change mentions of “CNAME” -> custom domain (#4627)\n@invinciblycool: Use validate_dict for more accurate error messages (#4617)\n@safwanrahman: fixing the indexing (#4615)\n@humitos: Update our sponsors to mention Azure (#4614)\n@agjohnson: Add cwd to subprocess calls (#4611)\n@agjohnson: Make restapi URL additions conditional (#4609)\n@agjohnson: Ability to use supervisor from python 2.7 and still run Python 3 (#4606)\n@humitos: Return 404 for inactive versions and allow redirects on them (#4599)\n@davidfischer: Fixes an issue with duplicate gold subscriptions (#4597)\n@davidfischer: Fix ad block nag project issue (#4596)\n@humitos: Run all our tests with Python 3.6 on Travis (#4592)\n@humitos: Sanitize command output when running under DockerBuildEnvironment (#4591)\n@humitos: Force resolver to use PUBLIC_DOMAIN over HTTPS if not Domain.https (#4579)\n@davidfischer: Updates and simplification for mkdocs (#4556)\n@humitos: Docs for hidding “On …” section from versions menu (#4547)\n@stsewd: Implement sphinx key from v2 config (#4482)\n@safwanrahman: [Fix #4268] Adding Documentation for upgraded Search (#4467)\n@humitos: Upgrade all packages using pur (#4318)\n@humitos: Clean CC sensible data on Gold subscriptions (#4291)\n@stsewd: Update docs to match the new triague guidelines (#4260)\n@xrmx: Make the STABLE and LATEST constants overridable (#4099)\n@stsewd: Use str to get the exception message (#3912)"
                    },
                    "highlight": {
                        "sections.content": [
                            "more accurate error messages (#4617)\n@safwanrahman: fixing the indexing (#4615)\n@humitos: Update our sponsors"
                        ]
                    }
                }
            ]
        },
        {
            "project": "rtd-test",
            "version": "latest",
            "title": "Read the Docs: Documentation Simplified",
            "path": "index",
            "link": "http://localhost:8000/docs/template/projects/rtd-test/en/latest/index",
            "highlight": null,
            "inner_hits": [
                {
                    "_source": {
                        "id": "first-steps",
                        "title": "First steps",
                        "content": "Are you new to software documentation or are you looking to use your existing docs with Read the Docs? Learn about documentation authoring tools such as Sphinx and MkDocs to help you create fantastic documentation for your project.\nGetting started: With Sphinx | With MkDocs\nImporting your existing documentation: Import guide\nUser Documentation\nVersions\nHow we envision versions working\nTags and branches\nRedirects on root URLs\nVersion warning\nBuild Process\nHow we build documentation\nUnderstanding what’s going on\nBuilder responsibility\nThe build environment\nWriting your own builder\nDeleting a stale or broken build environment\nBuild environment\nRead the Docs features\nGitHub, Bitbucket and GitLab Integration\nAuto-updating\nInternationalization\nCanonical URLs\nVersions\nVersion Control Support Matrix\nPDF Generation\nSearch\nAlternate Domains\nConnecting Your Account\nSupport\nUsage Questions\nCommunity Support\nCommercial Support\nFrequently Asked Questions\nMy project isn’t building with autodoc\nHow do I change my project slug (the URL your docs are served at)?\nHow do I change the version slug of my project?\nHelp, my build passed but my documentation page is 404 Not Found!\nHow do I change behavior for Read the Docs?\nMy project requires different settings than those available under Admin\nI get import errors on libraries that depend on C modules\nClient Error 401 when building documentation\nDeleting a stale or broken build environment\nHow do I host multiple projects on one custom domain?\nWhere do I need to put my docs for RTD to find it?\nI want to use the Blue/Default Sphinx theme\nI want to use the Read the Docs theme locally\nImage scaling doesn’t work in my documentation\nI want comments in my docs\nHow do I support multiple languages of documentation?\nDoes Read The Docs work well with “legible” docstrings?\nCan I document a python package that is not at the root of my repository?\nWhat commit of Read the Docs is in production?\nHow can I avoid search results having a deprecated version of my docs?\nConfiguration File\nVersion 2\nVersion 1\nGuides\nAdding Custom CSS or JavaScript to a Sphinx Project\nEnabling Build Notifications\nMy Build is Using Too Many Resources\nI Need Secrets (or Environment Variables) in my Build\nFeature Flags\nEnabling Google Analytics on your Project\nManage Translations\nKeep Building Docs With Old Version Of MkDocs\nBuild PDF format for non-ASCII languages\nRemoving “Edit on …” Buttons from Documentation\nSpecifying Dependencies\nWiping a Build Environment\nPublic API\nAPI v2\nEmbed API\nWorkflow\nHow to use it\nExample API Response\nFeature Documentation\nWebhooks\nWebhook Integrations\nWebhook Creation\nUsing the generic API integration\nDebugging webhooks\nResyncing webhooks\nPayload validation\nTroubleshooting\nBadges\nStatus Badges\nStyle\nProject Pages\nCustom Domains\nSubdomain Support\nCustom Domain Support\nCustom Domain SSL\nProxy SSL\nrtfd.org\nLocalization of Documentation\nSingle project in another language\nProject with multiple translations\nVersion Control System Integration\nGitHub\nBitbucket\nGitlab\nAdditional variables\nSubprojects\nAdding a Subproject\nSharing a Custom Domain\nSearch\nConda Support\nActivating Conda\nCustom Installs\nCanonical URLs\nExample\nEnabling\nImplementation\nLinks\nSingle Version Documentation\nEnabling\nEffects\nPrivacy Levels\nUnderstanding the Privacy Levels\nUser-defined Redirects\nQuick Summary\nRedirect Types\nImplementation\nAutomatic Redirects\nRoot URL\nSupported Top-Level Redirects\nRedirecting to a Page\nContent Embedding\nSitemaps\nAbout Read the Docs\nContributing to Read the Docs\nRoadmap\nRead the Docs Team\nGoogle Summer of Code\nCode of Conduct\nPrivacy Policy\nAdvertising\nSponsors of Read the Docs\nRead the Docs Open Source Philosophy\nThe Story of Read the Docs\nPolicy for Abandoned Projects\nDMCA Takedown Policy\nDeveloper Documentation\nChangelog\nInstallation\nSearch\nArchitecture\nTesting\nBuilding and Contributing to Documentation\nDesign Documents\nFront End Development\nBuild Environments\nHow we use symlinks\nInteresting Settings\nInternationalization\nOverview of issue labels\nSecurity\nDesigning Read the Docs\nRTD Theme\nCommercial Documentation\nRead the Docs Commercial Features\nCustom Domains\nOrganizations\nSharing\nAnalytics\nCustom Install Documentation\nInfo about custom installs\nCustomizing your install\nLocal VM Install"
                    },
                    "highlight": {
                        "sections.content": [
                            "the Docs\nRoadmap\nRead the Docs Team\nGoogle Summer of Code\nCode of Conduct\nPrivacy Policy\nAdvertising\nSponsors"
                        ]
                    }
                }
            ]
        }
    ]
}

What are your thoughts on this approach?
@ericholscher @davidfischer

This looks great. I think we'll need to index some more data in order to generate the links. We need to know the id attribute of the H2 section so we can properly generate a link to it.

I didn't follow.
I mentioned to ignore the value of link because I have rtd-test as a subproject of template and so the link is not simple.
For generating links -- we can have the full_path (#5821) and then we have to add #section-id to it and we have the link.

Ah, I missed the section_id in the results 👍

I think we should change the document and index every sections like sphinx_domains and then run a aggregation query to show the results. It maybe a complex work in the backend, but I think that would be the optimal solution and good user experience for the users.

@safwanrahman Not sure I follow, can you explain a bit more?

@ericholscher If we index each page section as a seperate entity, as we are doing with domains, While the user search, we can show them all the sections as well as domains by each page category.
Like Something like If someone search "foo", we can show the users something like this

Page 1 Name

The title of the section

The content of the section

The title of the section

The content of the section

Domain Object

Domain object description

Page 2 Name

The title of the section

The content of the section

Domain Object

Domain object description

I believe that's what we're doing now with nesting. The goal would then be to also add the Sphinx Domains to a nested Page object, so each Page would return both domains and sections.

I believe that's what we're doing now with nesting. The goal would then be to also add the Sphinx Domains to a nested Page object, so each Page would return both domains and sections.

Yeah. But in that case, it would be better to have them in separate entity rathar than using nested. Its quite hard to manage the nested mapping as well as it increases the query time and CPU usages of Elasticsearch. I can help with the mapping and query if needed.

I was recommended the Nested approach by an engineer at Elastic, so I'm tempted to trust their judgement. I don't think we need to worry about performance here until we hit issues.

I understand. I think in that case we can go with the nested approach and you may also ask him if its better to index each sections separately rathar than using nested.

I've merged the html_file PR, so if you merge from master, it should make this PR a bit cleaner 👍

@ericholscher
Merged. :+1:

Main site search --

Looking at the screenshot, we need to mark the results as safe so that the 's get rendered.

@ericholscher
Ohh... I didn't noticed that.
I have marked the string as safe and pushed the code.

👍 Merged into the feature branch as a base


Certificate -> CertificateRequest on rpc.proto

Motivation
The current proto struct is called Certificate, but it isn't really representing that
Proposal
Rename it to what it actually represents
Test Plan
CI

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2084  👈
#2081
#2079
#2074
main

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

Join @andresilva91 and the rest of your teammates on  Graphite

Merge activity

Jun 18, 8:14 AM EDT: @andresilva91 started a stack merge that includes this pull request via Graphite.


update e2e testing scenarios

Changes

Implement ClusterNetworkManager in apiclient for relevant API calls
Update fixture enable_vlan to create cluster network when the Harvester version over v1.0.3

Will not fix
need to update terraform test cases and resources

[ ] harvester_e2e_tests/integration/test_terraform.py::test_create_network_using_terraform::setup
[ ] harvester_e2e_tests/integration/test_terraform.py::test_create_volume_using_terraform::setup
[ ] harvester_e2e_tests/scenarios/test_vm_networking.py::test_create_vm_using_terraform::setup

randomly failed, need to figure a better way to test

[ ] harvester_e2e_tests/scenarios/test_create_vm.py::test_create_vm_on_available_cpu_node
[ ] harvester_e2e_tests/scenarios/test_create_vm.py::test_update_vm_on_available_cpu_node

affinity will be added, but while update VM, affinity will be removed automatically, need to check whether it is API issue or not

[ ] harvester_e2e_tests/scenarios/test_vm_networking.py::TestVMNetworking::test_remove_vlan_network_from_vm
[ ] harvester_e2e_tests/scenarios/test_vm_networking.py::test_update_vm_vlan_network_to_management

Tested on harvester-runtests#80

Instead of modifying the existing fixtures, let's create a new directories and have new fixtures there. Because in future it will become tough and tedious work to remove the old code.

Instead of modifying the existing fixtures, let's create a new directories and have new fixtures there. Because in future it will become tough and tedious work to remove the old code.

Extending old fixtures is the simplest way to fix multiple test cases, otherwise we will need to update all test cases.
(it would almost equals to re-write those test cases if use new fixtures)

@lanfon72 Can you squash all the commits to 1 commit and then we can merge this.

@lanfon72 Can you squash all the commits to 1 commit and then we can merge this.

It requires to update in repository settings.


Allowing custom URI scheme for CORS allowed origin list

Is your feature request related to a problem? Please describe.
I am trying to add 'ionic://localhost' to the CORS allowed origin list of the Azure SignalR resource, but this is getting blocked by the validator (both on the Portal and through AZ CLI as well).
Describe the solution you'd like
Custom URI schemes for CORS allowed origin list to be allowed.
Additional context
I am working on an Ionic app for iOS (via WebView) with the @microsoft/signalr ts client library. http | https are reserved schemes on iOS, which is why the Ionic app uses ionic as the URI default scheme.
The Azure Portal as well as the AZ CLI for SignalR validates the CORS origin allowed list entries based of the following format: [HTTP|HTTPS]://[www.]domain.[TLD][:portnumber].
Would it be possible to relax the schema part of the URI validation - so custom schemas are allowed?
A current workaround is to use '*' to allow all origins.
Alternatively I will have to port the @microsoft/signalr ts client library to Cordova to do native http requests.

Any luck on this issue?


Clean up the source deps for horizon/swift

Horizon had a double entry for memcache, picked the one that sets a pin.
Swift doesn't use mysql, not sure why we were installing it into the
venv.

:thumbsup:


Update master wrapper

And build logic to use Kotlin 1.8.10 and the latest kotlin-dsl plugin

@bot-gradle test and merge

I've triggered a build for you.

@bot-gradle cancel

I've cancelled the pre-tested commit build.

@bot-gradle test and merge

I've triggered a build for you.


add Immanuel Kant Gymnasium Hiltrup (kant.ms.de)

The immanuel Kant Gymnasium is a public school in 48165 Münster, Germany. The public school website is kant-hiltrup.de.

@maximilian-hack First stage of verification passed, official domain is kant-hiltrup.de as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://kant-hiltrup.de/series/podkant/

@maximilian-hack Thank you for your patience while waiting for a review and processing your request. Pull request merged.


What is the frame selection(sampling) criterion of ScanNet dataset?

As you mentioned at the MVS2D paper,
ScanNet dataset sampled from original set by 86324 triple images for training and 666 triple images for testing.
I wanna know the criterion of frame sampling.

Hi @nicesonnday , we first select every ~20 frame among a ScanNet's full sequence, and sample the target frame that we want to predict depth,  finally sample some frames(2 in our ScanNet exp) around the target frame. It's similar to DPSNet's implementation: https://github.com/sunghoonim/DPSNet/blob/master/sequence_folders.py


feat: add Ticket api integration

Changes Made 🎉

[x] feat: add supabase ticket api integration
[x] feat: add placeholders for ticket image upload

Describe Changes
Integration with Supabase API to get Ticket information.
Add placeholder for image upload.
Visuals (Optional)

Checklist ✅

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Amazing PR luis, thank you for all the time and the contribution!

The new commit resolve most of the requested changes. The only remaining concern is how are we going to implement the rate limiting for image upload.


chore: bump argoproj-labs/go-git to v5.4.7. Fixes #10600

This PR bumps https://github.com/argoproj-labs/go-git to latest version v5.4.7, which has the potential fix for cloning issues with azure devops.
Fixes #10600

So bumping go-git does not fix the Azure Devops issue entirely. It adds a workaround that needs to be implemented. See https://github.com/argoproj/argo-workflows/issues/11705#issuecomment-1793778023 where I've added details and back-links


Stepper motors at office are too tall

I just went through and built a blot from one of the demo kits in the office.
The stepper motors we have are too tall for the blot's legs and the machine rests on it's motors

These are just the wrong motors. Will fix in future by getting the right ones.


Reorganize Lexeme storage

Currently Lexemes are loaded into WordBundles and retrieved from there in form of a list of (id,lexeme) pairs. This should be reorganized: Lexemes should be obtained by end user from Vocabularys by ids, for example:
example_characters.ru_RU.words:
"bear" [Муж] {
  медведь
}

Client code will use a Vocabulary like this:
new Vocabulary("example_characters.ru_RU.words").get("bear").baseForm() // "медведь"

This issue is replaced with #54


handle literals in comment text

Handle literals in comment text data migration.

Ill hit the merge on this as we need this fix for deploying


New command: m365 pp environment get

Usage
m365 pp environment get [options]
Description
Gets information about the specified Power Platform environment.
Options

Option
Description

-n, --name <name>
The name of the environment to get information about.

--asAdmin
Run the command as admin and retrieve details of environments you do not have explicitly assigned permissions to.

Examples
Get information about the Power Platform environment named Default-d87a7535-dd31-4437-bfe1-95340acd55c5.
m365 pp environment get --name Default-d87a7535-dd31-4437-bfe1-95340acd55c5

Get information about the Power Platform environment named Default-d87a7535-dd31-4437-bfe1-95340acd55c5 as Admin.
m365 pp environment get --name Default-d87a7535-dd31-4437-bfe1-95340acd55c5 --asAdmin

Additional Info
Should mimic endpoints defined in the m365 pp environment list

Can I work on this?