Resource 'Microsoft.Authorization/policyDefinitions' output not valid on Initiative resource

Bicep version
Bicep CLI version 0.3.1 (d0f5c9b164)
Describe the bug
Re-using the ID output of 'Microsoft.Authorization/policyDefinitions@2020-09-01' resource on 'Microsoft.Authorization/policySetDefinitions@2020-09-01'  is coming out with an error.
Deployment failed. Correlation ID: fc7c1a9b-4aa2-4e56-b285-7fdf91082a8a. {
  "error": {
    "code": "InvalidCreatePolicySetDefinitionRequest",
    "message": "The policy set definition 'generalInitiative' request is invalid. Referenced policy definitions must be of type 'Microsoft.Authorization/policyDefinitions'."
  }
}

To Reproduce
Deploy using the following code.
targetScope = 'managementGroup'

resource policy 'Microsoft.Authorization/policyDefinitions@2020-09-01' = {
  name: 'allowedResourceType'
  properties: {
    displayName: 'Allowed resource type'
    policyType: 'Custom'
    mode: 'All'
    description: 'This policy enables you to specify the resource types that your organization can deploy.'
    metadata: {
      category: 'custom'
      source: 'bicep'
      version: '1.0.0'
    }
    parameters: {
      listOfResourceTypesAllowed: {
        type: 'Array'
        metadata: {
          displayName: 'Allowed resource types'
          description: 'The list of resource types that can be deployed.'
          strongType: 'resourceTypes'
        }
        defaultValue: [
             Standard_B1ls
             Standard_B1ms
             Standard_B1s
        ]
      }
    }
    policyRule: {
      if: {
        not: {
          field: 'type'
          in: '[parameters(\'listOfResourceTypesAllowed\')]'
        }
      }
      then: {
        effect: 'audit'
      }
    }
  }
}

resource ini_GeneralGovernance 'Microsoft.Authorization/policySetDefinitions@2020-09-01' = {
  name: 'generalInitiative'
  properties: {
    policyType: 'Custom'
    displayName: 'General Initiative'
    description: 'General Governance via bicep'
    metadata: {
      category: 'custom'
      source: 'bicep'
      version: '1.0.0'
    }
    parameters: {}
    policyDefinitions: [
      {
        policyDefinitionId: policy.id
      }
    ]
  }
}

Additional context
From this URL the 'policyDefinitionId:' object param just needs to be a string, and if hardcoded it works without the error.

I tried to reproduce this error but couldn't exactly as this param is missing from above snippet:
policiesParamsObject.allowedLocations

Just edit the original post and set some defaults to that param

@anthony-c-martin - it looks like we are not generating the policy Id correctly.  This is because we don't have a managementGroup() function to properly emit this - is that right? I think we already have an issue for this but am having trouble finding it.

@anthony-c-martin - it looks like we are not generating the policy Id correctly. This is because we don't have a managementGroup() function to properly emit this - is that right? I think we already have an issue for this but am having trouble finding it.

Yes, exactly. #1228 is the original issue.

Closing as dup of #1228


NPM reports hundreds of vulnerabilities

Summary
NPM reports vulnerabilities regarding the packages installed:
"found 470 vulnerabilities (245 low, 203 moderate, 21 high, 1 critical)"
Steps to Reproduce

Clone project
Run npm install

Additional info

Postleaf version: 1.0.0-beta.1
Node version: 8.15.1
Operating system: Ubuntu 18.04.2

Note: This issue tracker is ONLY for bug reports and feature requests. If this is a personal support issue, please visit postleaf.org/support.

I'm aware. Now that Node 10 LTS is out I need to run updates and get it running on that release (a few users mentioned trouble with Node 10).
I'm extremely busy with the upcoming Surreal CMS release right now so if anyone wants to work on this let me know!

I am already working on it till date i update the sequlize classes, alot of
updates are in queue, i will generate a PR soon for postleaf.
On Wed, Mar 6, 2019, 9:26 PM Cory LaViska<EMAIL_ADDRESS>wrote:

I'm aware. Now that Node 10 LTS is out I need to run updates and get it
running on that release (a few users mentioned trouble with Node 10).
I'm extremely busy with the upcoming Surreal CMS
https://www.surrealcms.com/ release right now so if anyone wants to
work on this let me know!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Postleaf/postleaf/issues/108#issuecomment-470162415,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC0DcDS-qWzfmDwp5GvJWpBf3lq9CrYHks5vT-U3gaJpZM4bgV_2
.

Beautiful! Are you using Node 10 LTS?

Yes.
On Wed, Mar 6, 2019, 9:45 PM Cory LaViska<EMAIL_ADDRESS>wrote:

Beautiful! Are you using Node 10 LTS?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Postleaf/postleaf/issues/108#issuecomment-470170278,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC0DcDIK7DAAAwcBx0RnLCQvH5VCKFHsks5vT-mOgaJpZM4bgV_2
.

@post2seth did you get this working?


.hasClass() error message is confusing when it fails

Say you have an element like <div id="fun" class="thing1 thing2 thing3">, and your testing code is written like assert.dom('#fun').hasClass('thing1').
IF it does not find a class, it fails with "Expected: thing1", "Result: thing8 thing2 thing3".
... I guess this is not a very important issue.

@cepm-nate the assertion message shows you what you expected to find and what classes are really on the element. I don't think there is much we can do to make this less confusing. If we removed the "Result: ..." part the assertion would be much less helpful if it failed.


fix: stop autocmds from duplicating on each SSR open

SSR creates instances when Ui:Open is executed but the autocmds are not treated like an instance they are sharing the same autocmds, these autocmds however are being duplicated on each run of Ui:Open causing bad side effects like data invalidation.
On instance creation a unique augroup is created and assigned and only one set of autocmds are allowed to exist each instance, when that instance of SSR is closed the assigned autocmds and augroup is removed for that instance only.

autocmd group is also added in #31


discover and tests

To be able to get feedback on this, I submit this pull request before the "added Attribute" pull request have been merged, so the contents of that pull request is also present here for now.
This adds discover capability and attribute support to existing interfaces and base classes. The contents of the "added Attribute" pull request is included here.
It's a rather large pull request, but I think it might be hard to find any suitable fragments to break it up into.
Signed-off-by: Daniel Persson<EMAIL_ADDRESS>

When implementing Discover, incl. full attribute support, there are several things to consider:

On what levels should the attributes be stored by default (in ObjectEnabler, BaseInstanceEnabler etc.)
Would a LwM2mResourceEnabler interface with a default implementation be reasonable?
How should we make the result of the full attribute chain (object / instance/ resource) available to the LwM2mInstanceEnabler implementation, for instance to implement a polling observe pattern on the client where the correct pmin and pmax needs to be known.

Regarding the fact that you would prefer DiscoverResponse discoverInstance(..., I agree. But how should we solve the fact that both a Discover on object level and instance level should return the same links for any instance, only without attributes if it's performed on the object level?
But having the ObjectEnabler own the entire attribute hierarchy, as I interpreted one of your comments, seems counter-intuitive to me. What is wrong with letting each instance own its own attributes, especially since the same resource id in two different instances could have different attribute values?
I thought about opening an issue where this could be discussed, but I'll keep this here for now.

Here a little description about the design :
LwM2mObjectEnabler interface is the contract. This is what must be implemented to add a new LWM2M object.
BaseObjectEnabler is an abstract class which could be used as base for implementing a new LWM2M object.
ObjectEnabler is an object implementation which delegate the "real" logic to LwM2mInstanceEnabler.

But having the ObjectEnabler own the entire attribute hierarchy, as I interpreted one of your comments, seems counter-intuitive to me.

I even think about putting the hierarchy at BaseObjectEnabler level. This advantage is to provide those features even for users which does not use ObjectEnabler and LwM2MInstanceEnabler. I do not go as deeper as you and so I could be wrong. But I feel this is possible because, we doesn't not need any information from LwM2MInstanceEnabler except available instances and resources supported (for this one we should add a kind of availableResource(instanceID) to the LwM2mObjectEnabler). Once we now that, we can store all the Attributes data at BaseObjectEnabler.
I feel that observe part could be implement at this level too playing around notifySender.
The risk I see about this solution.

maybe the BaseObjectEnabler would become too large. (delegate the code to others classes, like AttributeTree could help)
I'm not sure of this but maybe keep synchronized AttributeTree with the real resource tree could be a problem(on deletion or addition).

Regarding the fact that you would prefer DiscoverResponse discoverInstance(..., I agree. But how should we solve the fact that both a Discover on object level and instance level should return the same links for any instance, only without attributes if it's performed on the object level?

I can not see the issue. Exactly the same way you do now ? get the link and remove attribute is needed. (I feel with the solution exposed above you don't need to do this at all)

I've pushed updates now that fixes some comments you had, including letting the LwM2mInstanceEnabler.discoverInstance and discoverResource return DiscoverResponse instead.
I'll have to think about how to move forward with this. We're in big need of being able to simulate Discover,  but being able to write attributes are just a minor part of that. I'm currently using the ObjectEnabler as a base class for our simulator objects, but that may have been a mistake since that also makes me dependent on LwM2mInstanceEnabler. It might be better for me to roll my own interfaces beyond LwM2mObjectEnabler, but I haven't realised that until just now.
And since I'm pausing this work, I think the "added Attribute" could be merged?

Yes, that integration sequence could make sense. I'll see if I can get time in the near future to work more on it.

I will probably not be able to work on this for some more months (vacation etc.), so you can decide whether you would like to merge the AttributeSet PR or not, and then close this. I see it as a fairly solid implementation of the LwM2m spec on attributes, so if there isn't any major changes planned for attributes in the next LwM2m releases, this could have a value even though it's not used anywhere yet.
We're still using read requests on individual resources as a method of discover, since we don't want to add real discover in our backend until we have full simulation support for it. For now, this works fairly well, which is why this haven't been prioritized the last few months.
It was a while since I worked actively on this, but I'll try to summarize my concerns for the future:

Link not being allowed to reference AttributeSet? I'm having a very hard time understanding this reasoning. It could be a very convenient first use case that is basically implemented already.
No mocking framework allowed in the tests? This really made me confused, it seems like an extremely uncontroversial addition to me.
I've had a very clear and rather advanced use case for the client parts of Leshan (our simulator), but making progress in the contributions feels hard and time-consuming. This might very well be me not being used to participating in open source projects, but if it's new functionality that's being added to fulfill the object specification (attribute handling and before also with the object versioning), it feels a bit discouraging to end up in implementation detail discussions like whether to put the attribute support in BaseObjectEnabler or ObjectEnabler. This can quite easily be corrected later, if we make a suboptimal decision in the first implementation.

I hope that we will find time in our project to prioritize Discover again later, then I will revisit this and try to break it up into smaller PRs.

Ok, thx a lot for @danielhqv for the clarification.
I still think that the minimum set of feature to start to integrate this in master is :

add attributeSet
use attributeSet for writeAttributeRequests
remove deprecate ObserveSpec
If I find time, I will try to take your work and integrate at least this part in master.

making progress in the contributions feels hard and time-consuming

I try to give valuable feedback as soon as possible, this is time-consuming to me too.
It seems you still feel that sometime my remarks are nitpicking, I'm sorry about that. I just share my ideas, It seems better to me than just integrate your works then rewrite it.
Anyway thx a lot for all your contributions. See you in few months ;)

I finally find time to integrate a part of your work #533.
So to sump-up :

add attributeSet  => #533
use attributeSet for writeAttributeRequests. => #533
remove deprecate ObserveSpec => #533
add support of writte attribute at client side => partially done in this PR but not yet integrated
enhance support of discover to return attributes. => partially done in this PR but not yet integrated

About discover, it was fixed to support optional resource but still not support attributes #532.

the server how to received the client sent data

the server how to received the client sent data


Forge install hangs when installing non existing repositories

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
No response
What command(s) is the bug in?
No response
Operating System
No response
Describe the bug
running forge install solmate causes forge to hang instead of producing an exception, as forge is trying to install  https://github.com/solmate. - forge  install Rari-Capital/solmate correctly resolves to the git repo.

I cannot reproduce this locally, just ran forge install asdf and it completed, although it did say "Installed asdf" instead of producing an error.

Was this fixed in #719?


Localized 404 pages

Hi, any recommendations on how to implement custom localized 404 pages?
I have custom localized 404 pages defined in my CMS.
It looks like next app router expects the not-found page to be in the root app/ directory, which complicates things a bit.
One hacky way I found:

create basic layout.tsx in root app/ dir
create the custom 404 page in app/[locale]/not-found/page.tsx
create app/not-found.tsx which reads the locale from x-next-i18n-router-locale header, and redirects to the correct localized 404 page.

But perhaps there is a smarter way. Could be nice to include in one of the examples maybe?

Sorry didn't see this: https://github.com/i18nexus/next-i18n-router/issues/36#issuecomment-1821887026
I guess this means we need to have to have a duplicate layout.tsx in the root app/ as well?

@i18nexus  Do you know of any public repos implementing this, from which I could take example?

Nevermind, got it working now finally 😅


Join coordinate data to master station names

Using our updated station coordinates, join these to the pandas dataframe for the parsed .msn file. Remove any stations not matched.

Closed by #314


Error 500 on the logs page.

Description
Hi! Absolutely love the project! Just something I stumbled upon when using the docker on unraid 6.9.2
When you go in settings > logs, you are greeted with a 500
Version
1.0.2 stable
Steps to Reproduce
Head into the logs page.
Expected Behavior
Please provide a clear and concise description of what you expected to happen.
Screenshots
If applicable, please provide screenshots depicting the problem.
Device

Platform: Unraid 6.9.2
Device: Macbook Pro
OS: MacOS
Browser: Chrome

Additional Context
You can find the error in the docker logs. There seems to be a mismatch in the naming of the log file. The page itself is looking for /logs/jellyseerr.log but when they are laid out, they are actually created as Jellyseerr.log
The naming convention for Overseerr was to not use any capitalization for the log files.
https://github.com/Fallenbagel/jellyseerr/blob/57cc48a699a595bb06cb98595fceca5202788031/server/logger.ts

For now you coukd use develop tag. We will soon be merging that with main branch and this issue will not be present there


ExceptionHandling for common input related cases.

An example of this would be when the user is not inputting the number of neurons on the output layer to hidden_layers() dense layer generator.

ValueError: Could not interpret optimizer identifier: <class 'keras.optimizers.Adam'> comes when no lr values are included in the scan, and where optimizer=optimizer['params] need to actually have the () behind it.

raise IndexError("single positional indexer is out-of-bounds") IndexError: single positional indexer is out-of-bounds > in the case when the grid downsampling reduces the sample to < 1 permutations

axis=self.obj._get_axis_name(axis))) KeyError: 'the label [val_acc] is not in the [index]' > reduction method will reduce to less than 1 in the first round (?!)

KeyError when one of the required parameters (like dropout) is not a single value of 0 in the dictionary.

The general case where something is wrong with the model that is being inputted (comes out as Unbound...)

It seems that first it is more important that nothing is swallowed (like now with _hr_out in scan()) so that the actual issues (like user model not compiling) are clear.

I think this is better closed for now. Things work well the way it is, and there are very few of these error messages in regular use.


bosh-cli should work with older directors that care that packages key is present

otherwise director raises undefined method each' for nil:NilClass`
This occurred today when building a release that had no packages.
--- a/release/manifest/release.go
+++ b/release/manifest/release.go
@@ -7,8 +7,8 @@ type Manifest struct {
  CommitHash         string `yaml:"commit_hash"`
  UncommittedChanges bool   `yaml:"uncommitted_changes"`

- Jobs         []JobRef             `yaml:"jobs,omitempty"`
- Packages     []PackageRef         `yaml:"packages,omitempty"`
+ Jobs         []JobRef             `yaml:"jobs"`
+ Packages     []PackageRef         `yaml:"packages"`
  CompiledPkgs []CompiledPackageRef `yaml:"compiled_packages,omitempty"`
  License      *LicenseRef          `yaml:"license,omitempty"`
 }

I'm going to close this due to inactivity. Ideally current bosh directors will be up to date, so this is no longer an issue. Feel free to reopen if you have further questions.


extrude method to extrude geometries in the Z direction

Ideally this would work for points, linestrings, and polygons, but right now we can restrict it to only working on polygons.
The idea would be to take a polygon, mesh it, and "extrude" it in the z-axis to create a 3d mesh.  We would also need a triangulation interface first, but that seems fairly easy to do, and there are plenty of packages which would do it.
This would make creating plots like the one below easier (yes it is bad practice, but it's cool)

Is there any reason we should not do this?
(In all seriousness, this could be useful for 3D hexbin plots as well)

Does it need a mesh? Not just 3d polygons?

Yeah, the sides have to be meshes and triangulation happens in ℝ² unless you do it yourself


Jackson Vera Pineda C212

Scheduler Project, Operative System 2023: SJF, STCF and Round Robin.

✅ - SJF
✅ - STCF
✅ - RR
❌ - MLFQ
Nota: 3


[Snyk] Upgrade @mui/material from 5.14.10 to 5.14.14

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @mui/material from 5.14.10 to 5.14.14.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 4 versions ahead of your current version.
The recommended version was released 22 days ago, on 2023-10-17.

Release notes

Package name: @mui/material

5.14.14 - 2023-10-17 Read more

5.14.13 - 2023-10-10 Read more

5.14.12 - 2023-10-04 Read more

5.14.11 - 2023-09-26 Read more

5.14.10 - 2023-09-18Sep 18, 2023
A big thanks to the 16 contributors who made this release possible. This release was mostly about 🐛 bug fixes and 📚 documentation improvements.
<EMAIL_ADDRESS>
[Chip] Add cursor CSS property reset (#38984) @ DiegoAndai

<EMAIL_ADDRESS>
[utils] Move @ types/prop-types back to dependencies (#39030) @ Methuselah96

<EMAIL_ADDRESS>
[NumberInput][base-ui] Warn when changing control mode with useControlled (#38757) @ sai6855
[Select][base-ui] Fix Select button layout shift, add placeholder prop (#38796) @ mj12albert
[useList][base-ui] Accept arbitrary external props and forward to root (#38848) @ mj12albert
[Autocomplete][base-ui] Added ref to getInputProps return value (#38919) @ DarhkVoyd

<EMAIL_ADDRESS>
[AccordionGroup][joy-ui] Fix console warning when using custom color (#38950) @ sai6855
[GlobalStyles][joy-ui] Ensure compatibility with RSC (#38955) @ mateuseap

Docs

[docs][base] Add Tailwind CSS + plain CSS demo on the NumberInput page (#38928) @ alisasanib
[docs][Dialog] Add non-modal dialog docs & demo (#38684) @ mnajdova
[docs] Fix number input wrong demo @ oliviertassinari
[docs] Exclude joy-ui LinearProgressCountup from visual regression (#38969) @ siriwatknp
[docs][joy-ui] Revise the Overview page (#38842) @ danilo-leal
[docs][material-ui][Pagination] Add TablePagination to the API components list (#38486) @ MonstraG

Core

[core] Add more context about useEventCallback @ oliviertassinari
[core] Allow deeper import of @ mui/utils (#38806) @ oliviertassinari
[core] Remove react-dom from @ mui/utils peerDependencies (#38974) @ michaldudak
[core] Remove react from styled-engine dependencies (#38971) @ michaldudak
[core] Fix image loading bug on Safari @ oliviertassinari
[core] Fix bundle size upload to S3 job (#38956) @ Janpot
[core] Move eslint to peer dependencies of eslint-plugin-material-ui (#39033) @ michaldudak
[docs-infra] Display markdown lists correctly in docs for props description (#38973) @ ZeeshanTamboli
[website] Improve lighthouse score (#39011) @ oliviertassinari
[website] Fix lighthouse issues @ oliviertassinari
[website] Create the InfoCard component (#38987) @ danilo-leal
[website] Small tweaks for performance @ oliviertassinari
[zero][next] Setup nextjs plugin package (#38852) @ brijeshb42

All contributors of this release in alphabetical order: @ alisasanib, @ brijeshb42, @ danilo-leal, @ DarhkVoyd, @ DiegoAndai, @ Janpot, @ mateuseap, @ Methuselah96, @ michaldudak, @ mj12albert, @ mnajdova, @ MonstraG, @ oliviertassinari, @ sai6855, @ siriwatknp, @ ZeeshanTamboli

    from @mui/material GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

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

Comparison is base (e35b96a) 78.10% compared to head (e812d4c) 78.10%.

:exclamation: Current head e812d4c differs from pull request most recent head e0d0e1e. Consider uploading reports for the commit e0d0e1e to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1883   +/-   ##
=======================================
  Coverage   78.10%   78.10%
=======================================
  Files          39       39
  Lines        3060     3060
  Branches      616      616
=======================================
  Hits         2390     2390
  Misses        479      479
  Partials      191      191

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


Migrate robot components to THREEjs

Fix #433

[x] Use the new webots.min.js viewer
[x] Restore the functionalities

[x] sliders
[x] leds
[x] device origins
[x] Robot size estimation to set the device origin size
[x] motor reset
[x] view reset

[x] Increase rendering quality using textured background and pbr
[x] Regenerate the robot components (required for some new features like PBR and USE-DEF)
[x] Side improvements

[x] Viewpoint fieldOfView seems wrong
[x] Fix robot components on the develop branch (update dependencies.txt)
[x] Add API to webots.json (pre/postRender callbacks, etc.)
[x] Fix static background texture load
[ ] Fix IndexedLineSet of Khepera1 => to be fixed in #455
[x] Add the Tinkerbots to components.json (now this is possible)
[x] Implement Cylinder/Cone side/top/bottom flags

It starts to work well:
Preview: https://cyberbotics.com/doc/guide/robots?version=feature-threejs-robot-component

It's now working much better. PBR is renders much better with environment maps:
https://cyberbotics.com/doc/guide/robots?version=feature-threejs-robot-component
It remains to fix:

[ ] the viewpoint initialization
[ ] a bug with quaternions (the angle is inverted when reseting some robots)
[ ] The Khepera1 IndexedLineSet causes a crash in webots.min.js

I don't get any crash when streaming the khepera.wbt simulation. I will check the robot component.
But there is an issue with the DistanceSensor USE nodes and the IndexedLineSet are only displayed for the DEF node.

Just discussed with Stefania, she can't reproduce the khepera issue, I'm going forward with this.

Cylinder and cones side/bottom/top flags are not implemented in webots.min.js, this is required to support the Khepera2 correctly.

Viewpoint field of view is now fixed; three.js defines the fov vertically rather than vertically:

Cylinder/Cone bottom/side/top flags are now supported as in Webots:

By the way I checked and the issue with the khepera1 IndexedLineSet USE/DEF is not reproducible in the develop branch.

I checked and the USE/DEF and clone mechanism works correctly. I don't know why the LineSegments are not rendered. Note that I get the same issue even using basic nodes instead of USE/DEF.
And once after rotating the viewpoint the missing IndexedLineSet appeared, so it could be a rendering issue rather than a node instantiation issue.

I fixed the rotation bug by giving the initial angle though the meta file.

Khepera1 is not working because of a bug in the THREE.Object3d.clone() function in threejs < r103, used here:
https://github.com/omichel/webots/blob/develop/resources/web/wwi/x3d.js#L66
The clone function alterates the line set material from MeshStandardMaterial to LineBasicMaterial:

This bug is reported here: https://github.com/mrdoob/three.js/issues/15974
.. and fixed in r103: https://github.com/mrdoob/three.js/pull/15062/files
(I tested and upgrading solves the issue).
I recommend to accept this PR with this bug, and to upgrade threejs in another PR: because this has side effects (GPUPicker cause warnings, etc.).

test me

Build Passed :ok_hand:
You can safely merge 'feature-threejs-robot-component' into 'develop'.

👍

Note for the reviewer:

the shadows are still perfectible (some artifacts are present on some worlds) but give a better result.
Khepera1 doesn't work for now: cf #455

👍

👎
The OP3 has still issues with the recent modifications we did on the X3DScene.getObjectById() function.

(this is fixed)
👍

:eyes:

👍

👍

test me

test me

Build Passed :ok_hand:
You can safely merge 'feature-threejs-robot-component' into 'develop'.

Build Passed :ok_hand:
You can safely merge 'feature-threejs-robot-component' into 'develop'.

👍


Readline visual glitch

When reading input lines without printing anything between them, a text glitch occurs.
I noticed this while running rustyline-async version 0.4.0 in terminal on Linux. Code:
use rustyline_async::{Readline, ReadlineEvent};

#[tokio::main]
async fn main() {
    let (mut readline, _printer) = Readline::new("> ".to_string()).unwrap();

    while let ReadlineEvent::Line(text) = readline.readline().await.unwrap() {
        readline.add_history_entry(text.to_string());
    }
}

https://github.com/zyansheep/rustyline-async/assets/24969682/5ceccec4-57ca-4ee9-8a82-f119ffffcaa1

Merged, Thanks for the fix! Not sure how that didn't get caught... might have been a regression from a previous commit. I'll push a crates.io release when I get around to it :)


[Syntax] Clean up syntax grammar for declaration nodes

Collected cleanups for the declaration grammar used by SwiftSyntax/libSyntax:

Split ActorDecl into its own syntax node, separate from ClassDecl
Update the list of declaration modifiers to match that of the language
Use FunctionSignature for initializers rather than its own parameter clause, which picks up (e.g.) proper support for async and the experimental reasync, and also unifies their parameter lists with that of function declarations
Factored out the "detail" of a decl modifier, so we have an optional parenthesized detail list rather than optional components
TypeAliasDecl's initializer (the = type) is not optional, so remove its optionality

https://github.com/apple/swift-syntax/pull/499
@swift-ci please clean test

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
@swift-ci please clean test

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
@swift-ci please clean test

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
@swift-ci please clean test

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
@swift-ci please test macOS

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
https://github.com/apple/swift-driver/pull/1140
@swift-ci please test macOS

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
https://github.com/apple/swift-driver/pull/1140
@swift-ci please test macOS

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
@swift-ci please test macOS

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
@swift-ci please test macOS

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
@swift-ci please test macOS

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
@swift-ci please test macOS

Different spurious failure, this time from LLDB. Trying again...

https://github.com/apple/swift-syntax/pull/499
https://github.com/apple/swift-stress-tester/pull/180
@swift-ci please test macOS


Small text in HTML mails

When I receive a mail in HTML format, it is displayed very, very small. I can increase its size by pinching the screen, but then the line breaks stay the same like for the small font, so a lot of scrolling is needed. Can I somehow increase the display size?

General settings > Display > Font size > Message body


Latest rust stable version (2022-08-08) is outdated as the current latest is 2022-08-11

Building rust-overlay with rust-bin.stable.latest provides:
rustc --version
rustc 1.63.0 (4b91a6ea7 2022-08-08)

But the current latest release is 1.63.1 (2022-08-11).

Here's what I tested on Arch Linux.
$ rustup install stable
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: latest update on 2022-08-11, rust version 1.63.0 (4b91a6ea7 2022-08-08)
info: downloading component 'cargo'

Where do you find 1.63.1?

You're right... Sorry for that! I think the dates got me confused, rustc is showing 2022-08-08 while rust RELEASES (and rustup apparently) show 2022-08-11.


Unable to connect to backend service

Received a notification that CrashPlan hadn't backed up in a day which usually means an update happened and I need to pull the latest image.  So I did that but now I cannot start CrashPlan, the web gui display - cannot connect to back-end service, retry. and the docker logs show the following continuously.
[supervisor     ] restarting service 'CrashPlanEngine'.
[supervisor     ] starting service 'CrashPlanEngine'...
[supervisor     ] service 'CrashPlanEngine' exited (with status 0).
[supervisor     ] restarting service 'CrashPlanEngine'.
[supervisor     ] starting service 'CrashPlanEngine'...
[supervisor     ] service 'CrashPlanEngine' exited (with status 0).
...

Gist of the long service.log.0 file is here: https://gist.github.com/bmorgenthaler/3dad97b33bc7511e939ad03a22f27df0

Tried removing the config directory and starting fresh to adopt a previous backup and it still is giving the same errors in the logs and won't start.

I think the same thing is happening to me.
I get this message in the GUI when I try to log in:

I solved this for me and this was the key for me UpgradeLevelDbEncryption::Unable to read previous universal storage properties., java.io.IOException: IO error: lock /usr/local/crashplan/conf/udb/LOCK: No locks available
My container is mounting it's config and source directory over NFS (backing up a NAS without native docker). I had the defaults from creating the docker volume for a NFS with portainer in the compose. This had been working just fine but with the latest update it broke. After playing around with the NFS options I have the following compose stanza now and it is working. I think the nolock was the key which was counterintuitive.
volumes:
  config:
    driver_opts:
      type: "nfs"
      o: "addr=<IP_ADDRESS>,rw,noatime,tcp,nolock"
      device: ":/docker/crashplan"

The nolock option disables locking on the server side.
How did you configure the export of the server side ?


Webservice parameter names - is null error

Just noticed traditionally the first letter of web service parameter names are converted to lowercase and it is still the case in 2018, objects/CSide extension. But this is no longer the case in ModernDev extension, is this intentional?
This causes the parameter is null error calling the web service function, spotted the difference on the wsdl.

Any input from Microsoft on this? Can we assume that the parameter will maintain their uppercase value in V2 or should we expect it to go the way of CSide in the near future?

Hi. Could you please provide repro steps for this issue? Are you working on the Nav 2018 or the latest Developer Preview?

That's simple create a codeunit with a function like so:
  procedure WebServiceProcedure(var Data : XmlPort SomeXMLPort);
  begin
    Data.IMPORT;
  end;

Now expose said codeunit as a web service. In good old CSide the parameter name is converted to data but in V2 the parameter remains as Data.
I think this has been like this forever in V2 and tested it in dynamics-nav:11.0.20977.0-finus.

Thanks for your response @DominikDitoIvosevic.


[GHSA-76p3-8jx3-jpfq] Prototype pollution in webpack loader-utils

Updates

CVSS
CWEs
Severity

Comments
Prototype pollution is only possible on a plain object if properties are set 2 or more levels deep. These are not equivalent:
result["__proto__.isAdmin"] = true; // doesn't change any prototype
result["__proto__"] = { isAdmin: true }; // changes prototype for result but not other objects
result["__proto__"]["isAdmin"] = true; // changes prototype for result and other objects
parseQuery.js only sets top-level attributes on a plain object. Property accessors cannot set nested values in a single bracket pair.
The for loop in parseQuery.js is for adding a number of top-level properties, not setting them recursively.

Hey there @JeremyRH 👋, if you'd like to get this CVE revoked you should reach out to the assigning CNA (mitre, https://cveform.mitre.org/) and request that this be revoked. The change of all impact to none does not seem in line with what you're describing.

Thank you! I wasn't sure how to request this be revoked.

@JeremyRH feel free to circle back here if/when it gets revoked and we're happy to reflect the state of the CVE 👍


Replace react-router-dom default error page

Adding this as a quick fix to remove the default error message.
This is due to a change in react-router-dom, where it now plays the role of <ErrorBoundary>
We may be able to remove the existing <ErrorBoundary> -- I need to research that more.

Coverage: 93.925% (-0.006%) from 93.93% when pulling b648854b2ab79c98f9a2509ccfb2fb281d793102 on cody-unexpected-error-page into dcf3b56e96dd1696b5164fa905954e402cc0e885 on main.


Microsoft Office 365 hotline

i have been calling for weeks, no one is answering the hotline. i need support.

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

ID: 94f68f42-3e1e-f119-c15b-83e788997eae
Version Independent ID: 0bf16d91-f0a3-96e4-8ddf-4ef00e613c7a
Content: Support information for Philippines
Content Source: Office365-Admin/support/philippines.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@makoicriador - Thank you for submitting feedback.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Please follow this link contact support for business products: https://docs.microsoft.com/office365/admin/contact-support-for-business-products
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.
NOTE:  We used to use this link to a video explaining how to open a support ticket.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y

@cmcatee-MSFT @kenwith @AndreaBarr - FYI.

Thank you for your response.
I appreciate the links and instructions you have given, unfortunately, my
issue is a bit different.
The Office365 account is from a previous partner, and said account is being
billed monthly on my personal credit card. Right now, i am unable to
contact her in any way possible for her to cancel her subscription, and I
have been paying for it for almost a year now.
What I need right now is for my credit card to be unbound from her
Office365 account, nevermind the balance, I will pay for it, as long as it
doesn't bill anymore on the next cycle.
Ultimately, I need my credit card to be cut, and I cannot do that unless
all monthly subscriptions being billed there will be removed.
I hope you can help me with this, I have been struggling to contact
Microsoft hotline for more than three months now.
Thank you.
On Fri, 15 Feb 2019, 22:03 mypil<EMAIL_ADDRESS>wrote:

@cmcatee-MSFT https://github.com/cmcatee-MSFT @kenwith
https://github.com/kenwith @AndreaBarr https://github.com/AndreaBarr

FYI.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/OfficeDocs-O365ITPro/issues/277#issuecomment-464060823,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AtaZFkpW2h_mNTh-xcePYHfGR6rM7Fs7ks5vNr4fgaJpZM4a6r_g
.

@makoicriador - thank you for providing this additional feedback. We have already informed the relevant team to investigate on the Philippines phone support hotline issue and they are still working on it. With regards to your other issue, I am checking with some people that could help to address your concern.
@cmcatee-MSFT @kenwith

It was recently brought up in a call with an agent that since I am unable
to unbound the Microsoft subscription, I can just call again and have it
blocked, given that I settle the remaining balance.
Can you confirm this? If so, please elaborate the process so I may
immediately act on this.
Thank you.
On Wed, 20 Feb 2019, 22:54 Joyce Y<EMAIL_ADDRESS>wrote:

@makoicriador https://github.com/makoicriador - thank you for providing
this additional feedback. We have already informed the relevant team to
investigate on the Philippines phone support hotline issue and they are
still working on it. With regards to your other issue, I am checking with
some people that could help to address your concern.
@cmcatee-MSFT https://github.com/cmcatee-MSFT @kenwith
https://github.com/kenwith
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/OfficeDocs-O365ITPro/issues/277#issuecomment-465610138,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AtaZFoPSo0OIG4VbXAlnEpHv_agKdf5kks5vPWGRgaJpZM4a6r_g
.

Hi @makoicriador,
My name is Russell and I'm part of the Microsoft support organization. While I can't answer your question from the information here, I'll try to get the right folks engaged to get this resolved for you. Additionally, I'd like to understand more about the challenge you've had with our phone number.
Can you send an e-mail to<EMAIL_ADDRESS>and I'll respond to get the information we need to move forward.
-thanks, Russell.

@makoicriador - Kindly work with Russell to help resolve your concern. We will proceed to close this issue.
Thank you for reporting and making the docs better. Much appreciated.

@AndreaBarr - This issue can be closed. Thank you.


Definitions of the visual attributes

Hi, from the paper I could only find the descriptions of the 10 general attributes in the Google sheet.
Could you please share the descriptions of other categories (Shape, Location, Pathological diagnosis) of attributes?
Thanks a lot!!

Hi @lofrienger
I am not quite getting your question here. Could you concrete it?
Best,
Gepeng.

Hi,
Please refer to here for more details.
Best


feature(log): add context menu to copy branch names

There's an issue in this PR when showing context menu for commit with both origin and local branches, in which the icon is only displayed for the remotes. @mickedefault Could you help me check what might be wrong?


Privacy/Term page darkmode/cursor/backtotop/ in privacy footer addition

Related Issue
Fixes #1216
Description
Added Dark Mode also there is bugs in terms and privacy pages.
Link Cursor not work / Backtotop not visible / in privacy page footer missing all that issues solved.
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
https://www.loom.com/share/50e344f3d30941a98ce4a40d96b8e492
https://www.loom.com/share/7410f230697a4744a768aaf70d5e2d5a
Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

@Suchitra-Sahoo Please check it and merge !
Thank You !


Error with liip

Q
A

Bug report?
[ ]

Feature request?
[ ]

Support request?
[ x ]

hi @cocolabssas ,
What does this error mean?

[2019-05-13 14:12:50] request.INFO: Matched route "liip_imagine_filter". {"route_parameters":{"_controller":"liip_imagine.controller:filterAction","_locale":"fr","filter":"listing_xxmedium","path":"uploads/listings/images/","_route":"liip_imagine_filter"},"request_uri":"https://localhost/fr/media/cache/resolve/listing_xxmedium/uploads/listings/images/"} []
[2019-05-13 14:12:50] security.INFO: Populated the TokenStorage with an anonymous Token. [] []
[2019-05-13 14:12:50] request.CRITICAL: Uncaught PHP Exception Symfony\Component\HttpFoundation\File\Exception\FileNotFoundException: "The file "/var/www/prod/cocorico/app/../web/uploads/listings/images/" does not exist" at /var/www/prod/cocorico/vendor/symfony/symfony/src/Symfony/Component/HttpFoundation/File/MimeType/MimeTypeGuesser.php line 123 {"exception":"[object] (Symfony\Component\HttpFoundation\File\Exception\FileNotFoundException(code: 0): The file "/var/www/prod/cocorico/app/../web/uploads/listings/images/" does not exist at /var/www/prod/cocorico/vendor/symfony/symfony/src/Symfony/Component/HttpFoundation/File/MimeType/MimeTypeGuesser.php:123)"} []

FileNotFoundException

Hi @gonzasylv,
It seems that you have a listing without image or you missed to add the image name in your twig template.

We close it as it seems there is no more activity on it. Feel free to reopen it if needed.


Mobile menu problem

On mobile (or small width browser) the menu relies on a hamburger toggle icon. When you click on a link, the menu does not toggle off, so continues blocking your view.
It is not clear to the user what has happened, there is no evidence that the page has changed.
We need to ensure the toggle class has been removed from the menu whenever a menu link is clicked, so users can always see the page content has updated.

This has been fixed. I still need to refactor the React code now that I understand better how props/state/components should be used together, but the frontend UX is fixed.


[Button] Dense button text is out of bounds when split

Describe the bug
The dense button in our layout has a fixed width depending on the page size and it is causing the button to show the text out of bounds (I believe the line height might be too high).

To Reproduce
See below as I have reproduced it inside the vivid storybook by just changing the label to Getting Started and adding a max-width=100px.
Expected behavior
The text should render in the center of the button.
Screenshots

Although this is certainly a fixable bug (and already addressed in vivid@next), what is the expectation if the text exceeds it's available inline size? Would a trimmed / ellipsis text be better?

I would think the simplest solution would be this:

I, myself, don't agree a button should be flexible in its block size, but I'd leave that decision for designers...
buttons is defined by design to have a fixed block size.
maybe stacked button would be better for this use-case?

@yinonov can we at least fix this issue by setting a line-height that is more in line with the font-size. line-height is usually set to font-size + 2px and in this case, the font-size is 12px and line-height is 24px.
All I am asking is that we change this in the next version so as to be unblocked.

maybe stacked button would be better for this use-case?

Not really, all I need is a dense button that can handle rendering on two lines if the text is too long for the width.

Sure reducing the line-height is a reasonable solution and enhancement. Will do 👍

@yinonov thanks for addressing the issue quickly.
Please, let me know when the fix is released so I can update our dependency.

will release momentarily. see - Prepare Vivid for release

Still an issue in v2.36.2.

fixed in v2.36.3


Send OTel resource with Trace Exporter.

Description
As part of replacing Heartbeat, we will be sending a custom metric containing the OTel resource. See spec
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


Add fermata attribute for mensural notes

The fermata attribute (found in the att.fermataPresent class) is only available for notes in CMN.
In this PR, I add the missing class att.note.anl.mensural (the logical, gestural, and visual corresponding classes already exist), and make it a member of att.fermataPresent, similar to how att.note.anl.cmn is a member of att.fermataPresent. Then include the newly introduced att.note.anl.mensural class in the classes of att.note.anl.

I do not have a problem with allowing <fermata>, but note that it is often called corona in mensural music.  with the link saying:

It is similar to the fermata in modern notation.

Perhaps there is no functional difference between them, in which case using fermata as the name for the mensural version is no problem. (I am not aware of any difference at all, at least in the music of Josquin).
Perhaps some mensuralists could comment on if there is any real difference between them?

Jesse Rodin cannot think of any difference between a fermata and a corona, so it should be safe to assume that they are equivalent.

Hi @craigsapp! Thank you for checking on this :)


Helm Chart - Please remove managed-identity-wallets Chart

Please remove Helm Chart /charts/managed-identity-wallets to avoid confusion.

Done


Routing audio from one sound card to another

hi,
I have two sound cards, build-in sound card and a usb sound card.
I want to redirect audio from built-in sound card microphone to usb sound card speakers
& audio from built-in sound card speaker to usb sound card microphone.
how do I do this using NAudio?

There is no automatic redirection. What you can do is capture audio from one device and play it from another. The BufferedWaveProvider helps with this - you can write captured audio into the BufferedWaveProvider while another device plays from it. However, it is important to understand that the latency will be fairly high using this technique, which may not be suitable.
As for directing speaker output into microphone input that is unfortunately not possible without using a virtual audio cable which is typically a paid third-party product

Ok, but in this case you said audio will not be duplicated, playing in both channels?


Is coco_detection.py line 45 an error?

Thanks for your error report and we appreciate it a lot.
Checklist
yes,it seems like no one see it
Describe the bug
IT seems like an little error or not?
in /mmdetection/configs/base/datasets/coco_detection.py line 45 and line 46
test=dict(
        type=dataset_type,
        ann_file=data_root + 'annotations/instances_val2017.json',
        img_prefix=data_root + 'val2017/',
        pipeline=test_pipeline))

Reproduction
I use retinanet to train my own model ,and I saw code in  coco_detection.py just like a error.
Environment
I use docker which U provided,and I added some useful thing
Error traceback
Bug fix
I think that should be
    test=dict(
        type=dataset_type,
        ann_file=data_root + 'annotations/instances_test2017.json',
        img_prefix=data_root + 'test2017/',
        pipeline=test_pipeline))

Hi @eguoguo321 ,
This is because usually we still use the validation set of COCO data during testing unless we want to submit test-dev or test set results to the evaluation server. Therefore, by default we still use instances_val2017.json.


wave_add_generic() fails for pulse lists with more than 5460 elements

When I call wave_add_generic(pulse_list) with more than 5460 elements in the pulse list, the function either hangs silently or displays ConnectionResetError: [Errno 104] Connection reset by peer
I cannot use wave_send_repeat() because in our application because the duty cycle will vary over time (We are generating motion curves to drive a high-precision micro-stepped motor).
I am using Python 3.5.3. You can replicate the error with this code:
import pigpio
import time

OUPUT_PIN = 23

pi = pigpio.pi()                        # initialize connection
pi.set_mode(OUPUT_PIN, pigpio.OUTPUT)   # set pin direction
pi.wave_clear()                         # clear the waveform buffer

periods = input("How many periods? ")   # prompt for number of periods

print("Creating pulse list...")
pulse_list=[]                               # create an empty pulse list

for i in range(0,int(periods)):             # for the specified number of periods
    # turn OUPUT_PIN on for 10us
    pulse_list.append(pigpio.pulse(1<<OUPUT_PIN, 0, 10))
    # turn OUPUT_PIN off for 10us
    pulse_list.append(pigpio.pulse(0, 1<<OUPUT_PIN, 10))

print("Pulse list done. Pulses:", len(pulse_list))

print("Adding pulses to waveform...")
pi.wave_add_generic(pulse_list)             # add the list of pulses to a waveform

print("Creating waveform...")
pulse_waveform_id = pi.wave_create()        # create and save an id for the waveform

print("Sending waveform...")
pi.wave_send_once(pulse_waveform_id)        # send the waveform

print("Done.")

This will give the output:
How many periods? 2731
Creating pulse list...
Pulse list done. Pulses: 5462
Adding pulses to waveform...
Traceback (most recent call last):
  File "example.py", line 27, in <module>
    pi.wave_add_generic(pulse_list)             # add the list of pulses to a waveform
  File "/usr/lib/python3/dist-packages/pigpio.py", line 2120, in wave_add_generic
    self.sl, _PI_CMD_WVAG, 0, 0, len(pulses)*12, extents))
  File "/usr/lib/python3/dist-packages/pigpio.py", line 1007, in _pigpio_command_ext
    dummy, res = struct.unpack('12sI', sl.s.recv(_SOCK_CMD_LEN))
ConnectionResetError: [Errno 104] Connection reset by peer

Putting in 2730 when prompted works fine, but as soon as you go to 1731 (corresponding to 5462 pulses in the pulse list) it breaks.

I think the maximum socket message is 65k.  You could change the constant in pigpio.h (I think) and rebuild.
A better solution would be to add less elements.  Say add 4000 at a time, starting each new block where the old one ended (ny making the first element a delay).

How do I add the delay to get them to line up? What would that look like?

Commit the waveform so far before the message gets too big.
Have a look at the following example code.
if len(pulse_list) > 4000:
   # commit waveform so far
   pi.wave_add_generic(pulse_list)
   pulse_list = []
   # start new waveform at end of last
   pulse_list.append(pigpio.pulse(0, 0, pi.wave_get_micros()))

We just hit this. Would you consider guard rails or a more helpful error?

Oh, and for anyone else: The constant is CMD_MAX_EXTENSION:
https://github.com/joan2937/pigpio/blob/c33738a320a3e28824af7807edafda440952c05d/command.h#L41

And this is the critical code, at least when using network connections (which is default when using the python library)
https://github.com/joan2937/pigpio/blob/c33738a320a3e28824af7807edafda440952c05d/pigpio.c#L7053-L7083


docs: convert Serialization.rst to Markdown

Converts one more doc file from .rst to Markdown for consistency.

@swift-ci please smoke test


content-disposition

Would be nice to be able to push data to cartodb and then read right back into TileMill. TileMill likes a helping hand to know the file format of urls that respond with geodata and setting content-disposition will enable this. So, if the user requests:
http://tileio.cartodb.com/api/v1/sql?q=SELECT * FROM places_by_lon_lat&format=geojson
Then having cartodb set content-disposition to something like foo.geojson or foo.json would allow the data to be autorecognized as geojson in tilemill.
ref: https://github.com/Vizzuality/cartodb/issues/217

great, thanks!


Seen and Typing on v2 and above

Operating system: Win 7
Messenger for Desktop version: Latest stable

This is a feature request, is it possible to add the disable seen and typing unto the v2 and above beta's? I think it wouldn't hurt that much that would make the app unstable as it is a minor feature.

Added in 2.0.5, will be released soon

Thanks man! Been waiting for this :)


Gracefully handle timeout errors for email notifier test

Test:
Attempt to establish an email notifier.
Enter an incorrect port number.
Click test.
Result:
Generic timeout exception.

Can you please make the error message more user friendly?

Master 4/21/18
Verified new UI
"Failed to connect smtp server: dial tcp: lookup smtp.office.365.com on <IP_ADDRESS>:53: no such host"


Release 5.1.0-alpha03

@matt-ramotar  please create next alpha release.

Will release after #641

@matt-ramotar When is the release planned for, please ?

@matt-ramotar in case you have not figured out the Sonatype problem yet, they did an account migration that seems to have broken username authentication for a big chunk of users.
If you generate a new token following this guide, then you can use the username and password from there as your new credentials and things should start working fine again.

Thanks! Just swapped, should be able to release today

The release seems to have run into https://github.com/Kotlin/dokka/issues/2956, according to the comments reducing JVM target to 11 works around this. I can send in a PR if required.

@msfjarvis That would be awesome, but no pressure

@msfjarvis That would be awesome, but no pressure

No sweat at all, it's here: #648
I haven't incremented the version there since I didn't know if you wanted that.

5.1.0-alpha03 has successfully deployed: https://central.sonatype.com/search?q=g%3Aorg.mobilenativefoundation.store+version%3A5.1.0-alpha03

Awesome, thanks again


How to run sagas in loop

First of all thanks a lot for providing community with this nifty tool. I am able to reduce lot of corners around my app.
One thing I was wondering how to achieve is how to run sagas in loop. i.e.
forEach(result, (item) => {
  yield fork(api.endpoint, item);
});

I am getting following error while trying so
Uncaught (in promise) Error: https://localhost:3000/fuses/fuse-react-redux/sagas/index.js: Unexpected token (30:12)
  28 |     yield put(actions.requestNewItems());
  29 |     forEach(result, (item) => {
> 30 |       yield fork(api.endpoint, item)
     |             ^
  31 |     });

saga works if put outside of loop with single item. e.g.
yield fork(api.endpoint, item)

I am not sure if by convention it's not supposed to work this way.

You can't yield from a  callback. Only from generators. A possible solution is
yield result.map(item => fork(api.endpoint, item))

That worked like charm. Thanks a lot. Everyday I am learning new and awesome stuff about sagas. Best complement to Redux.


newline-after-import has weird autofix for IIFE with leading semicolon

Affected Code
I'm writing a file in which I require a file and then use an async IIFE to wrap my code.
const composeTest = require('./lib/composeTest')

;(async () => {
  const tests = [
    await composeTest(/* arguments go here */),
  ]

  for (const test of tests) await test()
})()

This provides the error:

Expected 1 empty line after require statement not followed by another require

And auto-fixes to this:
const composeTest = require('./lib/composeTest')

;

(async () => {
  const tests = [
    await composeTest(/* arguments go here */),
  ]

  for (const test of tests) await test()
})()

Semicolons before IIFEs are required when relying on ASI which is why it is a common convention for developers who don't use them to place a semicolon immediately before them, as my first code sample shows.
Configuration
My full configuration is very large.
The following minimal configuration can reproduce this issue:
module.exports = {
  'parserOptions': {
    'ecmaVersion': 8,
  },

  'env': { 'node': true },
  'plugins': ['import'],

  'rules': {
    'semi': ['error', 'never'],
    'import/newline-after-import': 'error',
  },
}

In Conclusion
I don't have any fixes in mind. I can move the semicolon to the end of the previous line and my code works fine and looks acceptable. I just wanted to provide the information that the auto-fix behaves this way in this situation.

In general, I'd say IIFEs are obsolete now that modules exist, even async ones since TLA is shipping, and ASI hazards are going to keep getting worse as the language evolves, so you may want to reconsider that choice.
That said, I'm happy to accept a PR that improves the autofix here; but to set expectations, I'm not planning on working on it on my own.


Change deprecated module name

The module django.contrib.admin.util was renamed to django.contrib.admin.utils in Django 1.9.
See release notes for more details on this: https://docs.djangoproject.com/en/1.9/internals/deprecation/#deprecation-removed-in-1-9

Closing due to #30 being merged.


[WIP] Configurable access logger with JSON support

This is a new access logger derived from (and replacing) the old one. It exists in its own accesslog package under middlewares and has similar-ish net/http filters to the existing solution. Its first concern is to implement the existing extended Common Log Format  behaviour, to provide a clean upgrade path for existing users.
But it's now split into pluggable parts, the important part being its formatter (the CLF formatter being the default). A new JSON formatter exists.
The file writing part is termed the log appender and is slightly enhanced: it allows buffered writing, or gzipped writing, and/or asynchronous writing via a channel/goroutine.
The final area of change is to the configuration: new settings are needed to control the new features. This is done with a new AccessLog type in types.go.
Notice that there are now three middlewares:

the first is the 'main' logger that tracks each request, builds log events, and despatches these to the log appender;
the second inserts knowledge about the frontend into the log-data context;
the third inserts knowledge about the backend into the log-data context.

There had previously been an error in tracking the frontend data: it operated on the incorrect assumption that there is a 1:N mapping from frontends to backends.

This PR supersedes #1114.

Unfortunately, I won't have time to review the PR this week. Will give someone else a chance, but happy to jump back on once time permits again and a review is still needed.
Apologies!

@rickb777 CI is still complaining go fmt didn't ran everywhere.

I ran go fmt - see the last commit.
What is it complaining about?

@rickb777 according to the latest run, it's complaining about middlewares/accesslog/logAppender_test.go and middlewares/accesslog/logFormatter_test.go.

There will be further commits added to this PR tomorrow.

Can someone try to reproduce the go fmt problem? I can't. I run go fmt and it seems fine, but the CI fails.

Try make fmt instead :)

gofmt -s does more than go fmt, I've learnt.  :)
Please don't merge this PR just yet - it's not ready both in gofmt terms and also because I've double-checking what appear to be some bugs. More info will follow.

@rickb777 added [WIP] in the title, fill free to remove it as soon as you think your PR is ready.

Why not just use logrus as it is used for error logs.  We could write a formatter for it for the text format. JSON could just use the logrus json formatter.  If we thought that was going to be slow, we could always implement MarshalJSON on the log object and it'd be used.  Using logrus would possibly be more flexible if we needed to add more fields/capabilities later on.

The most recent commit, switching from reflection to a simpler map implementation, improved the speed of JSON logging as measured by the microbenchmarks by a factor of about 2.5.

I'm still having trouble with make fmt. It works fine for me but Travis is still unhappy. :-(

@rickb777 are all those commits normal? Specifically https://github.com/containous/traefik/pull/1230/commits/40b3a1dff71a6287365da817f697a48489764a87 ?

Yes sorry, it looks like the next theme of work has crept in here rather than onto a different branch. I'll check it out.

This is ready for merge now.

@rickb777 There are still way too much commits in this PR (21). Not sure why :thinking:

The large number of commits is a problem for me. I could throw this PR away and do it all again, using rebasing to avoid the complex graph of merge history I can see here in git. It isn't possible to do a simple squash because on this complex graph.
Maybe on Monday then...

This PR has now been superseded by PR #1293


Watchers fired in the last x iterations

I am getting some angular errors when using the following code. The script seems to work but I would like to suppress these errors. Could you help me find out what is going on?
Controller:
'use strict';

angular.module('preSalesQuestionnaireApp')
  .controller('QuestionnaireCtrl', function ($scope, $http) {
    $http.get('app/questionnaire/schema.json').success(function(resschema) {
      console.log(resschema);
      $scope.schema = resschema;
    });

    $http.get('app/questionnaire/form.json').success(function(resform) {
      console.log(resform);
      $scope.form = resform;
    });

  $scope.model = {};
  });

questionnaire.html:
<form sf-schema="schema" sf-form="form" sf-model="model"></form>

form.json:
[
  "projectname",
  {
    "type": "help",
    "helpvalue": "
Select the deal typeNew
"
  },
  {
    "key": "dealtype",
    "type": "radiobuttons",
    "title": "Deal Type",
    "notitle": true,
    "style": {
      "selected": "btn-success",
      "unselected": "btn-default"
    },
    "titleMap": [
      { "value": "OnPremise", "name": "OnPremise" },
      { "value": "CaaS", "name": "CaaS" }
    ]
  },
  {
    "type": "submit",
    "title": "Save"
  }
]

schema.json:
{
  "type": "object",
  "properties": {
    "projectname": {
      "type": "string",
        "minLength": 2,
        "title": "Project Name",
      "description": "Customer Name or alias"
    },
    "dealtype": {
      "type": "string",
      "title": "Deal Type",
      "enum": ["OnPremise", "CaaS"]
    }
  }
}

Error:
Error: [$rootScope:infdig] 10 $digest() iterations reached. Aborting!
Watchers fired in the last 5 iterations: [[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":{"type":"string","minLength":2,"title":"Project Name","description":"Customer Name or alias"},"ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":{"type":"string","title":"Deal Type","enum":["OnPremise","CaaS"]},"ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}],[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":"<<already seen>>","ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":"<<already seen>>","ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}],[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":"<<already seen>>","ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":"<<already seen>>","ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}],[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":"<<already seen>>","ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":"<<already seen>>","ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}],[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":"<<already seen>>","ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":"<<already seen>>","ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}]]
http://errors.angularjs.org/1.4.0/$rootScope/infdig?p0=10&p1=%5B%5B%7B%22ms…%2C%7B%22name%22%3A%22CaaS%22%2C%22value%22%3A%22CaaS%22%7D%5D%7D%7D%5D%5D
    at REGEX_STRING_REGEXP (angular.js:68)
    at Scope.$get.Scope.$digest (angular.js:15594)
    at Scope.$get.Scope.$apply (angular.js:15824)
    at done (angular.js:10263)
    at completeRequest (angular.js:10435)
    at XMLHttpRequest.requestLoaded (angular.js:10376)
Uncaught Error: [$rootScope:infdig] 10 $digest() iterations reached. Aborting!
Watchers fired in the last 5 iterations: [[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":{"type":"string","minLength":2,"title":"Project Name","description":"Customer Name or alias"},"ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":{"type":"string","title":"Deal Type","enum":["OnPremise","CaaS"]},"ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}],[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":"<<already seen>>","ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":"<<already seen>>","ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}],[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":"<<already seen>>","ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":"<<already seen>>","ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}],[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":"<<already seen>>","ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":"<<already seen>>","ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}],[{"msg":"schemaForm.form[0]","newVal":{"title":"Project Name","description":"Customer Name or alias","schema":"<<already seen>>","ngModelOptions":{},"key":["projectname"],"type":"text"}},{"msg":"schemaForm.form[1]","newVal":{"title":"Deal Type","schema":"<<already seen>>","ngModelOptions":{},"key":["dealtype"],"type":"select","titleMap":[{"name":"OnPremise","value":"OnPremise"},{"name":"CaaS","value":"CaaS"}]}}]]
http://errors.angularjs.org/1.4.0/$rootScope/infdig?p0=10&p1=%5B%5B%7B%22ms…%2C%7B%22name%22%3A%22CaaS%22%2C%22value%22%3A%22CaaS%22%7D%5D%7D%7D%5D%5D
["projectname", Object, Object, Object]

I get these as well, and they grow exponentially as the size of the schema grows. If I start cutting down the schema, I reach a point that the errors go away, but it's a pretty small schema at that point, with maybe 20 properties at most.

Please add a gist or plunkr so it can be easily debugged.

I've moved on from trying to use this library, so I won't have anything to add, maybe the OP can

Oh, that is too bad. ASF is really going places not.
But at least my advise works on other projects as well. :-)

I am facing a similar issue. So, I am setting form values inside an ajax call. The form basically contains some drop downs which in turn are populated by a service created in angular. Plane javascript function has been written which takes some parameters and gets the relevant drop down values.
And then in my view I am utilising the schema form like this.
The values have been set on rootScope so don`t worry about the $root part in the tag.
Now, the sf-schema attribute gives me [$rootScope:infdig] error. I have tried removing it and it doesn`t give me the error.
 I cannot give you a plnkr for it and I also cannot provide you the actual code as well. But see if you can help.
I also tried $rootScopeProvider.digestTtl(400) but it works some time and some time it doesn`t. And it has performance issues as well.

It is very difficult to find out what is the problems from descriptions like this, I am sorry, but at least for me, a plunkr is necessary for me to gain the needed insight in the code.
That said, I would perhaps recommend you to chain the $http.get's, they may happen in any order as it is now.

With chaining i mean:

    $http.get('app/questionnaire/schema.json').success(function(resschema) {
      console.log(resschema);
      $scope.schema = resschema;
      $http.get('app/questionnaire/form.json').success(function(resform) {
          console.log(resform);
          $scope.form = resform;
        });
    });

@nicklasb do you have a working plunkr i can fork to recreate the issue for you? I don't have time to get all the dependencies pulled in to replicate the issue, but I do have a simple working test case

@nikmartin, no I don't actually, not with ASF.
However that is something that would be good for the project to have, feel free to create a baseline ASF plunkr, and we can use that to create an official one to use in cases like this.

Found this, not sure how relevant the source is, but you could just copy/paste from ASF.
http://plnkr.co/edit/7Oqxxl?p=info

This demonstrates the isse:
https://plnkr.co/edit/ayyGY7JRCZ9bijhEItr1?p=preview
after the form is displayed, check the console, and about 10 seconds later, thousands of exceptions will be thrown in the console

Well, that is a huge schema.
As this doesn't produce the schema, your error is at some point between:
var agencySchema = {
  'id': 'https://app.nitropcr.com/api/schema/agency',
  '$schema': 'http://json-schema.org/draft-04/schema#',
  'title': 'NitroPCR Agency Schema',
  'type': 'object',
  'properties': {
    'id': {
      'type': 'string'
    },
  }
};

.. and the full schema.
I would recommend a simple binary search.

ALso, feel free to add this plunker to the readme:
https://plnkr.co/edit/5F0Gu1?p=preview
It's a plunker of the demo that's in the readme.

I would recommend a common binary search to find the offending schema parts.

I'm not sure I understand. If the error is purely related to the size of the schema, then I'm not sure how to proceed, as the size of the schema is what it is. The schema itself is a valid json-schema (v4)

Digging into the error a bit, the first error seems to be thrown by:
'pattern': '^[0-9]{2}$'
So something is not handling that string very well

I am suggesting not that the size is the issue, but some construct within
it.
On 27 Apr 2016 16:45, "Nik Martin"<EMAIL_ADDRESS>wrote:

I would recommend a common binary search to find the offending schema
parts.
I'm not sure I understand. If the error is purely related to the size of
the schema, then I'm not sure how to proceed, as the size of the schema is
what it is. The schema itself is a valid json-schema (v4)
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/json-schema-form/angular-schema-form/issues/433#issuecomment-215106781

OK, well the plunker is there that replicates the issue, that's about all I have to offer at the moment.

I was able to continue with my task by adding this to my app:
.config(['$rootScopeProvider',function ($rootScopeProvider) {
    $rootScopeProvider.digestTtl(15);
  }])

So @PierrickI3, in your case, try:

angular.module('preSalesQuestionnaireApp')
.config(['$rootScopeProvider',function ($rootScopeProvider) {
    $rootScopeProvider.digestTtl(15);
  }])
  .controller('QuestionnaireCtrl', function ($scope, $http) {

The default digestTtl is 10, and something is triggering this, so bumping it by 5 fixed it for me in my VERY LARGE schema. This probably isn't a permanent fix, but at least I can continue without so many errors. I don't understand all the ramifications of doing this, but here's the docs for it: https://docs.angularjs.org/api/ng/provider/$rootScopeProvider

@nikmartin, I just saw the plunkr, it looks great!
Ok. I would say that this is a difficult one. Obviously, loads of watchers are created when a huge schema like this is loaded, so it actually may be a permanent fix.
For one, because this is a very special use case, and that setting makes angular view those as unstable, which they might not be.
However, I created schemas with hundreds of fields recently when I tested converting schema.org into json-schema, and had no such problems, and I had some 10 megabyte schemas there. So I am guessing that something in that schema triggers watches to be created.

So I am guessing that something in that schema triggers watches to be created.

Yes, we use MOST of the features of json-schema v4, so there may be some edge cases that are tripping it. We use regex pattern: {} validation functions, in the form of format: {} properties, etc.

Hm. It seems to be a plain complexity issue. If I remove the regex patterns, the error doesn't happen during initialisation. However it happens later on, when I navigate the form instead.

I think that perhaps some others should take a look at this issue and decide if there is anything to do here, @davidlgj , perhaps.

@nikmartin @nicklasb there are way too many watchers in the current bootstrap decorator in the name of flexibility, with the Material repo I made a number of values like title a one-way bind and more than halved the number of watchers. I suspect the same changes need to occur in the bootstrap repo. Otherwise as soon as you set all those values you trigger the watchers. A bugfix issue needs to be added to the bootstrap decorator, it could be a breaking change for some use cases. But I think it would certainly help the situation.

Ok, good that there seems to be an explanation.
Well, I would think that WRT breaking, that would mean that people would in some way edit titles and for some reason expect that would continue to be supported? I cannot see that any mentioning of support for that in the documentation.
Wouldn't this maybe affect some others that have had strange performance issues?

The new alpha would be good to get some feedback on regarding the issues here. If it is still worthwhile documenting the work around then @nicklasb can certainly look at updating that :)

Updated to use the latest version
https://plnkr.co/edit/C9mM5feGGZ0N7povA84G?p=preview

I believe this is fixed in the latest updates (alphas) for the eventual 1.0.0 release.
We remove many watchers and replace them with one-time binding. The example plunker no longer has the issue even without the config value.
Please re-open if there are still issues in these versions.
ps. @nikmartin I added the plunker to the create issue template and will try to remember to add to documentation soon, cheers :)


StarRocks external table type is base table

General Question

I am using  select * from information_schema.tables  to show all tables in databases, i see StarRocks external table type is BASE TABLE, why type is not EXTERNAL TABLE like mysql external table type?

Is this issue resolved? But, the corresponding PR is not merged, right?

Is this issue resolved? But, the corresponding PR is not merged, right?

yes


Using multiple .Order() methods when querying doesn't work as expected.

Bug report
Describe the bug
Using more than one .Order() method in a query doesn't seem to work.  Only the first .Order() method is honored.
To Reproduce
Given a model with the following structure (and a corresponding table in a Supabase project):
[Table("Contacts")]
public class Contact : BaseModel
{
	[Column("first_name")]
	public string FirstName { get; set; }

	[Column("middle_name")]
	public string MiddleName { get; set; }

	[Column("last_name")]
	public string LastName { get; set; }
}

Making the following query:
response = await client.From<Contact>()
            .Order("last_name", Ordering.Ascending)
            .Order("first_name", Ordering.Ascending)
            .Order("middle_name", Ordering.Ascending)
            .Get();

Results in a list of Contact models that are only ordered by the "last_name" column.
Expected behavior
The resulting list should be ordered by the "last_name" column, then by the "first_name" column, then by the "middle_name" column.
Screenshots
The Supabase Edge API Network Log seems to indicate the proper ?order= query parameter is being created, but it is not returning records int he correct order, as described above:
"search": "?order=last_name.asc.nullsfirst&order=first_name.asc.nullsfirst&order=middle_name.asc.nullsfirst",

System information

OS: iOS 17.0 simulator (also happens on Windows 11)
Version of supabase-csharp: 0.14.0

Additional context
This is happening in a .NET MAUI application targeting iOS, Android, Windows, and Mac Catalyst.

Here's a screenshot of the resulting Models array from the debugger.  As you can see, the first two items are in the wrong order:

I believe it's a matter of it being a comma separated query list instead of an additional order query variable! (see here).
If you want to do a PR, that'd be awesome! Otherwise I'll get to it when I can. The relevant code should be around here in Table.cs:
https://github.com/supabase-community/postgrest-csharp/blob/20240e65ba20768eddce361a4b85914e2c1b17d0/Postgrest/Table.cs#L658-L667

Thanks @acupofjose.
Ah. I see.  So, the query parameter needs to be formatted as a single, comma-separated list of order expressions, as in:
?order=last_name.asc.nullsfirst,first_name.asc.nullsfirst,middle_name.asc.nullsfirst

not as multiple chained query parameters, as in:
?order=last_name.asc.nullsfirst&order=first_name.asc.nullsfirst&order=middle_name.asc.nullsfirst

I'll try to see if I can make a PR to address it, but I can't promise anything as I've never made any edits to this codebase.  Fingers crossed.

You’ve got it! That’s the necessary change. Like I said, the PR is appreciated (we love new contributors) but if you can wait, I’m happy to get to it myself.

Understood, thanks.
Since I'm using the project, I'd like to be able to contribute.  I'll give it a shot and make a PR if I can get it working.


Remove "Body exceeded 1mb limit" error

Hi there,
I'm trying to seed my local database with 1000 users and 1000 posts.
However I'm greeted with the following error:
"Body exceeded 1mb limit"
So postgres is complaining that the seed.sql file is too big.
I've tested inserting a smaller number of rows and it works fine.
Any ideas how I could get around this?
Thanks!

Hello,
I've currently toying around with a seed file that's around 3mb which is full of mostly JSON plus a few functions for inserting the data.
I'm running 1.8.2 and I'm getting the following error while trying to seed... Error: bufio.Scanner: token too long
I also tried to seed in the dashboard (local) but the limit there is 1mb.
Would importing from a csv be the prefered method here?

Hello @sweatybridge,
I've currently toying around with a seed file that's around 3mb which is full of mostly JSON plus a few functions for inserting.
I'm running 1.8.2 and I'm getting the following error while trying to seed...
Error: bufio.Scanner: token too long.
I also tried to seed in the dashboard (local) but the limit there is still 1mb (Body exceeded 1mb limit).
Is there another way to seed large amounts of data?

Hi @eeston , we have made the scanner buffer size configurable. You might need to play around with buffer sizes to fit your seed file. Perhaps 5mb could be a good start
SUPABASE_SCANNER_BUFFER_SIZE=5mb supabase db reset

I'll need to do the same in my cloud instance of supabase too. I assume the 1mb will still be an issue on that dashboard?

Yes, the hosted dashboard has the same body size limit. We will look into extending the CLI to push your seed data to cloud instance using supabase db push. The related ticket is https://github.com/supabase/cli/issues/160

Fantastic...I'll test this at the weekend. Thanks for your help @sweatybridge

Hi @sweatybridge,
Just had a play around with this and unfortunately it still fails with the same error. Not a big deal locally but for the hosted dashboaed I think I'll end up splitting the data into multiple chunks. I assume the csv upload option is also limited to 1mb?

I assume the csv upload option is also limited to 1mb?

I just checked with our support team. The csv upload option does not impose such size limits. You should be able to upload 3mb of seed data using it.

Is there another way to seed large amounts of data?

The best way to seed a lot of data is through the COPY command:
https://www.postgresql.org/docs/current/sql-copy.html
It looks like you've go mostly JSON data - I have a small tutorial which could help with that:
https://paul.copplest.one/knowledge/tech/postgres-data.html

Thanks for the info @kiwicopple.
I ended up inserting the data in 5000row chunks...wasn't too much trouble. Good to know for next time though! 👍

hi guys, i'm facing the same error i have installed version 1.42.7 (with brew today).

@ricardosikic have you tried setting SUPABASE_SCANNER_BUFFER_SIZE=5MB or larger value before supabase start?

Hi no, I just ran supabase db remote commit and then dumped it with --data-only. Where is that line located?

It's a env var so you can do it like this
SUPABASE_SCANNER_BUFFER_SIZE=5MB supabase start

Hi ✋, didn't work. I was thinking of trying to connect to my localhost instance with pgadmin and seed the tables with an csv file.

What's the size of your seed.sql file? Could you also post the cli logs here?

hi, 4kb. But the format is like
--
-- Data for Name: objects; Type: TABLE DATA; Schema: storage; Owner: supabase_storage_admin
--

COPY storage.objects (id, bucket_id, name, owner, created_at, updated_at, last_accessed_at, metadata) FROM stdin;
d2-86ba-5ec4dfe1891d	avatars	0.4968305670106038.jpg	ed385cb4-b74e-4587-9cf7-468aed9c10e8	2023-02-12 01:02:38.420795+00	2023-02-12 01:02:38.892079+00	2023-02-12 01:02:38.420795+00	{"eTag": "\\"700f2fc6bb91124e58b5ad51cff51449\\"", "size": 268015, "mimetype": "image/jpeg", "cacheControl": "max-age=3600", "lastModified": "2023-02-12T01:02:39.000Z", "contentLength": 268015, "httpStatusCode": 200}
4-48cf-9635-e934e5083988	logo-image	logo/.emptyFolderPlaceholder	\N	2023-02-25 19:34:24.734096+00	2023-02-25 19:34:24.82976+00	2023-02-25 19:34:24.734096+00	{"eTag": "\\"d41d8cd98f00b204e9800998ecf8427e\\"", "size": 0, "mimetype": "application/octet-stream", "cacheControl": "max-age=3600", "lastModified": "2023-02-25T19:34:25.000Z", "contentLength": 0, "httpStatusCode": 200}

@ricardosikic I see, yup the error message is different from what's posted previously in this thread.
Also, is this from db dump --data-only or regular pg_dump? We are using column inserts so I'm surprised to see copy statements here.

Hi, yes the with the command and your las advice my error Error: bufio.Scanner: token too long. disappeared. It was related with Bufio error. Thanks

Hi all, I feel like I'm missing something.
Any time I run scoop install supabase I only get v1.50.4 of the CLI (apparently the latest version, updated at 4/12/2023 4:39:38 PM). Also, I can't just run SUPABASE_SCANNER_BUFFER_SIZE=5MB supabase start on Windows PowerShell.
Can anyone give a bit more context please?

Hi @jadghadry, you can set env vars on powershell like this
$Env:SUPABASE_SCANNER_BUFFER_SIZE = '5mb'
supabase start

Related new issue that has emerged -> https://github.com/supabase/cli/issues/1058
referencing here for anyone on Google who is now seeing this SUPABASE_SCANNER_BUFFER_SIZE error upon database start or reset :)

@sweatybridge Hello,  I use supabase, docker host which docker container should take this env?

which docker container should take this env?

This env is set on your host machine where supabase cli in installed. You don't need to set it inside any container.


CPS-46 Refactor imports

Put each model in its own Python file, to reduce the chance of having circular references on imports.

Codecov Report

Merging #66 into master will increase coverage by 0.75%.
The diff coverage is 99.18%.

@@            Coverage Diff             @@
##           master      #66      +/-   ##
==========================================
+ Coverage   92.05%   92.81%   +0.75%
==========================================
  Files          32       65      +33
  Lines        1574     1739     +165
==========================================
+ Hits         1449     1614     +165
  Misses        125      125

Impacted Files
Coverage Δ

connect/models/activation_tile_response.py
100% <ø> (ø)

connect/models/product_stats.py
100% <100%> (ø)

connect/models/agreement.py
100% <100%> (ø)

connect/models/param.py
100% <100%> (ø)

connect/models/event.py
100% <100%> (ø)
:arrow_up:

connect/models/product_stats_info.py
100% <100%> (ø)

connect/models/schemas.py
92.64% <100%> (ø)
:arrow_up:

connect/models/customer_ui_settings.py
100% <100%> (ø)

connect/models/configuration.py
100% <100%> (ø)

connect/models/ext_id_hub.py
100% <100%> (ø)

... and 74 more

Continue to review full report at Codecov.

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


FN: A previously identified attacker may mask a new attack

If we have an attacker that was identified and flagged because of activity on protocol A one month ago (alert was raised) and now the attacker attacks protocol B, no new alert would be raised. If protocol B subscribes to the AD to pause their protocol, they would not receive that alert.

Lets put this on the backburner; lets pay close attention to this in our recall analysis to assess whether any protocol context specific FNs are caused by this issue. If so, lets prioritize this one. But for now, lets put this as a P2.


Error message: PSO with VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST when patchControlPoints = 0

LunarG SDK <IP_ADDRESS>. In my test I use one PSO with VK_PRIMITIVE_TOPOLOGY_TRIANGLE_LIST and patchControlPoints set to 0. No error message when I set patchControlPoints to 1 with the same triangle list input assembly. Please note the different input assemblies.
Invalid Pipeline CreateInfo State: VK_PRIMITIVE_TOPOLOGY_PATCH_LIST primitive topology used with patchControlPoints value 0. patchControlPoints should be >0 and <=32. For more information refer to Vulkan Spec Section '21.7. Tessellation Pipeline State' which states 'patchControlPoints must be greater than zero and less than or equal to VkPhysicalDeviceLimits::maxTessellationPatchSize' (https://www.khronos.org/registry/vulkan/specs/1.0-extensions/xhtml/vkspec.html#VkPipelineTessellationStateCreateInfo)
My mistake is that I do attach a default  VkPipelineTessellationStateCreateInfo with patchControlPoints=0 to my PSO even if no tessellation is used. Per spec the PSO::pTessellationState should be NULL if no tessellation is used. However, the error message is misleading. I suggest to additionally check if the inputAssembly is compatible if PSO::pTessellationState is not NULL

This issue has been resolved.


"Internal server error: URI malformed" when using a percent sign in URL

Describe the bug
When migrating from CRA to vite, I hadn't updated the %PUBLIC_URL%/favicon.ico to be /favicon.ico in the index.html file. Removing %PUBLIC_URL% fixed it for me.  Seems related but not the same as #6300.
Go to this URL:
http://localhost:3000/%
In stackblitz, you can just append a percent symbol to the URL of the browser preview:

The repro URL redirects to /% and should also demonstrate the error in the console.
Reproduction
https://stackblitz.com/edit/vite-p1heqq
System Info
System:
    OS: macOS 11.6
    CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
    Memory: 1011.30 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 14.15.2 - ~/.nvm/versions/node/v14.15.2/bin/node
    Yarn: 1.22.15 - /usr/local/bin/yarn
    npm: 6.14.9 - ~/.nvm/versions/node/v14.15.2/bin/npm
  Browsers:
    Chrome: 97.0.4692.71
    Firefox: 95.0
    Safari: 15.0
  npmPackages:
    @vitejs/plugin-react-refresh: ^1.3.6 => 1.3.6
    vite: 2.8.0-beta.1 => 2.8.0-beta.1

Used Package Manager
pnpm
Logs
4:21:47 PM [vite] Internal server error: URI malformed
      at decodeURI (<anonymous>)
      at viteTransformMiddleware (/Users/../dev/map-service/health-check/node_modules/.pnpm/vite@2.8.0-beta.1/node_modules/vite/dist/node/chunks/dep-e4dc9ea2.js:52449:19)
      at call (/Users/../dev/map-service/health-check/node_modules/.pnpm/vite@2.8.0-beta.1/node_modules/vite/dist/node/chunks/dep-e4dc9ea2.js:40973:7)
      at next (/Users/../dev/map-service/health-check/node_modules/.pnpm/vite@2.8.0-beta.1/node_modules/vite/dist/node/chunks/dep-e4dc9ea2.js:40917:5)
      at /Users/../dev/map-service/health-check/node_modules/.pnpm/vite@2.8.0-beta.1/node_modules/vite/dist/node/chunks/dep-e4dc9ea2.js:52092:28
      at viteServePublicMiddleware (/Users/../dev/map-service/health-check/node_modules/.pnpm/vite@2.8.0-beta.1/node_modules/vite/dist/node/chunks/dep-e4dc9ea2.js:52131:9)
      at call (/Users/../dev/map-service/health-check/node_modules/.pnpm/vite@2.8.0-beta.1/node_modules/vite/dist/node/chunks/dep-e4dc9ea2.js:40973:7)
      at next (/Users/../dev/map-service/health-check/node_modules/.pnpm/vite@2.8.0-beta.1/node_modules/vite/dist/node/chunks/dep-e4dc9ea2.js:40917:5)
      at next (/Users/../dev/map-service/health-check/node_modules/.pnpm/vite@2.8.0-beta.1/node_modules/vite/dist/node/chunks/dep-e4dc9ea2.js:40895:14)
      at next (/Users/../dev/map-service/health-check/node_modules/.pnpm/vite@2.8.0-beta.1/node_modules/vite/dist/node/chunks/dep-e4dc9ea2.js:40895:14) (x4)
  vite:time 1.29ms /% +7s
  vite:cache [304] /@vite/client +7s
  vite:time 0.89ms /@vite/client +106ms
  vite:cache [304]<EMAIL_ADDRESS>+7ms
  vite:time 0.56ms<EMAIL_ADDRESS>+7ms

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

What is the expected behaviour here? /% is a malformed URI so the server reported it, it is still working when you make changes to a file.

In Vite 2.9.1, when the malformed URL is entered. The browser will show an error instead and will not crash the server:


fix link

Signed-off-by: kcoriordan<EMAIL_ADDRESS>What this PR does / why we need it
missed one link in app-toolkit readme!
Which issue(s) this PR fixes

Fixes: #
Describe testing done for PR

Special notes for your reviewer

LGTM


Back to dev

Coverage remained the same at 81.866% when pulling eac701a581715f8cbc1f677270f2e3f7b7d15a19 on back_to_dev into 16278cd23777cb928243f99e29f3d097d21bc749 on master.

Coverage remained the same at 81.866% when pulling eac701a581715f8cbc1f677270f2e3f7b7d15a19 on back_to_dev into 16278cd23777cb928243f99e29f3d097d21bc749 on master.


Feature: Display download progress in OneDrive folders

What's the Problem?
I'm enjoying using Files, but the indicator of the file download process in One Drive is missing, without this window that the default file explorer has, in Files it's confusing to know if the user clicked or not, if you can put it this window with download progress bar for one drive gets better.
Solution/Idea
window with download progress bar for one drive
Requirements

Display progress bar in tooltip when hovering over files
Display progress bar in status column

Files Version
Version: <IP_ADDRESS> OS Version: 10.0.19044.1586

Is this an issue in the preview version? https://files.community/download/preview

Yes

@mswr do you see the progress in a notification?


⚠ Spryr has degraded performance

In f451325, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4189 ms

Resolved: Spryr performance has improved in 2f5e241 after 23 minutes.


W7 integration test class

For viewing purposes.

Coverage decreased (-0.2%) to 54.704% when pulling 9d415f087711ede706c5697f582b2d4778ee16b8 on w7-integration-test-class into e98e12e3dfa286945e0781186366e744c23bcf4e on pytest-slow-tests-skip-marker.

Coverage decreased (-0.2%) to 54.701% when pulling e23319b55c76bef2f4d933a3cb78153917842094 on w7-integration-test-class into d876107ba3dd9271ded0beea441bdf48718037cb on pytest-slow-tests-skip-marker.

Coverage decreased (-0.2%) to 54.708% when pulling 1d5fa2e9532bb40b64aad7fe05ae4befef62ff47 on w7-integration-test-class into d876107ba3dd9271ded0beea441bdf48718037cb on pytest-slow-tests-skip-marker.


Failed Restore on Data.Analysis-Samples-HousingML notebook

On the command line, could you run dotnet try --version and report the result?


feat: mobile menu

:warning: Drawer doesn't automatically close currently. Didn't figure out why exactly yet.
Seems you need to wrap closing links in <SheetClose asChild></SheetClose>, however that messes up the styles of the navlink.

@rolznz Any idea on how to close the sheet automatically after clicking a link?

closing PR due to github bug


Added roslibjs definition

Definition for http://wiki.ros.org/roslibjs

roslibjs/roslibjs.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/roslibjs
http://bower.io/search/?q=roslibjs
others?

[X] has a test file? (roslibjs/roslibjs-tests.ts or others)
[ ] pass the Travis-CI test?

rename roslibjs/roslibjs.d.ts to roslib/roslib.d.ts
https://www.npmjs.com/package/roslib

@vvakame renaming done

fix travis ci failed. https://travis-ci.org/borisyankov/DefinitelyTyped/builds/84950967

@vvakame Damn it! I thought I comitted the fix already. Now it's fixed also for travis :+1:

thanks mate!


Pushing sample markdown file for github test 3

Hello, this is my submission for GitHub-Test3

@ztd5049 Nice work with Git Test part 3! have pulled in your branch to main and deleted your branch on the remote repo. You can now delete the zackD-GitHubTest3 in your local version of the textAnalysis-Hub.


feat: Added policy path variable to lambda module IAM role policy

Description
Added policy path variable to lambda module IAM role policy
Motivation and Context
We need the path variable for the policy created by lambda module
Breaking Changes
no breaking change
How Has This Been Tested?
I have tested and validated these changes using this branch

This PR is included in version 4.21.0 :tada: