problem with momentjs

Type of Issue
[x ] Bug Report
[ ] Feature Request

Description
I have a build error when I include momentjs.
Cannot call a namespace ('moment')

I check the other articles about momentjs but couldn't make it work.
Maybe I'm missing something
How To Reproduce
I have used the https://github.com/dherges/ng-packaged.
In my package.json I have installed momentjs:
"moment": "^2.19.1",

In my ng-package.json I have:
  "externals": {
      "moment": "moment"
    }

In my my-lib/package.json I put the peerDependencies like:
{
  "name": "@moblibs/my-lib",
  "version": "1.0.0",
  "repository": "https://github.com/dherges/ng-packaged.git",
  "author": "david<EMAIL_ADDRESS>  "license": "MIT",
  "private": true,
  "peerDependencies": {
    "@angular/core": "^4.1.2",
    "@angular/common": "^4.1.2",
    "moment": "^2.19.1"
  }
}

In my component I import it like:
import * as moment from 'moment';

When I build my my-lib I have the following error
BUILD ERROR
Cannot call a namespace ('moment')
Error: Cannot call a namespace ('moment')
    at error (C:\wksp\componentgeneration\ng-packaged\node_modules\rollup\dist\rollup.js:185:14)
    at Module.error (C:\wksp\componentgeneration\ng-packaged\node_modules\rollup\dist\rollup.js:8390:3)
    at Node.bind (C:\wksp\componentgeneration\ng-packaged\node_modules\rollup\dist\rollup.js:6419:17)
    at eachChild.child (C:\wksp\componentgeneration\ng-packaged\node_modules\rollup\dist\rollup.js:5819:34)
    at keys.forEach.key (C:\wksp\componentgeneration\ng-packaged\node_modules\rollup\dist\rollup.js:5847:5)
    at Array.forEach (native)
    at Node.eachChild (C:\wksp\componentgeneration\ng-packaged\node_modules\rollup\dist\rollup.js:5840:13)
    at Node.bind (C:\wksp\componentgeneration\ng-packaged\node_modules\rollup\dist\rollup.js:5819:8)
    at Node.bind (C:\wksp\componentgeneration\ng-packaged\node_modules\rollup\dist\rollup.js:6242:9)
    at eachChild.child (C:\wksp\componentgeneration\ng-packaged\node_modules\rollup\dist\rollup.js:5819:34)

Expected Behaviour
To be able to build my library without error with momentjs.
Version Information
@angular/cli: 1.4.9
node: 7.9.0
os: win32 x64
@angular/common: 4.4.6
@angular/compiler: 4.4.6
@angular/core: 4.4.6
@angular/forms: 4.4.6
@angular/http: 4.4.6
@angular/platform-browser: 4.4.6
@angular/platform-browser-dynamic: 4.4.6
@angular/router: 4.4.6
@angular/cli: 1.4.9
@angular/compiler-cli: 4.4.6
@angular/language-service: 4.4.6
typescript: 2.5.3

please include any version information that might be relevant, e.g. other third-party libraries
"moment": "^2.19.1",

I made it work modifying the import in my library component FooComponent
from
import * as moment from 'moment';
to
import * as momentImported from 'moment'; const moment = momentImported;
I read that in https://stackoverflow.com/questions/39519823/using-rollup-for-angular-2s-aot-compiler-and-importing-moment-js
With that said now I'm able to generate the lib, install it into my project, build my project for prod and aot enabled and start it and test it in a browse.
Of course it works without giving any errors but is this the bes way ?
thanks
O

This is the way for moment.js
Please see #163

yes but if I wollows that article it is said that to use moment in code the import should be:
import ... from 'moment';
but this should be
import * as momentImported from 'moment'; and then
const moment = momentImported;
Otherwise rollup doesn't work.

I agree with @ovione.
If you don't use the
import * as momentImported from 'moment'; const moment = momentImported;
You get the Cannot call a namespace ('moment') Error

Why is this issue closed? I am having the same issue. And adding the
"lib": {
"externals": {
      "moment": "moment"
    }
}

Does not help. I am still having the problem.
When using
import * as moment from 'moment';
I get the following
BUILD ERROR
Cannot call a namespace ('moment')
Error: Cannot call a namespace ('moment')

The other import possiblities give me errors aswell:
import moment from 'moment'
time-line/node_modules/moment/moment"' has no default export
import * as momentImported from 'moment'; const moment = momentImported;
Cannot find module 'momentImported'
Id appreciate any help. Thanks very much.

I have the same problem with using of lodash (_). I tried all solutions found across the internet.
but only this worked import * as lodashImported from 'lodash'; const _ = lodashImported;.
No changes in files (adding globals, externals, umdModuleIds) to ng-package.json) helped.
With this solution you also dont have to do any other change in any file.
So externals setup is not necessary - @matheo is not completely right.
I will be glad to find better solution because this is kinda ugly. :(

I've moved to ES6 imports like
import { findIndex } from 'lodash';
and probably I'm not using the external alias anymore.

So no one is going to fix this problem seriously between ng-packagr contributors?

@matheo The problem with your solution is that you are importing the whole lodash library, no tree shaking!

Same problem here and solved with @matheo 's solution, THANX~
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

the same issue also happens with deepmerge


Switching vars in call to geom_threedpie()  can cause error message

Mike -
One last very quick question, (if I may).
This works fine:

ggplot(mtcars) +
geom_threedpie(aes(as.factor(cyl))) +
facet_wrap(~gear, labeller = label_both) +
theme_void() + theme(legend.position="bottom")

but ,
(if I simply switch the vars cyl and gear),
then it doesn't work:

ggplot(mtcars) +
geom_threedpie(aes(as.factor(gear))) +
facet_wrap(~cyl, labeller = label_both) +
theme_void() + theme(legend.position="bottom")
returns:
Error in grid.Call.graphics(C_polygon, x$x, x$y, index) :
invalid line type

How to avoid the error message? .
What am I doing wrong?. THANKS, Mike!!

Thanks for the report @sfd99
I believe this is due to an empty factor level for cyl = 8, gear = 4.
Will investigate ...

I've just made some changes and this now works for me (b7c8b6ab).

new threed PKG v0.1.1
works perfectly now!.
Mike - you are an ACE.
Looking forward
to updates to this great pkg.
Love it!


installer

For an installer or something
https://vkbansal.me/blog/trying-eloquent-artisan-commands-outside-laravel/

https://github.com/RachidLaasri/LaravelInstaller

Create artisan command that can run internally

[ ] create database
[ ] run migrations based on environment


Don't process infinite request lengths

Would cause unbounded memory growth.
Can I haz prize?

RE: https://github.com/aspnet/KestrelHttpServer/issues/181#issuecomment-151241986

@Tratcher could you provide more context? Related, covered by, clashing etc
Or just my prize comment :) Which I think is also invalidated by creating a public PR

Just referencing our existing notes on the topic.

@blowdart

@benaadams In case your question was serious if you'd have reported it though the bug bounty rather than a github issue and we hadn't already known then it would have qualified.

@blowdart yeah, wasn't really serious and knew would invalidate but creating a public patch.
Serious follow up though; security issues post live (rc2?) would you like them addressed privately i.e. don't post a patch for it to public repo?

@benaadams Yea, once we get past RC1 escrow I'd much rather they were reported directly. And that way they'd be bounty eligible if you report through MSRC ;)

Still need to plumb in the values; but making sure I'm reading from config in the right way/place etc

Currently this isn't a show stopper as in the recommended hosting models (fronted by IIS or ngnix) they would terminate these requests at their configured limits.

Major issue is its not exact but in Vector.Size increments is that a problem?

On my machine, Vector<byte>.Count is 16. I know it could be larger on other machines, but I don't think we change our Seek algorithm to scan in smaller strides just to be able to enforce more precise limits.

Been struggling what to do with MaxUploadBytes but that can be a filter; sorting this out now.

I'm closing this, and will raise issue instead as I ended up accidentally deleting my repo with the changes in :(


App Design - Bar Graph & Filters

NOT READY FOR MERGER
Feel free to test out the first few filters on the Bar Graph.
Waiting for layout lecture to complete filters and application on bar graph.

Looks fantastic


Cannot define higher order functions in Python

This TS:
function foo(bar: (n: number) => number): number {
    return bar(3)
}

produces this PY:
def foo(bar: (number) -> number):
    return bar(3)

with these errors:
error: main.py(1,22): error TS9553: expecting ')' near `->`
error: main.py(1,25): error TS9553: expecting ':' near `number`
error: main.py(1,31): error TS9555: unexpected token near `)`
error: main.py(1,32): error TS9553: expecting <nl> near `:`
error: main.py(2,5): error TS9573: unexpected indent near `return`
error: main.py(2,12): error TS9508: can't find called function "bar"
error: main.py(2,12): error TS9516: name 'bar' is not defined

Still repros.


LZ: Final screen has error about not finding an object with undefined id

Could not find object from stage with id undefined kiigame.js:903:17

Without finding any secret stuff.

This no longer seems to happen.


Feature/issue 176/add refactor token management

Linked Issue: #176
Description / Things done in this PR:

Switched from AsyncStorage to expo secure store. More secure, better performance.
Updated/refactored axiosInstance to align with expo secure store and fix a bug where we would always get 401 if there was an error.
Added test cases. More substantial test cases should be added for axios instance later on.
Refactored the code to be more exception oriented, rather than focusing on if statements.

I know im repeating myself but we must remember to remove the console.log conatining the refresh tokens and other sensitive info. Besides that, fantastic work

Yes, of course I agree with you too. All the consoles.log will be taken out once I finish my next task/issue. That way I know everything is set up correctly.


test

Current Protocols cover image from https://currentprotocols.onlinelibrary.wiley.com/doi/abs/10.1002/cpns.76:

Screenshot from v1.6.0a2-pre


Don't always delete database on resync

Instead of deleting the database, make it default to only clearing data from each of the syncing-related tables. Offers and DID names for example should remain unless otherwise specified by the user.

https://github.com/xch-dev/sage/pull/141


series color order doesnt works

version: "0.2.11"

<px-vis-pie-chart
  series-color-order='["dv-light-green","dv-light-orange","dv-light-red"]'
  chart-data='[{"percentage":"60","x":15,"y":"IPA"},{"percentage":"20","x":1,"y":"Pils"},
{"percentage":"20","x":1,"y":"Lager"}]'
...></px-vis-pie-chart>

Code examples CodePen

The CodePen you posted seems to be showing the series in the order you specified (green, orange, red) - maybe this has been fixed? If so, please close this issue.

@randyaskin it seems work fine. close it


Added fuzzilli integration

Added Fuzzilli integration.
Build:
CC=clang python tools/build.py --fuzzilli=on --lto=off

Fuzzing:
swift run FuzzilliCli --profile=jerryscript ~/jerryscript/build/bin/jerry-fuzzilli

@nszetei Please check the errors reported by the cppcheck.

One more note: JerryScript has the policy of one commit per PR. So, when all technicalities will get sorted out, be prepared for a request to squash all commits, rebase them on latest master, and force push it to your GH branch.

@nszetei Any update on this?

@nszetei ping?

@nszetei 3rd ping?

Sorry, I don't have a time to work on this anymore, so I am closing this issue.


Feature/redux comments

This PR:

Refactors field level comment widget to subscribe to the redux commenting state directly, so as to act more similarly to how commenting needs to be handled in Draftail
Creates a new CommentableEditor component wrapping DraftailEditor as a controlled component when commenting is turned on, and adds the initial functionality for inline comments in Draftail
It does not include:
Full styling for Draftail - text contrast is inadequate for instance (this will be done in a future ticket)
Accessibility for comment annotations (though any suggestions on making comment highlights simultaneously editable and able to navigate easily to the comment in question are very welcome, I'm aware the current solution isn't yet adequate for this)
Preventing comment decoration of links or other entities, so they remain accessible (https://github.com/wagtail/wagtail/pull/6861
Darker highlights for overlapping comments (https://github.com/wagtail/wagtail/pull/6861)
Saving and loading Draftail comments from the database (future ticket)
Tests for CommentableEditor - these are needed, but it would be great to get an overall assessment here first

This should be reviewed with https://github.com/jacobtoppm/wagtail-comment-frontend/pull/7 npm linked, and this should be reviewed at the same time
One issue that needs fixing: using the object spread operator for eg props seems to have broken eslint. Is this something we're not supporting, or do we need to adjust our config?

Re tests: yep, they're needed, but given the changes we've previously needed when doing Draftail comments, it would be good to get a nod on the rest of the code first to okay the general approach

Typescript conversion all looks good to me!


RDS: restore_db_instance_from_db_snapshot is not implemented

import boto3
import boto

with moto.mock_rds2():
  rds = boto3.client("rds", region_name="us-west-2")
  rds.restore_db_instance_from_db_snapshot(
    DBInstanceIdentifier="blah",
    DBSnapshotIdentifier="blahblah",
  )

...
.tox/py36/lib/python3.6/site-packages/moto/core/responses.py:296: in call_action
    "The {0} action has not been implemented".format(action))
E   NotImplementedError: The restore_db_instance_from_db_snapshot action has not been implemented

Python 3.6.5
boto3==1.9.170
moto=1.3.8

Thanks; setting as a feature request.


Image:when create image from dockerfile, can't upload war file

In GitLab by @luotian-github on Mar 23, 2018, 10:27
imageconfig clean delete api  body to query

In GitLab by @wknet123 on Nov 8, 2019, 07:48
That's really a limitation, will fix it after this release.

In GitLab by @sokril on Nov 8, 2019, 07:48
fix backend with pr #1191

In GitLab by @yhua123 on Nov 8, 2019, 07:48
when upload war, ADD or COPY must from ./ . first step remind user correct their directory, later add validation.

In GitLab by @sokril on Nov 8, 2019, 07:48
fix with #1827

In GitLab by @sokril on Nov 8, 2019, 08:20
closed

In GitLab by @sokril on Nov 8, 2019, 08:20
assigned to @luotian-github


Get HTTP 503 when requesting SSL Certificate, besides the use of VIRTUAL_PORT

Error description:
I want to run the shlinkio/shlink:latest container on my server with your nginx reverse proxy setup.
Problem: The Letsencrypt Validation Service gets a 503 error from nginx-web container when it tries to access the ACME Challenge
Steps to reproduce

I use the following docker-compose.yaml

version: '3'

volumes:
  db:

networks:
  shlink:
  webproxy:
    external:
      name: webproxy

services:
  db:
    container_name: shlink-url-db
    image: mariadb
    restart: always
    volumes:
      - db:/var/lib/mysql
    environment:
      # from env files
      MYSQL_ROOT_PASSWORD: ${MYSQL_ROOT_PASSWORD}
      MYSQL_DATABASE: ${MYSQL_DATABASE}
      MYSQL_USER: ${MYSQL_USER}
      MYSQL_PASSWORD: ${MYSQL_PASSWORD}
    networks:
      - shlink

  shlink-url-shortener:
    image: shlinkio/shlink:latest
    container_name: shlink-url-shortener
    environment:
      # Shlink Config
      SHORT_DOMAIN_HOST: ${SERVICE_DOMAIN}
      SHORT_DOMAIN_SCHEMA: https
      # The name of a query param that can be used to visit short URLs avoiding the visit to be tracked.
      DISABLE_TRACK_PARAM: notrack
      # Reverse Proxy Settings
      VIRTUAL_HOST: ${SERVICE_DOMAIN}
      VIRTUAL_PORT: 8080
      LETSENCRYPT_HOST: ${SERVICE_DOMAIN}
      LETSENCRYPT_EMAIL<EMAIL_ADDRESS>      # DB Settings
      DB_DRIVER: mysql
      DB_NAME: ${MYSQL_DATABASE}
      DB_USER: ${MYSQL_USER}
      DB_PASSWORD: ${MYSQL_PASSWORD}
      DB_HOST: db
    expose:
      - "8080"
    depends_on:
      - db
    networks:
      - webproxy
      - shlink

The .env File for this docker-compose is

# Global Vars
SERVICE_DOMAIN=links.avil.io

# Mariadb Setup Vars
MYSQL_ROOT_PASSWORD=someMariaDBrootPW

# Shared Setup Vars between MariaDB & Shlink
MYSQL_DATABASE=shlink
MYSQL_USER=shlink
MYSQL_PASSWORD=someMySQLPW

Change the SERVICE_DOMAIN var when running these test files
Change the LETSENCRYPT_EMAIL to a personal one instead of mine.
Run docker-compose up -d to start the thingy

Expected result
The ACME Challenge can be executed successfully.
Error result
The Letsencrypt Validation Service gets a 503 error from nginx-web container when it tries to access the ACME Challenge
Comments (Things I checked and tried)

I added all necessary config to the shlink container, being:

env var VIRTUAL_HOST: ${SERVICE_DOMAIN}
env var VIRTUAL_PORT: 8080
env var LETSENCRYPT_HOST: ${SERVICE_DOMAIN}
env var LETSENCRYPT_EMAIL<EMAIL_ADDRESS>use network webproxy
expose port "8080" (besides being already exposed through the dockerfile of shlink)

I especially used the VIRTUAL_PORT env var

I deleted all previously generated folders for links.avil.io in nginx-data/certs folder to have a fresh starting point.

Suggestion
As a follow up suggestion to this issue:
Do you want to create some kind of FAQ File, which answers the most asked questions?
It's the second time now that i encounter this problem.
I fixed it the first time by re-cloning the repository and deleting the data folder.
But i don't want to re- setup the whole reverse-proxy-system each time i encounter this error.
My feeling tells me, that the system seems confused if it can't connect to the service container on the very first certificate request. But i can't proof this.
Anyway, the FAQ should have a section for

I get a HTTP error 503 when ACME Challenge is validated?
This could mean:
1. A connection error between the reverse proxy and your service container.

Is your VIRTUAL_PORT property set when service container runs on a port other than 80?

2. ...

Hello @bjesuiter...
I am really out of time at these months... but I will come back to this repo and improve a lots of things, including a couple videos... but for now this is the least I can do, try to reploy to issues...
Your settings seems to be fine... you don´t need to expose the port 8080 in order to proxy work.
Did you check the network webproxy to see if the shlink container is connected to this network?
Did you check the nginx configuration to see if the proxy created the virtual host? and if the ip address of the shlink is correct there?
It seems somehow your container is not connected to the correct network...
Also, what is the logs on the nginx-web container? and the letsencrypt container? and the shlink container if the settings are correct in the nginx conf file?

@evertramos Thank you for your suggestions, I will look into it!
Yes, I know this problem with little time, so don't feel stressed ^^

@evertramos
It works now. Here are some things I found:

The nginx-gen container sometimes exits with code 2. It won't restart, even when doing ./start.sh again => this would explain the problem with the 503, because without this container there is no proper vhost definition, if i recall correctly.

When i delete the ./data bind-mount volume, restart the reverse proxy docker-compose and restart all service container afterwards, it works again.

Let´s keep it open and if you can provide more details I will get a test environment soon.
Thanks again!!

I see this problem from time to time with nginx-gen container shutting down, usually just after I start the three containers that make up the stack. Once I restart it, it seems to stay up without issue.

I recommend spinning up Portainer.io and using it to quickly monitor the stack as it comes up. Makes it easy to see / restart as needed.

I noticed that after the last update on the proxy containers stop the nginx-gen from stopping... if anyone find this issue again, please reopen and we can study together.


updated validations.py python script.

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR
@margamanterola

@googlebot  I signed it!


enforce self.dtype as a numpy type

addresses the nbytes problem described in #9185

[X] Closes #9185

It looks like this doesn't always work given the property test error.
How about just surrounding the .nbytes call in the repr function with a try / except?

Closing because I figured out how to fix in grib2io.  It turns out to be just one line of code where I can enforce the dtype to be a numpy dtype.  Needed to stop thinking about supplying nbytes and instead make sure dtype was usable by xarray.
Appreciate the comments here and in #9185 because they were helpful in guiding me where to look.


Nx dependencies pinned versions

Current Behavior
The current version 0.7.0 points to specific versions of Nx libraries, eg. @nx/js@:16.8.1
If my project is using anything other than this specific version, npm is not happy as versions are conflicting.
Expected Behavior
Is there any chance you can make it a little more permissive, maybe pointing to ^16.8.1 so I can use a more recent version of the nx libraries in my nx workspace and still use your library (which is super helpful btw).
GitHub Repo
No response
Steps to Reproduce

Nx Report
Node   : 20.7.0
   OS     : darwin-arm64
   npm    : 10.1.0

   nx                 : 16.9.1
   @nx/js             : 16.10.0
   @nx/jest           : 16.10.0
   @nx/linter         : 16.9.1
   @nx/workspace      : 16.9.1
   @nx/cypress        : 16.9.1
   @nx/devkit         : 16.9.1
   @nx/esbuild        : 16.10.0
   @nx/eslint-plugin  : 16.9.1
   @nx/node           : 16.10.0
   @nrwl/tao          : 16.9.1
   @nx/vite           : 16.9.1
   @nx/web            : 16.9.1
   nx-cloud           : 16.4.0
   typescript         : 5.1.6
   ---------------------------------------
   Community plugins:
   @naxodev/nx-cloudflare : 0.7.0
   ---------------------------------------
   The following packages should match the installed version of nx
     -<EMAIL_ADDRESS>     -<EMAIL_ADDRESS>     -<EMAIL_ADDRESS>     -<EMAIL_ADDRESS>     -<EMAIL_ADDRESS>     -<EMAIL_ADDRESS>     -<EMAIL_ADDRESS>     -<EMAIL_ADDRESS>
Failure Logs
No response
Operating System

[X] macOS
[ ] Linux
[ ] Windows
[ ] Other (Please specify)

Additional Information
Great work, hope you can keep maintaining it

Hey, @maphe, thanks for the feedback. Yeah, I can do that. Nx is setting those dependencies for me now, so I didn't look too much there, but what you say makes sense.
I will update all dependencies now and ensure they are less strict for future dependencies.
In the meantime, you can try running the following.
npm install --legacy-peer-dep

Cool thanks. Yeah that's what I did for now, using --legacy-peer-dep, but it's gonna be nicer not to have to do it anymore. Thanks again

I will push a fix soon. I tried to also upgrade to the latest Nx and Wrangler, but I'm having some issues with wrangler dev.
Out of curiosity, how are you using the plugin?
Are you using it for working with workers or the NextJS adapter?
Thanks.

I'm using it for a worker within a monorepo, among other non-cloudflare apps and libraries.
Not sure if that's helpful info to you but I was able to upgrade my monorep to use "wrangler": "^3.11.0" and the serve command for the worker seems to still be working fine.

Thanks for the info; I'm glad it is helpful to you.
Yeah, it is only affecting a few users. I will try restarting my computer and see if that helps, lol.
I will publish the fix for this issue later today.

Sure, no worries, no rush. Thanks for the effort 👍

Hey, sorry I have a couple questions I figured I can just put them in this thread

would it be possible for the publish task to run npx wrangler deploy instead of wrangler deploy? so it relies on whatever wrangler version the package.json points to, and doesn't require the team to install wrangler globally and keep up to date
is there a way to pass an environment to the publish command? like I have some stuff in [env.production] and [env.production.vars] in wrangler.toml which I'd like to be applied on publish

As you may be able to tell, this is my first time playing around with cloudflare workers so let me know if I'm missing something.
Thanks again

Hey! No problem.

Thanks for bringing this on. I should do the same as with the serve and read wrangler from the project's node_modules. That's the way the nx teams do it. I just remembered that I needed to migrate the publish command when I migrated the serve command.
Ideally, you should be able to pass your arguments, which will be forwarded to the nx command, but I will double-check that when I start working on the publish migration PR.

But you are right. I need to align with the wrangler options on my schema. I'll be sure to have it done.
That said, you should be able to install the package without the previous problems on version 0.8.0. It should be live later tonight.

Cool thanks a lot.

It is live now!

Give it a try whenever you can, and let me know if it worked

I'm still getting some conflicts but I can't tell anymore if they're directly coming from your package or some others. There is some mention of wrangler but mostly it's esbuild causing mess.
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/esbuild
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer esbuild@"*" from<EMAIL_ADDRESS>npm ERR!   node_modules/@esbuild-plugins/node-globals-polyfill
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/wrangler
npm ERR!       dev<EMAIL_ADDRESS>from the root project
npm ERR!       2 more (@naxodev/nx-cloudflare, @cloudflare/next-on-pages)
npm ERR!   3 more (@esbuild-plugins/node-modules-polyfill, vite, wrangler)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx/esbuild
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nrwl/esbuild
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/esbuild
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/esbuild
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nrwl/esbuild
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
Anyway that's for sure better than before. Thanks for the fix 👍

Yeah, @nx/esbuild is not mine. That's coming from somewhere else.

@maphe version 0.8.0 is out, and I added support for all wrangler dev and wrangler deploy args.
Also, now the deploy (aka publish) executor reads the binary directly from the node_modules.

Perfect. Thanks a lot!


Random housekeeping

Description

Here is a few unrelated code improvements suggested by Lint and such.
Please refer to the individual commit messages when review this pull request.

Ooops, that was a mistake.


maxWidth

I may be missing the obvious but how did you intend for the maxWidth to be used?
I understand passing this in modalAttributes parameter but not seeing the connection back to the component?

Changing the max-width is not supported (yet). I ran into some issues where it did not respond well to browser resizing.


Test against Python 3.8, drop 3.5 testing

This aligns with the classifiers and discussion in #368.

Thanks!


Support nested object type to arguments in custom queries and mutations

Environment information
System:
  OS: macOS 14.4.1
  CPU: (8) arm64 Apple M1
  Memory: 179.41 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 18.19.0 - /opt/homebrew/opt/node@18/bin/node
  Yarn: 1.22.19 - ~/.nvm/versions/node/v18.18.2/bin/yarn
  npm: 10.2.3 - /opt/homebrew/opt/node@18/bin/npm
  pnpm: 8.8.0 - /usr/local/bin/pnpm
NPM Packages:
  @aws-amplify/backend: 1.0.2
  @aws-amplify/backend-cli: 1.0.3
  aws-amplify: 6.3.1
  aws-cdk: 2.141.0
  aws-cdk-lib: 2.141.0
  typescript: 5.4.5
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
Arguments support the props as type 'BaseModelField | EnumType<readonly string[]>' in custom mutation for now.
However I hope Gen2 support nested object type to the arguments.
Take the schema as an example:
// Input type
const InsertDataInput = {
  value: a.string().required(),
  name: a.string(),
  edge: a.string(),
  vertex: a.string(),
  property: a.string(),
};

// Mutation
insertData: a
    .mutation()
    .arguments({ input: InsertDataInput })
    .returns(a.ref("InsertDataResult"))
    .authorization((allow) => allow.authenticated("userPools"))
    .handler(a.handler.function(mutation)),

How to resolve:
Add nested object type to the type BaseModelField  or the object type to CustomArguments.
Alternatives:
Overriding the schema of AppSync. But it maybe be complex to override the schema.
https://docs.amplify.aws/react/build-a-backend/data/override-resources/

Hi @Hidenori14, I've marked this as a feature request. Can you explain a bit more your use case for why this would be a useful feature? Do you want to be able to pass objects with the field definitions like so?
.arguments(InsertDataInput)

This would work. The nesting within { input } seems to be the issue but just want to understand the use case better.

Hi @chrisbonifacio
Thank you for your comment.
I've already created the schema with CDK like this. I defined some types as input and used it as input for mutation because it 's easier to understand what input mutation needs.
I know Amplify Gen2 is so helpful to generate schema and deploy AppSync from the definition. For that reason, I want to request the feature.
input InsertDataInput {
  content: String
  author: String
}

type Mutation {
  insertData(input: InsertDataInput): InsertDataResult
}

I just ran into this too. In my case i like to have all arguments for a mutation under an input argument.
In Gen 1 i was able to do this:
input CreateOrganizationInput {
  key: String!
  name: String!
  introduction: AWSJSON
}

type Mutation {
  createOrganization(input: CreateOrganizationInput!): Organization
}

I would expect to be able to do the same in Gen 2 using a custom type, but currently i am not:
CreateOrganizationInput: a.customType({
  key: a.string().required(),
  name: a.string().required(),
  introduction: a.json(),
}),

createOrganization: a
    .mutation()
    .arguments({
      input: a.ref("CreateOrganizationInput").required()
    })
    .returns(a.ref("Organization"))

The GraphQL mutations autogenerated by Amplify also use this convention of having an input argument. I want my schema to be consistent. Not the autogenerated mutations taking an input argument with other nested arguments and my custom mutations not using an input argument.
But really problematic is that i'm not able to create for example a filter functionality just like there is on the autogenerated queries:
await client.models.Todo.list({
  filter: {
    or: [
      {
        priority: { eq: '1' }
      },
      {
        priority: { eq: '2' }
      }
    ]
  }
});

I see no way to create this using custom mutations, correct?

The same goes for the use case searchable / connecting OpenSearch:
In Gen 1 there was a @searchable directive to autogenerate search queries:
https://docs.amplify.aws/gen1/javascript/tools/cli-legacy/searchable-directive/
input SearchableCommentFilterInput {
  id: SearchableIDFilterInput
  organizationID: SearchableIDFilterInput
  forumID: SearchableIDFilterInput
  feedbackID: SearchableIDFilterInput
  parentID: SearchableIDFilterInput
  text: SearchableStringFilterInput
  textRaw: SearchableStringFilterInput
  pinned: SearchableBooleanFilterInput
  owner: SearchableStringFilterInput
  reportsCount: SearchableIntFilterInput
  contentStatus: SearchableContentStatusFilterInput
  hideReason: SearchableReportReasonFilterInput
  moderatorsGroup: SearchableStringFilterInput
  administratorsGroup: SearchableStringFilterInput
  createdAt: SearchableStringFilterInput
  updatedAt: SearchableStringFilterInput
  moderatedAt: SearchableStringFilterInput
  and: [SearchableCommentFilterInput]
  or: [SearchableCommentFilterInput]
  not: SearchableCommentFilterInput
}
input SearchableCommentSortInput {
  field: SearchableCommentSortableFields
  direction: SearchableSortDirection
}

type Query {
  searchComments(
    forumID: ID!
    filter: SearchableCommentFilterInput
    sort: [SearchableCommentSortInput]
    limit: Int
    nextToken: String
    from: Int
    aggregates: [SearchableCommentAggregationInput]
  ): SearchableCommentConnection
}

This way you were able to search for content like this:
query SearchPosts {
  searchPosts(filter: { title: { match: "Stream" } }) {
    items {
      id
      title
    }
  }
}

In Gen 2 we have no out-of-the-box solution for search. This article mentions how to connect OpenSearch in a Gen 2 application: https://docs.amplify.aws/vue/build-a-backend/data/custom-business-logic/search-and-aggregate-queries/
But without the support for nested arguments / custom types there is no way to create search queries that have the same functionality as the example above with Gen 1. You can't have dynamic search arguments since there is no way to have nested arguments.

@thomasoehri
You're right. If adding nested object type to the type BaseModelField, CloudFormation failed because Amplify Gen2 automatically generated schema and now Gen2 cannot create right nested schema like input.
CloudFormation failed like this.
The CloudFormation deployment has failed.
Caused By: ❌ Deployment failed: Error: Internal Failure while saving the schema.


Build fails on latest rust nightly

Hi!
I tried building this locally using the instructions in the readme to get rust nightly with rustup (I don't really know anything about building things with rust).
I got the following build errors:
error[E0277]: the trait bound `EventId: std::convert::From<&std::string::String>` is not satisfied
   --> /home/grdryn/.cargo/registry/src/github.com-1ecc6299db9ec823/ruma-identifiers-0.11.0/src/lib.rs:697:21
    |
697 |                     $crate::$name::try_from(&string)
    |                     ^^^^^^^^^^^^^^^^^^^^^^^ the trait `std::convert::From<&std::string::String>` is not implemented for `EventId`
...
763 |     diesel_impl!(EventId);
    |     ---------------------- in this macro invocation
    |
    = note: required because of the requirements on the impl of `std::convert::TryFrom<&std::string::String>` for `EventId`

error[E0277]: the trait bound `RoomAliasId: std::convert::From<&std::string::String>` is not satisfied
   --> /home/grdryn/.cargo/registry/src/github.com-1ecc6299db9ec823/ruma-identifiers-0.11.0/src/lib.rs:697:21
    |
697 |                     $crate::$name::try_from(&string)
    |                     ^^^^^^^^^^^^^^^^^^^^^^^ the trait `std::convert::From<&std::string::String>` is not implemented for `RoomAliasId`
...
764 |     diesel_impl!(RoomAliasId);
    |     -------------------------- in this macro invocation
    |
    = note: required because of the requirements on the impl of `std::convert::TryFrom<&std::string::String>` for `RoomAliasId`

error[E0277]: the trait bound `RoomId: std::convert::From<&std::string::String>` is not satisfied
   --> /home/grdryn/.cargo/registry/src/github.com-1ecc6299db9ec823/ruma-identifiers-0.11.0/src/lib.rs:697:21
    |
697 |                     $crate::$name::try_from(&string)
    |                     ^^^^^^^^^^^^^^^^^^^^^^^ the trait `std::convert::From<&std::string::String>` is not implemented for `RoomId`
...
765 |     diesel_impl!(RoomId);
    |     --------------------- in this macro invocation
    |
    = note: required because of the requirements on the impl of `std::convert::TryFrom<&std::string::String>` for `RoomId`

error[E0277]: the trait bound `RoomIdOrAliasId: std::convert::From<&std::string::String>` is not satisfied
   --> /home/grdryn/.cargo/registry/src/github.com-1ecc6299db9ec823/ruma-identifiers-0.11.0/src/lib.rs:697:21
    |
697 |                     $crate::$name::try_from(&string)
    |                     ^^^^^^^^^^^^^^^^^^^^^^^ the trait `std::convert::From<&std::string::String>` is not implemented for `RoomIdOrAliasId`
...
766 |     diesel_impl!(RoomIdOrAliasId);
    |     ------------------------------ in this macro invocation
    |
    = note: required because of the requirements on the impl of `std::convert::TryFrom<&std::string::String>` for `RoomIdOrAliasId`

error[E0277]: the trait bound `UserId: std::convert::From<&std::string::String>` is not satisfied
   --> /home/grdryn/.cargo/registry/src/github.com-1ecc6299db9ec823/ruma-identifiers-0.11.0/src/lib.rs:697:21
    |
697 |                     $crate::$name::try_from(&string)
    |                     ^^^^^^^^^^^^^^^^^^^^^^^ the trait `std::convert::From<&std::string::String>` is not implemented for `UserId`
...
767 |     diesel_impl!(UserId);
    |     --------------------- in this macro invocation
    |
    = note: required because of the requirements on the impl of `std::convert::TryFrom<&std::string::String>` for `UserId`

error: aborting due to 5 previous errors

error: Could not compile `ruma-identifiers`.
warning: build failed, waiting for other jobs to finish...
error: build failed

Thank you for reporting, this seems to be due to a change in Rust regarding the from and try_from trait. I'm working on a fix.

Cool, thanks, I look forward to trying this out! :)

I just merged a branch that should fix the latest nightly errors. I also updated the travis configuration to not use a docker container anymore, as this should help to spot problems with updates on nightly earlier. It increases the built time on the CI, but that should not be a problem.
It also leads to a wrong test coverage, but I'll fix that in another PR.

Cool, thanks, I look forward to trying this out! :)

That great to hear, but make sure you're not trying in a production environemement, because it will pollute your homeserver with aliases that will potentially change in the future. I'm still trying to figure out what's the right way to store state (in a separate database or as part of the room).

Closing this, since this was fixed by #41. Feel free to reopen if there are still problems.


Create secure in-memory directory on macOS

Fixes #29
Note: Untested on MacOS so far. May need some tweaking.

Tested on macOS. After a few small fixes it works fine for me.

Signal handling is IMHO out of scope for this PR, but we should have a look at that later.


add numShards to job config

Codecov Report

Merging #227 into master will decrease coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #227      +/-   ##
==========================================
- Coverage   69.25%   69.24%   -0.02%
==========================================
  Files         155      155
  Lines       20701    20701
==========================================
- Hits        14337    14334       -3
- Misses       5263     5264       +1
- Partials     1101     1103       +2

Impacted Files
Coverage Δ

subscriber/common/rules/job_config.go
72.78% <ø> (ø)
:arrow_up:

subscriber/common/message/message_parser.go
53.93% <100%> (ø)
:arrow_up:

metastore/schema_fetch.go
74.46% <0%> (-6.39%)
:arrow_down:

datanode/peer_source.go
51.25% <0%> (-3.75%)
:arrow_down:

subscriber/common/job/driver.go
71.98% <0%> (+2.12%)
:arrow_up:

Continue to review full report at Codecov.

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


Please add a note for WPJed windows 10 devices dsregcmd output

=========
Dsregcmd /status --> AzureADPRT only shows status for AADJ/HAADJ PRT not for WPJ PRT

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

ID: 3d3bcf99-60c3-876c-c421-3351e507a81b
Version Independent ID: c906978e-acf2-462c-d7ff-20221872a793
Content: Primary Refresh Token (PRT) and Azure AD - Azure Active Directory
Content Source: articles/active-directory/devices/concept-primary-refresh-token.md
Service: active-directory
Sub-service: devices
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@NagaCSC Thanks for your feedback! We will investigate and update as appropriate.

@NagaCSC can you please clarify on what you are looking to change on the Microsoft Doc here? I'm not sure where you would like to add : dsregcmd in regards to the article.

Hi Frank,
How do we verify windows 10 device has PRT or not. via dsregcmd /status. which was not there in this article. I sync with Ravi and he will update the doc in next release with suggested updates.

After further discussion in regards to this issue, it looks like Ravi Vennappusa is also looking into this issue,

We'll add a note about ignoring the PRT section for AAD registered devices

#please-close


Minor spelling corrections / clarifications + resolve issue #19778

I want to clarify something about using global step with tf.contrib.model_pruning, which I think is not clearly explained (and lead to me not seeing my mistake for 3 weeks). Also, address the illegal summary names from issue #19778.

The following code will give you #19778:
import tensorflow as tf
import tensorflow.contrib.model_pruning as pruning

tf.reset_default_graph()

# Global step.
global_step = tf.train.get_or_create_global_step()

# Input data.
data = tf.get_variable('data', shape=[1, 10, 10, 1], initializer=tf.random_normal_initializer())

# Single conv layer with pruning mask.
outputs = 1
kernel = [2, 2]
conv = pruning.masked_conv2d(data, outputs, kernel)

with tf.Session() as sess:

    # Pruning hyperparameters.
    pruning_hparams = pruning.get_pruning_hparams().parse("")

    # Pruning object.
    pruning_obj = pruning.Pruning(pruning_hparams, global_step=global_step)

    # Pruning summaries.
    pruning_obj.add_pruning_summaries()

    # Summary.
    summary_writer = tf.summary.FileWriter('.', graph=sess.graph)


move adding to actions to the plugin definition phase

add_actions should not be called here: https://github.com/senecajs/seneca-github-provider/blob/main/src/github-provider.ts#L83
Instead it should occur here: https://github.com/senecajs/seneca-github-provider/blob/main/src/github-provider.ts#L27
You need a reference to an initialized Octokit instance of course, but you have it already:
https://github.com/senecajs/seneca-github-provider/blob/main/src/github-provider.ts#L23
Seneca completes are plugin prepare actions before executing anything else, so no entity actions will execute until octokit is ready.

Hey Richard. I linked a PR to this issue. I couldn't accomplish this task exactly the way we talked because I didn't find a proper way to get around the needing of the callback here: https://github.com/senecajs/seneca-github-provider/blob/main/src/github-provider.ts#L44
I tried a alternative path: resolving the callback inside the actions called by seneca.


Update licensing info

According to @bhousel in #3207, the mention of BSD "is throwback to when the iD source code included our own custom d3 bundle, which we don't do anymore."
Also, add extension to the license file, to match the other standard text files at the root of the repo.

Thank you!


BUGFIX: Supplier framework with null declaration

When a supplier first registers interest in a framework the declaration
is null.  This handles the case
when it is null.

:+1:


Random walk due to vertical diffusivity

In the current version of Parcels, is there a method for implementing random walk due to vertical diffusivity? I am working with NEMO AMM7 data and have the necessary vertical diffusivity values but have been unable to find a way of implementing them so far.
Thanks for your help

Hi @charlotteclubley,
A random walk can definitely be implemented in a kernel. This study by Ross and Sharples 2004 shows a nice way to implement the random walk. In parcels, you can add the diffusivity field to your FieldSet and a random number generator is available as ParcelsRandom, i.e. you can import it as:
from parcels import ParcelsRandom
The challenge currently is the derivative needed in Eq. 1 from Ross and Sharples. There is development of this in PR #979 , but this is not finished yet. The easiest solution is to compute the derivatives of the entire diffusivity field in preprocessing and load those as another Field.
Let me know if that helps!


kube-dns & kubernetes-dashboard pods crashing on Kubernetes 1.9

Is this a request for help?:
NO
Is this an ISSUE or FEATURE REQUEST? (choose one):
ISSUE
What version of acs-engine?:
Version: v0.12.0
GitCommit: 1d332296
GitTreeState: clean

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.9
What happened:
When deploying hybrid (Linux/Windows) Kubernetes cluster, kube-dns and kubernetes-dashboard pods land in CrashLoopBackOffstate:
$ kubectl get pods --namespace=kube-system
NAME                                            READY     STATUS             RESTARTS   AGE
heapster-7768c79696-79bxl                       2/2       Running            0          34m
kube-addon-manager-k8s-master-18208945-0        1/1       Running            0          33m
kube-apiserver-k8s-master-18208945-0            1/1       Running            0          33m
kube-controller-manager-k8s-master-18208945-0   1/1       Running            0          33m
kube-dns-v20-55498dbf49-rpzhb                   1/3       CrashLoopBackOff   20         34m
kube-dns-v20-55498dbf49-zpgz4                   1/3       CrashLoopBackOff   20         34m
kube-proxy-5lnt9                                1/1       Running            0          34m
kube-proxy-xnvl6                                1/1       Running            0          34m
kube-scheduler-k8s-master-18208945-0            1/1       Running            0          33m
kubernetes-dashboard-868965c888-ghgnz           0/1       CrashLoopBackOff   10         34m
tiller-deploy-589f6788d7-lr4h5                  1/1       Running            0          34m

This prevents me from using Kubernetes dashboard.
Service discovery within the cluster is impossible.
What you expected to happen:
kube-dns and kubernetes-dashboard to be in Running state.
How to reproduce it (as minimally and precisely as possible):
acs-engine emplate:
{
  "apiVersion": "vlabs",
  "properties": {
    "orchestratorProfile": {
      "orchestratorType": "Kubernetes",
      "orchestratorRelease": "1.9"
    },

    "masterProfile": {
      "count": 1,
      "dnsPrefix": "k8s-sl31065",
      "vmSize": "Standard_D2s_v3"
    },
    "agentPoolProfiles": [
      {
        "name": "linuxpool1",
        "count": 1,
        "vmSize": "Standard_D2s_v3",
	      "storageProfile": "ManagedDisks",
        "availabilityProfile": "AvailabilitySet",
        "osType": "Linux"
      },
      {
        "name": "windowspool1",
        "count": 1,
        "vmSize": "Standard_D2_v3",
        "storageProfile": "ManagedDisks",
        "OSDiskSizeGB": 100,
        "availabilityProfile": "AvailabilitySet",
        "osType": "Windows"
      }
    ],

    "linuxProfile": {
      "adminUsername": "[REDACTED]",
      "ssh": {
        "publicKeys": [
          {
            "keyData": "[REDACTED]"
          }
        ]
      }
    },
    "windowsProfile": {
      "adminUsername": "[REDACTED]",
      "adminPassword": "[REDACTED]"
    },
    "servicePrincipalProfile": {
      "clientId": "[REDACTED]",
      "secret": "[REDACTED]"
    }
  }
}

Anything else we need to know:

For anyone looking, #2174 fixes the issue if you use networkPolicy azure.

Yes. If you want to use networkPolicy azure, please use #2174 . It should be merged soon.

Yes, indeed, the principle didn't have "Contributor" role on the resource group.
After setting that, all system pods were running without problems.

Thanks for confirming your fix @magnock FYI v0.13.0 release includes #2174 above.

Thank you @jackfrancis, I used v0.13.0 and all pods are running good, but we still have the internal windows DNS problem, windows containers can't resolve hostnames and can't access Internet. I've seen some quick fixes :

using container from this image : microsoft/windowsservercore:1709_KB4074588
or
by setting DNS client using powershell
$adapter=Get-NetAdapter Set-DnsClientServerAddress -InterfaceIndex
$adapter.ifIndex -ServerAddresses <IP_ADDRESS>,<IP_ADDRESS> Set-DnsClient -InterfaceIndex
$adapter.ifIndex -ConnectionSpecificSuffix "default.svc.cluster.local"

Are theses changes already merged to master ? any new release that will include that ?
Thx

@magnock Why do you consider using microsoft/windowsservercore:1709_KB4074588 a quick fix?

@msorby There is some discussion about that on https://github.com/Azure/acs-engine/issues/2027, But it doesn't really help.
If I restart my cluster, I need to check the DNS containers IPS, rebuild windows image with new DNS IPs and then redeploy windows containers :( (OR using env variables)


Usability feedback from modelling Interchain Security

I recently ported the Interchain Security TLA+ specification from @Kukovec to Quint. This worked fairly well and was a successful endeavor so far.
Previously, I also attempted to replicate the difftest model https://github.com/cosmos/interchain-security/blob/main/tests/difference/core/model/src/model.ts (a reference implementation of ICS in Typescript) in Quint. This attempt was aborted, as it turned out this was more difficult than anticipated.
I want to collect some painpoints I had while working with Quint:

Error messages from the parser for effect mismatches are hard to digest. For example, error messages for effect mismatches look like this:

Expected [runningValidatorSet,outstandingPacketsToConsumer,outstandingPacketsToProvider,receivedMaturations,maturationTimes] and [outstandingPacketsToProvider,receivedMaturations,maturationTimes,outstandingPacketsToConsumer] to be the same
Trying to unify entities ['runningValidatorSet', 'outstandingPacketsToConsumer', 'outstandingPacketsToProvider', 'receivedMaturations', 'maturationTimes'] and ['outstandingPacketsToProvider', 'receivedMaturations', 'maturationTimes', 'outstandingPacketsToConsumer']
Trying to unify Read[v1121] & Update['runningValidatorSet',
....

I'd suggest prefacing the messages by printing the variables that occur in one but not the other. Without such a diff, it's very hard to spot which variables differ among eg 10 variables that appear in both. It's also challenging to see which side of an action is which here, though I suspect that is harder to solve and I don't have a concrete suggestion how to display this better.

The parser seems to hang sometimes - I had to restart VSCode a few times to get it to restart. I unfortunately didn't keep a concrete example, so this might not be very helpful, but I occasionally got the parser to just stop doing things. This might be a VSCode problem, I had that with other tools, too, but with the Quint parser it happened every couple of hours.

When there is an error in the file, I had the experience that the parser becomes unreliable for the whole file.
For example, when I wrote an action half-way, realized I needed to change something else in the code to make the action work, and left an action half-written with a syntax error and tried to change some other code before continuing,
completely unrelated parts of the code started giving error messages.
This seems to be handled better by parsers for other languages, where typically errors somewhere in the code seem much more constrained to one location and you wouldn't expect e.g. a type mismatch in one class cause an unrelated error to pop up in another class.

The hover tooltips are super helpful to see types and effects, but sometimes they don't show me what I'd expect.
For example, in a block like this:

evidences.forall(evidence => true)

hovering over evidence showed me the definition of forall, when I would have expected to see the type of evidence.

In the REPL, Is there a built-in way to get a dump of the whole state? Of course it's possible to define a val for it, but this seems like a common enough use-case that it would be nice to have it built-in.

When testing, I sometimes got an assertion failure. In the REPL, is there a way to just rerun the part of the test until the failure automatically, so that I can take a look at the state? Of course I can rerun the action, but I might not hit the same failure. verbosity=5 is not sufficient for what I want, since it doesn't print the full state. Making a verbosity config that prints all the variables might also be a nice idea.

A bit of a vague painpoint I had is the inherent 'modify-once' nature of Quint (this would also hold in TLA+, btw, nothing inherent to Quint here). When I tried to replicate the difftest model that is very close to the implementation, I ran into the issue that e.g. in EndBlock, the same data structure is modified multiple times, e.g. imagine the staking module processes a change in the validator set, but the slashing module also removes a validator. In a standard programming language, this is easy - just run the staking module EndBlock, then the slashing module EndBlock. In Quint, both of these would have to modify the same variable. Optimally, I'd want an EndBlock action in both modules, but since they can't modify the same variable, the workarounds are a bit weird - the best thing I came up with was splitting the logic for modifying the validator set out from the action and calling it separately, but this doesn't feel very nice to me, since now the "caller" is burdened by the logic of reconciling the different changes to the validator set. It might be nice to have an example that shows how to handle something like this, maybe similar to the 'protocol anatomy' showing some best practice for this.

======
Despite the pain points, I'm very happy to be using Quint instead of TLA+ for this - writing the language is a breeze most of the time, and reading it is a pleasure. If you have any questions about the writeup, please feel free to reach out - it's hard to precisely convert these things into words at times, so I'm happy to have a chat if it helps!

Thanks a lot for the detailed feedback @p-offtermatt! We will definitely process it into smaller chunks :)


MicroBitButton.h missing in MicroBit.h when DEVICE_BLE=0

When building pxt-microbit with DEVICE_BLE=0 against this repo, we get a compile error as MicroBitButton is not defined.  I traced this down to the following issue in MicroBit.h in this repo:

MicroBitButton.h is not included directly in MicroBit.h, but only indirectly by MicroBitButtonService.h, which is only included in MicroBit.h when DEVICE_BLE=1

Thanks @tballmsft!
Easy one - can we squeeze a fix for this into our planned next release @JohnVidler?

I suspect MicroBitButton.h was only included in the BLE code because it was in the V1 code, and it's really a mistake: MicroBitButtonService doesn't seem to use MicroBitButton and should be using DEVICE_ macros rather than MICROBIT_.
MicroBitButton is in the compat folder and only occurs here
https://github.com/microsoft/pxt-microbit/blob/2dccb52fcfe9edd6a420cfd5718c4e80452a03ad/libs/core/pins.cpp#L647

It's not critical to fix this in lancaster, as we have a solution for pxt-microbit. In libs\core\pxtcore.h, I also see
#ifndef __PXTCORE_H
#define __PXTCORE_H

#include "MicroBit.h"
#include "MicroBitImage.h"
#include "ManagedString.h"
#include "ManagedType.h"

So clearly MicroBit.h wasn't designed to include everything we need in pxt-microbit, across V1 and V2, but to provide compat with V1.

Nevertheless, it's odd to have MicroBitButton.h appear in MicroBit.h for one build and not for another.

Okay, so it looks we just need to include MicroBitButton.h into MicroBitCompat.h, as MicroBitCompat.h is already included in MicroBit.h.

Fixed in v0.2.65 by including MicroBitButton.h in MicroBitCompat.h:  https://github.com/lancaster-university/codal-microbit-v2/commit/0c67e627f29eaaef1c7821710eebc75b73cd0441


121 odb elconnectivity performance

Fix #121

@DKreuter I made the assumption that the maximum number of nodes an element can have is 20. Is that correct? Please confirm or correct. Thanks.

If we assume only 2nd order elements (highest order implemented in Ansys, Abaqus afaik), we can set the number to 20. From my point of you we should proceed with the max number


Add cluster DNS domain value

When the Kubernetes cluster isn't using the default "cluster.local" DNS domain, deployments fail. This PR allows the DNS domain to be configurable, leaving "cluster.local" as the default.

Thank you for fixing this, LGTM

LGTM! Thank you for the contribution


OPLIST for m-mutex.h elements

I understand that I'm trying to do OOP using C and m*lib containers as base (data + common methods). Maybe I'm going too far...
More or less with the same motivations on #34 , I need to embed an m_mutex_t and an m_cond_t into a tuple. I'm saying it is related because the buffer is indeed a data-structure plus some mutex/condition variables to provide its blocking/atomic features. Now I need a blocking/atomic behavior for a dictionary so I wanted to embed all the necessary (dictionary, mutex, condition variable) into a tuple. I'm stuck because the latter are intended to be used as global variables (like buffer until yesterday).
Tell me if I'm going to be cumbersome and/or if what I prospect has flaws.

I am seeing some issues for SET and INIT_SET?
What will be the specification of these operators for such type?

I see the semantic issue. On the practical scenarios I was thinking I never would need to copy such structures. Generalizing a condition variable doesn't got a state (expect than the list of blocked threads but it would be too complex to manage and not so useful); the mutex got a state and, forcing the concept, it could be copied. Again, just an exercise to force the semantic: not practical use.
Dummy SET and INIT_SET could be fine.
If you don't like the idea, maybe I can just define an OPLIST for m_mutex_t and m_cond_t just to make it works for me (hint?). I was just thinking that if you provide atomic/blocking structures like the m-buffer.h elements, how I could extend such properties to other data-structures. That's what I need.

Thinking about this: I don't really need the nestability of mlib containers to group such kind of atomic/blocking objects. I can still get any kind of mlib container and group it with the necessary mutex/cond to make it atomic/blocking by means of a plain structure. I will never copy/nest it.
Maybe there could be some kind of general approach to get atomicity on the operations on a container.  A general approach to the blocking mechanism looks more difficult.
Feel free to close this if don't see a more general feature for the m*lib framework.

I don't think providing the oplists for mutex or conditional variables is the right way. They cannot be copied. They are linked with the protected data: we cannot access the protected data method without using the lock. You will need to write all the access code yourself, and some of the operator (like _get) cannot be encapsulated without a change of the function prototype (we need to copy the data we get, as the data may be changed by another thread once we release the lock).
I'm currently thinking about the general approach and how to do it. I think an oplist based transformation may do the job (kind of if the container provided PUSH, I can provide a protected PUSH method). Some method will need some changes (like GET) as seen above. Some others may need to lock both arguments to work (to copy a container into another) which may result in deadlock if not done properly.
Doing so, I have analyzed the use of the operators in M*LIB (in order to uniformize their use) and performed an API incompatible change (!): _remove for dict & B+Tree has been renamed into _erase in order to differentiate properly with _remove for Array & List that take incompatible arguments (I kept a compatibility layer, you'll get deprecated warnings about their usage).

I have committed the new module "m-protect.h" that create a new container that automatically add mutex lock on operations of the given containers.
Example:
ARRAY_DEF(array1, int)
PROTECT_DEF(parray1, array1_t, ARRAY_OPLIST(array1))

DICT_DEF2(dict1, int, int)
PROTECT_DEF(pdict1, dict1_t, DICT_OPLIST(dict1))

(If you have a better name for the module, feel free to propose).
Beware: I haven't fully tested it yet, not all operators are defined and its oplist is not defined so it cannot be chained.

By the way, I don't understand why you wanted a conditional variable for protected dictionary access?

I was speaking of conditional variable because I was thinking on a way to make insert/extract, push/pop operations blocking when necessary.
For the name: at the moment it provides only mutex locking so an alternative could be ATOMIC_DEF. It is in some way related to m-atomic.h, right?

Ok
Currently, there is no way for insert / push to be blocking as the container don't have a fixed maximum size (there is a planned change to support such feature through custom allocation, but it is not available yet).
So only _get, _erase & _pop can be blocking.
I don't want to add such container in m-atomic.h: this header shall define only what is defined by stdatomic.h. It only exists due to C++ and non C11 compilers.

I have renamed the header as m-concurrent.h and the macro as CONCURRENT_DEF.
blocking methods are available:

bool name ## _get_blocking(base_type *p, concurrent_t out, key_t key, bool blocking);
bool name ## _pop_blocking(base_type *p, concurrent_t out, bool blocking);
There is no blocking variant for _push & _set as explained before.

oplist & formal tests remain to be done.
Could you tell me if it answers your needs?

I'm glad it answers your needs!
Non concurrent container (circular) buffer already exist: you can use dual-push-list or deque for this. However, they need a specialize oplist to provide such interface properly. Their exported oplist provide a stack interface (PUSH=push_back and POP=pop_back), whereas they need a queue interface (PUSH=push_front and POP=pop_back). You can override the operator PUSH when using DEQUE_OPLIST in the meantime.
Note that the provided fixed size buffer (m-buffer) is likely to be faster than a concurrent of deque for communicating data.
Pretty much any container is supported by m-concurrent at the moment. I tested list, list-dual-push, array, deque, deque and tuple. Probably also dict_set, dict_oa, dict_store, b+tree, rbtree work fine (otherwise it is a bug).

Non concurrent container (circular) buffer already exist: you can use dual-push-list or deque for this. However, they need a specialize oplist to provide such interface properly. Their exported oplist provide a stack interface (PUSH=push_back and POP=pop_back), whereas they need a queue interface (PUSH=push_front and POP=pop_back). You can override the operator PUSH when using DEQUE_OPLIST in the meantime.
Note that the provided fixed size buffer (m-buffer) is likely to be faster than a concurrent of deque for communicating data.

Yes, I know I could use the linked list to get an unlimited stack or queue data-structure but, as you suggest, this implies different level of efficiency.
I was thinking that now the buffer (and variants in m-buffer.h) is now a specific case of the, more general, approach to use an ordinary (read unsafe against concurrency) container and make it concurrency secure using the m-concurrent.h additional layer. I would be a unifying approach and you could deprecate the whole m-buffer.h.

I was looking at the code of _get_blocking method in m-concurrent.h: am I wrong or if blocking=false the code doesn't get anything...? The same for _get_blocking.

:(
I have fixed this. Thanks for your report.

oplist & formal tests remain to be done.

What do you mean with "oplist remain"? Should I expect a CONCURRENT_OPLIST macro so I can embed a concurrent container into another? If I understood your arguments on "SET/INIT_SET methods vs mutex/cond" it should not be possible/make-sense, right? In such case I will group several concurrent containers using an ordinary structure.

What do you mean with "oplist remain"? Should I expect a CONCURRENT_OPLIST macro so I can embed a concurrent container into another?

Yes I plan to add a CONCURRENT_OPLIST macro.

If I understood your arguments on "SET/INIT_SET methods vs mutex/cond" it should not be possible/make-sense, right?

What I mean is you cannot copy the lock without copying the protected data together. Once you have a proper container that handle both (like the concurrent one), you can copy all the container. The methods _init_set & _set are already written for container and these methods lock the mutex while copying the data and release them afterwards.

Could I suggest to include the classical _get method too in a concurrent container so, If one is interested only in getting the mutual exclusive access (without any blocking behavior), it is sufficient to change the container definition (with the double _def macro) but it is not necessary to search/replace any _get(...) invocation with a _get_blocking(..., false) one?

I am not sure to understand what you want.
The _get method has an issue for concurrent container: since this method returns a pointer to the internal data of the requested element within the container, this pointer may become invalid due to an update of the container in another thread (for example, if the array is reallocated). As such, I think that the _get method is not doable in a safe way for concurrent container. This explains the reason of having _get_copy & _get_blocking methods.

The _get method has an issue for concurrent container: since this method returns a pointer to the internal data of the requested element within the container, this pointer may become invalid due to an update of the container in another thread (for example, if the array is reallocated). As such, I think that the _get method is not doable in a safe way for concurrent container. This explains the reason of having _get_copy & _get_blocking methods.

Ok, now it is clear.

Trying to replace non-concurrent variant of a dict with the new concurrent secure one: it looks that in the _set_at the last parameter is not defined as const (as in dict). The const makes sense here.

Is it a bug or I'm using the new CONCURRENT_OPLIST macro in a wrong way?
#include "m-concurrent.h"
#include "m-dict.h"
#include "m-string.h"
#include "m-tuple.h"

DICT_DEF2(string_pool, string_t, string_t)
#define STRING_POOL_OPLIST                                                     \
    DICT_OPLIST(string_pool, STRING_OPLIST, STRING_OPLIST)
#define M_OPL_string_pool_t() STRING_POOL_OPLIST

CONCURRENT_DEF(string_pool_ts, string_pool_t, STRING_POOL_OPLIST)
#define STRING_POOL_TS_OPLIST                                                  \
    CONCURRENT_OPLIST(string_pool_ts, STRING_POOL_OPLIST)
#define M_OPL_string_pool_ts_t() STRING_POOL_TS_OPLIST

int main() {
    M_LET(pool, string_pool_ts_t) {
        //
    }
}

$ gcc -I custom-libs/include test/test-mini.c
In file included from custom-libs/include/m-concurrent.h:28,
                 from test/test-mini.c:1:
test/test-mini.c: In function ‘main’:
custom-libs/include/m-core.h:661:52: error: pasting "M_TOBOOLI_" and "(" does not give a valid preprocessing token
 #define M_BOOL(x)                   M_RET_ARG2(M_C(M_TOBOOLI_, x), 1, useless)
                                                    ^~~~~~~~~~
custom-libs/include/m-core.h:107:29: note: in definition of macro ‘M_C2I’
 #define M_C2I(a, ...)       a ## __VA_ARGS__
...

Fixed in master.

 :)
I think I will need to do something ugly to fix it (like for buffer). :(

Fixed in master.

Doc has been committed. So far, I think everything has been done for this evolution.


When refresh the composer web, all lg files will be appended an empty line

Describe the bug

When refresh the composer web, all lg files will be appended an empty line
No SHA is shown

Version

ab052fc806178f7c88d5f5102b4f8dfc22bac926
Browser

[x] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[x] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

It comes from a helper function help migrate single common.lg to multiple lg, this helper function would be disabled soon.

addressed via https://github.com/microsoft/BotFramework-Composer/pull/2164


New version on NonGNU ELPA

Please consider bumping the ;; Version: header so that a new version is released on NonGNU ELPA.
The latest version is 1.0.5: https://elpa.nongnu.org/nongnu/rust-mode.html

Released a new version today.


Using data from training

Hello again,
I have had an issue with training before which with your great help I surpassed it and now encounter a new issue regarding the matter.
I have trained a new set of wav files and gathered and saved specified weights with the command:
CUDA_VISIBLE_DEVICES="" python main.py --init_noise_std 0. --save_path segan_allbiased_preemph \                                           --init_l1_weight 100. --batch_size 100 --g_nl prelu \                                           --save_freq 50 --preemph 0.95 --epoch 86 --bias_deconv True \                                           --bias_downconv True --bias_D_conv True
Now I'm trying to regenerate a wav file with the command:
CUDA_VISIBLE_DEVICES="" python main.py --init_noise_std 0. --save_path segan_allbiased_preemph \                                        --batch_size 100 --g_nl prelu --weights segan_allbiased_preemph --preemph 0.95\                                       --test_wav 'Test\ Folder/Source/split_008F01001.WAV.wav' --clean_save_path 'Test\ Folder/Target'
And encounter the error saying:
Unable to open table file segan_allbiased_preemph/train: Failed precondition: segan_allbiased_preemph/train: perhaps your file is in a different file format and you need to use a different restore operator?
Where did I go wrong and how can I do it correctly?

Sorry NOW I get the concept I have to specify the checkpoint. I always go head first to asking then try to look around the code.

can you tell me how to solve the problem @amhajavi ?


Form Title is not validated

DataError: (raised as a result of Query-invoked autoflush; consider using a session.no_autoflush block if this flush is occurring prematurely) (psycopg2.DataError) value too long for type character varying(200)

Created a PR to fix the same : https://github.com/levlaz/braindump/pull/92

Fixed in https://github.com/levlaz/braindump/pull/92


Are IP addresses static or will they ever change?

Wondering if these  IP addresses static or will they ever change?  If they do change, how is this communicated so we don't suddenly lose access?

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

ID: e1a62365-4312-8aad-d2f1-bb5c4184adf1
Version Independent ID: 2ba5b809-8025-d7ee-c756-d6d1bab033fb
Content: Azure SQL Database and SQL Data Warehouse Connectivity Architecture
Content Source: articles/sql-database/sql-database-connectivity-architecture.md
Service: sql-database
Sub-service: development
GitHub Login: @rohitnayakmsft
Microsoft Alias: rohitna

@mapoitras The Gateway IP's can change. If you check the following link you will find the Gateways have changed recently and have been communicated here.
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-gateway-migration
It also mentions how this is communicated:

Hope this helps.

@mapoitras Please get back to us if any questions. If not we will close the thread by EOD.


prompt vis with tokenized dataset

currently it takes text prompts, but we want it to integrate nicely with e2e eval demo

it was already done this way


[main] Update actions

Cron -knative-prow-robot
/cc we don't use Prow
/assign we don't use Prow
Produced by: knative-sandbox/knobots/actions/update-actions
Details:

Codecov Report

Merging #246 (52dbd0a) into main (93df53c) will decrease coverage by 0.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #246      +/-   ##
==========================================
- Coverage   80.32%   80.05%   -0.27%
==========================================
  Files          20       20
  Lines         747      747
==========================================
- Hits          600      598       -2
- Misses        133      135       +2
  Partials       14       14

Impacted Files
Coverage Δ

pkg/vsphere/adapter.go
63.28% <0.00%> (-1.57%)
:arrow_down:

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 93df53c...52dbd0a. Read the comment docs.


Out of Memory Exception

Getting an Out of Memory exception when trying to export my games.

The game's I'm trying to add to Steam are Forza Horizon 3 and Halo 5: Forge.  Tried just FH3, and it still crashes (the OoM exception pops up 4 times when I try and export).  Tried with both Steam open and closed while exporting.

Ok, looks like it's just FH3 having issues being added.  Halo 5: Forge added fine.

I as well am having the issue adding Forza Horizon 3 and receive the same error message. I don't have other Windows10 games to attempt but based on the your post carnageX it sounds like it's isolated to FH3.

It's a problem when it is trying to find what image use as logo, i'm investigating.

Some live tile images found on Forza Horizon 3 directory seems to have a invalid file format, writing the fix now.

Fixed now on 2.2.1.

Can confirm this is fixed and working now as of 2.2.1.
Thank you so much @BrianLima for the continued updates and support! <3

@TheloniousDotFunk You're welcome :D
I'm glad you guys like my tool.

Fantastic - confirmed fixed for me as well.
From one developer to another, thanks for the updates, appreciate it!


Build test packages for windows, linux-x64, linux-arm, linux-arm64 and macOS

PR Summary
Create test packages for windows, linux and macOS.
PR Context
We need the test packages for release automation tests for all the platforms that we support.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

@PoshChan Please get test failures

@PoshChan please try windows

@adityapatwardhan, I do not understand: please try windows
Commands available in this repo for you:

retry <target> this will attempt to retry only the failed jobs for the target pipeline
rebuild <target> this will perform a complete rebuild of the target pipeline, rerun can be used in place of rebuild
Supported values for <target> which can be a comma separated list are: static,windows,macos,linux,all
get failures this will attempt to get the latest failures for all of the target pipelines
remind me in <value> <units> this will create a reminder that will be posted after the specified duration
<value> is a number, and <units> can be minutes, hours, or days (singular or plural)


MorphOS: finalize compilation and test baserel support

The current state of our AmiSSL sources actually almost compiles for MorphOS/PPC. However, even though the sources might properly compile we need to properly test the 'baserel' support and how we have to setup baserel handling on MorphOS. Perhaps we also need some help from MorphOS developers having some more experience with compiling baserel aware shared libraries for MorphOS.

As we still don't have a MorphOS developer taking care of the proper baserel support we will release 4.0 without MorphOS support :( Hopefully we will find someone taking care of it in the near future.

Please note that there are reports that the OS3/m68k binaries seem to work fine on MorphOS. However, great performance improvement could be achieved with a native MorphOS binary of AmiSSLv4.

Could you give a status update on AmiSSL for MorphOS please? This would be very important to have for an upcoming project of mine. If you have a MorphOS build of AmiSSL I'll be happy to test it and report if it's working.

@jens-maus
I'm sorry, i don't want to hijack this, but is the missing AmiSSLv4 support for MorphOS the reason why YAM can't get another "official" release?
Thank you


Make it work with Laravel 11.9 and symfony/process v7.1.0 in composer.json

What happened?
When I run composer require salahhusa9/laravel-updater I got this error:

salahhusa9/laravel-updater[v0.0.1, v1.0.0, ..., v1.0.2] require illuminate/contracts ^10.0 -> found illuminate/contracts[v10.0.0, ..., v10.48.12] but these were not loaded, likely because it conflicts with another require.

salahhusa9/laravel-updater[v1.1.0, ..., v1.2.0] require symfony/process ^6.3 -> found symfony/process[v6.3.0, ..., v6.4.8] but the package is fixed to v7.1.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
Root composer.json requires salahhusa9/laravel-updater * -> satisfiable by salahhusa9/laravel-updater[v0.0.1, v1.0.0, ..., v1.2.0].

How to reproduce the bug
Install Laravel 11.9.2 and then install the package.
Package Version
2.0.0
PHP Version
8.3.6
Laravel Version
11.9.2
Which operating systems does with happen with?
Linux
Notes
thanks

are you sure Laravel Version is 11.9.2

Yes but maybe is another package that has the conflict
Il giorno ven 7 giu 2024 alle ore 17:39 salah eddine bendyab <
@.***> ha scritto:

are you sure Laravel Version is 11.9.2
—
Reply to this email directly, view it on GitHub
https://github.com/salahhusa9/laravel-updater/issues/49#issuecomment-2155087340,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFTFXFUX3VDFZNIPTQHL4NTZGHH3LAVCNFSM6AAAAABIWXRI72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGA4DOMZUGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Davide Garzetti
Visionova srl
Via Noce 71,  25125 Brescia (BS)
tel +39<PHONE_NUMBER>
www.visionova.it

Try now

It works. Thank you very much


 You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

...looks like CI is still on Go 1.8.


VM1: Linux kernel names camera controls differently on some systems

this causes a software crash at startup

other laptop:
valid control names
  Brightness (user: 0)
    range: 1 to 16
    default: 8
    step: 1
  Contrast (user: 1)
    range: 1 to 16
    default: 8
    step: 1
  Saturation (user: 2)
    range: 1 to 16
    default: 8
    step: 1
  Hue (user: 3)
    range: -32768 to 32767
    default: 0
    step: 1
  White Balance, Automatic (user: 12)
    range: 0 to 1
    default: 1
    step: 1
  Gamma (user: 16)
    range: 1 to 64
    default: 32
    step: 1
  Gain (user: 19)
    range: 0 to 63
    default: 8
    step: 1
  Power Line Frequency (user: 24)
    range: 0 to 2
    default: 1
    step: 1
  White Balance Temperature (user: 26)
    range: 1800 to 10000
    default: 5000
    step: 10
  Sharpness (user: 27)
    range: 1 to 16
    default: 5
    step: 1
  Auto Exposure (cam: 1)
    range: 0 to 3
    default: 3
    step: 1
  Exposure Time, Absolute (cam: 2)
    range: 1 to 10000
    default: 100
    step: 100
  Focus, Absolute (cam: 10)
    range: 0 to 65535
    default: 0
    step: 0

my laptop
valid control names
  Brightness (user: 0)
    range: 1 to 16
    default: 8
    step: 1
  Contrast (user: 1)
    range: 1 to 16
    default: 8
    step: 1
  Saturation (user: 2)
    range: 1 to 16
    default: 8
    step: 1
  Hue (user: 3)
    range: -32768 to 32767
    default: 0
    step: 1
  White Balance Temperature, Auto (user: 12)
    range: 0 to 1
    default: 1
    step: 1
  Gamma (user: 16)
    range: 1 to 64
    default: 32
    step: 1
  Gain (user: 19)
    range: 0 to 63
    default: 8
    step: 1
  Power Line Frequency (user: 24)
    range: 0 to 2
    default: 1
    step: 1
  White Balance Temperature (user: 26)
    range: 1800 to 10000
    default: 5000
    step: 10
  Sharpness (user: 27)
    range: 1 to 16
    default: 5
    step: 1
  Exposure, Auto (cam: 1)
    range: 0 to 3
    default: 3
    step: 1
  Exposure (Absolute) (cam: 2)
    range: 1 to 10000
    default: 100
    step: 100
  Focus (absolute) (cam: 10)
    range: 0 to 65535
    default: 0
    step: 0

fixed by making properties optional and aliasing to same display name. We might consider a longer term fix like indexing on V4L2 control ID which may be more stable


Metadata API refactor

Refactoring all metadata API endpoints into a single common view class.
No functional changes to the API itself.

@matmair got to pick the low-hanging fruit when you find them :)


rgw:modify testcase rgw header when bucket  or user quota is disabled

By default quota is disable at user/bucket level.
if quota is disable then these value will not return so need to modify test_head_bucket_usages
'X-RGW-Quota-User-Size'
'X-RGW-Quota-User-Objects'
'X-RGW-Quota-Bucket-Size'
'X-RGW-Quota-Bucket-Objects'

to Fix: https://tracker.ceph.com/issues/68211
Signed-off-by: Raja Sharma<EMAIL_ADDRESS>Tracker: https://tracker.ceph.com/issues/68211

Contribution Guidelines

To sign and title your commits, please refer to Submitting Patches to Ceph.

If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

When filling out the below checklist, you may click boxes directly in the GitHub web UI.  When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x].  Spaces and capitalization matter when checking off items this way.

Checklist

Tracker (select at least one)

[x]  References tracker ticket
[ ] Very recent bug; references commit where it was introduced
[ ] New feature (ticket optional)
[ ] Doc update (no ticket needed)
[ ] Code cleanup (no ticket needed)

Component impact

[ ] Affects Dashboard, opened tracker ticket
[ ] Affects Orchestrator, opened tracker ticket
[x] No impact that needs to be tracked

Documentation (select at least one)

[ ] Updates relevant documentation
[x] No doc update is appropriate

Tests (select at least one)

[ ] Includes unit test(s)
[ ] Includes integration test(s)
[ ] Includes bug reproducer
[x] No tests

Show available Jenkins commands

jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard cephadm
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox
jenkins test windows
jenkins test rook e2e

cherry-picked to ceph-master


Refactoring to pull out code + flags that creates a database

I'm expecting to pull more of the flag interactions code into the helper class in future PRs. I know the name server_helper isn't great but naming things is hard!

Reviewed the first commit, moving on.

I generally like the "unique_ptr for db reference" commit (other than the noise), but I can't help but think it'd be even better if ProvideDatabase returned a unique_ptr<Database>. In "modern C++", that's a common pattern to return a smart pointer, so that even if you screw up and ignore the return value, you don't leak.

General comment: I find it nicer to have two blank lines between most top level things, à la Python. Look at database.h for an example.

All right, went over all this, let me know when you've pushed some updates.

I'm not as keen on this because formatters don't support it and as I use an
IDE I can navigate around code easily without worrying about its fiddly
layout.
Plus most of our code doesn't have this so any alleged benefits we might
get from it don't currently exist anyway. And it's something done by Python
programmers (guilt by association). I rest my case m'lud.
On 5 November 2015 at 16:10, Pierre Phaneuf<EMAIL_ADDRESS>wrote:

General comment: I find it nicer to have two blank lines between most top
level things, à la Python. Look at database.h for an example.
—
Reply to this email directly or view it on GitHub
https://github.com/google/certificate-transparency/pull/1031#issuecomment-154105074
.

ProvideDatabase() now returns a unique_ptr

Think it's mostly done. PTAL.

LGTM, but I'm very curious to see what rebasing/squashing/merging strategy you'll take... :wink:

I think I shall be using the "Friday Afternoon" strategy.
On 6 November 2015 at 14:20, Pierre Phaneuf<EMAIL_ADDRESS>wrote:

LGTM, but I'm very curious to see what rebasing/squashing/merging strategy
you'll take... [image: :wink:]
[image: image]
https://cloud.githubusercontent.com/assets/40400/10999014/81931132-8491-11e5-9c72-0c85b4fa8261.png
—
Reply to this email directly or view it on GitHub
https://github.com/google/certificate-transparency/pull/1031#issuecomment-154420333
.


etc/GPUutil/gpuMemMonitor

This is an executable -- should be excluded from git?

Yes it should and it is from now on, thanks!


Cannot get current IP: Unhandled exception: Invalid Int32: "<!DOCTYPE html PUBLIC "-" (ArgumentError)

Hi!
I want to try out the service but I run into below error:
benjamin@benjamin:~/hetzner-k3s$ hetzner-k3s create --config cluster_config.yaml | tee create.log
[Configuration] Validating configuration...
Unhandled exception: Invalid Int32: "<!DOCTYPE html PUBLIC \"-" (ArgumentError)
  from /usr/lib/crystal/core/string.cr:438:83 in '??'
  from /usr/lib/crystal/core/pointer.cr:132:6 in 'groups'
  from /home/runner/work/hetzner-k3s/hetzner-k3s/lib/ipaddress/src/ipaddress/ipv6_mapped.cr:99:18 in 'initialize'
  from /home/runner/work/hetzner-k3s/hetzner-k3s/lib/ipaddress/src/ipaddress/ipv6_mapped.cr:87:5 in 'new'
  from /home/runner/work/hetzner-k3s/hetzner-k3s/src/configuration/networking_components/allowed_networks.cr:20:20 in 'validate_current_ip_must_be_included_in_at_least_one_network'
  from /home/runner/work/hetzner-k3s/hetzner-k3s/src/configuration/networking_components/allowed_networks.cr:12:5 in 'validate'
  from /usr/lib/crystal/core/gc/boehm.cr:147:5 in 'parse_and_run'
  from /home/runner/work/hetzner-k3s/hetzner-k3s/src/hetzner-k3s.cr:96:1 in '__crystal_main'
  from /usr/lib/crystal/core/crystal/main.cr:129:5 in 'main'
  from src/env/__libc_start_main.c:95:2 in 'libc_start_main_stage2'

I checked the function validate_current_ip_must_be_included_in_at_least_one_network and
private def validate_current_ip_must_be_included_in_at_least_one_network(errors, networks, network_type)
    current_ip = IPAddress.new("<IP_ADDRESS>")

    begin
      current_ip = IPAddress.new(Crest.get("http://whatismyip.akamai.com").body)
    rescue ex : Crest::RequestFailed
      errors << "Unable to determine your current IP (necessary to validate allowed networks for SSH and API)"
      return
    end

    included = false

    networks.each do |cidr|
      included = check_current_ip_in_network(errors, cidr, current_ip, included, network_type)
    end

    unless included
      errors << "Your current IP #{current_ip} must belong to at least one of the #{network_type} allowed networks"
    end
  end

I think the problem lies in here: http://whatismyip.akamai.com. When I try to open this page manually, this shows up:

You might want to change this to http://ipv4.whatismyip.akamai.com/?
Looking forward to try out hetzner-k3s.
Thanks

Hi, it's likely they had a temporary glitch because I tried now and it works for me. Can you try again?

Thanks for letting me know! That's super weird. Is there some other way to reliably detect the ip address that works in your location?

hi!
I have never had any issues with https://ipinfo.io/ip

Hey I just released v2.0.4 which uses ipinfo as you suggested. It is now building :)

It's working now! Thanks for your support.

No prob 👍


Regex for multiline comments

The following regex worked better for my purposes:
var multilineComment = /\/\*[^*]*\*+([^\/*][^*]*\*+)*\//gm;

It allows me to strip comments from my .css and .scss files such as this:
/* ============================================================================
   @MASTER STYLESHEET
   ========================================================================= */

What do you think?

I've got the same issue, I have a bounch of files filled with comments like this and right now they are not being cleaned up.

This will be fixed by tonight, adding support for /* */ style comments, just writing some tests. This repo has had some major entropy due to my negligence but I finally have time to get it back up to a really solid place.

resolved


Integrate the Package Details page with the backend

Purpose
The purpose of this PR is to integrate the Package Details page with the backend
Preview
https://admin-portal-git-fork-jayasanka-sack-wire-api-medicinesfor-lk.vercel.app/packages/1
Approach

Make API call functions static
Replace DonorAidPackage  with AidPAckage type
Fetch the aid Package from the API
Fetch comments from the API
Wire edit comment function
Wire edit status function
Wire edit item function
Refactor the StatusPosts component to UpdateComments to match with the backend naming conventions.
Create interfaces for missing types
Update response payload types

Issues
The following issues are with relevant APIs:

No API to delete Comments
No API to post Comments
No API to delete Package Items
Aid package items don't include the quotation field when fetching an Aid Package (GET /AidPackage)
No way to get the pledge status. (To render the pie chart)

There seems to be some conflicts... please resolve

There seems to be some conflicts... please resolve

Done.


IOS app won't sync to iCloud - "failed to update some records"

I have the OctoPod app running on my iPhone 14, but it won't sync printer info to the cloud.
Error message from app's log is:
"Failed to push changes for printer: http://[IP on local network]. Error: Failed to modify some records."
When I try to run OctoPod on my AppleTV it just shows "retrieving printer info..." and never completes.
I've removed & reinstalled the app on my phone, but it didn't help.
Any idea what setting(s) I might be missing?
Thank you

Exactly the same happening to me. I also tried ‘Reset iCloud data from printers’ and still getting the same error. Apple TV won’t load anything. Any fix?

Same here. My printers will not sync between devices. What's going on?

Sadly I've given up - never got it working, and at the same time managed to break my printer (damage unrelated to Octoprint).
The new one I've ordered to replace it is not compatible with Octoprint, at least not yet?
Good luck to you all.  Maybe I'll be back some day.

Same issue here!!

Same issue here. Can’t sync to iCloud, getting identical error as above.

Sadly I'm getting the same error as well. I did a little googling and found this post on Stack Exchange where there may be an issue with the way the app is trying to access a zone, but I'm not an iOS app developer so I can't say for sure.

Yep, getting the same issue here as well. I was trying to change the name of my printer on my Apple TV and now I can't get it to sync from any iOS devices.

Me too

Hi guys,
Sorry this is happening to all of you. Wonder if you can help me gather more information so I can troubleshoot this. Could you do the following and share the results:

Open OctoPod and go to "Settings"
Click on "Devices"
Click on "Reset printers from iCloud"
If this fails and click on "View activity log"
Paste screenshot or results here

Thanks,
Gaston

Sent from my iPhoneOn Mar 4, 2024, at 12:30 AM, Gaston Dombiak @.***> wrote:
Hi guys,
Sorry this is happening to all of you. Wonder if you can help me gather more information so I can troubleshoot this. Could you do the following and share the results:
Open OctoPod and go to "Settings"
Click on "Devices"
Click on "Reset printers from iCloud"
If this fails and click on "View activity log"
Paste screenshot or results here
Thanks,
Gaston
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Sure thing. The first two messages pop up when clicking, "Reset printers from iCloud data."
The last two are from clicking, "Reset iCloud data from printers."

Same result as the others. Nothing happens, screenshot attached:
￼

On Mar 4, 2024, at 12:30 AM, Gaston Dombiak @.***> wrote:
Hi guys,
Sorry this is happening to all of you. Wonder if you can help me gather more information so I can troubleshoot this. Could you do the following and share the results:
Open OctoPod and go to "Settings"
Click on "Devices"
Click on "Reset printers from iCloud"
If this fails and click on "View activity log"
Paste screenshot or results here
Thanks,
Gaston
—
Reply to this email directly, view it on GitHub https://github.com/gdombiak/OctoPod/issues/683#issuecomment-1975761492, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABV46S2NUO4PHDRSMXKJVTLYWQBGDAVCNFSM6AAAAABBA46CCSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZVG43DCNBZGI.
You are receiving this because you commented.

Hey guys, I created a new version that will help me collect more data to see what’s going on with this error.  If you are already a beta tester go ahead and install the new version and follow the steps I mentioned above. Share a screenshot with the results. You might want to rotate the phone for the screenshot if the text is not fully visible.
If you are not a beta tester then send me a message and I’ll add you to the list of testers.
Thanks
Gaston

If you are not a beta tester then send me a message and I’ll add you to the list of testers.
 I'd like to help you out.

You can reach me at @.***  I would be happy to help test.  Sent from my iPhoneOn Mar 11, 2024, at 4:29 PM, camrichmond @.***> wrote:
If you are not a beta tester then send me a message and I’ll add you to the list of testers.
 I'd like to help you out.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Please add me to the beta testers, I’d be glad to help out. Sent from my iPhoneOn Mar 11, 2024, at 4:01 PM, Gaston Dombiak @.***> wrote:
Hey guys, I created a new version that will help me collect more data to see what’s going on with this error.  If you are already a beta tester go ahead and install the new version and follow the steps I mentioned above. Share a screenshot with the results. You might want to rotate the phone for the screenshot if the text is not fully visible.
If you are not a beta tester then send me a message and I’ll add you to the list of testers.
Thanks
Gaston
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Hey guys, I created a new version that will help me collect more data to see what’s going on with this error. If you are already a beta tester go ahead and install the new version and follow the steps I mentioned above. Share a screenshot with the results. You might want to rotate the phone for the screenshot if the text is not fully visible.
If you are not a beta tester then send me a message and I’ll add you to the list of testers.
Thanks Gaston

Hi, please add me to the beta list for the version to troubleshoot Octopod.
Thanks in advance! Hope to hear from you soon.

Good question about sending me a message. :) You can send me an email to gdombiak at gmail.
Thanks,
Gaston

Good news! Thanks Michael Goran for sharing your screenshots and providing vital information. Everyone, give it a try and let me know if things are now resolved.
Thanks,
Gaston

I can report that all is working.

Good! I got confirmation from 2 people that this issue is now resolve. Sorry for taking this long to resolve it. Too many other things are keeping me busy atm.


Add initial pre-commit configuration

This PR adds an initial configuration for pre-commit which includes most of the checks currently being done by PlasmaPy.
This doesn't include any configuration stuff that would normally go into pyproject.toml yet.

To learn more about what these pre-commit hooks do, it's worth checking out the support hooks page in the pre-commit docs.


Look up parquet columns by name case-insensitively

Parquet schemas are case sensitive but hive is not so camelCase parquet fields are not found when accessed as lowercase hive columns.

No, nested fields with caps are still broken (IQ-129).

@zhenxiao, does this look good to you?  Also, any ideas on how we can test for this?

@dain @billonahill the fix looks good to me.
Kind of difficult to reproduce it in our current test case. Let me think of a way.

@dain @zhenxiao yeah, I also looked at the tests to see how to verify this in a test case but I came up blank. Let me know if you have any ideas.
Also, since submitting this patch I released that we need to further patch the twitter fork to handle hive reserved words. When a parquet field is a reserved Hive word (i.e., keyword, location), we append an '_' to the field name before adding to Hive. This works fine when looking up presto columns by position, but not by name. As a result we also need to check for a match after stripping the _ (see  https://github.com/twitter-forks/presto/pull/32/files). This isn't something we want in the OSS master but I am curious how others deal with reserved Hive keywords.

@dain @billonahill @zhenxiao I created a PR for a simple unit test.

@dain @billonahill
@nezihyigitbasi 's PR looks good to me. What do you think?

@dain @zhenxiao unit tests look good to me. Thanks @nezihyigitbasi!
I just refactored this patch to be easier to further patch on a private branch, like we're doing in https://github.com/twitter-forks/presto/pull/32/files.

Merged, thanks!


Release a fix for the 32 bit architectures

Would it be possible to release a new version with the fix for #971 ?
Sorry, I don't like this type of request but we really need that fix for a system in production.

I want to do a few more modifications to Inspector, but after that, I will make the release. So few days, a week tops.

Released