Consistency in lists/objects

Thanks for your work, I'm VERY interested in something that deals with formatting in my place =)
One thing that struck me upon trying it out tonight, though, was that it does not handle "siblings" consistently. That is, given a list of, say, { id, name } objects; if one of them has a name large enough to reach the line limit, then this object, and this object alone, will be printed over 4 lines, while its siblings will be printed on 1 line. The "exploded" one will have a trailing comma, too, while obviously the one-liners will not.
I'm not sure whether this should be seen as a bug, or if the solution is to format all sibings the same, or even, if there should be a general option to output "tall" code.
That last option would be my favourite: personally, for the sake of readability, I tend to have my objects with the curly braces on their own line, and one attribute per line. Likewise, I tend to have my JSX tags formatted like so:
<MyComponent
  attribute={attr}
/>

Basically, adopt the same reasoning as elm-format: scrolling is cheap, and nothing beats consistency and spacing.

That's sort of the point of the formatter. It will fit code where it can. The printer will forcibly break a lot of constructs because that's how they look bests, but objects are going to collapse like that.
There are many other times where a short objects is what you want, and this is the kind of styling that I think we need to be less opinionated about. If you add more it's not more work to break it vertically when needed because the formatter will do it for you.

from https://github.com/jlongster/prettier/issues/43#issuecomment-271676281

Actually, I think that we never need a short object, while we sometimes need a long one. Consistency should lead us to more often than not use the long version.
Unless lower number of lines is an actual, useful thing to aim for?

@Augustin82 Can you write in your description what in the input and expected output in the issue description? Is this similar to #88?
JSX one attribute per line has been requested elsewhere. May be you can remove that from the description  to keep it succint.

Thanks for your time, @vramana , I've updated the issue.
It is somewhat similar to #88, I guess, with this one maybe being more general and regarding general philosophy more than an extreme (albeit real) example.

This is an issue for React Native StyleSheet.create where the output is not ideal ( https://github.com/facebook/react-native/blob/master/Examples/Movies/MovieCell.js#L71 ):
var styles = StyleSheet.create({
  textContainer: {
    flex: 1,
  },
  movieTitle: {
    flex: 1,
    fontSize: 16,
    fontWeight: '500',
    marginBottom: 2,
  },
  movieYear: {
    color: '#999999',
    fontSize: 12,
  },
  row: {
    alignItems: 'center',
    backgroundColor: 'white',
    flexDirection: 'row',
    padding: 5,
  },
  cellImage: {
    backgroundColor: '#dddddd',
    height: 93,
    marginRight: 10,
    width: 60,
  },
  cellBorder: {
    backgroundColor: 'rgba(0, 0, 0, 0.1)',
    height: StyleSheet.hairlineWidth,
    marginLeft: 4,
  },
});

outputs
var styles = StyleSheet.create({
  textContainer: { flex: 1 },
  movieTitle: { flex: 1, fontSize: 16, fontWeight: "500", marginBottom: 2 },
  movieYear: { color: "#999999", fontSize: 12 },
  row: {
    alignItems: "center",
    backgroundColor: "white",
    flexDirection: "row",
    padding: 5
  },
  cellImage: {
    backgroundColor: "#dddddd",
    height: 93,
    marginRight: 10,
    width: 60
  },
  cellBorder: {
    backgroundColor: "rgba(0, 0, 0, 0.1)",
    height: StyleSheet.hairlineWidth,
    marginLeft: 4
  }
});

As for the "sometimes I want to use long form, sometimes I use short form": elm-format is very good at that. If you have a record on a single line, elm-format will keep it on a single line. However, once it's on multiple lines or has mixed formatting (some fields are on single line, some are on separate lines), elm-format will split all fields into separate lines.
This is great, as it let's me control when each style is used. Of course one could argue that formatting like that is not consistent, but I think being able to control these two cases (short and long form objects) is important, as @nperichSYKES argued.
Single-line record after formatting:

Mixed-line record before formatting:

Mixed-line record after formatting:

That being said, I don't know if it'd be possible with prettier, since the readme says it disregards the original formatting:

In technical terms: prettier parses your JavaScript into an AST and pretty-prints the AST, completely ignoring any of the original formatting. Say hello to completely consistent syntax!

@ravicious: prettier reads the original source code to maintain empty lines, so we can technically implement what you describe.
Thanks a lot for the input!

@ravicious #495 is an implementation of what you suggested

@vjeux
Thank you very much for putting this in, it's great!
Shouldn't the same reasoning apply to arrays as well?
Original:
export const appLocales = [
  'en',
  'cn',
  'es',
];

Changed to:
export const appLocales = ['en', 'cn', 'es'];

Expected it to stay the same.
I strongly believe that "pretty" output means "output that can communicate the most information in the most consistent way with as little effort as possible". For me, being able to know that there are three locales in a split second without having to parse a list and make out if the commas are in, or out, of the quotes, is invaluable, and removing that is making the code less readable.
Thanks for your time and great work (on this and other stuff ^^).

I just wanted to chime in (maybe a bit late) to second @ravicious comment. I also think the way elm-format handles the single/multi line format depending on original format is fantastic and I would really love if prettier could work that way.
I think many times the desired format has more to do with "local consistency" than with global rules that apply everywhere throughout a codebase.
Anyways, awesome project! really grateful for your work!

Why aren't arrays following the same reasoning applied to objects?

Can this be re-opened per gustavopch's comment?

Really interesting discussion here. I agree that local consistency is often the key to readability, but that sure seems like a difficult thing for an algorithm to enforce.
This may be a terrible or infeasible idea, but I kind of find myself wishing the Prettier would allow me to "hint" how I want an object or list to be formatted/reformatted.
What I mean by this is, let's say I current have this:
const objectWithThreeProperties = { foo: "foo", bar: "bar", baz: "baz" };
Now I go in and add a line break:
const objectWithThreeProperties = {
foo: "foo", bar: "bar", baz: "baz" };

Now, if I format this, Prettier should say, "Oh, he wants to split this", and spit out:
const objectWithThreeProperties = {
    foo: "foo",
    bar: "bar",
    baz: "baz"
};

If I change my mind, I just do:
const objectWithThreeProperties = { foo: "foo",
    bar: "bar",
    baz: "baz"
};

If I format this, Prettier should say, "Oh, he wants to join this", and spit out:
const objectWithThreeProperties = { foo: "foo", bar: "bar", baz: "baz" };
So, basically, it compares the current formatted (assuming that is known) with the edited original and realizes that the edited original has a different line-break intent than the currently formatted, then it tries to make the new formatted version match the intent.

@devuxer Prettier already takes hints about object literals. If there’s a newline anywhere inside it, it will stay expanded. If not, it will stay on a single line as long as it doesn’t get too long. So you can add a random newline somewhere to force Prettier to expand an object literal, and you can manually join it all up on a single line (so not exactly like your suggestion, but doable) to attempt to make it single-line.
https://prettier.io/docs/en/rationale.html#multi-line-objecs

@lydell, Yes, so really my suggestions boils down to making it easier to join it back up again.

I was wondering, would it be possible and/or would it make sense to align the values of object literals using spaces, when the object literal is multiline but the values are not?
For example this:
const theme = {
  container:                'react-autosuggest__container',
  containerOpen:            'react-autosuggest__container--open',
  input:                    'react-autosuggest__input',
  inputOpen:                'react-autosuggest__input--open',
  inputFocused:             'react-autosuggest__input--focused',
  suggestionsContainer:     'react-autosuggest__suggestions-container',
  suggestionsContainerOpen: 'react-autosuggest__suggestions-container--open',
  suggestionsList:          'react-autosuggest__suggestions-list',
  suggestion:               'react-autosuggest__suggestion',
  suggestionFirst:          'react-autosuggest__suggestion--first',
  suggestionHighlighted:    'react-autosuggest__suggestion--highlighted',
  sectionContainer:         'react-autosuggest__section-container',
  sectionContainerFirst:    'react-autosuggest__section-container--first',
  sectionTitle:             'react-autosuggest__section-title',
}

is arguably easier to read than this:
const theme = {
  container: 'react-autosuggest__container',
  containerOpen: 'react-autosuggest__container--open',
  input: 'react-autosuggest__input',
  inputOpen: 'react-autosuggest__input--open',
  inputFocused: 'react-autosuggest__input--focused',
  suggestionsContainer: 'react-autosuggest__suggestions-container',
  suggestionsContainerOpen: 'react-autosuggest__suggestions-container--open',
  suggestionsList: 'react-autosuggest__suggestions-list',
  suggestion: 'react-autosuggest__suggestion',
  suggestionFirst: 'react-autosuggest__suggestion--first',
  suggestionHighlighted: 'react-autosuggest__suggestion--highlighted',
  sectionContainer: 'react-autosuggest__section-container',
  sectionContainerFirst: 'react-autosuggest__section-container--first',
  sectionTitle: 'react-autosuggest__section-title',
}

@tobia Your subject has almost nothing related with the issue's original subject. We try our best to keep discussions focused.
Also, this was already discussed, we won't include that inside Prettier, see #1622.


missing return cb

Not sure if this is a problem, but why trying to replicate https://github.com/mapbox/mapbox-studio/issues/1047 (callbacks called more than once) I noticed that tl-vector consistently uses return cb except in this one place:
diff --git a/index.js b/index.js
index 587357d..4741c23 100644
--- a/index.js
+++ b/index.js
@@ -414,7 +414,7 @@ function tm2z(uri, callback) {
     var unpacked = false;

     var once = 0;
-    var error = function(err) { if (!once++) callback(err); };
+    var error = function(err) { if (!once++) return callback(err); };

     // Check for unpacked manifest
     exists(base + '/.unpacked', function(exists) {

noting I also see return not used with the callbacks at https://github.com/mapbox/node-get/blob/43cae553f4335a7ab3963772d7fef8a86e439725/lib/index.js#L294-L295 and https://github.com/mapbox/node-get/blob/43cae553f4335a7ab3963772d7fef8a86e439725/lib/index.js#L315-L316

A return isn't necessary in all these cases -- each has a semaphore preventing multiple calls to the callback and there's nothing else in this error function for a return to prevent.

thanks, closing.


Error in Symfony > 2.5

This commit https://github.com/FriendsOfSymfony/FOSCommentBundle/commit/ba54b4327b403748b359b9b139be1d58363f2266
removed
use Symfony\Component\Validator\Validator\ValidatorInterface;
That import is needed in Symfony > 2.5 and Symfony 3,  or the if ( https://github.com/FriendsOfSymfony/FOSCommentBundle/blob/master/Controller/ThreadController.php#L402 ) always fail.
I made a pull request to fix it https://github.com/FriendsOfSymfony/FOSCommentBundle/pull/554

Fixed in https://github.com/FriendsOfSymfony/FOSCommentBundle/pull/554


ScreenSpaceCameraController Bug

Camera moves past entity if rendered size is too small.
To test, put the single pixel dot below the horizon, then zoom all the way in. If the camera -> Entity ray also intersects the ellipsoid, the camera will zoom past the entity.  Try the same thing with the 5 pixelSize entity, or load a model, it will be fine.
I'm not very familiar with the changes made over the past year that include globe detection but this seems to be related, as rolling it back to commit aaf6bd8a5ca26dba0ce4ac113b9ffd58708fad13 fixes the issue.
Sandcastle example
Browser:
Chromium: 101.0.4951.54 (Official Build) (64-bit)]
Operating System:
Pop!_OS 22.04 LTS

Thanks for the report @TJKoury! I can reproduce the issue and it does appear to be a regression.


revalidateTables after 1.0.9 doesn't return cached data during refetch

Describe the bug
This is critical for us. We're stuck on an old version and not sure how best to proceed. Any pointers would be greatly appreciated.
We upgraded cache-helpers/swr 1.0.9 to latest 1.7.5. We noticed a lot of new re-renders and flickering in our app. After spending quite a while in the bowels of swr and comparing the behavior of the two versions we found the main difference. For a bit of background, we use quite a few rpc methods for more complex data fetching, and thus use the explicit revalidateTables when related data changes.
What we saw is that when a table revalidation occurs, the associated useQuery data is set to undefined while the refetch is in progress. Even when the cache has a copy of the data as it was previously fetched.
To make this easier I was able to create a reproducible test case that shows our issue in a vanilla react-native + supabase app + cache-helpers.
To Reproduce
Here's the repo that shows the behaviour: https://github.com/jmwind/swr-cache-helpers-bug. It has a repo with easy instructions on how to dupe.
Expected behavior
I'd expect that if the cache has data that the revalidateTables doesn't clear the cache while revalidating. Or maybe it's calling something new in SWR. I didn't have time yet to dig into all the cache-helper implementation.
Additional context
Happy to help. Ping me on Twitter jmwind at any time.

hey @jmwind, thanks for the repro! are you able to pin point with what version this starts to happen? I will definitely take a look at this asap, but 1.0.9 to 1.7.5 is a big jump. If you could figure out what version this started with it would speed up my debugging a lot.

a question regarding the repro: why do you put trips into revalidateTables of the trips mutation? this is not something I have had in mind when implementing this, and this is can cause the flickering.

@psteinroe that's just an example. What we do is we have a table profiles and a rpc/profile_extended. When profiles is mutated we revalidateTables on rpc/profile_extended. In the example repo, you can also simply remove the revalidateTable on the trips and just do profiles when trips are edited. The behaviour diff is the same. I could also add an rpc to show you how it's the same.
For now, let me bisect by hand and pinpoint when the change happened. As you said, there are a lot of versions ;)

@psteinroe ran a manual bisect with the repo I provided to show the problem. The example works up to 1.5.0, but breaks in version >1.6.0.
Happy to help troubleshoot more.

Also checked that swr version is the same between cache-helpers/swr 1.5.0 and 1.6.0
peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>

this commit is the only one that makes sense as a root cause, but it actually fixed the revalidation and should not break them... I think the reason is that some other mutation is going on that sets the data to null and the revalidate then works and refetches and repopulates the data.
https://github.com/psteinroe/supabase-cache-helpers/commit/a4d14bdb2a286d22c624767db5fe6f21a2ee6111#diff-16ab35c6c2d3521f6d299935618050664a4a1fc0fc82bc75b95a7435bd67622e

Yep, that looks like it's the change. Related to revalidation, but no idea why that would trigger a different behaviour in swr.
Here's another test I just ran. Put console.logs into useSWRHandler.revalidate and compared the output in the sample repo between 1.5.0 and 1.6.0.

I am quite sure that this worked before, but I think we have to change that part back to just mutate(key) without passing the options.

I reverted that change with this patch, it now works fine
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 6e03e89..59d3969 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -312,7 +312,7 @@ function useDeleteItem(opts) {
         cacheKeys: getMutableKeys(Array.from(cache.keys())),
         getPostgrestFilter,
         revalidate: (key) => {
-          mutate(key, __spreadProps(__spreadValues({}, opts), { revalidate: true }));
+          mutate(__spreadProps(__spreadValues({}, opts), { revalidate: true }));
         },
         mutate: (key, data) => {
           var _a;
@@ -340,7 +340,7 @@ function useMutateItem(opts) {
         cacheKeys: getMutableKeys(Array.from(cache.keys())),
         getPostgrestFilter,
         revalidate: (key) => {
-          mutate(key, __spreadProps(__spreadValues({}, opts), { revalidate: true }));
+          mutate(__spreadProps(__spreadValues({}, opts), { revalidate: true }));
         },
         mutate: (key, data) => {
           var _a;
@@ -369,7 +369,7 @@ function useUpsertItem(opts) {
         cacheKeys: getMutableKeys(Array.from(cache.keys())),
         getPostgrestFilter,
         revalidate: (key) => {
-          mutate(key, __spreadProps(__spreadValues({}, opts), { revalidate: true }));
+          mutate(__spreadProps(__spreadValues({}, opts), { revalidate: true }));
         },
         mutate: (key, data) => {
           var _a;

but that's not the right solution as per swr docs. the mutate is not bound but global, so we have to pass the cache key as the first argument.

I haven't gotten into the swr code yet ;)
I'd also like to know why passing the key doesn't work. As I agree, that should do the same thing. But at least we know there's a behavior diff between the two (step 1). And there's a test we could add to cache-helpers to catch this subtle change in the future. I can help and write a test case now.

can you check the pr? and a test case would be great, thanks!

Do you remember why you added that? I didn't see how it was related to the test in the same commit.
Let me help you, I'll write a test and submit. Give me 30mins.

mutate(__spreadProps(__spreadValues({}, opts), { revalidate: true }));

this will not do anything or at least have undefined behaviour, which is why I changed it the way I did. main point of the pr was to pass the cache key as the first argument, and I assumed that if I set null or undefined as data it will just not do anything but revalidate with the options appleid as third argument. but that does not seem to be the case.

@psteinroe added a test here https://github.com/psteinroe/supabase-cache-helpers/pull/470

Was able to have this fail before and pass after the patch.
Locally, the useSubscriptionQuery always fails for me but all the other tests in postgrest-swr pass reliably. Sorry if I missed something here, but tried to follow your pattern.

Thanks @psteinroe! We use cache-helpers in our product a lot, so feel free to reach out if you need a hand with anything.

thanks for the sponsorship, means a lot! 🫶


mars: features, optimizations and bug-fix from upstream.

expose available webservice addresses in marsjob status.
support shared-memory mount, optimize environments injection and other bug fix.
support marsjob persistency.

lgtm


Bugfixes for server.close() and server.destroy()

@feross @mikeal

LGTM -- thanks for catching this.

0.96.5


I noticed that Jukebox can only load up to the first 15 images of something if it's got a lot in sex shack. Perhaps you could make a "next" option for loading the next set?

<@!134310073014026242> I've tried this twice. Does it want me to put quotes around it?
This suggestion was created by a user and sent by the bot:
jukebox-botto#8602

Won't fix because of limitations in discord
you can't change attachments of a message to make a menu or link to an image directly from pixiv


Pages for Group Basic Concepts

Task  -> Assignee

[ ] Basic Concepts ->
[ ] Project Structure ->
[ ] Astro Pages ->
[ ] Astro Components ->
[ ] Frontend Components (React, Svelte, Vue, and more) ->
[ ] Component Hydration ->
[ ] Layouts -> @ewatch
[ ] Styling -> @itskitto
[ ] Content (Markdown) -> @jgil-r
[ ] Data Fetching ->
[ ] Pagination ->
[ ] Collections ->
[ ] Build & Deploy ->

Layouts -> ewatch

I'll take the styling portion! I want to read more about it so it'll force me to sit down and digest the information on it 😁

Could I get assigned to Content (Markdown)?

Could I get assigned to Content (Markdown)?

Gotcha! Are you in the Discord btw? If so what's your username?

Could I get assigned to Content (Markdown)?

Gotcha! Are you in the Discord btw? If so what's your username?

Yes I am, chuy#5231

I'll take Component Hydration

@itskitto @FredKSchott I added a new page to this section URL Sanitization, not sure if the title is ideal or if it should be part of another group, please let me know your thoughts.
This came out of this PR: https://github.com/snowpackjs/astro-docs/pull/19#discussion_r657479290

After moving everything over from the Astro repo, we're in pretty good shape! Here's what I think is left to do:

Layouts
Pages
build & deploy

Getting close!!!

Done! All pages are now available! 🥳
Curious to hear what people would like to do next! Two steps that jump to mind are:

Edits: Give someone's page a read if you didn't write it yourself, and create a PR to help edit their work. Good chance to review that everything is correct as well, in case something has changed.
Copy these docs into the main astro repo: Now that the docs are complete, we should copy them back into the main astro repo so that any changes made in the main repo are easy to port onto here. (This came up on Discord, but once the site is ready we can move the entire thing into the main astro repo, so this is just a temporary copy step until that work is done).


RspTms missing scale factor for DID 705, 706, 712

IEEE 1547-2018 sets a range requirement of 0.5 to 60s. IEEE 2030.5 specified resolution in 1/100 of a second. SunSpec models provide only integer resolution.
Proposed Solution
Add a RspTms_SF to the three models.
Better Solution
Note in the units field that the value is specified in milliseconds, which is what the name seems to indicate.
IEEE 1547-2018:

IEEE 2030.5: (from sep.xsd)
<xs:element name="openLoopTms" minOccurs="0" maxOccurs="1" type="UInt16">
            <xs:annotation>
              <xs:documentation>
                     Open loop response time, the time to ramp up to 90% of the new target in
                     response to the change in voltage, in hundredths of a second. Resolution is
                     1/100 sec. A value of 0 is used to mean no limit. When not present, the device
                     SHOULD follow its default behavior.
             </xs:documentation>
            </xs:annotation>
          </xs:element>

Which units field is value specified in milliseconds?

None are. That's a suggestion.
The naming convention "Tms" indicates to me that the field is "Time in milliseconds". Maybe something else was intended.
One issue with using milliseconds: You limit the period to about 65.5 seconds, which may be too short for some applications.

In this case the 'Tm' is the abbreviation used for time in SunSpec information models so Tms is in seconds. All the models with RspTms are being updated to have a scale factor just in case sub-second accuracy is required.

Ah, didn't know that was the naming convention (though I suspected it could be). IEEE 1547 requires fraction of a second resolution, so adding the SF is a good step. Thanks.

One potential issue: 1547-2018 and HECO have trip requirements with ranges fro 160ms to 1000s. I think we need to make trip time registers 32 bit with a scale factor of -2 for hundredths of a second resolution.


Add support for timestamp granularities for Create Transcriptions endpoint

Feature Request
Is your feature request related to a problem? Please describe.
OpenAI has added support for timestamp granularities, "word" or "segment", to the Create Transcriptions endpoint. Documented here: https://platform.openai.com/docs/api-reference/audio/createTranscription
Describe the solution you'd like
Allow passing "word", "segment" or both to the Create Transcriptions endpoint.
Describe alternatives you've considered
Right now I will have to access the OpenAI API directly to use this feature. It is a bit cumbersome, which is why I use this library!
Additional context
N/A

@StephenHodgson
Thank you for adding support for this.  It is very much appreciated!


Script not opening with Url

When i tried to open the interface with the link, i got to a file explorer. I needed to rename the app.php to index.ph to start automatically.

Did you checked out the whole project?
There has to be a ".htacces" file in the folder "web" and there is defined, that app.php is used as index-page, something like:

DirectoryIndex app.php

Because of security, a file explorer you should never see!


Overwrite magic refresh period on XNG

This is required because of a global minimum value for this parameter, otherwise XNG refuses to create the sampling port with INVALID_PARAM.

Replaces https://github.com/DLR-FT/a653rs/pull/7


bug: unable to set enabled=true for synthetic monitors

enabled = true cannot be set for http synthetic monitors (I guess same with browser).
The field is defined as int instead of bool as seen in https://github.com/dtcookie/dynatrace/blob/master/api/config/synthetic/monitors/http_synthetic_monitor_update.go#L66

I guess this PR should fix the issue: https://github.com/dtcookie/dynatrace/pull/6/files


Bug: git sensor is not able to fetch latest commits

📜 Description
It bugs out when trying to fetch the latest commits. There is no error in UI but could see below error in git-sensor logs :
error in git cli operation","msg":"fatal: detected dubious ownership in repository
error in updating repository","err":"exit status 128
👟 Reproduction steps

This is happening in all the applications with latest release.
Note : It'll not happen in new applications or newly created workflows.

👍 Expected behavior
CI should have fetched the latest commits
👎 Actual Behavior
CI is not able to fetch the latest commits
☸ Kubernetes version
NA
Cloud provider

NA

🌍 Browser
Chrome
🧱 Your Environment
NA
✅ Proposed Solution
NA
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#5434

RCA
Git in it's newer versions checks if the current user is the owner of the git repository folder, and will produce "detected dubious ownership" error if the current user is not the owner. We have recently updated our git version for shallow cloning due to which old git materials saved in devtron as root user started throwing error when devtron User was running git fetch.
Reproduced this issues by saving git material as root User using old git sensor image (when we use to run container as root user) and then fetching commits as devtron User.


Add Open Graph metadata to the profile site

In order to improve the information that is shown in social networks and in search engines, perform complete the following tasks:

Create a OpenGrahProfileRoute class using this as an example that should fetch the profile of the user from catalyst and build the title and metadata tags.
Configure the rollouts sites file so when an instance of the route created before is requested, it builds it.
Configure the domains file so when the site is loaded, the route class is executed.

Done!! this is live, closing the issue


Clear output buffer during CallbackInstrument DSP

When connecting CallbackInstrument to the Mixer after another node, it will return the buffer as is. This will double the values inside the Mixer, and it can be fixed by filling the output buffer with zeros during DSP.

Hey @aure, could this be merged?


Bluetooth: controller: legacy: Fix missing first conn event

Fix missing first connection event due to first connection
event ticks_slot overlapping with the initiator window
ticks_slot.
Signed-off-by: Vinayak Kariappa Chettimada<EMAIL_ADDRESS>

Am I right in assuming that the change still does not completely fix the problem, but only a step on the way?

@mtpr-ot This fixes the issue. And my manual testing covers the lines 1206-1208. As mentioned in the other comment, those changes are incorrect. I will get back to this PR next week.

close/reopen to retrigger CI.

@mtpr-ot please review the changes, added new interface and does not impact split controller (but will be useful for future)

ctrl.c, line 1735: Would it be better to define 1250 as a constant, and use the constant name instead of hardcoded 1250?

ctrl.c, line 1735: Would it be better to define 1250 as a constant, and use the constant name instead of hardcoded 1250?

I have created this: https://github.com/zephyrproject-rtos/zephyr/issues/23314


ENH: Properties for digital surface twins

When this PR is done, digital surface twins have properties attached to them.
See #904 for more details.
This includes changes in the Fontend:

Users can See & Edit Properties

And changes in the Backend:

Properties are stored

Design example: Obsidian

Looks good!

Here is what i came up with to copy this:

Looks good!

I changed the way the "discard" "save" button looks:

I also want to add a tooltip to those buttons.
But this requires to add a 3rd party lib "Popper" and i wanted to get some feedback before.
Any Opinions?

Please keep the text for those. Icons only if there is no space.Am 20.12.2023 20:16 schrieb Ioannis Nezis @.***>:
I changed the way the "discard" "save" button looks:
2023-12-20_20-14.png (view on web)
2023-12-20_20-14_1.png (view on web)
I also want to add a tooltip to those buttons.
But this requires to add a 3rd party lib "Popper" and i wanted to get some feedback before.
Any Opinions?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Alright 👍
Is the "SAVE" intentionally all caps?
And should the edit button also be text?

The test fail because the api response now contains the 'properties' field.
This is a easy fix, but i would like to wait until the properties are stored properly.

The test fail because the api response now contains the 'properties' field. This is a easy fix, but i would like to wait until the properties are stored properly.

 It is very annoying to add those fields manually to every test.

@IoannisNezis I've added a couple of comments and a (non-functional) example test in the new file test_properties.py.
I think you need to switch from many-to-many to a one-to-many relationship where the property has a ForeignKey to surface. The serializer then also needs the surface like here:
https://github.com/ContactEngineering/topobank/blob/dc540ae1856ccb6558db80a6dfab7ac42a9e504e/topobank/manager/serializers.py#L92
In the test you can then create a property like here:
https://github.com/ContactEngineering/topobank/blob/dc540ae1856ccb6558db80a6dfab7ac42a9e504e/topobank/manager/tests/utils.py#L30


Support partial evaluation in CLI

Category
Other
Describe the feature you'd like to request
Be able to do partial evaluation in the CLI
Describe the solution you'd like
Introduce an optional parameter "--partial" in the CLI, so to change the entity mode to partial and be able to do partial authorization and give residual result.
Describe alternatives you've considered
None
Additional context
No response
Is this something that you'd be interested in working on?

[X] 👋 I may be able to implement this feature request
[ ] ⚠ This feature might incur a breaking change

Hi @Neio, thank you for your interest in Cedar. Partial evaluation is currently an experimental feature and not ready for production use. Hence, we cannot accept any PR related to this feature. I hope you can understand it.


Keyboard and Mouse Freeze

Description of the new feature / enhancement
Quick shortcut to disable all input from keyboard and mouse except the hotkey combination.
Scenario when this would be used?
Useful when cleaning keyboard or watching movie to prevent distraction.
Supporting information
BlueLife KeyFreeze

Scenario when this would be used?
Useful when cleaning keyboard or watching movie to prevent distraction.

Or, as it has been suggested so many times before:

When executing a long script that will take a long time, it is vital to prevent someone else from typing or some object from pressing our keyboard.
using this feature in a big office, while doing a presentation remotely, with the host of a remote CLI, etc.
Blocking inputs on a pc running as kiosk


ONS visualisations not rendering on Firefox and Safari

Chrome/Edge/Brave can parse new Date('2021 FEB'), but Safari and Firefox cannot.
data key in visualisation needs to be recalculated using correct date format

The ONS JSON response contains month as full month name, as in February. Change the data input from 2021 FEB (under the date key) to 2021 February 1. Safari and Firefox then parse new Date('2021 February 1') correctly

Safari and Firefox also parse new Date('2021 FEB 01') correctly

https://github.com/EconomicsObservatory/ECOdataHUB/commit/0640b87455b862ef807271466ac70ac95e8f7fe5 bakes the raw data into the JSON spec, by first running it through a pandas.to_datetime query

Fixed by using toDate on the date key. For future reference, might be useful to autoparse dates as datetime:  either "toDate(datum.year+' '+datum.month+' '+1)" or "datetime(datum.year, datum.month, 1)"


Issue #29 - Fix for Sitemap containing unpublished items

Check if a page is published only in the context publication and not in any publication when generating the navigation/sitemap

Incorporated in DXA 2.2


Dynamically switch between Tab and Space based on the global or buffer options?

Is there a way to dynamically figure out the indentation (space/tab) to use in a snippet? Right now I'm creating text nodes with indent string. I use get_indent_str() to figure out whether to use tab or space? I'm just wondering if there is a cleaner way?
function M.get_indent_str()
  local tab_stop = vim.opt.softtabstop:get()

  if vim.o.expandtab then
    return string.rep(' ', tab_stop)
  end

  return '\t'
end

fmt(
    bt([[
      function ({})
        {}{}
      end
    ]]),
    {
      i(1),
      t(indentation),
      i(2),
    }
  )

Oh luasnip should expand \t to either whatever is given by expandtab and tabstop.
Does that work?

It's working. Thanks.


Add files via upload

Means?
On Sat 27 Oct, 2018, 11:52 PM Sri Harsha<EMAIL_ADDRESS>wrote:

Closed #51 https://github.com/SriHarshaGajavalli/Git-Tutorials/pull/51.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SriHarshaGajavalli/Git-Tutorials/pull/51#event-1930437062,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbnTHHChZYd0WmgXqD2QCtPcft-J1QtHks5upKRYgaJpZM4X9jUk
.


Add conditional to kernel remap

Fix bug where the multiboot section ends
up on the same page as one of the elf
sections, thereby getting mapped twice by the
remap utility. The OS now silently does nothing
if it finds one of the pages it wants to map multiboot
to taken.

If you want to muck around with one of the ld solutions, I'm ok with that, but this for sure works.


Config option for changing fieldbag Name.

Versions:

VueJs: 2.0
Vee-Validate: 2.0.0-beta.17

Description:
Is there a way change the fieldbag name , just like errorBag to avoid conflicts?
Currently vee-validate does not play well with https://github.com/ratiw/vue-table , because vue-table uses fields as a required prop.
Any help would be greatly appreciated 👍

There is already an option, it is just undocumented at this time. The below code should work:
const config = {
    fieldBagName: 'fields', // change if property conflicts.
};

Vue.use(VeeValidate, config);

I tried updating to 2.0.0-beta.18 but the fieldBagName config does not seem to be working at the moment.
Its still conflicting with other dependencies.
Mayb that's the reason its undocumented.

try fieldsBagName it was misspelled in a couple of places, it was not documented because it does not work nicely with Vue 1.x versions.

@logaretm Works perfectly now! Thanks :)

Great, sorry about the confusion, I even misspelled it in the docs 😞

VeeValidate uses "fields" by default which causes a namespacing issue. To solve, it name their field anything else.... e.g. Naming it "veeValidateFields" fixed it for me.
const config = {
    fieldBagName: 'veeValidateFields', // change if property conflicts.
};

Vue.use(VeeValidate, config);


feat(wasi_provider): Implements logging for wasi

This implements logging for the wasi provider. The actual logs function
is untested as there isn't an easy way to do it outside of integration
testing. Also, the logging logic from kubelet isn't fully hooked up yet
(see #33).
Please also note that I made some changes to the logs method on the Provider
trait to more clearly reflect the data available (essentially just the path
from the GET request).
Closes #23

Ok, so I cleaned things up to use a file we create at module runtime instead, which we then maintain a handle to. Let me know if you like it better


Document the exception files that are used

And move the skip_version one to a separate file.

Done in https://github.com/pombase/genome_changelog/commit/401ae09de011c3c53f5811845f6fecd6d6ad2e75


Add mutable-content key to aps dictionary.

We would like to add the mutable-content key to aps dictionary.  The mutable-content field tells iOS that the notification has content that can be changed by a service extension before delivery.  It allows for functionality like rich notifications.
Documentation:
https://developer.apple.com/reference/usernotifications/unnotificationserviceextension
http://willowtreeapps.com/blog/wwdc-2016-rich-notifications-in-ios-10/

I believe apns_extra was added to allow for such new fields without having to change the record definition and upgrade the dependency each time. Is there a reason you need to define it separately?

Ah, I was not aware of that field.  Thanks @jwheare .  I'll give it a try and close this PR out when I've verified it.

I'm using this in an Elixir project, but the following doesn't seem to work:
apns_msg(   apns_extra:  [{:"mutable-content", 1}] )
Is it the way the atom is converted to binary?

@richardleebr in our Erlang project we're sending:
#apns_msg{ apns_extra=[ {'mutable-content', 1} ] }
It isn't erroring out either, but we haven't build the iOS app side out so I can't confirm whether it's actually working yet :) I'll let you know when we get there.
One thing you might want to check is your UNNotificationExtensionCategory. I believe a corresponding category should be set in the apns_extra field for rich notifications to work.


python3Packages.azure-identity: mark as enabled

Motivation for this change
now supports 3.8, 3.9
msal patch no longer necessary
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/un-disabling-a-python-package-in-an-overlay/10593/8

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/un-disabling-a-python-package-in-an-overlay/10593/8

python 3.9 needs astroid to support 3.9
https://github.com/NixOS/nixpkgs/pull/109375

2 packages built:
python37Packages.azure-identity python38Packages.azure-identity

python 3.9 needs astroid to support 3.9
https://github.com/NixOS/nixpkgs/pull/109375

2 packages built:
python37Packages.azure-identity python38Packages.azure-identity

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109375 run on x86_64-darwin 1

1 package marked as broken and skipped:

python39Packages.azure-identity

2 packages built:

python37Packages.azure-identity
python38Packages.azure-identity

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109375 run on x86_64-darwin 1

1 package marked as broken and skipped:

python39Packages.azure-identity

2 packages built:

python37Packages.azure-identity
python38Packages.azure-identity


Fix: layout animations on Android

Summary:
Layout animations are not working on the new architecture, because the animation driver is not added to the mounting coordinator. When the app starts running, ReactInstance.java calls startSurface on FabricUIManager.java, which starts the surface handler. The animation driver has to be added to the mounting coordinator after the surface handler starts because the mounting coordinator is created there, so I've added a check that will prevent adding an animation driver if the surface handler is not running.
On the other hand, we could just call startSurface from the Binding.cpp which adds an animation driver internally, but I guess there is a reason to not do that 🤔

Changelog:
[ANDROID] [FIXED] - add animation driver to the mounting coordinator on Fabric

Test Plan:

Tested on examples from docs in rn-tester.

Also, I don't think that setting UIManager.setLayoutAnimationEnabledExperimental(true) is necessary anymore 🤔

If I understand correctly, we already call setMountingOverrideDelegate when we call startSurface. Do you know why that isn't working and we need a second call?

If I understand correctly, we already call setMountingOverrideDelegate when we call startSurface. Do you know why that isn't working and we need a second call?

Which function do you refer to exactly?

If you mean the one defined in Binding.cpp, this function is not called. ReactInstance calls startSurface on FabricUIManager.java, which does not call any of Binding.cpp functions that call setMountingOverrideDelegate. I am not sure if that's on purpose, so I just added new function that adds animation driver from the FabricUIManager.

Hmm, startSurfaceWithConstraints and startSurface in FabricUIManager don't seem aligned.  Maybe the issue here is that when startSurface is used, and we later call updateRootLayoutSpecs we miss some of these steps?

Working on a fix for this - I believe I found the discrepancy.

Closing in favor of:

https://github.com/facebook/react-native/pull/46691


Not Working Properly

Xcode 9
Swift 4
After setting the constraint to the bottom button in the view when clicking on a text field it just moves the button up and doesn't move the uiview at all

Hi @WillMays1, thanks for reporting. If you want to move the view, you need to create a bottom constraint attached to the bottom of the view. All this library does is it increases the height of the constraint when the keyboard comes out. So if you attached the constraint to the button, it will go up with the keyboard, but this won't affect the view. Let me know how it goes.

Ok it moves now but not all the way up probably about 75%

What do you mean "not all the way up probably about 75%" sorry? Can you draw a picture?

Sorry, I don't quite understand what's going on there. :) I would try doing a demo app with a simple case, just to see how it works before applying to more complicated real app. Also, there is a demo app in this project, you might want to look how it works as well.

Ok now its properly adding the space but not automatically moving the view up

It's hard for me to say what's going on without knowing the details of the layout and the code. One can also use a workaround, instead of entering text in-place, open a modal dialog with a text input and let the user enter the text there. In this case there would be no need to move stuff around. Just an alternative.

I have a UIView inside a UIScrollView.
I created the bottom constraint.
Attached the buttom constraint to the following IBOutlet:
@IBOutlet weak var bottomLayoutConstraint: NSLayoutConstraint!
let underKeyboardLayoutConstraint = UnderKeyboardLayoutConstraint()
and I have this code in the viewDidLoad and it is still not working:
underKeyboardLayoutConstraint.setup(bottomLayoutConstraint, view: view,
bottomLayoutGuide: bottomLayoutGuide)
Any ideas?

Thanks for the info, this is not enough information for me to know what's causing the issue. There are plenty of things that can go wrong, which depends on how one sets up the auto layout constraints. I'm repeating myself, but this library only increases the length of the auto layout constraint and makes it equal to the height of the keyboard (plus a margin). That's all it does. It does not scroll the scroll view to ensure your view is above the keyboard.
One way to troubleshoot the problem would be to go to your storyboard and manually set the height of the constraint equal to the height of the keyboard. This way one can see if changing the constraint length is enough.
Here is how one can get the height of the keyboard.


Update update-skywalking_data_collect_protocol version to 8.9.0

Signed-off-by: Faseela K<EMAIL_ADDRESS>Commit Message: Update update-skywalking_data_collect_protocol version to 8.9.0
Additional Description:
Fixes #19181

cc @phlax

cc @wbpcode @Shikugawa

Thanks for this update. LGTM and cc @Shikugawa

/lgtm deps
/cc Skywalking owners not already tagged @dio @lizan
https://github.com/envoyproxy/envoy/blob/main/CODEOWNERS#L64-L65

i was just about to land this then noticed that 8.9.1 is now available - im thinking lets bump to that version #19250

@wbpcode @Shikugawa could you have another quick look at this we bumped instead to 8.9.1

It's OK for me. But it's a bit strange, the commit of v8.9.1 and v8.9.0 are the same.


pasting excel grid into squire should result table not text

Expect a html table from pasting excel grid.
clipboard copy from excel in text/html type will be something like below.
...

 <col width=87 span=3 style='width:65pt'>

  1
  2
  3

  4
  5

  6
  7

...

...

 <col width=87 style='width:65pt'>

  2

...

and the code will strip
 and/or
, results appending bunch of trs or just a td in fragment.
I think it's not exactly a squire bug, but It'll be nice if we can treat it.
let me know if you want me to make a pr for this.

should it? I'm not sure if it should, in fact it made me happy that it did treat it as text. Me saying i like it doesn't mean it is correct but i thought i would at least let my feelings known :)

hey @MrMcGibblets  :)
As I think about the situation, that is MS excel & MS Clipboard Formats problem.
And the real problem is IE makes a table out of
asdf
 but not the others. That's inconsistent.
but I must admit it is a bit tricky to solve this. I patched the code in my repo by regex finding dangling td, tr with out table.

I've merged your fix, thanks!


fix: now workspace top nav link works as expected

Description
It was discovered that if you weren't onboarded we always redirected to /feed from / so the redirect to the last accessed workspace would never happen.
Now we no longer redirect to /feed if you haven't onboarded.
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
Fixes #2789
Mobile & Desktop Screenshots/Recordings

Steps to QA

Log in
Click on the Workspace link in the top nav.
You're redirected to the last accessed workspace, even if you haven't completed onboarding.

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?


How to visualize or output the value of the drift rate, boundary, and the value of 'x' during the simulation for a fitted model with given parameters. I want to visualize the process of how the information is accumulated and how the boundary is changed like the figure below:

Use the simulate_trial function.
Also, in the future, please ask questions like this in the Discussions section rather than reporting it as a bug.


Fix garbled Chinese response in browser. close #1559

https://github.com/apache/incubator-apisix/blob/master/Contributing.md#how-to-add-a-new-feature-or-change-an-existing-one
Summary
Modify APISIX Nginx template to solve #1559
Full changelog

Add charset utf-8; in APISIX Nginx config template

Issues resolved
Fix #1559

@xxm404 it will be better if you can add test cases for this PR

@xxm404 it will be better if you can add test cases for this PR

This problem only occurred in the browser, how to test by test Nginx

Hi, @xxm404 :
Consider the following code for increased  flexibility?
include mime.types;
{% if http.charset then %}
charset {* http.charset *};
{% end %}

Hi, @xxm404 :
Consider the following code for increased flexibility?
include mime.types;
{% if http.charset then %}
charset {* http.charset *};
{% end %}

Good idea, But in my opinion, Nginx charset won't be modified frequently, We shouldn't complicate config.yaml

@xxm404 many thx, merged already


Side navigation is not closeable by selecting utility menu items (mobile).

Bug Report
Description
Currently, application-layout injects props into child components to provide access to key features such as checking if the side-nav is open and an event to manually close it. The utility-menu cannot get access to these props and therefore cannot manipulate the side-nav if needed.
Additional Context / Screenshots
In the .gif below, after selecting a leaf menu item the user then has to close the navigation manually to see the new content.

Expected Behavior
In mobile viewports, selecting a leaf menu item should be able to close the side navigation.
Environment

Component Name and Version: terra-application-layout (v. 2.13.0)
Browser Name and Version: All
Node/npm Version: Node 8.9.2/npm 5.7.1
Webpack Version: 3.11.0
Operating System and version (desktop or mobile): Mobile (all)

cc: @bjankord

This issue will be mitigated by #275. The menu will close upon presentation of the utility menu at tiny/small breakpoints.


Analysis: 33% of dependency updates in this repository can be merged.

Hey there :wave:Our bot, Adaptly, found that 4 out of 12 currently open dependency update PRs can be merged.That's 33% right there:View Safe to Merge PRs1. Bump babel to ^7.22.112. Bump prettier to ^3.0.23. Bump stylis to ^4.3.04. Lock file maintenance:mag_right:   How does Adaptly know this?It analyses changelogs of dependencies updated in a PR.If no breaking changes are found in the changelogs, PR is marked as good to merge.:sparkles: Try Adaptly yourselfFeel free to try Adaptly on your repositories and finallymerge dependency update PRs. Let us know if you have any questions.Best of luck with your<EMAIL_ADDRESS>

@brijeshb42, aren't you on community support this week?

Yes. I am. I thought since you mentioned Adaptly in our last meeting, you'd like to take that up as an integration. I will anyways checkout the individual renovate bot PRs.


i don't know it's sftp bug or vscode bug

I jush want to upload a single file,  but when  I use "sftp : upload" with fast key  , it will upload my all floders files

up
latest vscode 1.25

#214


expose component in package itself

We can expose the component in this addon directly. So there is no need to add code yourself after adding this component as dependency.
I'm not sure if index.js is still needed. Looks bit like duplicated code now.

This is essentially a feature that allows you to extend the component in your own code however you wish and it also doesn't directly pollute your app's namespace.
This was a decision made following some of the emerging ember-cli conventions so I'd be happy to review this decision if there is some good examples of components doing this in the wider community

Also the test would need to pass to consider merging

This has now been solved in #16 and released under version 4.0.0
Let me know if you have any issues


react-tether typings module doesn't match library's export

Description
When using @types/react-tether with react-tether and the following tsconfig.json:
    "compilerOptions": {
        "noImplicitAny": false,
        "removeComments": false,
        "preserveConstEnums": true,
        "experimentalDecorators": true,
        "sourceMap": true,
        "noEmitOnError": true,
        "jsx": "react",
        "target": "es5",
        "module": "commonjs",
        "noEmit": true,
        "importHelpers": true,
        "allowSyntheticDefaultImports": true
    }

Importing the component through import TetherComponent from 'react-tether'; and using it, TSC will compile succesfully, but on runtime React will throw an error with:

Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined.

Steps to Reproduce

Install react-tether (last version, 0.5.7)*
Install @types/react-tether (last version, 0.5.1)
Import and use the component
Transpile the file
Run it

Expected behavior: [What did you expect to happen?]
React tether works properly
Actual behavior: [What actually happened?]
React throws an error where the value of the import is undefined.
*Note: I already tested with matching versions 0.5.1 on both react-tether and @types, but it still doesn't work
Reason behind
Debugging on the transpiled code, when we import react-tether we get directly TetherComponent class, ready to be used by react.
However, when using it after importing with import TetherComponent from 'react-tether', it transpiles to something like React.createElement(TetherComponent.default, ...), and as it doesn't have default defined, it tries to create an undefined element.
By importing with import * as ReactTether from 'react-tether';, then we are forced to use it as ReactTether.default by TSC (because it understands ReactTether as module), so we get the same transpilation
Temporal workaround
We must trick the module loader AND tsc, by doing this:
import * as ReactTether from 'react-tether';
import TetherComponentType from 'react-tether';
const TetherComponent = (ReactTether as any) as typeof TetherComponentType;

This is quite ugly. So I'm importing ReactTether as a module (when it gets used after transpiling, it doesn't call .default, and on runtime, I know that it gets imported as a the component), and cast it to the type of TetherComponentType, so I get all the type checks from TSC.
Request
I'm out of ideas on how to fix this. I would really appreciate if anyone has some hint, and I'm happy to further investigate and fix it.

Those definitions are not from us. Please open it on the correct repo, see https://github.com/DefinitelyTyped/DefinitelyTyped.

Woops, my bad! I thought I posted it in the definitions repo.
Sorry!


Sync changes from website back to OSS version

This syncs the changes from the internal fork shipped with our website back to the OSS version.

@cla-bot check

@cla-bot check

@cla-bot check


Added regultory compliance to package-composite-v3

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-ruby
Nothing to generate for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-java

Automation for azure-sdk-for-js
A PR has been created for you:
https://github.com/Azure/azure-sdk-for-js/pull/2547

Automation for azure-sdk-for-go

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5978
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5978/commits/99a7bed9c3b1bc644bd7198a5f2c1c901fcd5da9


Add logical assignment operators &&= and ||=

It's a follow-up on #92 and #328.

Let's also add >>= and <<= to the scope here so that all common operations have their augmented counterparts?

Sure, let's go for it


Feature: Provide an example Azure Function

Would be useful to see an azure function

@cdavernas

Hey @AshleyJButcher!
What do you want to see? An Azure Function serving an AsyncAPI document? Or an AsyncAPI document describing an AzureFunction? Both?
Anyways, I'm sorry but I won't have time to do so any time soon, got a lot cooking on the stove. You are however more than welcome to submit a PR addressing it!


Issue with verifying a webhook using Svix in my Express.js app

Bug Report
Hi everyone, I’m having an issue with verifying a webhook using Svix in my Express.js app.
Version
<EMAIL_ADDRESS>Platform
Clerk Authentication and User Management
Node version v20.17.0
Express version 4.21.0
Description
According to the Svix documentation, I should pass the raw payload directly into the Webhook.verify() method, but that’s not working for me.
I tried this code:
import express from "express";
import { Webhook } from "svix";
import bodyParser from "body-parser";
const router = express.Router();
router.post(
  "/clerk",
  bodyParser.raw({ type: "application/json" }), // Using raw body-parser
  async (req, res) => {
    const WEBHOOK_SECRET = process.env.WEBHOOK_SECRET;
    const payload = req.body;
    const headers = req.headers;
    const svix_id = headers["svix-id"];
    const svix_timestamp = headers["svix-timestamp"];
    const svix_signature = headers["svix-signature"];
    const wh = new Webhook(WEBHOOK_SECRET);
    let evt;
    try {
      evt = wh.verify(payload, {
        "svix-id": svix_id,
        "svix-timestamp": svix_timestamp,
        "svix-signature": svix_signature,
      });
    } catch (err) {
      console.log("Error verifying the webhook:", err.message);
      return res.status(400).json({ success: false, message: "Verification failed." });
    }
    // Further processing of the webhook event...
    return res.status(200).json({ success: true });
  }
);
export default router;

I expected to see this happen: My database syncs with Clerk user data.
Instead, this happened: I get this error: Error verifying the webhook: Expected payload to be of type string or Buffer. Please refer to https://docs.svix.com/receiving/verifying-payloads/how for more information.
Oddly enough, when I JSON.stringify() the payload before passing it to verify(), everything works fine:
  try {
      evt = wh.verify(JSON.stringify(payload), {
        "svix-id": svix_id,
        "svix-timestamp": svix_timestamp,
        "svix-signature": svix_signature,
      });
    } catch (err) {
      console.log("Error verifying the webhook:", err.message);
      return res.status(400).json({
        success: false,
        message: "Webhook verification failed.",
      });
    }

I am having the same issue:
Error verifying webhook: Expected payload to be of type string or Buffer. Please refer to https://docs.svix.com/receiving/verifying-payloads/how for more information.
when I log the event it returns undefined.
Could this be a middleware issue?

I have learned that it sounds like Express already deserializes the JSON body into a JavaScript object. It works with JSON.stringify() because there were no (whitespace, field ordering, etc.) differences between the original body and what JSON.stringify() produced. However, you should not rely on that always being the case, which is why they have a warning in the documentation about using JSON.stringify().

Indeed. You need to use the body parser to prevent that behavior: https://docs.svix.com/receiving/verifying-payloads/how#nodejs-express

Hi @tasn , thanks for the reply. I'm using body-parser, but I still get an error message.
Code
``
import express from "express";
import { Webhook } from "svix";
import bodyParser from "body-parser";
import createUserAccountWithProfile from "../services/webhooks/createUserAccountWithProfile.js";
import updateUserAccountWithProfile from "../services/webhooks/updateUserAccountWithProfile.js";
const router = express.Router();
router.post(
"/clerk",
bodyParser.raw({ type: "application/json" }),
async (req, res, next) => {
const WEBHOOK_SECRET = process.env.WEBHOOK_SECRET;
if (!WEBHOOK_SECRET) {
return next(
new Error("You must have a WEBHOOK_SECRET in your .env file.")
);
}
const payload = req.body;
const headers = req.headers;

const wh = new Webhook(WEBHOOK_SECRET);

let evt;

try {
  evt = wh.verify(payload, headers);
} catch (err) {
  console.log("Error verifying the webhook:", err.message);
  return res.status(400).json({
    success: false,
    message: "Webhook verification failed.",
  });
}

const eventType = evt.type;

if (eventType === "user.created") {
  const { id, email_addresses, first_name, last_name, image_url } =
    evt.data;

  let fullName = [first_name, last_name].filter(Boolean).join(" ").trim();

  if (!first_name && !last_name) {
    fullName = null;
  }

  const email = email_addresses[0].email_address;
  const imageUrl = image_url;
  const acceptTermsPrivacyAndAdult = true;

  try {
    await createUserAccountWithProfile(
      id,
      email,
      fullName,
      imageUrl,
      acceptTermsPrivacyAndAdult
    );

    console.log(
      `User with ID ${id} has been created and saved to the database.`
    );

    return res.status(200).json({
      success: true,
      message: "User created and saved to the database.",
    });
  } catch (error) {
    console.error("Error saving the user:", error);
    return res.status(500).json({
      success: false,
      message: "Internal server error while saving the user.",
    });
  }
} else if (eventType === "user.updated") {
  const {
    id,
    email_addresses,
    username,
    first_name,
    last_name,
    image_url,
  } = evt.data;

  let fullName = [first_name, last_name].filter(Boolean).join(" ").trim();

  if (!first_name && !last_name) {
    fullName = null;
  }

  const email = email_addresses[0].email_address;
  const imageUrl = image_url;
  const activated = true;

  try {
    await updateUserAccountWithProfile(
      id,
      email,
      username,
      fullName,
      imageUrl,
      activated
    );

    console.log(`User with ID ${id} has been updated in the database.`);

    return res.status(200).json({
      success: true,
      message: "User updated in the database.",
    });
  } catch (error) {
    console.error("Error updating the user:", error);
    return res.status(500).json({
      success: false,
      message: "Internal server error while updating the user.",
    });
  }
} else {
  console.log(`Unknown event type received: ${eventType}`);
  return res.status(400).json({
    success: false,
    message: `Unknown event type: ${eventType}`,
  });
}

}
);
export default router;
``
|Error message
Error verifying the webhook: Expected payload to be of type string or Buffer. Please refer to https://docs.svix.com/receiving/verifying-payloads/how for more information.

Hi @tasn , thanks for the reply. I'm using body-parser, but I still get this error message:
Error verifying the webhook: Expected payload to be of type string or Buffer. Please refer to https://docs.svix.com/receiving/verifying-payloads/how for more information.
import express from "express";
import { Webhook } from "svix";
import bodyParser from "body-parser";
import createUserAccountWithProfile from "../services/webhooks/createUserAccountWithProfile.js";
import updateUserAccountWithProfile from "../services/webhooks/updateUserAccountWithProfile.js";

const router = express.Router();

router.post(
  "/clerk",
  bodyParser.raw({ type: "application/json" }),
  async (req, res, next) => {
    const WEBHOOK_SECRET = process.env.WEBHOOK_SECRET;
    if (!WEBHOOK_SECRET) {
      return next(
        new Error("You must have a WEBHOOK_SECRET in your .env file.")
      );
    }

    const payload = req.body;
    const headers = req.headers;

    const wh = new Webhook(WEBHOOK_SECRET);

    let evt;

    try {
      evt = wh.verify(payload, headers);
    } catch (err) {
      console.log("Error verifying the webhook:", err.message);
      return res.status(400).json({
        success: false,
        message: "Webhook verification failed.",
      });
    }

    const eventType = evt.type;

    if (eventType === "user.created") {
      const { id, email_addresses, first_name, last_name, image_url } =
        evt.data;

      let fullName = [first_name, last_name].filter(Boolean).join(" ").trim();

      if (!first_name && !last_name) {
        fullName = null;
      }

      const email = email_addresses[0].email_address;
      const imageUrl = image_url;
      const acceptTermsPrivacyAndAdult = true;

      try {
        await createUserAccountWithProfile(
          id,
          email,
          fullName,
          imageUrl,
          acceptTermsPrivacyAndAdult
        );

        console.log(
          `User with ID ${id} has been created and saved to the database.`
        );

        return res.status(200).json({
          success: true,
          message: "User created and saved to the database.",
        });
      } catch (error) {
        console.error("Error saving the user:", error);
        return res.status(500).json({
          success: false,
          message: "Internal server error while saving the user.",
        });
      }
    } else if (eventType === "user.updated") {
      const {
        id,
        email_addresses,
        username,
        first_name,
        last_name,
        image_url,
      } = evt.data;

      let fullName = [first_name, last_name].filter(Boolean).join(" ").trim();

      if (!first_name && !last_name) {
        fullName = null;
      }

      const email = email_addresses[0].email_address;
      const imageUrl = image_url;
      const activated = true;

      try {
        await updateUserAccountWithProfile(
          id,
          email,
          username,
          fullName,
          imageUrl,
          activated
        );

        console.log(`User with ID ${id} has been updated in the database.`);

        return res.status(200).json({
          success: true,
          message: "User updated in the database.",
        });
      } catch (error) {
        console.error("Error updating the user:", error);
        return res.status(500).json({
          success: false,
          message: "Internal server error while updating the user.",
        });
      }
    } else {
      console.log(`Unknown event type received: ${eventType}`);
      return res.status(400).json({
        success: false,
        message: `Unknown event type: ${eventType}`,
      });
    }
  }
);

export default router;

You have to wrap the payload -- where you first instantiate it -- in a JSON.stringify(req.body)

@celestelayne, you shouldn't need to do that (and it'll probably break things down the line, even if make it work now).
@MichaelvdVeer, can you try asking the Express people? Seems to be an issue there?

@tasn  But is it true that, according to the Svix docs, unlike in Express, you do need to use JSON.stringify in Fastify?
I will ask Express if they have an answer about this issue.

@celestelayne
@tasn
With help from Express, I found the solution. In my index.js file, I had app.use(express.json()) declared before the webhook route, which was causing the body to be parsed as JSON before it reached the middleware that expects a raw Buffer.
I’ve now moved app.use(express.json()) to be placed after the webhook route, and that resolved the issue.
Here is my current code. Can you confirm if this is the right way?
import express from "express";
import { Webhook } from "svix";
import bodyParser from "body-parser";
import createUserAccountWithProfile from "../services/webhooks/createUserAccountWithProfile.js";
import updateUserAccountWithProfile from "../services/webhooks/updateUserAccountWithProfile.js";

const router = express.Router();

router.post(
  "/clerk",
  bodyParser.raw({ type: "application/json" }),
  async (req, res, next) => {
    const WEBHOOK_SECRET = process.env.WEBHOOK_SECRET;
    if (!WEBHOOK_SECRET) {
      return next(
        new Error("You must have a WEBHOOK_SECRET in your .env file.")
      );
    }

    const payload = req.body;
    const headers = req.headers;

    const svix_id = headers["svix-id"];
    const svix_timestamp = headers["svix-timestamp"];
    const svix_signature = headers["svix-signature"];

    if (!svix_id || !svix_timestamp || !svix_signature) {
      return res.status(400).json({
        success: false,
        message: "An error occurred -- no svix headers present.",
      });
    }

    const wh = new Webhook(WEBHOOK_SECRET);

    let evt;

    try {
      evt = wh.verify(payload, {
        "svix-id": svix_id,
        "svix-timestamp": svix_timestamp,
        "svix-signature": svix_signature,
      });
    } catch (err) {
      console.log("Error verifying the webhook:", err.message);
      return res.status(400).json({
        success: false,
        message: "Webhook verification failed.",
      });
    }

    const eventType = evt.type;

    if (eventType === "user.created") {
      const { id, email_addresses, first_name, last_name, image_url } =
        evt.data;

      let fullName = [first_name, last_name].filter(Boolean).join(" ").trim();

      if (!first_name && !last_name) {
        fullName = null;
      }

      const email = email_addresses[0].email_address;
      const imageUrl = image_url;
      const acceptTermsPrivacyAndAdult = true;

      try {
        await createUserAccountWithProfile(
          id,
          email,
          fullName,
          imageUrl,
          acceptTermsPrivacyAndAdult
        );

        console.log(
          `User with ID ${id} has been created and saved to the database.`
        );

        return res.status(200).json({
          success: true,
          message: "User created and saved to the database.",
        });
      } catch (error) {
        console.error("Error saving the user:", error);
        return res.status(500).json({
          success: false,
          message: "Internal server error while saving the user.",
        });
      }
    } else if (eventType === "user.updated") {
      const {
        id,
        email_addresses,
        username,
        first_name,
        last_name,
        image_url,
      } = evt.data;

      let fullName = [first_name, last_name].filter(Boolean).join(" ").trim();

      if (!first_name && !last_name) {
        fullName = null;
      }

      const email = email_addresses[0].email_address;
      const imageUrl = image_url;
      const activated = true;

      try {
        await updateUserAccountWithProfile(
          id,
          email,
          username,
          fullName,
          imageUrl,
          activated
        );

        console.log(`User with ID ${id} has been updated in the database.`);

        return res.status(200).json({
          success: true,
          message: "User updated in the database.",
        });
      } catch (error) {
        console.error("Error updating the user:", error);
        return res.status(500).json({
          success: false,
          message: "Internal server error while updating the user.",
        });
      }
    } else {
      console.log(`Unknown event type received: ${eventType}`);
      return res.status(400).json({
        success: false,
        message: `Unknown event type: ${eventType}`,
      });
    }
  }
);

export default router;

That looks good to me 👍
I'll close this but will make sure we also update our docs soon to make note of express.json().

I’ve now moved app.use(express.json()) to be placed after the webhook route, and that resolved the issue.

Oh, so it was essentially ignoring the body-parser because it was JSON parsing in the middleware?

@tasn But is it true that, according to the Svix docs, unlike in Express, you do need to use JSON.stringify in Fastify?

Nope, that's wrong! @svix-jplatte, mind removing the Fastify example and say that it was wrong?

Sure. As in, keep the section for it but replace its content (the code snippet) with a removal note?

I’ve now moved app.use(express.json()) to be placed after the webhook route, and that resolved the issue.

Oh, so it was essentially ignoring the body-parser because it was JSON parsing in the middleware?

@tasn I think the body will already be parsed as JSON before it hits the router's middleware due to express.json() and it won't be parsed again (i.e., it will remain a JavaScript object and won't revert back to a Buffer or other format).

The documentation has now been updated: https://docs.svix.com/receiving/verifying-payloads/how#nodejs-express


Is it possible to view the "previous" message?

Say a bot receives message A1. Is it possible to find the message directly before, some A0?
Example:
Joe: message1
Bob: message2
On "message2", find the message message1.
Is there a way to do that now, or should I just cache the previous message?

You can take the timestamp of the message and use it to call the getThreadHistory function with amount set to 1.  They're ordered from oldest to newest so the one you want should be the first one in the array.
var stopListening = api.listen(function(err, event) {
    if(event.type === "message") {
      api.getThreadHistory(event.threadID, 1, event.timestamp, function(err, data) {
        if (err) {
          throw err;
        }

        let previousMessage = data[0];
      });
    }
  });


Kali Linux Apple Silicon(ARM64) Issue

Hey,
I tried running Kali Linux Apple Silicon(ARM64) on UTM VM on my Macbook M1 Pro. The process I followed was pretty straightforward. Installed UTM and then installed image installer of Kali Linux in .iso format. After I ran UTM, chose 'Virtualize' -> Other -> selected the relevant boot iso image file -> set the memory at 2047 MB and selected 2 CPU cores -> 34 GB of drive size -> gave Downloads as my shared directory path -> then I double clicked on the VM in the sidebar -> clicked edit -> added a new 'serial' under Devices -> increased the font size to 20 -> saved!
Then I tried to run the VM, and as soon as the two windows pops up, both shows a UEFI Interactive Shell v2.2.
Now, I tried researching quite a lot on this issue. Sadly, I couldn't able to wrap my head around all the fancy terminologies. There was this one solution, where typing EXIT on the shell will take you to this window where you can try to boot from the file through 'Boot Maintenance Manager'. Did that also, but didn't work.
Another solution. which I remember, I tried changing the order of the boot which is shown in 'Boot Manager'. That too didn't work out. Now at last I decided to get help from the GitHub community. I am still an amateur at this, so kindly excuse me. I have attached some screenshots if that could be of any help in any way :)

You should probably run Kali Linux in Apple Virtualization instead of QEMU. I've had lots of issues with Kali in QEMU unfortunately.
No idea what you're doing wrong, though. Let's go through the process step by step.

Download the Kali Linux Apple Silicon installer image: https://cdimage.kali.org/kali-2023.1/kali-linux-2023.1-installer-arm64.iso
Open UTM, create new virtual machine
Select "Virtualize" and then "Linux"
check "Use Apple Virtualization"
Click "Browse" under "Boot ISO Image" and select the Kali Installer iso you downloaded earlier
Make hardware decisions, CPU memory storage sharing etc
Boot the VM and go through the install process

Insufficient data.
You MUST download the "Apple Silicon (ARM64)" installer iso which at the time of this writing is kali-linux-2023.1-installer-arm64.iso. Even if it's not from my link, please confirm that is the case. Or explain what "isn't working" when you tried my link.
You can try verifying the checksum of the iso if you think it's correct. There's no reason why the image format shouldn't be recognized. Please also provide the config.plist of the virtual machine so it can be checked (view the help for how to do that, I can't walk you through it).
More screenshots, video recording, anything - there's nothing for anyone to troubleshoot in that screenshot except an error that doesn't make sense.

Hi, have you have fixed the issue yet? I just encountered this issue today and I need help :)

@cyberRat86 this isn't something to be fixed in UTM as it currently stands. Kali boots fine in UTM in both AVD and QEMU modes. Generally this is going to be a config or disk image issue.
Provide steps to reproduce, exact error methods, troubleshooting steps, etc.

So UTM is useless to me now ??

So UTM is useless to me now ??

I think that depends entirely on your usecase. It sounds like all you're using UTM for is running Kali, and if that's not working, yes, it could be useless.
More broadly, showing up wondering if something is fixed without providing any additional context isn't helpful, or likely to get support for troubleshooting your issue.
If you're having trouble running Kali in UTM, tell us more. What kind of virtualization? What ISO image? What options did you set? What error message did you receive? Be specific. Be precise. Have you gone through the steps I documented above? What was the result?

okay I fixed it lol
The way you do not get the UEIF thing is, when setting up Kali on the UTM, there is a part that says BOOT ISO IMAGE, it comes out directly after clicking virtualize. When you put browse next to "boot iso image, put your desktop, whatever that is named. My desktop is called desktop. And then you do the rest of the settings and bam, now it works !!!

okay I fixed it lol
The way you do not get the UEIF thing is, when setting up Kali on the UTM, there is a part that says BOOT ISO IMAGE, it comes out directly after clicking virtualize. When you put browse next to "boot iso image, put your desktop, whatever that is named. My desktop is called desktop. And then you do the rest of the settings and bam, now it works !!!

I didn’t understand can you please explain

I had the same behavior. After a long search I found the solution. My guess is that you created a VM with the "Virtualize" option in the Startup section and probably saw the following warning with the message "The selected boot image contains the word 'arm64' but the guest architecture is 'x86_64'. Please make sure you have selected an image that is compatible with 'amd64'.", but ignored it:

... as a result, you have a stopped terminal, as shown above.
I recommend the next steps:

Open UTM and click the "+" button to create a new VM.
Select "Virtualize" if you have an ARM-based Mac (such as those with Apple M1 or M2 chips), or "Emulate" if you have an Intel-based Mac and want to emulate ARM.
Proceed with the next steps as shown on https://youtu.be/9zdjQ9w_v_4?t=281

https://www.youtube.com/watch?v=U09soewiu18 See this vdo if you're still having trouble installing kali linux on mac. I'm having Apple m1 and it worked for me but remember set cpu core as 1.


[FLINK-15241] Revert the unexpected change of the configuration for M…

…esos CPU cores
What is the purpose of the change
This PR Revert the unexpected change of the configuration for Mesos CPU cores. Now, if not explicitly set "mesos.resourcemanager.tasks.cpus", the cpu cores will be setted to the "taskmanager.numberOfTaskSlots"
Brief change log
Change the condition of using fallback cpu configuration in TaskExecutorResourceUtils#getCpuCores to "fallback > 0.0"
Verifying this change
This change added tests and can be verified as follows:

MesosTaskManagerParametersTest#testConfigNoCpuCores

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no

cc @tillrohrmann

Thanks for the review @tillrohrmann . Comments addressed.

@flinkbot run travis


Why using slice.call(obj) when _.isArray(obj) is true?

In _.toArray:
if (_.isArray(obj)) return slice.call(obj);

Why using slice.call(obj) when _.isArray(obj) is true?
Why not just return obj ? I don't understand, please tell me :)

It's to create a new instance of an array, so modifications do the original do not affect the returned value.

Oh, I get it. Thank you for your response : )


Follow redirect on first health check to backend

Follow 301 redirect on first health check to the backend to avoid sending requests using the incorrect protocol (http instead of https)
Fixes #523

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

13 of 23 (56.52%)  changed or added relevant lines in 5 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 81.928%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

Shared/Exceptions/BackendException.cs
0
3
0.0%

Shared/Networking/PreflightHttpClient.cs
4
11
36.36%

Files with Coverage Reduction
New Missed Lines
%

Exceptions/BackendException.cs
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
15450

Relevant Lines:
18858

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

20 of 23 (86.96%)  changed or added relevant lines in 5 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.08%) to 93.257%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

Shared/Exceptions/BackendException.cs
0
3
0.0%

Files with Coverage Reduction
New Missed Lines
%

Exceptions/BackendException.cs
3
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.08%

Covered Lines:
17440

Relevant Lines:
18701

💛  - Coveralls


inversion problem

hello my friend, I have some problem
in my case I have to use pywt.downcoef, butI don't know what is the inversion code for reconstructing back my signal, I mean how can I reconstruct my signal with only using the approximation coefficients through your package? does your package have any inverse function for that? I mean pywt.idowncoef or something like that?
sincerely

I mean how can I reconstruct my signal with only using the approximation coefficients through your package? does your package have any inverse function for that? I mean pywt.idowncoef or something like that?

I guess pywt.upcoef (docs) is what you're looking for.

Question was answered, closing this issue.


dune-release: [ERROR] Could not retrieve release ID from response, unexpected Github API error: "Not Found"

I'm receiving the titular error on version 1.4.0 and
uname -a
Linux comp 5.4.89-1-MANJARO #1 SMP PREEMPT Tue Jan 12 23:39:44 UTC 2021 x86_64 GNU/Linux

[sf@comp emojitsu]$ dune-release publish -vv
dune-release: [INFO] dune-release 1.4.0 running
dune-release: [INFO] Parsing opam file emojitsu.opam
[-] Skipping documentation publication for package emojitsu: no doc field in emojitsu.opam
[-] Publishing distribution
dune-release: [EXEC:115057] ['git' 'rev-parse' '--git-dir']
dune-release: [EXEC:115058] ['git' '--git-dir' '.git' '--work-tree' './'
                             'describe' '--always' 'HEAD']
[-] Publishing to github
dune-release: [EXEC:115059] ['git' 'rev-parse' '--git-dir']
dune-release: [EXEC:115060] ['git' '--git-dir' '.git' '--work-tree' './'
                             'describe' '--always' 'HEAD']
dune-release: [EXEC:115061] ['git' 'rev-parse' '--git-dir']
dune-release: [EXEC:115062] ['git' '--git-dir' '.git' '--work-tree' './'
                             'describe' '--always' 'HEAD']
dune-release: [EXEC:115063] ['git' 'rev-parse' '--git-dir']
dune-release: [EXEC:115064] ['git' '--git-dir' '.git' 'rev-parse' '--verify'
                             '0.0.2']
dune-release: [EXEC:115065] ['git' 'rev-parse' '--git-dir']
dune-release: [EXEC:115066] ['git' 'rev-parse' '--git-dir']
dune-release: [EXEC:115067] ['git' '--git-dir' '.git' '--work-tree' './'
                             'describe' '--always' 'HEAD']
dune-release: [EXEC:115068] ['git' '--git-dir' '.git' 'rev-parse' '--verify'
                             '0.0.2']
[?] Push tag 0.0.2 to git@github.com:shonfeder/emojitsu.git? [Y/n]
Y
[-] Pushing tag 0.0.2 to git@github.com:shonfeder/emojitsu.git
dune-release: [EXEC:115069] ['git' '--git-dir' '.git' 'push' '--force'
                             'git@github.com:shonfeder/emojitsu.git' '0.0.2']
[?] Create release 0.0.2 on git@github.com:shonfeder/emojitsu.git? [Y/n]
Y
[-] Creating release 0.0.2 on git@github.com:shonfeder/emojitsu.git via github's API
dune-release: [ERROR] Could not retrieve release ID from response, unexpected Github API error: "Not Found"

I've also tried pinning master, and am getting the same result, but with a more verbose logging:
[sf@comp emojitsu]$ dune-release publish -vv
dune-release: [INFO] dune-release 1.4.0-140-g5384dff2f7 running
dune-release: [INFO] Parsing opam file emojitsu.opam
[-] Skipping documentation publication for package emojitsu: no doc field in emojitsu.opam
[-] Publishing distribution
[-] Publishing to github
dune-release: [EXEC:116031] ['git' 'rev-parse' '--git-dir']
dune-release: [EXEC:116032] ['git' '--git-dir' '.git' '--work-tree' './'
                             'describe' '--always' 'HEAD']
dune-release: [EXEC:116033] ['git' 'rev-parse' '--git-dir']
dune-release: [EXEC:116034] ['git' '--git-dir' '.git' 'rev-parse' '--verify'
                             '0.0.2']
dune-release: [EXEC:116035] ['git' 'rev-parse' '--git-dir']
dune-release: [EXEC:116036] ['git' '--git-dir' '.git' 'rev-parse' '--verify'
                             '0.0.2']
dune-release: [EXEC:116037] ['git' '--git-dir' '.git' 'rev-parse' '--verify'
                             '0.0.2^0']
dune-release: [EXEC:116038] ['git' '--git-dir' '.git' 'ls-remote' '--quiet'
                             '--tags'
                             'https://github.com/shonfeder/emojitsu.git'
                             '0.0.2']
dune-release: [EXEC:116042] ['git' '--git-dir' '.git' 'rev-parse' '--verify'
                             'ee7f8e78fc320cb2142e6cd91a3a80150da47268^0']
[-] The tag 0.0.2 is present and uptodate on the remote: skipping the tag push
[?] Create release 0.0.2 on https://github.com/shonfeder/emojitsu.git? [Y/n]
Y
[-] Creating release 0.0.2 on https://github.com/shonfeder/emojitsu.git via github's API
dune-release: [DEBUG] [curl] executing request: { meth=POST;
                      url="https://api.github.com/repos/shonfeder/emojitsu/releases";
                      headers=""; body="" }
dune-release: [DEBUG] [curl] with args: --user
                      shonfeder:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

                      --location --silent --show-error --config -
                      --dump-header - --data
                      {"tag_name":"0.0.2","name":"0.0.2","body":"CHANGES:\n\n- Reduce dependency footprint\n"}
dune-release: [DEBUG] [curl] response received: {code=404;
                      headers=x-github-request-id: 8518:0AC4:874F6:17E0DB:601DBCCF

x-github-request-id: 8518:0AC4:874F6:17E0DB:601DBCCF

vary: Accept-Encoding, Accept, X-Requested-With

vary: Accept-Encoding, Accept, X-Requested-With

content-security-policy: default-src 'none'

content-security-policy: default-src 'none'

referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin

referrer-policy: origin-when-cross-origin, strict-origin-when-cross-origin

x-xss-protection: 1; mode=block

x-xss-protection: 1; mode=block

x-content-type-options: nosniff

x-content-type-options: nosniff

x-frame-options: deny

x-frame-options: deny

strict-transport-security: max-age=31536000; includeSubdomains; preload

strict-transport-security: max-age=31536000; includeSubdomains; preload

access-control-allow-origin: *

access-control-allow-origin: *

access-control-expose-headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset

access-control-expose-headers: ETag, Link, Location, Retry-After, X-GitHub-OTP, X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Used, X-RateLimit-Reset, X-OAuth-Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval, X-GitHub-Media-Type, Deprecation, Sunset

x-ratelimit-used: 6

x-ratelimit-used: 6

x-ratelimit-reset:<PHONE_NUMBER>

x-ratelimit-reset:<PHONE_NUMBER>

x-ratelimit-remaining: 54

x-ratelimit-remaining: 54

x-ratelimit-limit: 60

x-ratelimit-limit: 60

x-github-media-type: github.v3; format=json

x-github-media-type: github.v3; format=json

content-length: 117

content-length: 117

content-type: application/json; charset=utf-8

content-type: application/json; charset=utf-8

date: Fri, 05 Feb 2021 21:46:55 GMT

date: Fri, 05 Feb 2021 21:46:55 GMT

server: GitHub.com

HTTP/2 404
server: GitHub.com
;
body="
{
  "message": "Not Found",
  "documentation_url": "https://docs.github.com/rest/reference/repos#create-a-release"
}
"}
dune-release: [ERROR] Github API error:
    Could not retrieve release ID from response
    Github API returned: "Not Found"
    See the documentation "https://docs.github.com/rest/reference/repos#create-a-release" that might help you resolve this error.

I tried with the same token using github's hub CLI, and it worked fine, so it does seem to be an issue with the request that's being sent to the GitHub API.

This is highly disturbing since the error suggests that the URL to the API endpoint is wrong but I just tested it myself and it seems to be valid as I'm able to gather the list of releases from it. According to the logs above, the tag was indeed there so
Indeed if the token was wrong you'd get a different error so something else must be going on here but I'm struggling to see what that could be. Were you able to reproduce this behaviour multiple times? Are you still running into this error if you try releasing with dune-release on that repo or on another one?

I'm getting the same error. Downgrading to 1.3.3 I get this extra message (not that the release was created):
{
                        "url":
                      "https://api.github.com/repos/LPCIC/elpi/releases/37804553",
                        "assets_url":
                      "https://api.github.com/repos/LPCIC/elpi/releases/37804553/assets",
                        "upload_url":
                      "https://uploads.github.com/repos/LPCIC/elpi/releases/37804553/assets{?name,label}",
                        "html_url":
                      "https://github.com/LPCIC/elpi/releases/tag/v1.13.0",
                        "id": 37804553,

The ID is there.

Hi, do you also get the same issue with the master version?

Hi, do you also get the same issue with the master version?

Hi :) Yes, I am getting the same error on master:
$ dune-release --version
1.4.0-140-g5384dff2f7

I just confirmed it's still happening.

Were you able to reproduce this behaviour multiple times? Are you still running into this error if you try releasing with dune-release on that repo or on another one?

@NathanReb, indeed, this is happening every single time. Just reconfirmed now. All the releases on this repo are the result of using github's hub CLI tool.
I just confirmed this is happening on another repo as well, on a freshly pinned reinstall of master.

I don't have any 404 with this url, I know you've tried the github cli with the same token, but maybe the token file that is used by dune-release is ill-formatted, not so long ago I had a similar issue because there was no linebreak after the token in that file, maybe you have the same issue.

Many thanks for the tip @gpetiot!
Solution:
I deleted the githuhub.token file and reran the publish command. dune-release then prompted me to enter my token. Apparently this fixed whatever the error had been in the formatting (I tried adding a newline manually first, but that didn't fix it), and the release went through successfully! :tada:
It would be helpful to add some validation to the token formatting, if that's at all possible. But I think I wouldn't have hit this in the first place if the features proposed in #339 where in place to fix expired credentials, so I'll close this under the assumption those additions will address the root cause (human error ;)).

Indeed the 404 must be a security feature so that you can't use the API to discover private repositories to which you don't have access to, I'm just a bit surprised it showed up for a public repo here.
Other users ran into this issue where a previously valid token wouldn't work anymore and where refreshing it in dune-release would solve the issue. It might be the case that we broke the token de.serialization.

I did quite struggle with this too, in the end only a new token + using master + entering the token via the console did work [all other choices resulted in strange errors]
The bizarre thing is that I did print the curl call that dune-release was doing, and when I did run it manually the release was properly created.

OK! It sounds like something might be up then, worthy of keeping this issue open until we can resolve the root cause.


Update pyproject.toml in pynxtools for nyaml2nxd tool from NeXus definition submodule

nyaml2nxdl tool should be installed from NeXus definition submodule once the PR1303 will be accepted by NIAC.

Closing this, because nyaml2nxdl is not directly needed as a dependency for pynxtools


python311Packages.types-awscrt: 0.19.3 -> 0.19.6

Changelog: https://github.com/youtype/types-awscrt/releases/tag/0.19.6
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 263915 run on x86_64-linux 1

16 packages built:

python310Packages.boto3-stubs
python310Packages.boto3-stubs.dist
python310Packages.botocore-stubs
python310Packages.botocore-stubs.dist
python310Packages.types-aiobotocore
python310Packages.types-aiobotocore.dist
python310Packages.types-awscrt
python310Packages.types-awscrt.dist
python311Packages.boto3-stubs
python311Packages.boto3-stubs.dist
python311Packages.botocore-stubs
python311Packages.botocore-stubs.dist
python311Packages.types-aiobotocore
python311Packages.types-aiobotocore.dist
python311Packages.types-awscrt
python311Packages.types-awscrt.dist


Switch from procyon to cfr

https://www.benf.org/other/cfr/

any argument or justification why? Procyon is actively developed, but if you want to allow multiple backends maybe write a pull request?

any argument or justification why?

cfr can decompile the things procyon cannot

if you want to allow multiple backends

we definitely want


Withdraw art

Description
Add and Withdraw Screen (aka FiatExchange) was missing artwork, so that was added.
Tested

Tested on multiple phones, 2 of their screenshots attached:

Related issues

Fixes #4921

Backwards compatibility
n/a

@medhak1 I think the art needs to be added to the private visual asset repo. @jeanregisser can confirm.

Got it, just added a pink placeholder image to the monorepo. Should be fine now!

Hi @tarikbellamine  i have verified task using Test flight build v1.2.0 (24) on Test flight build 1.2.0(24)
Test scenarios:

Verify user is able to see the Add & Withdraw button when tapping on hamburger menu
Verify user is able to see the artwork on Add & withdraw page

Please let me know if any thing else i need to verify for this task.
Thanks !

Hi @tarikbellamine i have verified task using  Android internal build 1.2.0(1004294313) and found the following
Device: Samsung Galaxy A70(9.0)
Test scenarios:

Verify user is able to see the Add & Withdraw button when tapping on hamburger menu
Verify user is able to see the artwork on Add & withdraw page

Please let me know if any thing else i need to verify for this task.
Thanks !