add resin config generate --ethernet and --wifi options for noninteractive cli

Currently resin config generate does not allow specifying all necessary options via the cli.
It requires navigating with arrow keys interactively via console rather than specifying parameters.
$ resin config generate --app iichip --output config.json
? Network Connection (Use arrow keys)
❯ ethernet
  wifi

This poses a problem to automation pipelines which currently need a work around using something like expect:
https://gitlab.ii.org.nz/iichip/resin-cli/blob/latest/config.exp
#!/usr/bin/expect -f
spawn resin config generate --app "$env(APP)" --output config.json
match_max 100000
expect "ethernet"
send -- "\r"
expect "Check for updates every X minutes"
send -- "\r"
expect eof

Our work around just hit's enter twice to enable ethernet, but adding wifi configuration to the pipeline would be great.
@ii wrapped this expect into a Docker container to allow us to generate the config.json during our resin-os image bulid:
docker pull iichip/resin-cli
docker run -e EMAIL="$EMAIL" \
           -e APP="$APP" \
           -e PASSWORD="$PASSWORD" iichip/resin-cli > config.json

 Front conversations

Hey there,
Thanks for the suggestion, it sounds like a good addition. The problem is that the set of question we ask to be able to generate a config.json comes from an external service (the CLI blindly asks such questions), so hardcoding --wifi/--ethernet options would not be a possible way forward. As a consequence, we have to add some way for allowed options to be computed at runtime, or put a generic option what you can pass any set of key/value combinations that will be applied on top of the retrieved question list. We could also accept a path to a json file containing certain defaults, like networkType: 'wifi'. Would that suit your needs?

Paired with a --show-opts and --generate-opt-file fill-me-out.json/yaml I think we have a winning combination!
Is there an API test suite or documentation area that addresses config generate and friends?
A quick look at https://docs.resin.io/runtime/data-api/ didn't reveal anything.

Sounds good! I'll try to allocate some time for this soon. In order to get unblocked, you could use https://github.com/resin-io-modules/resin-device-config, which is the low-level module that generates configuration to create a simple script that does what you want. You could also take a look at https://github.com/resin-io/resin-config-json, which is the module that injects config.json to the device, in case you need that as well!

In general I get quite a few requests for completely non-interactive resin config generate (so it's possible to use the script automated). Would that be possible to include in the near-term updates? Would help with things like the workflow we've shown in our preloading and preprovisioning blogpost

Fixed and released in 6.9.0, see the docs for config generate for the full details.
Example:
resin config generate --app MyApp --network wifi --wifiSsid mySsid --wifiKey abcdefgh --appUpdatePollInterval 1


The suite release defines a standard for GitHub releases for suite components

There is a standard for how GitHub tags and releases are done in component projects

Projects included in the OSS suite must have:

Tagged versions that correspond to artifacts with the same version, and the tags must be annotated
CHANGELOG.md file that has the keepachangelog-formatted changes for each tagged version
A GitHub release associated with the tagged version that includes a copy/paste of the CHANGELOG section for that tagged version

Note: prereleases are not included in the suite, and the suite will ignore them
Note: the suite release does not support patching old versions at current, because that overrides the semver ordering of releases and latest is sorted by creation time (TODO: revise suite flow so that it pulls the highest semver release rather than latest release)

Note: it's important that the links in the changelog are markdown links, or they won't resolve when moved into markdown files in the repo
That is, the changelog issue links should be written as [cyberark/conjur#123](https://github.com/cyberark/conjur/issues/123)

Here are some potential resources:

https://docs.gitlab.com/ee/development/changelog.html
https://depfu.com/blog/what-makes-a-good-changelog (talks about the trifecta of “consistency, readability, relevance”)

Also, this:
What warrants a changelog entry?
• Any change that introduces a database migration, whether it's regular, post, or data migration, must have a changelog entry.
• Security fixes must have a changelog entry, without merge_request value and with type set to security.
• Any user-facing change should have a changelog entry. Example: "GitLab now uses system fonts for all text."
• Performance improvements should have a changelog entry.
• Any contribution from a community member, no matter how small, may have a changelog entry regardless of these guidelines if the contributor wants one. Example: "Fixed a typo on the search results page."
• Any docs-only changes should not have a changelog entry.
• Any change behind a feature flag should not have a changelog entry - unless the feature flag has been defaulted to true. The entry should be added in the merge request removing the feature flags. If the change includes a database migration (regular, post, or data migration), there should be a changelog entry for the migration change.
• A fix for a regression introduced and then fixed in the same release (i.e., fixing a bug introduced during a monthly release candidate) should not have a changelog entry.
• Any developer-facing change (e.g., refactoring, technical debt remediation, test suite changes) should not have a changelog entry. Example: "Reduce database records created during Cycle Analytics model spec."

split into what we do want and what we don’t want in changelogs

this should go in the community repo in the Conjur/CONTRIBUTING.md file, and break it out into a section for contributors (who need to know about the changelog guidelines) and for maintainers (who need to know about tagging and github releases)
we should maybe also add something to the PR review process notes to say we'll look at the changelog to make sure it's updated appropriately


Minor rewriting and renaming of NameMap

Title is quite explicit. Namer has been renamed ValuePrinter, Printer is now InstPrinter. name_inst becomes get_const_inst and no longer takes self (we don't need a trait object anymore). Backends have been rewritten accordingly. ValuePrinter is now an associated type of InstPrinter (Printer was generic over Namer before). As a result, X86Printer, CudaPrinter and MppaPrinter are no longer public. An alternative would have been to make each concrete implementation of ValuePrinter public, but I don't see the point of doing that. The possibility of further splitting ValuePrinter in ConstPrinter and Namer has been discussed but postponed as it does not offer any obvious immediate advantage.

bors r=Elarnon

bors retry

bors retry

bors retry

bors retry


fetchurl: check that url is a string

Otherwise we (may) get a hard to debug issue in the tarball job.

I thought I'd better give a chance to some peer review; otherwise I plan to merge in a few days.

Why did this not error earlier? The change is 11 months old.

I don't know a way, but before this the error I got was completely without a trace, so I had to bisect.  Nested lists (cause urls = [url]) often work, but the tarballs job fails on them... except it apparently doesn't comb through patches or some similar reason why we haven't hit the other commit in this PR until now.

I don't know a way, but before this the error I got was completely without a trace, so I had to bisect. Nested lists (cause urls = [url]) often work, but the tarballs job fails on them... except it apparently doesn't comb through patches or some similar reason why we haven't hit the other commit in this PR until now that I add the type-check.

I was just asking incase it would be easy but lets unblock the channel now!

To be clear, the tarball job should have been unblocked just by the "grandparent" commit that I pushed to master directly.  (also other issues are blocking the channel right now, unfortunately)

To be clear, the tarball job should have been unblocked just by the "grandparent" commit 10cb065 that I pushed to master directly. (also other issues are blocking the channel right now, unfortunately)

Well, GitHub UI can't reflect that and you also not mentioned it.

My comment about the tarball breakage was meant for similar situations in the future (so that they're easier discovered).  In any case, we can change the code, so everyone can keep commenting...


Trying to access array offset on value of type null

Thanks again for this great package.
Am struggling with the following situation for some hours... the GUI works, when saving I get following exception
"message": "Trying to access array offset on value of type null",
"exception": "ErrorException",
"file": "/vendor/digital-creative/nova-inline-morph-to/src/InlineMorphTo.php",
"line": 285,

Debugging shows that
$this->meta[ 'resources' ]->where('className', $resourceClass)->first()
returns null (but $resourceClass is valid).
Any idea what the issue might be?

does dd($this->meta[ 'resources' ]) returns an empty array? or it also contains the dd($resourceClass) in it?

I just tried seems to be working fine, double-check that the ->types([]) are all Nova\Resource class not Model class, and that you are using the correct trait HasInlineMorphToFields

thanks for your help again - the reason was being blind and having assigned the wrong model class


Support Guillemets

According to the Wikipedia, guillemets are used to indicate book or album
titles.
Reference:
https://en.wikipedia.org/wiki/Guillemet#Uses

If this change is acceptable, please let me know whether I should also bump the MINOR version of this package in package.json.

@alxtsg Thanks!
I've released https://github.com/azu/sentence-splitter/releases/tag/3.1.0


Bump build number (again).

Checklist

[X] Used a fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

The Azure tests for previous builds were cancelled for some reason, so I am trying again.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Feature Request: improve health check

It looks like docker-compose supports these health statuses:

health: starting
healthy
unhealthy

I configured healthcheck in compose.yml:
healthcheck:
test: ["CMD", "check-health.sh"]
interval: 10s
timeout: 5s
retries: 3
If the container status changes from -> "health: starting" to "unhealthy" it would be great to fail the composeUp Task (including shutting down the stack: composeDown). Otherwise the gradleTask "composeUp" will hang forever and the compose stack will stay alive.

Would be great to have this feature. What do you think?

A quick win, would be to have a timeout configured for the composeUp task, e.g.:
compose.healthCheckTimeoutInSeconds = 60
The composeUp task, could than fail if container's do not get healthy within that timeframe ... and starts shutting down the stack (composeDown)

I just realised, shutting down the stack on healthCheckTimeout ^^ should be optional. For local development its nice to ssh into an unhealthy container.
compose.healthCheckTimeoutInSeconds = 60
compose.composeDownOnHealthCheckTimeout = false
... and according to another feature request, it would be great to define all these for a specific configuration, e.g.:
compose.integrationTest ={
composeFiles:["stack-integration-test.yml"]
healthCheckTimeoutInSeconds = 60
composeDownOnHealthCheckTimeout = true
}
compose.dev ={
composeFiles:["stack-dev.yml"]
healthCheckTimeoutInSeconds = 60
composeDownOnHealthCheckTimeout = false
}

Regarding to timeouts - there is waitForTcpPortsTimeout and waitForHealthyStateTimeout properties. Both defaults to 15 minutes - that's probably why you think there is no timeout : )
Regarding to calling composeDown when something goes wrong - it must be ensured by finalizedBy in your Gradle script. Please note that finalizedBy is used by isRequiredBy method that is part of our extension.

So I hope both issues are already addressed by the plugin.


Error with empty array

Hi,
I am having errors if I start with an empty array.
My app begins with an empty array and them I add photos using the camera.  If I start with a few photos in the array at the begining, same number than ion-gallery-row or more, everything works fine but if I let the array empty, I can not add photos later.
If I insert only one photo, the columns does not fit well, the image fill the screen like the new images added.

Are you using the latest version ?
Are you passing an empty array to the directive at startup ?
That issues was fixed a couple of versions ago.
Didn't get that last part of the columns, can you do a screenshot of the issue ?

I am using the versión 0.1.10.
At startup, I am passing an empty array that I fill in later with a factory.

This photo shows what happen if I pass an array with just one photo and, after a few seconds, push another.

This two images show what happen if I insert more than one photo at the beginning. As you can see, in all that three images, there is one photo in a second row. This photo has been inserted using $timeout.
I do not know if this is the normal behavior or, with row_size = 5, the last image is the right one.

I'm having the same issue with a version downloaded last night.  Workflow is the same in my case, start with no images, add some via camera, in all cases I've tested the image that I just took isn't shown until after I refresh that view (IE navigate away and then come back).  Doing some more digging and hopefully a better reproduce plan shortly.

What ionic version are you using ?

Whatever is most recent. Out of pocket at the moment but will confirm when I get home.

My ionic version is 1.7.12

I think the issue here is around this code below (the ion-gallery controller):
Initially, $scope.ionGalleryRowSize is set to 0 when there are no items in the ionGalleryItems.  This is done by ionGalleryHelper.getRowSize.  Then draw gallery gets called when new items are added to the list, and _drawGallery is called again.  The real issue is that $scope.ionGalleryRowSize isn't getting reset when calling _drawGallery.  Moving the first two lines in the controller into the _drawGallery function fixes the issue.
function controller($scope){
      $scope.ionGalleryRowSize = ionGalleryHelper.getRowSize(parseInt($scope.ionGalleryRowSize) || ionGalleryConfig.row_size, $scope.ionGalleryItems.length);
      $scope.actionLabel = ionGalleryConfig.action_label;

      var _drawGallery = function(){
        $scope.items = ionGalleryHelper.buildGallery($scope.ionGalleryItems,$scope.ionGalleryRowSize);
        $scope.responsiveGrid = parseInt((1/$scope.ionGalleryRowSize)* 100);
      };

      _drawGallery();

      (function () {
        $scope.$watch(function () {
          return $scope.ionGalleryItems.length;
        }, function (newVal, oldVal) {
          if(newVal !== oldVal){
            _drawGallery();

          }
        });
      }());

    }

I am filling the gallery from a database.  If i have a single image in the query the gallery does not load.  if i have more than one image in the query, everything works fine.  any ideas? Im not sure if its related to this issue or not.

@pedroabreu any chance of taking a look at the PR? https://github.com/pedroabreu/ion-gallery/pull/31

@ggoforth sorry, I'll have a look today or tomorrow (crazy couple of weeks)

@ggoforth @alconesp I'm sorry if this isn't the right place to post, but since you brought it up: how are you guys starting with an empty array (no images), and then adding photos (e.g. with the camera)? I have the camera part down, but when I try something like
app.controller('ACtrl', function($scope) {
  $scope.images = [];
  $scope.buttonClicked = function() {
    $scope.images.push({src: "[image path]"});
  }
});

I get the javascript error
Error: Attempted to assign to readonly property.
buildGallery@file:///var/mobile/Containers/Bundle/Application/A5D6027C-5133-45E5-97C0-B5AA36094440/wl.app/www/lib/ion-gallery/dist/ion-gallery.min.js:1:1433
...

so wondering how you guys were to dynamically add images to the gallery successfully (@alconesp you mentioned you used a factory?). I'm a very big angular newb. Thanks!

Nevermind, stepping through ion-gallery.js in Safari debugger shows that my error is caused by the same root issue for what @alconesp originally noticed, which is solved by @ggoforth's fix (and I didn't read one of his comments carefully enough). Thanks @ggoforth for fixing, and @pedroabreu for merging, and the awesome plugin!

Fixed with #31


Multi version compatibility, unit tests, Github Actions, gitignore

Hi,
Thanks the great work !
Support for python 3.11 and 3.12
The main purpose of this pull request is to make the package compatible with multiple python versions.
In addition to python 3.10, we make sure the package works for python 3.11 and 3.12.
Version 3.13 is not yet available for torchvision. Version 3.9 is too old for multiple packages such as numpy, scipy, etc...
Unit tests and CICD
In order to make sure of multi-version compatibility, I added unit tests and CICD in Github Actions.
You can find a run example here: https://github.com/forzagreen/sinatools/actions/runs/11786476426/job/32829838996
So far, here is the status of test coverage:

[x] Tests are OK for modules morphology, semantic_relatedness, and utils.

To verify:

Tests for modules ner, relations, and wsd work locally, but not in Github Actions. It seems to be related to torchtext (unfortunately, the project is not maintained anymore).
Module synonyms doesn't return what's stated in the documentation. Related to https://github.com/SinaLab/sinatools/issues/3.

gitignore
Deleted many files, based on the gitignore standard for python.

I'm looking forward for you review/thoughts/comments/suggestions.
Wael

@TymaaHammouda

Following is a matrix of versions compatibilities, by looking only at packages torch, torchvision, and torchtext:
| 3.8 | 3.9 | 3.10 | 3.11 | 3.12 | 3.13 |
-- | -- | -- | -- | -- | -- | -- | --
torch 2.5.1 | ❌ | ✅ | ✅ | ✅ | ✅ | ✅ | PR
torch 2.4.1 | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ |
torch 2.3.1 | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ |
torch 1.13.0 | ✅ | ✅ | ✅ | ✅ | ❌ | ❌ | Current
  |   |   |   |   |   |   |
torchvision 0.20.1 | ❌ | ✅ | ✅ | ✅ | ✅ | ❌ | PR
torchvision 0.14.0 | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | Current
  |   |   |   |   |   |   |
torchtext 0.18.0 | ✅ | ✅ | ✅ | ✅ | ✅ | ❌ | PR
torchtext 0.14.0 | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ | Current
  |   |   |   |   |   |   |
Current | ✅ | ✅ | ✅ | ❌ | ❌ | ❌ |
PR | ❌ | ✅ | ✅ | ✅ | ✅ | ❌ |

Apparently the ner module works only with python 3.10, since  this was the version used for training.
I will close this PR for now and create smaller ones later.


Feature request: support pyproject.toml version strings

Python version strings, at least as defined in pyproject.toml files, use something to the sort of [N!]N(.N)*[{a|b|rc}N][.postN][.devN].
Situation
>>> semver.Version.parse("<IP_ADDRESS>")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\vers\.pyenv-win-venv\envs\project\Lib\site-packages\semver\version.py", line 608, in parse
    raise ValueError(f"{version} is not valid SemVer string")
ValueError: <IP_ADDRESS> is not valid SemVer string

Possible Solution/Idea
Support more (all?) possible Python version strings.
Additional context

See https://python-poetry.org/docs/pyproject/#version
See https://peps.python.org/pep-0440/#public-version-identifiers (PEP 440)
Compare https://github.com/python-semver/python-semver/issues/284

Hi @bersbersbers, :wave:
thanks for your bug report, much appreciated! :+1:
Your request goes beyond what the semver spec and this library supports. Python version strings are unfortunately not fully semver compatible. This is the bad news.
The good news is that to some degree it's possible to convert from one version spec to the other. I covered this already in the section Converting versions between PyPI and semver. The documentation mentions explicitly PEP 440.
If something is not covered in the documentation, I'm more than happy to amend the text. However, adding support for PEP440 into the library is out of scope.
Is the above documentation sufficient for your use case?

This is great, thank you!
Sorry for opening this without any need - I had searched for PEP 440 in the issue without finding anything, yet had not checked out the docs before. I guess other people doing the same will now at at least find this very issue ;)

Don't worry, this is absolutely no problem. :slightly_smiling_face: Thanks for commenting.
Yes, there was a similar feature request some time ago. Seems I need to advertise the docs more prominently. :wink:


Running fastsurfer with Freesurfer 7.4 throws an mris_info error

Question/Support Request
We've been using fastsurfer recently as a Docker/singularity dowloaded from dockerhub and it worked just fine.
We built a docker container including fastsurfer in the workflow of processing on our clusters and other institutions.  However we are getting an error in the surface reconstruction:
@#@FSTIME  2023:05:29:18:50:13 mris_info N 1 e 1.94 S 0.33 U 2.80 P 161% M 350488 F 0 R 157384 W 0 c 5 w 296 I 10016 O 8 L 3.66 7.80 11.68
Incorrect header information detected in /out/fastsurfer/sub-HC01_ses-01/surf/rh.orig.nofix: vertex locs is not set to surfaceRAS. Exiting...

I noticed that issue comes from this sanity check step:
# Check if the surfaceRAS was correctly set and exit otherwise (sanity check in case nibabel changes their default header behaviour)
cmd="mris_info $outmesh | grep -q 'vertex locs : surfaceRAS'"
echo "echo \\"$cmd\\" " |& tee -a $CMDF
echo "$timecmd $cmd " |& tee -a $CMDF
echo "if [ \\${PIPESTATUS[1]} -ne 0 ] ; then echo \\"Incorrect header information detected in $outmesh: vertex locs is not set to surfaceRAS. Exiting... \\"; exit 1 ; fi" >> $CMDF

Environment

FastSurfer Version: ...
 However now I get this error:
./recon-surf.sh --sid sub-01_ses-01 --sd /out/fastsurfer --t1 /out/fastsurfer/sub-01_ses-01/mri/orig.mgz --asegdkt_segfile /out/fastsurfer/sub-HC062_ses-01/mri/aparc.DKTatlas+aseg.deep.mgz     --parallel --threads 15 --py python3.8  --no_fs_T1 --allow_root
ERROR: Flag --no_fs_t1 unrecognized.

Inside recon-surf.sh the code looks like this:
    --no_fs_T1 )
    get_t1=0
    shift # past argument
    ;;

I removed the flag --no_fs_T1 from my code and it worked, maybe updating to --no_fs_t1 in recon-surf.sh could solve this issue.

Thanks, this looks like a bug and should be a separate issue. I will close this one here as it was due to the FreeSurfer Version. We also updated our code to check for supported versions so that users should get an error in #321 .
Will start a new issue with the incorrect no_fs_T1 passing between run_fastsurfer and recon_surf.


[release-0.19] Add the missing 0.18 and 0.19 eventing manifests

Proposed Changes

Add the missing 0.18 and 0.19 eventing manifests

/test pull-knative-operator-upgrade-tests


Allow the looking up of applications with the owner

Depends on https://github.com/resin-io/resin-sdk/pull/352 and we need to update the package.json when that PR is deployed as well.
change-type: minor
Connects-to: #594
Signed-off-by: Cameron Diver<EMAIL_ADDRESS>

The SDK change has now been released.


improve prerelease.

will by default postfix '-beta' if none is found. or will respect '-rc' if found etc
#37

so we will end up with x.y.z-beta.1 by default right? Shouldn't we test this versioning logic?

yeah, i have a task with a checklist of tests left to write, so i have added that to the list.
https://github.com/skyglobal/component-helper/issues/1


Question: Is there an API?

Hi there, is there an API for Streama?

Please refer to this issue: https://github.com/dularion/streama/issues/239


Add filter for dates (before and after).

Fixed


ColumnAdapter duplicates

When defining a table that needs multiple column adapters like
CREATE TABLE show_details (
  _id LONG NOT NULL PRIMARY KEY AUTOINCREMENT,
  downloadedAt CLASS('org.threeten.bp.LocalDateTime') NOT NULL,
  startTime CLASS('org.threeten.bp.LocalDateTime') NOT NULL
);

The Mapper requires adding the same column adapter mulitple times:
protected Mapper(Creator<T> creator, ColumnAdapter<LocalDateTime> downloadedAtAdapter, ColumnAdapter<LocalDateTime> startTimeAdapter) {

I expected it to detect the class and require the column adapter only once.

We currently do this because while the class is the same the mapping may
not be. For example, one may store a Date in two ways (yyyy-mm-dd and ISO
8601) in two columns of the same table.
Since these don't change much, I personally don't think the repeated nature
when columns are the same is a big deal. Do you agree? Do you have tables
that have large numbers of the same classes using the same adapter or is it
just cases of two?
On Thu, Apr 21, 2016, 5:58 AM Paul Woitaschek<EMAIL_ADDRESS>wrote:

When defining a table that needs column adapters like
CREATE TABLE show_details (
_id LONG NOT NULL PRIMARY KEY AUTOINCREMENT,
downloadedAt CLASS('org.threeten.bp.LocalDateTime') NOT NULL,
startTime CLASS('org.threeten.bp.LocalDateTime') NOT NULL
);
The Mapper requires adding the same column adapter mulitple times:
protected Mapper(Creator creator, ColumnAdapter downloadedAtAdapter, ColumnAdapter startTimeAdapter) {
I expected it to detect the class and require the column adapter only once.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/square/sqldelight/issues/247

I also don't think it's a big deal, and actually prefer it this way. As @JakeWharton said, the same class might be mapped/marshaled in two different ways. Checking the columnIndex or key in the map/marshal methods would be kind of annoying.
What if there were an overloaded constructor? That way you can provide multiple adapters for the same class, or not, depending on your needs. Is something like that cumbersome to generate?

I don't think having different serialization strategies for the same class is a good idea in the first place.
Its not really that many. At most 3 for a class. But its a little annoying when preparing mapper and marshal.
But if it helps you keep the library simple that's worth it.
What would be really delight for me were some place where I could specify the column adapters I'm using. That way one would not need to define them over and over again for each class. Like you can register TypeAdapters for Gson.

It's very common, actually, since there are a lot of generic types for
representing data (like ByteString) which might want to be rasterized in
different ways in underlying storage (like base 64, hex, utf8, ascii)
depending on use.
If we had a central registry we would need a way to resolve these
disambiguations (like Gson does with @JsonAdapter and @SerializedName) in
the SQL create table statement. If these were required to be specified
everywhere you used the generated types I would agree with you, but there's
only one canonical definition (the model subclass) in practice it's not
that bad.
On Fri, Apr 22, 2016 at 5:23 PM Paul Woitaschek<EMAIL_ADDRESS>wrote:

I don't think having different serialization strategies for the same class
is a good idea in the first place.
Its not really that many. At most 3 for a class. But its a little annoying
when preparing mapper and marshal.
But if it helps you keep the library simple that's worth it.
What would be really delight for me were some place where I could specify
the column adapters I'm using. That way one would not need to define them
over and over again for each class. Like you can register TypeAdapters for
Gson.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/square/sqldelight/issues/247#issuecomment-213592954


separate the interface logic from the core logic into different files

This was done as the initial step of an attempt to create a react component for the xterm.js core.
I believe it would make refactoring much easier, once the layers are completely separated, and this way the core can be required separately and new interfaces would be easier to implement.
The communication is done using events.
I hardly changed any code, I only separate the methods into different files. Core containing everything that doesn't have to do with the browser, and Interface takes care of the rest. Interface inherits from Core and it is was xterm.js exports, so it shouldn't affect anyone, unless they're listening to the 'refresh' event which was changed a bit.
Let me know what you think :)

Things do listen to refresh, what changed exactly?
term.on('refresh', term.compositionHelper.updateCompositionElements.bind(term.compositionHelper));

Also "Interface" is a bit ambiguous, Browser.js may be better? @parisk thoughts? @iMoses what were your plans in regards separating the other modules?

I haven't notice any use of the refresh event in the code, so I assume it is being used by an external source. I can change the name of the new event or revert the event arguments and adjust my code changes to work with it.
What has changed is that instead of calling 'this.refresh' directly, the Core now emits an event which can be caught by any interface to be rendered as it see fits. The event changed a bit, instead of returning a single object argument, it now returns two arguments, start and end. The main benefit is that Core can now be initialized as a stand alone without breaking anything and it still announces UI related actions using events.
I agree about Interface being too ambiguous, haven't thought of a better name yet.
Eventually I see the entire "Interface" becomes the View that is used to render the UI, and views can change according to implementation, such as a React Component.
In regard to other modules, I started playing with the concept of separating everything into smaller files/modules, but it was too big of a change and I ain't sure it actually made anything more readable. So what I did, locally, is separate "charset", "colors" and "events" into helper files. I'm also thinking about turning CSI and ESC into external commands which the Core uses.
I'm trying to focus first on the Core, which is a single module, separating everything else away from it. Currently I'm working on a React UI which uses this Core, that way I'm slowly learning what more can be done to support multiple interfaces. Once my experiment will be done, I'll go back and refactor the "Interface" (events, Viewport, CompositionHelper, addons) according to the changes. So for the moment I don't have a complete plan for all modules, I hope to get there slowly :)

I think I have to take a deeper look in this PR to see if namings are 👍 .
@iMoses how does the current architecture affect you in creating a React component for xterm.js?

The current architecture is tightly coupled with rendering logic.
There's no way to import or run the Terminal without it.
It highly complicates the creation of different interfaces, such as a React component that takes care of it's own rendering logic.
I think a better, more complete example would be a better explanation. I'll work on it but it would take me a couple of days.
What I've done, in my own project, is removed everything that is somehow connect to the document or window objects from Terminal, and replaced some of them with event, such as 'refresh' and 'resize' that passes the same parameters that the original function received. (I realized that some of it overrides current events, in the final code I could change them if necessary)
In my customized interface I listen to  and emit events to communicate with the library.

@iMoses, I am moving forward with closing this, since it got quite obsolete and many changes have happened till this got opened.
We will open up a new issue for separating rendering and state logic, which will be helpful hopefully.


Enhanced backport PR creation

Consider the following

adding reviewers (who? admins? | how? hub API?)
adding milestone (how? hub API?)

This relevant data can be extracted from hub pr list -f %au|%rs|%Mn <PR_NUMBER> and then passed to hub pull-request in .circleci/config.yml


Sign in question mark does nothing

Version 0.4.3 (0.4.3)

Sign in question mark does nothing

it does actually trigger the modal, but it is behind the auth screens (so not visible).


[Q] Reusable CTE (psql)

Hey 👋 I have been using Kysely and loving it but I have been trying to create a reusable CTE but its not working as expected / the types are being messed up so I 'm wondering if anyone has managed to get this to work.
example (simple)
Say you have a super simple query like:
const res = await db
  .with('something', eb => eb.selectFrom('dogs').select('coat'))
  ...rest of query

I want to extract the .with() into a reusable function that can be used. Trying to do this I only managed it to work using the QueryCreator<DB> however this works only if the .with is the only CTE being used. If there are more, then it stops working, presumably since the type is now QueryCreator<DB & { previous cte(s) }> which breaks the type inference, etc.
Is there a way to make this work so that you can bring in your CTE's like .with('blah', cteFn())?
Thanks a ton :)

Unfortunately that's only currently possible by either using the exact QueryCreator type or loosening type-safety by doing this: https://kyse.link/?p=s&i=RQ4GXkErV7QZ1ECUYVxC
Note that you can incorrectly use the exressionBuilder by listing tables that don't exist.

Hi 👋
Are there any plans to include this type of feature in the future? Having composable queries through re-usable CTEs is really handy when writing large queries.
Currently if you do something like this:
const petNames = db
  .selectFrom("pet")
  .select(["name", "id", "owner_id"]);

const cte1 = db
  .with("petNames", () => petNames)
  .selectFrom("petNames")
  .select("id");

const cte2 = await db
  .with("cte1", () => cte1)
  .selectFrom("cte1")
  .select("id")
  .execute();

The query gets pretty messed up (albeit still functional), since it will nest the various CTE within each other.

Wrap the CTE in a function that receives the query builder as the param

Right, I tried that as per above, but that gets pretty frustrating if you want to have multiple CTEs, or use CTEs within a different CTE no?

Your example should be something like
const cte2 = await db
  .with("cte1", cte1)
  .selectFrom("cte1")
  .select("id")
  .execute();

I've tried that as well but that raises a type error unfortunately.


Let cordovaEmailComposer.open() fail promise when "cordova is not defined" for testing in browser

FEATURE REQUEST
The cordovaEmailComposer.open method throws the following error when testing in a browser:

ReferenceError: cordova is not defined
at Object.open (ng-cordova.js:1575)

The open() method returns a promise.
I propose to use the existing promise to give feedback in case that cordova is required. The promise could be made to fail/rejected when cordova is not available.
This would allow the failure to be handled and/or ignored more easily and (in my opinion) more consistently as the failure callback of a promise is already used to resolve failures.

This is a great suggestion. Could you make a pull request for this feature request? We'd be happy to look at this issue further then.


[CPU] Extend LLVMCPUTile API to pass a set of tile sizes

This is so that LLVMCPUTile doesn't have to figure out what tile sizes should be used and they can be provided externally.

Closing stale PR.


[bug] Hello world app, title bar problem (macOS)

Describe the bug
Hello,
When I focus a hello world app and mouse over the title bar, the bar expands downwards by a very slight margin and changes in colour. I recorded the issue using QuickTime. When the window is out of focus, mousing over it does nothing out of the ordinary.
Reproduction

Create a new hello world app with default settings using yarn create tauri-app.
Run cargo tauri dev and focus the window.
Move the mouse onto the title bar. It should expand and change in colour. When you move the mouse anywhere else, the bug disappears until you move the mouse back onto the bar.

Expected behavior
The title bar should neither expand nor change in colour.
Platform and versions
Operating System - Mac OS, version 12.3.0 X64

Node.js environment
  Node.js - 17.7.1
  @tauri-apps/cli - 1.0.0-rc.6
  @tauri-apps/api - 1.0.0-rc.2

Global packages
  npm - 8.5.2
  pnpm - 6.11.0
  yarn - 1.22.17

Rust environment
  rustup - 1.24.3
  rustc - 1.59.0
  cargo - 1.59.0
  toolchain - stable-aarch64-apple-darwin

App directory structure
/dist
/src-tauri
/.git

App
  tauri - 1.0.0-rc.4
  tauri-build - 1.0.0-rc.4
  tao - 0.6.4
  wry - 0.13.3
  build-type - bundle
  CSP - unset
  distDir - ../dist
  devPath - ../dist

Stack trace
No response
Additional context
No response

Uploaded the video:
https://user-images.githubusercontent.com/11315492/162288406-75870144-8775-427f-98a3-0b9a72f31436.mov
Not seeing this bug in my apps on macOS 10.15, so I assume this bug is specific to macOS 11+.

Can't believe you noticed this lol good eyes. Opened a PR in wry. Thanks for the detailed report!


Feature | Mount entire project and load multiple config files

What?

Mount whole project instead of only the current layer.
Load all .tfvars files found in global and account config directory when running a terraform command that requires it.

Why?

Allows for greater flexibility when working in a project.
Enables future planned features.

References

Closes #90

hello, this PR seems to make the following documentation outdated: https://leverage.binbash.com.ar/first-steps/leverage-project-setup/#fill-in-the-configuration-file
I had few problems in the bootstrap credential section.

@thpham thanks for your comment. In order to help you here it would be great if you could open an associated issue with more detail at https://github.com/binbashar/le-ref-architecture-doc/issues
It would be great if you could also join us on our Binbash Leverage community Slack channel https://join.slack.com/t/binbashar/shared_invite/zt-fw1692b6-9k4ADsWJ47lKacszphXM1w in order to try to fix this ASAP.
Thanks again for your valuable collaboration here, and looking forward to your updates no this issue.
CC: @binbashar/leverage-ref-architecture-aws-admin @binbashar/leverage-ref-architecture-aws-dev

@thpham I think we've already found the issue related with your comment @angelofenoglio we'll collab with the PR ASAP 💪🏼
CC: @diego-ojeda-binbash

@diego-ojeda-binbash let's consider we still new to fix the terraform image version in the template from 1.0.9 to 1.1.9 => https://github.com/binbashar/le-tf-infra-aws-template/blob/master/template/build.env.template
CC: @angelofenoglio @lgallard @rodriguez-matias


rhel8: (disk.py:75) | Unable to get disk metrics for /var/lib/co ntainers/storage/overlay: [Errno 13] Permission denied: '/var/lib/containers/storage/overlay'

When deploying datadog-agent from scratchon a new RHEL-8 system the agent would start but the log would be full of warnings like:
2019-12-01 15:50:33 UTC | CORE | INFO | (pkg/collector/runner/runner.go:327 in work) | Done running check file_handle, next runs will be logged every 500 runs
2019-12-01 15:50:41 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:118 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:75) | Unable to get disk metrics for /var/lib/co
ntainers/storage/overlay: [Errno 13] Permission denied: '/var/lib/containers/storage/overlay'
2019-12-01 15:50:41 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:118 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:75) | Unable to get disk metrics for /var/lib/co
ntainers/storage/overlay/d8be2543311fc0b0368c548a53d84d1d2ce7a85e592db9723f2872e9eeb87400/merged: [Errno 13] Permission denied: '/var/lib/containers/storage/overlay/d8be2543311fc0b0
368c548a53d84d1d2ce7a85e592db9723f2872e9eeb87400/merged'
2019-12-01 15:50:56 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:118 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:75) | Unable to get disk metrics for /var/lib/co
ntainers/storage/overlay: [Errno 13] Permission denied: '/var/lib/containers/storage/overlay'
2019-12-01 15:50:56 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:118 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:75) | Unable to get disk metrics for /var/lib/co
ntainers/storage/overlay/d8be2543311fc0b0368c548a53d84d1d2ce7a85e592db9723f2872e9eeb87400/merged: [Errno 13] Permission denied: '/var/lib/containers/storage/overlay/d8be2543311fc0b0
368c548a53d84d1d2ce7a85e592db9723f2872e9eeb87400/merged'
2019-12-01 15:51:11 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:118 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:75) | Unable to get disk metrics for /var/lib/co
ntainers/storage/overlay: [Errno 13] Permission denied: '/var/lib/containers/storage/overlay'
2019-12-01 15:51:11 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:118 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:75) | Unable to get disk metrics for /var/lib/co
ntainers/storage/overlay/d8be2543311fc0b0368c548a53d84d1d2ce7a85e592db9723f2872e9eeb87400/merged: [Errno 13] Permission denied: '/var/lib/containers/storage/overlay/d8be2543311fc0b0
368c548a53d84d1d2ce7a85e592db9723f2872e9eeb87400/merged'

debug info
sudo -u dd-agent df -a
Filesystem     1K-blocks     Used Available Use% Mounted on
sysfs                  0        0         0    - /sys
proc                   0        0         0    - /proc
devtmpfs        16076144        0  16076144   0% /dev
securityfs             0        0         0    - /sys/kernel/security
tmpfs           16089196<PHONE_NUMBER>8   1% /dev/shm
devpts                 0        0         0    - /dev/pts
tmpfs           16089196    25576  16063620   1% /run
tmpfs           16089196        0  16089196   0% /sys/fs/cgroup
cgroup                 0        0         0    - /sys/fs/cgroup/systemd
pstore                 0        0         0    - /sys/fs/pstore
bpf                    0        0         0    - /sys/fs/bpf
cgroup                 0        0         0    - /sys/fs/cgroup/perf_event
cgroup                 0        0         0    - /sys/fs/cgroup/cpuset
cgroup                 0        0         0    - /sys/fs/cgroup/net_cls,net_prio
cgroup                 0        0         0    - /sys/fs/cgroup/rdma
cgroup                 0        0         0    - /sys/fs/cgroup/hugetlb
cgroup                 0        0         0    - /sys/fs/cgroup/freezer
cgroup                 0        0         0    - /sys/fs/cgroup/cpu,cpuacct
cgroup                 0        0         0    - /sys/fs/cgroup/devices
cgroup                 0        0         0    - /sys/fs/cgroup/blkio
cgroup                 0        0         0    - /sys/fs/cgroup/pids
cgroup                 0        0         0    - /sys/fs/cgroup/memory
configfs               0        0         0    - /sys/kernel/config
/dev/sda1      491644368 23222424 468421944   5% /
selinuxfs              0        0         0    - /sys/fs/selinux
debugfs                0        0         0    - /sys/kernel/debug
mqueue                 0        0         0    - /dev/mqueue
systemd-1              -        -         -    - /proc/sys/fs/binfmt_misc
hugetlbfs              0        0         0    - /dev/hugepages
tmpfs           16089196    25576  16063620   1% /run/netns
tmpfs            3217836        0   3217836   0% /run/user/0
/dev/sda1              -        -         -    - /var/lib/containers/storage/overlay
overlay                -        -         -    - /var/lib/containers/storage/overlay/d8be2543311fc0b0368c548a53d84d1d2ce7a85e592db9723f2872e9eeb87400/merged
tmpfs            3217836        4   3217832   1% /run/user/1000
binfmt_misc            0        0         0    - /proc/sys/fs/binfmt_misc

I suspect that the datadog-agent gets a bit confused about docker-podman containers. Please let me know if futher info is needed in order to avoid these warnings.

I have the same issue on Ubuntu:
2020-05-13 09:22:00 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:116 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:75) | Unable to get disk metrics for /var/lib/docker/containers/1f1aa05864e3c9e59ef69a35f9a0ad225f72cbea88b2bc2d481d25e3f103b9f1/mounts/shm: [Errno 13] Permission denied: '/var/lib/docker/containers/1f1aa05864e3c9e59ef69a35f9a0ad225f72cbea88b2bc2d481d25e3f103b9f1/mounts/shm'
2020-05-13 09:22:00 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:116 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:75) | Unable to get disk metrics for /run/docker/netns/bc1e4ea407be: [Errno 13] Permission denied: '/run/docker/netns/bc1e4ea407be'

Sane issue on Ubuntu:
2021-03-26 05:50:42 PDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:122 in LogMessage) | disk:blah42 | (disk.py:132) | Unable to get disk metrics for /var/lib/docker/overlay2/blah42/merged: [Errno 13] Permission denied: '/var/lib/docker/overlay2/blah42/merged'. You can exclude this mountpoint in the settings if it is invalid.
2021-03-26 05:50:42 PDT | CORE | WARN | (pkg/collector/python/datadog_agent.go:122 in LogMessage) | disk:blah42 | (disk.py:132) | Unable to get disk metrics for /run/docker/netns/default: [Errno 13] Permission denied: '/run/docker/netns/default'. You can exclude this mountpoint in the settings if it is invalid.

Same issue here as well in ubuntu 20.04
 2022-05-27 07:49:46 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:124 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:135) | Unable to get disk metrics for /var/lib/docker/overlay2/XXXXXXXXXXXXXXXXXX/merged: [Errno 13] Permission denied: '/var/lib/docker/overlay2/XXXXXXXXXXXXXX/merged'. You can exclude this mountpoint in the settings if it is invalid.
2022-05-27 07:49:46 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:124 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:135) | Unable to get disk metrics for /run/docker/netns/XXXXXXXXXXX: [Errno 13] Permission denied: '/run/docker/netns/XXXXXXXXX'. You can exclude this mountpoint in the settings if it is invalid.

Is there a solution to this? I had the same mistake
Sep  2 10:13:33 ip-172-31-31-224 agent[541]: 2022-09-02 10:13:33 -03 | CORE | WARN | (pkg/collector/python/datadog_agent.go:124 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:140) | Unable to get disk metrics for /run/docker/netns/2ed194a27967: [Errno 13] Permission denied: '/run/docker/netns/2ed194a27967'. You can exclude this mountpoint in the settings if it is invalid.

The only working solution for me was to add datadog to root group. Eventually we decided to skip metrics for these by excluding it from config.

+1 from us for RHEL7 and 8
Excluding the file system types doesn't help, we have to exclude the mount points
file_system_exclude:
- overlay
- overlay2
- shm
- merged
- nsfs
mount_point_exclude:
- /var/lib/containers/storage
- /run/docker/netns
- /var/lib/docker/overlay2
- /run/user

+1 - same problem running on Ubuntu 22.04
Unable to get disk metrics for /var/lib/docker/overlay2/94ba973afaf3e52dc9a2d97531138424a310698a4c9263b80e292bf05e797deb/merged: [Errno 13] Permission denied: '/var/lib/docker/overlay2/94ba973afaf3e52dc9a2d97531138424a310698a4c9263b80e292bf05e797deb/merged'. You can exclude this mountpoint in the settings if it is invalid.
Already exclude this mount point and restart, but no help.

It's happening to me as well.
$ tail /var/log/datadog/agent.log
2023-07-18 08:40:56 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:131 in LogMessage) | disk:67cc0574430a16ba | (disk.py:135) | Unable to get disk metrics for /var/lib/docker/overlay2/80e74c9efbf4aa3cd1dbbc6116027c83b6503935daaf970819b4507a55e6a771/merged: [Errno 13] Permission denied: '/var/lib/docker/overlay2/80e74c9efbf4aa3cd1dbbc6116027c83b6503935daaf970819b4507a55e6a771/merged'. You can exclude this mountpoint in the settings if it is invalid.
2023-07-18 08:40:56 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:131 in LogMessage) | disk:67cc0574430a16ba | (disk.py:135) | Unable to get disk metrics for /var/lib/docker/containers/b362627fa7e3c4a7fe391dd1e4b598846b67147db9c0a752714a8e6e13511955/mounts/shm: [Errno 13] Permission denied: '/var/lib/docker/containers/b362627fa7e3c4a7fe391dd1e4b598846b67147db9c0a752714a8e6e13511955/mounts/shm'. You can exclude this mountpoint in the settings if it is invalid.

$ cat /etc/datadog-agent/conf.d/disk.d/conf.yaml
init_config:
  file_system_exclude:
    - merged
    - nsfs
    - overlay
    - overlay2
    - shm

$ datadog-agent version
Agent 7.46.0 - Commit: b2f5e36 - Serialization version: v5.0.85 - Go version: go1.19.10

This is weird:
$ datadog-agent configcheck
[skipped]
=== disk check ===
Configuration provider: file
Configuration source: file:/etc/datadog-agent/conf.d/disk.d/conf.yaml.default
Config for instance ID: disk:67cc0574430a16ba
use_mount: false
~
===

$ ls -l /etc/datadog-agent/conf.d/disk.d
total 16
-rw-r--r-- 1 dd-agent dd-agent  223 Jul 18 08:28 conf.yaml
-rw-r--r-- 1 dd-agent dd-agent 9549 Jul  6 13:48 conf.yaml.default

I managed to get this configuration working in `` for a host using Docker:
init_config:
instances:
    - use_mount: false
      excluded_filesystems:
        - overlay
        - tmpfs
        - nsfs
      excluded_mountpoint_re: /run/docker/netns/.*


Smudge error: Error downloading Pods

Starting this morning my CI has started throwing errors when trying to install your SDK:
Downloading Pods/AgoraRtcEngine_iOS/AgoraRtcKit.xcframework/ios-arm64_armv7/AgoraRtcKit.framework/AgoraRtcKit (326 MB)
      Error downloading object: Pods/AgoraRtcEngine_iOS/AgoraRtcKit.xcframework/ios-arm64_armv7/AgoraRtcKit.framework/AgoraRtcKit (d233218): Smudge error: Error downloading Pods/AgoraRtcEngine_iOS/AgoraRtcKit.xcframework/ios-arm64_armv7/AgoraRtcKit.framework/AgoraRtcKit (d23321862cff3e5270bbb98b0d48d6caf55086521d28103587a6e689c86fd4c3): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.
      Errors logged to '/Users/vagrant/git/.git/lfs/logs/20230512T181804.526821.log'.
      Use `git lfs logs last` to view the log.
      error: external filter 'git-lfs filter-process' failed
      fatal: Pods/AgoraRtcEngine_iOS/AgoraRtcKit.xcframework/ios-arm64_armv7/AgoraRtcKit.framework/AgoraRtcKit: smudge filter lfs failed

Hey, I showed this to some engineers and they don't think it's coming from Agora's end. There's a few reports around this with CocoaPods or git lfs, you might want to ask in one of those repos.
This repo is specifically for the Swift Package installation.


Where JWT token is read from and how to use it with GraphiQL?

In the documentation, it says:

After a JSON Web Token has been verified and decoded, the resulting claims will be serialized to the PostgreSQL database in two ways:

However, it is not clear where the JWT token is read from?
Also, since I'm using database roles to limit access to the database objects, it would also be very useful to use JWT with GraphiQL - this would allow me to easily test whether all permissions are set correctly for my queries for various roles. Any idea how to do it?

The JWT is read from your Authorization header. So say you had a token xyz. That token would be retrieved from a header that looked like:
Authorization: Bearer xyz

Currently, there isn’t a way to add headers in the GraphiQL interface, I’m sure there are some roundabout ways of doing it though. Watch @eugenehp’s work in the space though. Some relevant issues:

https://github.com/graphql/express-graphql/issues/101
https://github.com/graphql/graphiql/issues/148
https://github.com/graphql/graphiql/issues/96
https://github.com/graphql/graphiql/issues/59

The recommendation on this though is to create your own custom version GraphiQL and use a custom graphQLFetcher function where you can add the network specific bits (such as Authorization headers). If a version of GraphiQL with headers isn’t available anytime soon, PostGraphQL could do this. For now, see here for a reference implementation of GraphiQL.

Thanks for the very detailed explanation. Okay, for now with GraphiQL I just can use a browser extension to inject an Authorization header when requesting a particular URL.
To storea and send JWT from the client: Relay, Redux. Any other useful links with good examples?

@calebmer  made a great point.
@meglio I would check the context of the graphql server where you pass headers, and then match them to whatever you have in your authorisation layer JWT, tokens, passport, etc.

Sorry @eugenehp I don't understand what you mean.

@meglio It depends on your goal really. From what I understood in your first message, you are looking for a way to check JWT on the side of GraphQL. For that purpose you could utilise GraphQL context and bypass it to your resolve method in the GraphQL type. Let me know if that makes sense.

Sorry still confused. "On the side of GraphQL" - you mean the GraphQL Server? Yes, it seems that postgraphql does it already and runs the "SET LOCAL ROLE" upon successful authentication.
What I was trying to understand is the best practice to manipulate this JWT on the client which works with a GraphQL server.

@meglio well, there are few ways to solve it, either pass it as your InputType to your mutation, or do HTTP headers, or do something exotic like doing HTTP query param in your injection layer of something like Relay.
So pretty much all old ways of handling JWT.
Let me know if you have any additional questions.

I will just say it may be easier than adding a browser extension. Just create your own GraphiQL endpoint and add the header here: https://github.com/graphql/express-graphql/blob/681b627c1a4bf01ea193ee9fe0077dd8d731bd76/src/renderGraphiQL.js#L106-L124, like so:
headers: {
  'Accept': 'application/json',
  'Content-Type': 'application/json',
  'Authorization': `Bearer ${myToken}`,
}

Where myToken comes from local storage, cookies, a custom UI which prompts you for a token, wherever you’ve chosen to have the user input the token.
You could always use the handy prompt browser function to like in this Codepen: http://codepen.io/calebmer/pen/PzOpjz. Then your code becomes:
headers: {
  'Accept': 'application/json',
  'Content-Type': 'application/json',
  'Authorization': `Bearer ${prompt('Enter your token:', '')}`,
}

Not the prettiest solution, but it works.

I think GraphiQL Mac app does all of that already. So if you are on Mac and
want use a standalone app, that might be a good choice too.
On Tuesday, July 12, 2016, Caleb Meredith<EMAIL_ADDRESS>wrote:

Closed #83 https://github.com/calebmer/postgraphql/issues/83.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/calebmer/postgraphql/issues/83#event-720142832, or mute
the thread
https://github.com/notifications/unsubscribe/ABxW78SgBIkKO0G5PCzLbK0Yc4F49wl0ks5qU5kHgaJpZM4JJEGJ
.

Just create your own GraphiQL endpoint

It involves making a new node.js project, compiling it and deploying, does it?

If you plan on deploying it. Or just using PostGraphQL as a library and overriding the GraphiQL endpoint (only exposed when making Accept: text/html requests): https://github.com/calebmer/postgraphql/blob/master/docs/library.md
Although, if the GraphiQL Mac app does that for you like @eugenehp mentioned, that may be your best bet 👍

I would suggest this ticket is not closed until this functionality is built into the project.  @calebmer it seems that if the project offers JWT support and encourages row-level security, then the bundled implementation of GraphiQL should also support this functionality.

However, installing this extension:
https://chrome.google.com/webstore/detail/modheader/idgpnmonknjnojddfkpgkljpfnnfcklj/related
Allows you to set a header:
Authorization: Bearer "YOUR_JWT_HERE"

I agree, @chadfurman, I’ll reopen. This functionality was actually implemented by @ferdinandsalis, but I haven’t had the time to go in and merge it yet.

See auth-graphiql (https://github.com/vitalcode/auth-graphiql) that wraps GraphiQL providing support for bearer token and arbitrary URL. Great for testing GraphQL services secured with OAuth 2.0.

The Apollo Client Developer Tools Chrome extension has GraphiQL built in and works with JWT authentication. However, this option would only work if you're using Apollo.

Easy implementation to get JWT Token support in GraphiQL
https://gist.github.com/sasso/3c3d728e0049d5b66a2c19b349b7f164

Another option is using https://github.com/skevy/graphiql-app as it has support for customising HTTP headers:

I agree an out-of-the-box solution would be nice here, but really IMO it seems like something that should live in GraphiQL itself, to avoid exactly the situation we have now where there's a handful for bespoke implementations of the same concept.

I know Caleb did some tweaks to the GraphiQL version that we were using (which I may have just broken by upgrading it... Definitely need to check that before release) to make it work better with schema watching - worth keeping in mind.

@bradleyayers Perhaps GraphiQL would accept a PR adding Header/JWT functionality - are there any issues on their tracker talking about it?

There's been a big of discussion about it, and basically the position of GraphiQL is that the network layer is out of scope by design. https://github.com/graphql/graphiql/issues/59#issuecomment-179137697
But it's quite a polarising issue. If GraphiQL wants to stay network agnostic, then presumably something like a graphiql-http project should exist to provide a HTTP-opinionated flavour that includes headers.

Bradley,
But how about putting an architecture where we could use middleware and
still have the flexibility?
Think like node.js express did with its connect library and later with
almost every middleware package.
On Sat, Jul 8, 2017 at 3:12 PM Bradley Ayers<EMAIL_ADDRESS>wrote:

There's been a big of discussion about it, and basically the position of
GraphiQL is that the network layer is out of scope by design. graphql/graphiql#59
(comment)
https://github.com/graphql/graphiql/issues/59#issuecomment-179137697
But it's quite a polarising issue. If GraphiQL wants to stay network
agnostic, then presumably something like a graphiql-http project should
exist to provide a HTTP-opinionated flavour that includes headers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/postgraphql/postgraphql/issues/83#issuecomment-313884018,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABxW7wLLpWY5soMoSe8ftEDydCH4IWRsks5sL_6_gaJpZM4JJEGJ
.

@bradleyayers Thanks for the lo-down, that makes sense. Looking at the GraphiQL docs it seems you can pass it various React children, e.g. GraphiQL.Toolbar, which we could leverage to add this functionality. Are you familiar with React - if so, I think adding this functionality should be fairly straight forward?

Indeed, that sounds like a reasonable approach.

Really interested to see this feature added; will save a huge amount of explaining when giving GraphiQL links to "uneducated" sources; "just type in the JWT in headers" vs "Oh yeah, you need to download some specific version, then set headers, point it at the right endpoint...etc"

I'd also like to see this feature added 👍

We've been using Graphql IDE, which is basically a more powerful version of graphiql, and it lets you add headers to every request. Might also be safer the use than exposing graphiql publicly.

Are you aware of anything that makes GraphiQL inherently unsafe to expose publicly or is it just a case of requiring more effort/knowledge to attack (run your own GraphiQL) and/or increased attack surface area?

GraphiQL exposes the full API with complete comments etc.  Being able to hide all the comments and documentation on the API in production is important.
Having GraphiQL enabled in production is simply bad form.
On a dev machine, i.e. locally, I'd not be concerned about it myself.

I think there's might be a misunderstanding on what GraphiQL does - all the information you mention is exposed by GraphQL itself directly, GraphiQL simply runs a GraphQL introspection query so it knows what to display. Turning GraphiQL off does not prevent this introspection query from running - you just need to run your own local copy of GraphiQL to execute it.
Here's the GraphQL introspection query you can use to see all the data your GraphQL API exposes:
https://github.com/graphql/graphql-js/blob/master/src/utilities/introspectionQuery.js
For many GraphQL APIs being able to see the documentation is important (take, for example, the GitHub GraphQL API), so I don't agree that having GraphiQL in production is bad form. https://developer.github.com/v4/explorer/
If you wish to lock down what end-users can see I'd advise that you filter the queries that are able to execute against your API. (Actually I'd advise that you always do this anyway!) There are a few ways to do this depending on what you want to achieve. The best, in my opinion, is to use persisted queries which acts as a query whitelist - that way only very specific GraphQL queries are allowed. This isn't always appropriate though, so another would be to perform some additional validation on the GraphQL queries that are received by the server. You might like to look at a few of the GraphQL built-in validations in this case:
https://github.com/graphql/graphql-js/blob/master/src/validation/index.js
Of course in v4 you could also add a fairly simple plugin that would remove the comment from every single field exposed by GraphQL, if those comments are something you don't want exposed to end users.
Hope this helps!

:+1: removing comment fields with a plugin sounds like a great plan.
Yes, there are cases where you want to expose your API documentation.  Facebook etc have a public API designed to be used by third-parties.  This is not always the case, and I would say in the majority of cases this is not true.
Could you elaborate on persisted queries?  You've mentioned them a couple of times and I'm not sure how to implement them with Postgraphql / Relay Modern.

I've hacked together support for a client's app using my forks:
https://github.com/benjie/persistgraphql-webpack-plugin
https://github.com/benjie/persistgraphql
Which instead of numbering the queries instead hashes them.
You can then mod your network layer to send instead of the query the query hash; then on the server you can prefix the graphql endpoint with a middleware which overwrites the query with the persisted query by looking up the hash received. It's purely a network layer concern this way. The hashed queries can be stored anywhere; personally I track them in git but they could be uploaded to S3 or similar instead.
I've not had time to publish anything on this yet.

@benjie makes sense.  Modding the network layer to transmit query hashes dynamically is an interesting approach

[semi-automated message] Hi, there has been no activity in this issue for over 8 weeks so I'm closing it to keep the issues/pull request manageable. If this is still an issue, please re-open with a comment explaining why.

Use postman. The latest version of postman supports GraphQL

You can use PostGraphile's --enhance-graphiql to gain a (simple) header editor.


Update Subuser Username Error

Overview

Looks like on Update Subuser Username a type is on the "task" param. Right now it appears as "setusername", when it should be "setUsername". The typo is currently resulting in the error below.
{
  "error": {
    "code": 404,
    "message": "Not found"
  }
}

This change will be live this afternoon.


Terminate insertion message after insertions

For each insertion, we output a dot character in stdout, but we don't add a newline to terminate the dots after the insertions (ref: https://github.com/opprop/annotation-tools/blob/4c2eed5a8de566483dfa56166dbdaedaca79a14e/annotation-file-utilities/src/annotator/Main.java#L931).
For example, this is the current output:
Read 1 annotations from default.jaif
Processing A.java
Parsed A.java
getPositions returned 1 positions in tree for A.java
.Writing /Users/zcai/Developer/tests/java/twofiles/out/A.java
Processing B.java
Parsed B.java
getPositions returned 0 positions in tree for B.java
Writing /Users/zcai/Developer/tests/java/twofiles/out/B.java

which contains ".Writing".
In CFI, we need to monitor the lines starting with "Writing" to find out what files to type check in ROUNDTRIP_TYPECHECK mode (ref: https://github.com/opprop/checker-framework-inference/blob/07ca7254887bb9186dc9c8187cd8582554a3ce09/src/checkers/inference/InferenceLauncher.java#L366). The dot is causing some files to be ignored.
This PR should fix the above issue. It should not affect the current CFI tests because none of them is using ROUNDTRIP_TYPECHECK mode.

Thanks! Modulo some rewording this looks good. Can you re-open the PR against eisop/annotation-tools? Are there any other differences left between the eisop and opprop versions of AFU? If there are, we should split them out and merge into eisop.

Thanks! I don't think there are any different files between the two versions: https://github.com/eisop/annotation-tools/compare/master...opprop:annotation-tools:master

New PR against eisop: https://github.com/eisop/annotation-tools/pull/56


Add support for loading bytecode from file

Many shells have a limit on the length of command-line arguments, so including the full bytecode of a large contract to be analysed on the command line may be impossible. Hence, I have added an option for loading the bytecode directly from a file.

Thanks a lot, I wanted to have this option as it simplifies doing lot of things.


Document offline installation/using hal off line

Per spinnaker/spinnaker issue 2640

any update on this?

Hi, @YGwen , it's on our plate, near term.

#1097

@YGwen Let us know if this is not sufficient.

Tried this but cannot download the BOM's to update it because of proxy denying access. Is there a way to just have it so it's a standalone installation right out of the box?


Dapr Workflow Java SDK

Dapr has released workflow as a part of 1.10 release. However the SKD available only in dot net.  Java being our main language for product development, we are looking for java sdk for workflow. Any future plans to release java sdk for workflow?

@cgillum ; @nyemade-uversky  - FYA, please review this issue.

This work is underway: https://github.com/dapr/java-sdk/pull/857


[7.x.x] Bump Dependencies #5347450269

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/5347450269

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Feature Request] 1.19.4 ?

Problem
I know you have the intention to update this mod to the 1.20 ecosystem in the near future, and i dont want to rush that by any means, but a possible update to 1.19.4 (if possible) would mean the world to me!  I'm trying to make a hardcore centered modpack, but other mods i want to include only are available from 1.19.4 onwards, if this is not possible then ill gladly sit tight until 1.20 becomes available !!
Feature
1.19.2 - 1.19.4
Other Solutions
No response
Additional Information
No response

Sadly, this is easier said than done. As I've mentioned before (I think), Mojang has decided to take the modding community into account even less than they did before. Please refer to this Fabric blog post for more details: https://fabricmc.net/2022/11/24/1193.html.
Previously, Mojang tried to avoid breaking changes and only introduced them in major updates, where they were somewhat expected. Nowadays, they don't seem to care anymore. So, while players receive minor updates with bug fixes and perhaps some smallish little features, mod developers are bombarded with numerous breaking changes that really, really could have been delayed until major updates.
Consequently, there's no longer a "1.20 ecosystem," "1.19 ecosystem," etc., as was the case with 1.18 and previous versions. Every update now requires evaluation on a per-item basis. And let me tell you, updating this mod to 1.19.3 and then to 1.19.4 is much more challenging than updating it to 1.19 was.
However, this doesn't mean I'll abandon this mod. No, of course not. I'll incrementally update it to every Minecraft version released since I last touched this project; I just need time for that. Unfortunately, I currently have very little time to spare for this project, much to my regret.


New beeper

Added beeper code found on internet ; supports more modern sound cards ?

Fixes #106 , hopefully ?


Proposal to refactor contracts folder for devUX

The contracts folder is starting to look messy with a large amount of files. External developers will also add the contracts to their projects when downloading npm package.
I propose to clean it up by introducing some folders; i.e. interfaces, utils, examples, libs and core for the main logic.
Example:
.
contracts
├── core
│   ├── Dispatcher.sol
│   ├── OpConsensusStateManager.sol
│   ├── OpProofVerifier.sol
│   └── UniversalChannelHandler.sol
├── examples
│   ├── Earth.sol
│   ├── GeneralMiddleware.sol
│   └── Mars.sol
├── interfaces
│   ├── ConsensusStateManager.sol
│   ├── IbcDispatcher.sol
│   ├── IbcMiddleware.sol
│   ├── IbcReceiver.sol
│   └── ProofVerifier.sol
├── libs
│   └── Ibc.sol
└── utils
    ├── DummyConsensusStateManager.sol
    ├── DummyProofVerifier.sol
    └── GasAudit.sol

External dApp devs would then mostly be interested in interfaces and demo folders.

Updated this to match contracts prior to public testnet


Gallery Slider in home page

Current Behavior

We can add a gallery slider displaying images from community workshops etc.
Desired Behavior

The slider will swiftly switch images . It will be built using html, css and js only.
Screenshots / Mockups

We can add it in the "Our Accomplishments" section, just below it.

I would like to work on this issue. Please assign it to me.

We can add it in the "Our Accomplishments" section, just below it.

Okay, go ahead @Shr-reny

I've added the gallery in home page, Do you want me to add anything else @akshathar-navada ?

Thanks for merging, plz add the GSSOC'23 labels too @Vaishnavi-Patil2211 !


Tools.hxml missing

He guys, so when I try to run the command haxelib run lime flixel, this error shows up:
Error: Could not process argument tools.hxml (file not found)
Invalid character:
Any help is appreciated

Did you download Lime from git? Not sure why else it would need to rebuild tools. But either way, it ought to be able to find tools.hxml.
Try these commands next:

haxelib run lime --version
haxelib run lime setup

All of them say the same thing:
Error: Could not process argument tools.hxml (file not found)
Invalid character:

Run haxelib libpath lime, which will give you the path to your lime installation. Navigate to that folder and check if there is a tools folder that contains a tools.hxml. If not, then perhaps lime has not installed correctly, try reinstalling it.

It does have a folder called tools, and yet there is a file called tools.hxml. So idk why it says that, I tried reinstalling and that didn't work, perhaps I need to install it through github?

I thik I have an idea, maybe I should download from github? I thik it has more compiled code.

Lime installed from haxelib should still work properly. What version does it show if you run: haxelib list lime?
Is your lime install in the default location? Should be C:\HaxeToolkit\haxe\lib\lime\x,x,x\. If it's somewhere else maybe there is a permission issue, where some access rights are preventing haxe from being able to see the tools.hxml file.
You can also try haxelib run lime setup -v to get verbose output.

Mine is 8.2.1, but the file directory is: C:\Windows\HaxeLib\haxe\lime\8.2.1, thre is no folder called lib.

I don't think it's a good idea to have it in the C:\Windows folder. Try moving your haxelib repository somewhere else, e.g. haxelib setup C:\HaxeToolkit\haxe\lib.

My filepath is already C:\HaxeToolkit\haxe, yet there is no folder called lib, should I create one?

Okay, so I've put all of library installs to the lib folder, but it still doesn't work. Any solutions?

So haxelib libpath lime now says C:\HaxeToolkit\haxe\lib\lime\8,2,1\, correct? To confirm, did you reinstall lime after changing the lib folder?

:\

Maybe I should add lime to the environment PATH variable?

If I had to guess, it can't find tools/tools.n, and it's trying to rebuild tools which is why it is referencing tools.hxml. That's weird because Lime from Haxelib definitely includes tools/tools.n. Looking at RunScript.hx, the only way that finding tools/tools.n wouldn't work with the if (!FileSystem.exists("tools/tools.n") code is if the current working directory were wrong, which is really odd. This to me seems like a larger issue than just Lime, and maybe something is broken in the Haxe installation.
I think that you should uninstall Haxe, delete the C:\HaxeToolkit directory completely, and then reinstall Haxe and Lime from scratch. Make sure to install Haxe to the default location of C:\HaxeToolkit, and not anywhere else like C:\Windows or C:\Program Files. Similarly, use the default path for Haxelib too. Then, try to install Lime again.

Nope. Still tried it and the problem still persists

Also try running tools.n manually. cd into the tools directory, then run neko tools.n.

Anyone find any solutions yet?

I did that 3 times, and the problem still persists, idk what to do anymore

What happens when you try neko run.n from Lime's root directory?

https://github.com/openfl/lime/issues/1865#issuecomment-2490214330

From another directory? neko path/to/lime/run.n
Because if that works too, you could set up an alias and bypass Haxelib altogether.

It says the same error ```
Error: Could not process argument tools.hxml (file not found)
Invalid character:

Good to know. Seems Haxelib isn't setting the right working directory either. The next step is to figure out what directory it's actually using.
Open up tools/RunScript.hx, and insert some trace statements near the bottom:
	//...
	Sys.exit(runCommand("", "haxe", args));
}

trace(Sys.getCwd());
trace(FileSystem.exists("tools/tools.n"));

if (!FileSystem.exists("tools/tools.n") || args.indexOf("-rebuild") > -1)
{
	rebuildTools();
}

Once you make the changes, run haxe run.hxml from the tools directory, and then retrigger the error and see what it prints.

Sorry if I was ayway for awhile, was busy lol, here is what it says and looks like:

You do need hxp to do anything with Lime. What happens after installing it?

After running the line again nothing happens..

That's a success. Now when you try haxelib run lime it should print more info.

AAAAAHHHHH IM GOING INSANE

Hmm. So it isn't making it that far down? Try neko run.n directly from the Lime folder, and make sure that prints the extra data.

That worked a few days ago.

Did tools.n get deleted somehow?
If not, does neko tools/tools.n at least work from the Lime directory?

Both wrong, and yeah I did add the two trace statements

It seems like haxe/neko are just unable to read from the tools directory for some reason?

Let's simplify. First, add these two lines at the very top of main():
public static function main()
{
	Log.info(Sys.getCwd());
	trace(FileSystem.exists("tools.n"));

	//...

This covers several possible issues:

Maybe trace() is broken but Log.info() isn't.
Maybe main() was exiting before getting to the bottom, where the old trace() statements were.
Maybe rebuilding run.n silently failed somehow.
Maybe running Neko apps fails somehow.
Maybe your machine can't handle the forward slash in "tools/tools.n".

Actually, I wonder if it really is that last one. Try neko tools\tools.n from the Lime directory.

When I try haxe -lib hxp --run RunScript it says this:

When I try neko tools/tools.n it says this:

When I try neko tools.n it says this:

Duplicate class field declaration

I didn't mean copy all the lines I posted, just the two that print information. Put them at the top of the existing main() function.
Log.info(Sys.getCwd());
trace(FileSystem.exists("tools.n"));

In Haxe there can only be one of each function, or you'll get that error.

When I try neko tools/tools.n

You have to try that from outside the tools directory, or there won't be a tools\tools.n for it to find.

When I try neko tools.n

Good to see that one still works.

Well, it's printing data, so that's good. Of course the rest of it doesn't work from there, but that wasn't the point of the test.
I guess the next step is to see if we can go back to Neko. Let's do a haxe run.n, followed by haxelib run lime.

Sorry, I misspoke. It's haxe run.hxml (from the tools directory as before), then haxelib run lime.

You need to be in the tools directory before calling haxe run.hxml.

Aha, it's running from System32 for some reason. Which also seems to be the folder Command Prompt starts in. I wonder if there's a way to turn that off, but I don't know where to start in that regard.
For now, I'll try updating RunScript to use the absolute path to tools.n. More on that in a half hour or so.

Ok, please replace RunScript.hx with my updated version, and give that a shot.

Download my updated version, or copy-paste if that's easier. (Be sure to select all if copy-pasting.)
Run haxe run.hxml again. As always, this must be done from the tools directory.
Try haxelib run lime.

Ok, so that was it. For some reason your computer likes to run things from System32, and this overrides Haxelib's normal behavior.
Switching to absolute paths makes it not matter which directory we're in, so that fixes it.
In that case, you should be good to go. I'd personally recommend haxelib run lime setup to install the lime shortcut, but that's up to you.

YES! Oh my God, thank you so much, it works now!

You're welcome, and thanks for sticking with me as we debugged this.

That's very strange that haxelib run is running things in C:\Windows\System32, do you think you might be able to share the output of haxelib list too? @Mcknight231


[DO NOT MERGE] Replace llvm_asm! with asm!

Resolves #223.
This removes all usages of llvm_asm! in three steps:

Replace llvm_asm! with intrinsics where possible.
Replace llvm_asm! with wrappers provided by the x86_64 crate.
Replace llvm_asm! with asm!.

@stlankes, you mentioned to wait with the assembly in macros.rs, but I had already done them. They are exclusively in the last commit. If you want, I can remove it again.

Do we have now two x86(_64) crates in the library?

Do we have now two x86(_64) crates in the library?

The x86_64 crate is what we migrated to in eduOS. It's the crate by the rust-osdev organization. I can adapt this change to use the x86 crate if you don't want to have the x86_64 crate.

Do we have now two x86(_64) crates in the library?

The x86_64 crate is what we migrated to in eduOS. It's the crate by the rust-osdev organization. I can adapt this change to use the x86 crate if you don't want to have the x86_64 crate.

I would prefer one crate. Which one is for me not so important. Both crates are good!

Do we have now two x86(_64) crates in the library?

The x86_64 crate is what we migrated to in eduOS. It's the crate by the rust-osdev organization. I can adapt this change to use the x86 crate if you don't want to have the x86_64 crate.

I would prefer one crate. Which one is for me not so important. Both crates are good!

All right. Then I'll migrate the new code to x86 for now. Evaluating a possible migration would be another issue.

Okay, I migrated back to x86.

Worked around an issue when migrating kernel_function!, see #234.
Windows CI is failing, because the NASM website is down.

I'll have a deeper look at early-clobber before I am confident in this again.

Okay, now that one output of llvm_asm has been identified as being wrongly specified as "=r" instead of "=&r", I wanted to check the other places.
Specifically, I worried about marking the output in PerCoreVariableMethods::smp as lateout resulting in code like mov rax,gs:[rax], but that is safe.
I further optimized asm!'s options and better clarified the workaround for #234.
This is ready for review again. :D

bors r+


User-defined literals

http://en.cppreference.com/w/cpp/language/user_literal

1234_c and 1234_elastic implemented


singularity execution error

Windows Version/build number

Windows 10 CLI ver output

MS Windows [Version 10.10.15063]

WSL "gcc --version" output

(Ubuntu5.4.1-2ubuntu~14.04) 5.4.1 20160904

WSL "uname -a" output

Linux hostname 4.4.0-43-Microsoft #1-Microsoft Wed Dec31 14:42:53 PST 2014 x86_64 x86_64 x86_64 GNU/Linux

Steps required to reproduce

git clone https://github.com/singularityware/singularity.git
cd singularity
./autogen.sh
./configure
make
sudo make install
sudo singularity run shub://vsoch/singularity-images

Copy of terminal output

$ sudo singularity run shub://vsoch/singularity-images
Progress |===================================| 100.0%
ERROR  : Could not virtualize file system namespace: Function not implemented
ABORT  : Retval = 255

Expected behavior

The sun is shining, the weather is sweet...
You say please, but all I see is pizza..

Strace (running strace -ff)

https://gist.github.com/ct-clmsn/25761696b27a32e553b1577b2f30b7c1

Attempted to run the singularity container software. The software compiles successfully. But, has runtime execution errors - specifically running the introductory tutorial.

Detailed logs emailed to support

fail from your strace (appreciated) is:
unshare(CLONE_FS)                       = -1 ENOSYS (Function not implemented)

Which was implemented somewhere along the way per message here, but I can't find a dupe issue# for it or an entry in the release notes.  Try FCU 16299 and you'll probably be alright; or at least get over that fail.

@therealkenc thanks for the quick turn-around! what's the best way to do that update/patch?

Install Windows 10 Fall Creators Update.

@benhillis @therealkenc ran the update - got a new error. will submit a new issue and close this one.


Recursive deletion of members on deletion of container

Opening this issue to start discussion on moving forward with recursive deletion of members within a containers. Related to https://github.com/solid/solid-spec/issues/172
I propose that we allow this from a specification level, this will allow for agents to remove a container without first reading & then deleting all its members.
An example of when this would be useful is seen when an agent wants to no longer utilise an application that had previously been given write access to a specific folder within the agents storage pod, the user may not have rights to all directories within that container, but its still their storage pod to do whatever they please with. If we allow recursive deletion, it means that the agent doesn't need to have read or write access to those member resources, but can still delete the entire folder.

There are to parts to this conversation:

The technical side where it may not be efficient to delete all contained resources
The WAC side where it may not be correct to allow an agent to delete a container if its members cannot be deleted by the agent

The technical limitation is what #172 is leaning on, with a mention of WAC as well.
Maybe the question should be:

If an agent "owns" a container, can they delete all data contained within that container, given its theirs

I have a feeling it leads into issues where pod providers are charging users a premium for storage, and a resource becomes locked by an external agent (like an app storing secrets related to the user, in the agents storage), and the pod provider can't just "unlock" or delete that file for them, so they're stuck, with a perpetual bill for a locked file.

If we allow recursive deletion, it means that the agent doesn't need to have read or write access to those member resources, but can still delete the entire folder.

That sounds very problematic. Therefore :-1:

Thats the reason I created this issue, to discuss possible issues & alternatives.
It would be great to know the areas in which you think it would be problematic, and other suggestions as to how it should work.

Another significant issue with recursive deletes has to do with how it deals with partial failure. Does recursive delete imply some sort of atomic and/or transactional processing on the backend? If so, that would be problematic for implementing Solid at scale.

I think that this relates to the need for a pod owner to be able to backup part or all of his pod.
I must be able to own my backup.
That is not possible if I, as owner, have no access to some of the ressources.

the need for a pod owner to be able to backup part or all of his pod

Important remark: from a technical perspective, there is no such concept as a “pod owner”. A pod is a collection of resources with access control, and some agents have certain permissions to certain resources. There is technically speaking no special role for the person that we would colloquially indicate as an owner, since that person can easily give other people Control permissions to resources and then be denied access.

I thought that the pod owner was the pod webId creator. And he allways exist even if he is denied access to some ressources. He could never been denied access to root pod ressources.

I thought that the pod owner was the pod webId creator.

In practice, in some deployments, yes, but the rights deriving from that are up to the provider, and not part of the Solid technical spec.
But note that “pod WebID creator” in general does not exist.
Take my example, for instance:

My WebID is https://ruben.verborgh.org/profile/#me
One of my pods is https://drive.verborgh.org/
I happen to have Control permissions to the root folder on that pod
But if anyone else were to be given those permissions, then there is no distinction between them and me from a Solid spec perspective.
However, since I also happen to control the server at drive.verborgh.org, I do have additional powers. But, importantly, those powers do not come from the Solid spec.

And he allways exist

So not necessarily, from a Solid spec perspective.
It is perfectly possible to create a pod with folders A and B, where only X has Control access to A and only Y has Control access to B. Neither A nor B can be called an owner, not technically (because the concept doesn't exist at that level), nor otherwise (because neither of them has access to everything).

He could never been denied access to root pod ressources.

Anyone can be denied access.

I understand your point except on what I call root pod ressources. May be a very bad wording. The contact point between solid spec and real.
It may not be a spec problem, but is a technical  implementation one.
I cannot trust my pod If I cannot delete or backup it. There must be something between pod provider and whoever control pod ressources, or else it seems that we are avoiding the pod concept that need to have some properties on a conceptual or practical point of view

I cannot trust my pod If I cannot delete or backup it. There must be something between pod provider and whoever control pod ressources

I understand and agree with this; but that agreement is outside of the Solid spec.

Then I may also agree that it has to do with the implementation of node-solid-server, and I see nothing in the actual project for that.
Where could there be a discussion and spec on that aspect which may or may not have practical implication with the solid spec implementation on node-solid-server ? Owner properties management ( change of mail recovery address, ... and pod management).

There probably needs to a separate specification for user management.

Thanks for writing this up @fabiancook, as you know my vote on this is to leave deletion as non-recursive.

the need for a pod owner to be able to backup part or all of his pod

Important remark: from a technical perspective, there is no such concept as a “pod owner”. A pod is a collection of resources with access control, and some agents have certain permissions to certain resources. There is technically speaking no special role for the person that we would colloquially indicate as an owner, since that person can easily give other people Control permissions to resources and then be denied access.

Sliding OT here, but I just wrote up https://github.com/solid/user-stories/issues/42 because clearly, that user can then give up control, leading to loss of control. Files can be corrupted and so I. I remember starting a list of such loss-of-control situations some time ago, but I seem to have lost it.
One possible path would be to introduce the owner concept.

Also need to consider security, in https://github.com/solid/solid-spec/issues/196


feat(Validate-form-field): Added react final form for validation

Signed-off-by: shakti97<EMAIL_ADDRESS>Added React final form as suggested by @DianaLease
Fixes #64

@DianaLease @dselman  have a look and suggest changes :)


Have the Create Environment command present the user with pyproject.toml optional dependencies to install

pyproject.toml files can define a [project.optional-dependencies] table which lists extras that can be installed. We should offer a multi-select when running Create Environment so folks have a chance to install those extras.
For instance, if they have a test extra and they select it, we could do pip install -e .[test] to install it. Multiple extras can be added the comma-separated list.

Should make sure the flow from a UI perspective should be similar to whatever is chosen for #20277 .


Fix description of some operator shortcuts in Javadoc

The patch is obvious.

Thanks!
We need your commits to be signed, and you please fix it?
https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

Also there are javadoc errors (see the CI logs)

Signed the commit and fixed the missing '}', sorry for the mistake :-(

Seems the CI build failure isn't due to my commit.
Building of Mutiny isn't stable, I met other errors when built the previous commit locally, that's why I didn't notice the missing '{',  there were a lot of errors which I thought not my fault...

/retest /test

Thanks!


Fix destructuring errors when building

Note:
The app builds and works properly with those errors, but they're annoying.
Repro steps
Try running:
yarn run build

You'll get (among others):
Cannot destructure property 'Color' of 'window.zeaEngine' as it is undefined.

Resolved in https://github.com/ZeaInc/zea-svelte-template/commit/cb3776813b91fb764324bbe88c43d2d32caef210 and https://github.com/ZeaInc/zea-svelte-template/commit/e39f4c2edae2feadcdee70a3891b532bbe1f2e9a


Enable opting-out of form submissions

Similar to Disabling Turbo Drive on Specific Links,
guard intercepting form subissions with a similar check for
[data-turbo-drive="false"] on the submitter, <form> element, or an
ancestor.
Similarly, do not intercept when the submitter or form element
specifies a method that isn't an HTTP verb (via
formmethod="dialog" attribute or method="dialog"
attribute, respectively).
In practice, HTTP submitting <form> elements will only ever declare
method="get" or method="post". The one exceptional case is
method="dialog", which we check for as a special case.
Testing
Since we're covering behavior for the <dialog> element and running
the suite in both Chrome and Firefox, the test suite needs to polyfill
support for the <dialog> element.

Would this be a good place to incorporate the changes from https://github.com/turbolinks/turbolinks/pull/495/files?
I've not manually tested Turbo Drive with non-fetch form submissions, but from the look of Session#start, the initial replace will still break the "Are you sure…?"  refresh behaviour after rendering a form submission: https://github.com/hotwired/turbo/blob/c52d87c9426ebbbb735e9e8947b3cbdfde8a2a10/src/core/drive/history.ts#L35
After a traditional POST, calling history.replaceState will replace the POST entry with a GET, and therefore refreshing won't trigger the confirm dialog. The fix was to store the initial restoration identifier as a property on the History instance rather than replacing the browser's history state.
I'd be happy to port these changes over if there's interest?

My I ask when would this be merged? 😂😂 Quite a few issues are depending on this to be fixed. It's preventing me to use hotwire to do so many things.

Just adding in case other folks come around, I believe contrary to the initial description of this PR, the necessary attribute on the <form> needs to be data-turbo="false", not data-turbo-drive="false".
In Rails parlance,
form_with model: @xyz, url: etc, data: { turbo: false }

Which is great because data: { 'turbo-drive' => false } doesn't look nearly as slick 😜


rage.ftl ru translation

line count is not 1:1
i think this could use another formatting pass but i think it's good otherwise.. lmk 👍

line count is not 1:1

That doesn't matter; what is more important is that the line lengths are approximately the same. I'll give it a pass if necessary.

line count is not 1:1

That doesn't matter; what is more important is that the line lengths are approximately the same (except for the manpage strings, where paragraphs are unwrapped). I'll give it a pass if necessary.

gotcha. i think the manpage was where i was the most uncertain. the lines before that section are pretty close.

Looks great, thank you! I've pushed a commit that adjusts some line wrapping, removes trailing spaces, and fixes a couple of bugs (some {reference-ids} were translated, breaking them and causing Fluent to fall back to the English strings).

thank you, happy to help! glad it wasn't too bad, definitely felt that rush to make the release 😅
will remember this if more work is needed in the future.


Problem in the automated provisioning of a new application into SDN Microservice Architecture

When a new application registers in registry office , RO will forward the new application information to TAR for approval.
Once a approver approves the new application , RO will receive the request /v1/regard-updated-approval-status with the approval details
Then, RO will call v1/embed-yourself  service in the new application.
Now , new application will send "v1/bequeath-your-data-and-die" request to its old release.

But until an admin approves a connection between the "v1/bequeath-your-data-and-die operation-client" of the new application and the "v1/bequeath-your-data-and-die operation-server" of the old application in Application layer topology, authorization will be failed.
So automated provisioning of a new application into SDN Microservice Architecture will not happen on receiving the request "v1/embed-yourself" from RO. We have to come up with a proposal to avoid this problem.

Comments have not been kept during transferring the issue from RegistryOffice to ApplicationPattern.
The latest state of the discussion was adding an instance of IntegerProfile for configuring some wait time

To be checked, whether closed by mistake.

I am not sure about the potential solution discussed above.
Please, delay spending efforts in implementing it.

Finally, another solution has been specified.
RO is addressing ALT://v1/add-operation-client-to-link for creating the Link
new application => OldRelease://v1/bequeath-your-data-and-die
before calling NewApplication://v1/embed-yourself.


explicit query parameters in get methods

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: mydmdm sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


BMRP: You did not choose a playermodel, or the model you chose is invalid.

Hello, I'm a co-owner of a new BMRP server, and after several long hours of work, we had gotten our server to work. Unfortunately, when we made our character and selected their model, we are using the default BMRP player models by the way, and yes we did try other models, it all gave us the same error. I had checked the CMD but no errors that could've related to this problem had come up. Does anyone know a fix?
EDIT: Turns out that there's an error in the BMRP code, does anyone possibly have working code?

Quick tipi have been waiting for a response on mine for 2 days, no one helps here and sorry man I have nooooo idea

You're going to have to provide the code that you're currently using for the faction if you want help. We cannot guess what the code it.
If you want faster support, ask on the Discord or the official forum at: www.forums.cloudsixteen.com


Tighten the filtering prefixes

as the current rules are a bit overzealous and may filter relevant
information.

Thanks for the pull request :).
Please note that this repo is not maintained anymore. The current repo is at https://github.com/apache/groovy

replaced by https://github.com/apache/groovy/pull/256


Support versioning the compiler

Closes https://github.com/hylo-lang/hylo/issues/1120

Adds a -V / --version flag to the compiler.
Adds a script to set the compiler version. This is mainly for use in CI so that tags can be set as the version before building. The script can also be called during local development to set the version to a git hash. It could help when triaging issues to understand the commit the compiler was built at. This was the motivation for the original issue.
Updates CI to set the version of the compiler either to a tag (if a v prefixed tag is pushed), or the git hash in all other cases.

You'll notice if you look at the build log that the version is currently 836ec749b5f023a2425d006cff8985b438a8b947, which doesn't match any of the commits in the PR. The reason for this is that pull_request events create a temporary merge commit on the runner. So what is actually being tested in pull_request events is a temporary local commit on the runner, which mimics the state of git after this branch is merged to main.
There is no problem here. When CI runs on merge to main it will correctly pick up the git hash of the HEAD of main.

Great work! Thanks a lot.