ORC-1251:Support Vectored IO in ORC [Draft]

Support the new fast Vectored Read API in ORC for parallel reads.
The patch was tested internally along with S3

Hi @dongjoon-hyun
Thanks for the review. Yeah, I understand we can't upgrade the Hadoop version directly just like this. This PR is to show how the integration can be done with the upcoming Vectored IO API  https://issues.apache.org/jira/browse/HADOOP-18103 in
upcoming Hadoop 3.3.5 release and discuss the best approach to get the changes committed.
Hi @omalley ,
This is the orc patch I was talking about. Please take a look whenever you get time. Thanks

FYI, Apache ORC 2.0 Milestone is created and aims to use Hadoop 3 dependency to access all Hadoop 2 and 3 clusters.

https://github.com/apache/orc/milestone/20

Support the new fast Vectored Read API in ORC for parallel reads. The patch was tested internally along with S3

Could you share some performance benchmark tests?

slides from berlin buzzword last week
https://docs.google.com/presentation/d/1U5QRN4etbM7gkbnGO3OW4sCfUZx9LqJN/

Gentle ping.

Let me close this PR since this commit has been stale over one year already.

As of today, this item is removed from Apache ORC 2.0.0 milestone.

@mukund-thakur @HarshitGupta11 Do you have any plan to revive this work?

Let me take over this for ORC 2.0.0.

I made a PR, please take a look.
https://github.com/apache/orc/pull/1708

Thank you, @williamhyun !


Why don't use all slices in CT scans for training but use one every 10 slices?

In the file data/get_train_jpgs.py, why did you only use one every 10 slices in the CT scans for training but not all slices?
    for idx, i in enumerate(range(0,V.shape[0],10)):
        if not 'healthy' in set_name and False:
            if not i in sums2:
                continue
        data=V[i,:,:]
        data[data>500]=500
        data[data<-1200]=-1200#-1200~500
        data=data*255.0/1700
        data=data-data.min()

        data=np.stack([data,M[i,:,:]*data,M[i,:,:]*255],-1)#mask one channel
        data = data.astype(np.uint8)

        cv2.imwrite(os.path.join(output_path_slices,'nor_'+set_name+'_'
                                 +name.split(',')[0].split('/')[-1].split('.nii')[0]
                                 +'_'+str(int(i/(V.shape[0])*100))+'.jpg'),data)

Thanks for so detailly reading my codes. The sampling stride was different for different types of data in our experiments, in order to keep numbers  of different classes in the same order of magnitude. You can see in the paper that influenza data is so little and we had many COVID-19 and CAPs. The second reason is a parctical consideration that using all slices in training  cost too much time and it influence the results slightly since the training slices we sampled and used were able to fit or almost overfit the network.

Do you think that applying stride = 10 will probably skip the important slices for diagnosis in the scans?

Sorry for no replying immediantly! Different types of data was sampled with different strides and so as to data of different centers. As a result, I can hardly remind why I used 10 but the question is really worth considerasion. Since we collected so many data that the influence is not crital, that the whole training process was similar to multi instance learnig with weak supervisoin.

Thank you for your answer.


Experimental top level init

Top level initialisation. Syntactic sugar for all the underlying packages. Currently a WIP. Unsure of the interface and requirements.

I really like the look of this, helps make services much more testable.

Removed the default service.

The interface still needs some work. Also getting screwed by initialisation. Setting stuff up in micro.NewService and then again in micro.Init seems like a bad idea. At the same time trying to integrate overriding with command line flags which proves to be a pain.

The interface still needs some work. Also getting screwed by initialisation. Setting stuff up in micro.NewService and then again in micro.Init seems like a bad idea. At the same time trying to integrate overriding with command line flags which proves to be a pain.


Exception calling ".ctor" with "1" argument(s):

Run /home/runner/work/_actions/oliver-butterley/lean-update/v1-alpha/scripts/getLatest.ps1
ForEach-Object: /home/runner/work/_actions/oliver-butterley/lean-update/v1-alpha/scripts/getLatest.ps1:10
Line |
  10 |  … $versions | ForEach-Object { [System.Management.Automation.SemanticVe …
     |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Exception calling ".ctor" with "1" argument(s): "The input string '' was
     | not in a correct format."
Error: Process completed with exit code 1.

see: https://github.com/Seasawher/mathlib4-tactics/actions/runs/11176249532/job/31069206463

There was a release marked as revert_lake_changes. Did this cause the error because the semver sorting wasn't sufficiently robust for such? Was this a problem with the command  ForEach-Object { $_ -replace '^v' }?

@oliver-butterley Thank you!!


Cassandra loves username instead of user

She really hates users without name.

Thanks for the fix :). This is great!

should modify the test code


[a11y]: Tearsheet previous and next buttons are not screen reader accessible

Package
@carbon/ibm-products
Browser
Firefox
Operating System
Windows
Package version
v2.44.0-rc.1
React version
No response
Automated testing tool and ruleset
manual
Assistive technology
JAWS
Description
Reported by Raghu during screen reader testing.
This refers to previous and next buttons (visually presented as  <, > symbols).
The prev and next buttons do not receive tab focus.
Also controls are not identified in Arrow key navigation, completely inaccessible for screen reader users.

[!NOTE]
Developers were not able to see this Next and Previous elements. Need to check with Raghu and team for screenshot when ever we were able to see these elements.

Recommended fix
Confirm the functional purpose of these controls:

Make the controls keyboard reachable/operable
Make sure there are proper label, role, and state assigned to these controls

User impact
When the screen reader doesn’t identify all page elements, it impacts the experience of users who are blind or have vision impairment. They can miss important information or fail to perform an action on the web page.
WCAG 2.1 Violation
4.1.2. Name Role Value
Reproduction/example
https://carbon-for-ibm-products.netlify.app/?path=/story/ibm-products-components-tearsheet--with-navigation&globals=viewport:basic
Steps to reproduce
Reported in the Tearsheet with navigation story.
Navigate tearsheet using arrow keys.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems

@elycheea @matthewgallo The previous (<) and next (>) buttons are absolutely hidden from UI and Screen readers as well.

It is only visible if the tab list can't contain items within the given width:

aria-hidden=true and tabindex=-1 are there.

In addition to that, it has a display: none style

He mentions his friend can see it in their system visually, possibly because of their screen resolution or zoom level.

@elycheea @matthewgallo These buttons are from the Carbon Tabs component, it has a tabindex=-1, which is why it is not accessible using the Tab key

In the Carbon docs, it is mentioned that:

@makafsal Can we check if there is an equivalent issue in the Carbon core repository or if it’s an issue in our implementation? It sounds like this is the expected behavior, but if this is being flagged for us both not in Carbon core, we may need to make adjustments.

confirmed that this is the intended behavior for the carbon Tabs component. once a Tab is in focus via the tab key the other tabs are accessible via arrow keys. this is the correct behavior seen in Tearsheet and in the example of tearsheet with navigation the next tab click appropriately taking you to the next input.
if this behavior is incorrect it needs to be addressed in core. we should follow up with Raghu to make sure this is correct.

@davidmenendez The left and right keys achieve functionality for keyboard users. It satisfies Raghu's concern.

As per the discussion with Regu, this is the expected behaviour, hence closing this issue.


feat(signals-preact): add possibility of deferring effect execution to the next frame

Resolve https://github.com/preactjs/signals/issues/228
This currently adds support for useEffect like execution to the useSignalEffect, this is supported by means of a new options second argument, which is an object that allows you to pass in a property named mode. By default we will do sync execution which is the behavior we have seen before, but we also allow for a new type of behavior, namely afterPaint which is the same method used as useEffect.
Currently I did not really see a need to add useLayoutEffect but we could in the future, for React we could implement this like the following:
export const useSignalEffect = (cb, opts) => {
  const [effectTrigger, setEffect] = useState(0);

  const effectFlush = useRef();
  const callback = useRef(cb);
  callback.current = cb;

  useEffect(() => {
    const notify = () => {
	if (mode === 'afterPaint') {
		setEffect((e) => e + 1)
	} else {
		eff.flush();
	}
    }
    const eff = createFlusher(() => callback.current(), notify);
    effectFlush.current = eff.flush;
    return eff.dispose
  }, Empty);

  useEffect(() => {
    if (effectTrigger > 0) {
      effectFlush.current()
    }
  }, [effectTrigger]);
}

Do note that this would only trigger after updating the DOM-node if the relevant property is used on a DOM-node as well
demo

Closing due to inactivity

@JoviDeCroock, we've added this in our codebase and it's working great so far: https://github.com/WordPress/block-interactivity-experiments/pull/226
The only problem is that we had to use the mangled properties instead:
// Using the mangled properties:
// this.c: this._callback
// this.x: this._compute
// https://github.com/preactjs/signals/blob/main/mangle.json
function createFlusher(compute, notify) {
	let flush;
	const dispose = effect(function () {
		flush = this.c.bind(this);
		this.x = compute;
		this.c = notify;
		return compute();
	});
	return { flush, dispose };
}

I changed the implementation a bit to ignore notifications that happen before the callback has been executed and thus prevent infinite loops:

https://github.com/WordPress/gutenberg/pull/53358
Stackblitz demo


Examples Add an example how to handle data streams with Dataloader

The example should include

how data streams such as generators can be used in conjunction with the Dataloader
how to achieve train/test split with such a setup

This example should not be bound to any release, we can publish them independently.

Does the image segmentation example solve this issue?


Move pointStyle types and update plugin link&render chart

Comming from #9458, set the canvasElement on next line as type so table stays more readable and no scrollbar appears

afterDatasetsDraw hook in the renderFlorChart was missing and link naar plugin interface was dead because it seems case sensetive


Updated peerDependency to reflect current requirements

☝

Fails

:no_entry_sign:
Please assign someone to merge this PR, and optionally include people who should review.

Warnings

:warning:
The README has not been updated. Please update the README.

:warning:

Branch being merged does not follow Git Flow

Messages

:book:
Could not find any browser results.

  Generated by :no_entry_sign: dangerJS against f96e2a6a0c2aab7e55685213c5302ebf7efbdd7e


Phaser v2.4.7 RC1 - running slow

Hi,
I haven't yet looked deeper into it, but just wanted to throw this into the round. The game shows the same or even slightly higher framerate with the newest update. Though, the character moves significantly slower. It seems as the p2.js physics run in slow motion.
Has anyone had the same or a similar issue?
I am using Phaser v2.4.7 RC1, phaser-tiled (latest release) and p2.js.

If you do nothing but swap 2.4.7 RC1 for 2.4.6 does it speed-up again?

yes, I did this couple times back and forth but couldn't figure why it should be slower eventhough the fps is equal...

Try this: set game.forceSingleUpdate = false somewhere when your game first starts. That's the only thing that I think would make any difference (in 2.4.7 this is now true by default)

Yes, it is the forceSingleUpdate parameter which caused the slow down. Sorry, for stealing your time here, I should have figured this after I have had the same issue couple of month's ago when I started using particle storm, which also has this parameter to true in the examples.
I am just wondering, what is the big advantage of this being "true", that the phaser default changed at this version? Maybe I should adjust my game to run well with forceSingleUpdate?
Thank you in advance for your answer!
Cheers

That's interesting. I'm not seeing any difference in the apps we've got that use p2, but it's not exactly an exhaustive study. All the flag does is insist that there is at least one call to 'update' per loop (plus as many extra are needed to catch-up), and one call to 'render'.
Without it the loop will determine for itself if it should call 'update' or not based on elapsed time, and other things. The problem is a bit two-folded. On slow systems and generally low powered devices, having it false causes all kinds of jerky movement and inconsistent display, even if it's rendering at 60 fps. On high-end kit you don't really notice it either way.

I will update our tech demo and send you the link asap, so you can see the effect for yourself.

You can see what switching "game.forceSingleUpdate = " does to the tech demo here: http://tarutarolegends.com/shoga9team/ , if you want. (and controls, when needed: http://tarutarolegends.com/demo-controls/)
You can close this issue... Thank you very much for your quick support/help!

Yeah I toggled it from the console and everything remains at the same speed other than the character movement (which is obviously done in p2), like it's running twice as slow, but the menus etc were all fine. Sadly I can't see any source to know what you're doing though in your update.

I do have an update object managing "characters", etc being hooked into the update cycle or spliced out. Then cycling through it on update:
    update(){
        this.updateArray.forEach((func) => {func();});
    }

on the character level, the controls are handled the same way as it is common in the examples. So, there is nothing extraordinary, despite this forEach.


[Revamp] Comment box input and edit field

Is your feature request related to a problem? Please describe
The current comment box input field is not expandable and the ui is also really old and it is very hard to navigate through the comment when you have written multiline comments. Although it was updated a bit in pr #3521 but it only increased the comment input box size to 4 rows and it was not expanding with the increasing no. of lines of comments. There is also no button like bold or italic for the comment styling which is usually required in comment input boxes.
Describe the solution you'd like
these are the solutions I thought of for now . Any new suggestions are welcomed:

make the comment box dynamically sized. (feature add)
update the comment box UI to give modern look. (update UI)
Add comment box text styling buttons & their functionality. (feature add)

https://user-images.githubusercontent.com/96580571/221549875-dc8bfa3b-9de6-41fc-a0b8-f1a40b8c9980.mp4
Describe alternatives you've considered
Any Suggestions or features are welcomed.
Additional context
No response
Are you working on this?
Yes

hi I want to work on this

@Arnabdaz Can i work on this issue assign this to me


Update MongoDb Id type String instead of Int

Describe this PR
This PR corrects Inadvertent error in Relations visualization table which made Post Id type Int for Mongodb.
Changes

Just edit Int to be String

Just edited extra one in:

One-to-many relationship

Thanks for catching this. Happy to merge it after the suggestion from Jan is addressed. :)

Done


Fixed tab indentation :bug: #389

I just realized I fixed this the wrong way, I'll reopen the pr when I'm ready

Hi @waterfoul thanks for this, let me know if you need any help. You'll also probably run into problems with the current version of our AST gonzales-pe as it currently crashes on tabs.
Hopefully updating soon :smile:


Additional configuration via extra settings

Edited 16/03/15

"gitignore" and  "env-example" also accept path of a files, not only urls
"gitignore.common" is false by default
"env-example" is false by default
"content-move" is renamed to "move-content" and set to false by default
"force-gitignore" has been removed
"prevent-overwrite" now allows fine-grained control using $files array
"register-theme-folder" has been added

Edited 08/03/15

renamed "force-content-move" to "content-move"
deleted "prevent-overwrite-hard" and added support for "hard" value in "prevent-overwrite"
added support for "ask" value in "prevent-overwrite"

I have the idea to make possible to configure some aspects of the way WP Starter works thanks to composer.json extra settings.
I think all those configuration can be made available using a single wpstarter object as property of extra root object.
{
    "extra" :
    {
       "wpstarter" : { }
    }
}

The configuration I plan to add are:

"gitignore" with possible values:

true:    installation process doesn't ask any question and add default .gitignore file
false:  installation process doesn't ask nor add  .gitignore file
"ask": installation process asks if to add  .gitignore file or not. Default behaviour.
$url: (string) should be the url or the path (relative to composer.json) of a .gitignore file. This file will be downloaded/copied and placed in project root folder
$gitinore (object) when used, no question is asked,  possible properties are:

"common": (bool) common unrelevant files are added to .gitignore file when true. Default false
"wp-content": (bool) wp-content folder is added to .gitignore file when true. Default true
"vendor": (bool) vendor folder is added to .gitignore file when true. Default true
"wp": (bool) WordPress package folder is added to .gitignore file when true. Default true
"custom": (array) additional entries to add to .gitignore file . Default empty array

"env-example"  with possible values:

true: installation process adds the default .env.example file
false: installation process doesn't add any .env.example file. Default behaviour.
"ask":  installation process asks if add .env.example or not
$url (string): the url or the path (relative to composer.json) of a default .env.example file. This file will be downloaded and placed in project folder. This way is easy to have custom shared settings across projects

"move-content" with possible values:

true:   the wp-content folder contents are always moved from WP folder to project content folder, no question is asked during installation
false:  the wp-content folder contents aren't moved and no question is asked during installation.  Default behaviour.
"ask": installation process asks if to move contents or not

"register-theme-folder" with possible values:

true:   the WordPress package wp-content folder is registered as additional theme folder (see #2 ) Default behaviour.
false:  the WordPress package wp-content folder is registered as additional theme folder.
"ask": installation process asks if to register WP wp-content folder as additional theme folder.

Note that "register-theme-folder" and "move-content" are incompatible settings. To allow wp-content folder movement "move-content" must be set to true and "register-theme-folder" to false.

"prevent-overwrite" with possible values:

true:  if any of target file exists it is not overwritten, a notice is printed to console.
false: installation process doesn't care if target files already exist, just overwrite them (actually this is not default behavior for .gitignore file so it will be overwritten if "force-gitignore" is true)
"hard": if a wp-config.php file exists in project folder, installation process ends immedialy, just printing a notice
"ask": if a file exists in target folder, installation process asks to overwrite it

$files: (array) array of files that should not be overwritten if found. is possible to use jolly characters to define files, e.g. "*.php". The default settings is [ ".gitignore" ] it means .gitignore file by default is not overwritten if found.

"verbosity"  with possible values:

0:  no notice is printed by installation process. All questions just take default behavior if a specific setting is not set
1: questions, warnings and errors are printed, all the rest (comments and informations) is skipped
2:  current and default behavior, everything is printed to console

Opinions?

I think all those configuration can be made available using a single wpstarter object as property of the extra root object.

I agree 100%

The configuration I plan to add are:

Not 100% convinced of the naming scheme yet. For e.g. prevent-overwrite - prevent to overwrite what exactly? I'm in for a as-verbose-as-possible approach :) Also, this could be multi-dimensional and instead of having just yes/no/additional, be a container that allows to fine tune what to overwrite and what not by allowing file names as keys.

verbosity with possible values: 0, 1, 2

What I like about npm is that you can use -v, -vv an -vvv to adjust the verbosity-level. Not that I think that this is the solution, but we could build upon it. I'm sure you remember this WP.SE answer. I'd just go with filter_var( 'verbosity', FILTER_VALIDATE_BOOLEAN ); for the 1st and 2nd verbosity level to allow 0, false, off, no "" to turn things off (equals current 0) and   1, true, on, yes to turn it on. For extra verbosity, we could use medium (3rd) and/or max/maximum for a possible 4th level.

"ask"

My suggestion would be to use synonyms here as well. While ask is viable in a lot of spoken languages, programmers might use prompt as well. And if a program can help remembering the right settings by simply aliasing possible synonyms, it can help making less mistakes by mis-configuration.

"gitignore" .. $url

While I think this is a great idea, I also think that this would make it possible to simply remove the defaults from the WPStarter stack. When there is an array allowed, we could point to the GitHub/gitignore repo in the docs and everybody could just cherry pick what s/he or the team needs. If the ignore files get appended to each other: Great move!

force-gitignore

Imo this could be added to the gitignore settings, reducing the amount of top level keys.
One more thing: When we got a final draft of extra settings we maybe should review the wording again and try to standardize as much as possible. Maybe just throw this out on Twitter and G+ and ask for a vote or something like that.

Not 100% convinced of the naming scheme yet. For e.g. prevent-overwrite - prevent to overwrite what exactly? I'm in for a as-verbose-as-possible approach :)

Ideally I would love to use WP Starter installation command as post-update-cmd script as well.
In that case a prevent-overwrite settings that in one line allow to prevent overwrite anything that already exists I think will be handy. But yes, I totally agree that a fine-grained control would be interesting as well, but more as an additional option than the unique choice.

What I like about npm is that you can use -v, -vv an -vvv to adjust the verbosity-level. [...]

TBH I prefer numeric approach and just "force" users to use numerical values validated via
$filtered = filter_var($verbosity, FILTER_VALIDATE_INT);
$verbosity = is_int($filtered) ? abs($filtered) : $default_verbosity;

Reason is that a boolean validation doesn't make a lot of sense to me for a setting that is level-based.
Moreover, filter_var($verbosity, FILTER_VALIDATE_BOOLEAN ) is dangerous because
filter_var('unrelated-string-here-probably-for-mistake', FILTER_VALIDATE_BOOLEAN ) will be evaluated as false turning off verbosity (and so dangerously skipping questions...).
Moreover, looking at your example: -v / -vv / -vvv, what I said IMO make sense: a boolean validation in that case is not possible.
Moreover, by using a numerical approach we have possibility to add any additional level in future. Even better we can use 0 / 10 / 20 so that in feature we can easily add levels in the middle. After that in the code that have to use the setting, we can check using >= and <= instead of = that way users may set priority in settings using any number between 0 and 20 and not only that specific 3 numbers.

"ask" ... My suggestion would be to use synonyms here as well.

Seems fine.

.gitignore... While I think this is a great idea, I also think that this would make it possible to simply remove the defaults from the WPStarter stack.

What I think it's nice in the default .gitignore in the repo is that is capable to ignore WP specific files / folders (WP path, wp-config.php) and .env file. Sure we can add that link to our docs, but I know for experience that a lot of users just don't read the docs. So to ignore sensible data per "default" IMO is better for users security. Of course, users that care can use config to do what they want.
Moreover, I'm formulating in my mind the idea to allow not only actual urls as $url setting for some files (.gitignore, .env.example), but also filesystem paths (relative to project root folder).
If we do that, people are able to create own Composer packages for those files, let Composer install them and then using extra setting to let WP Starter move files in right place.
Example:
{
    "require" : {
          "wecodemore/wpstarter"        : "1.5",
          "gmazzap/my-wpstarter-files" : "*"
    },
    "extra" : {
         "wpstarter"                                : {
              "gitignore"        : "vendor/gmazzap/my-wpstarter-files/.gitignore",
              "env-example" : "vendor/gmazzap/my-wpstarter-files/.env.example"
         }
   }
}

This way we let Composer download the files for us (and so we get support for private repositories and ssl for free) and at same time people are able to create their own WP Starter packages to share settings among projects as easy as heaven :)

force-gitignore ... Imo this could be added to the gitignore settings, reducing the amount of top level keys.

Maybe we can just remove this setting and just use prevent-overwrite to prevent .gitignore overwrite. If we add fine-grained control for prevent-overwrite (as you suggested) that will be super easy and actually makes force-gitignore redundant.

One more thing: When we got a final draft of extra settings we maybe should review the wording again and try to standardize as much as possible. Maybe just throw this out on Twitter and G+ and ask for a vote or something like that.

100% agree.

I edited OP, changes described there. Below there is entire wpstarter setting object using all current proposed settings with their default values:
{
    "extra" : {
        "wpstarter" : {
            "gitignore" : "ask",
            "env-example" : false,
            "move-content" : false,
            "register-theme-folder" : true,
            "prevent-overwrite" : [
                ".gitignore"
            ],
            "verbosity": 2
        }
    }
}

Configuration has been implemented in v.2.0


Travis -> GHA

Ultimately we should unfork ourselves. We made some changes in the name of supporting ruby 2.2(?), which causes rubocop to fail, and even undoing that:

The existing tests ALL fail in travis (bundler version issue)
My attempt to migrate tests to GHA also all fail for similar core issues.

Upstream has already moved to GHA, anyways...

https://app.shortcut.com/aptible/story/26223/gha-migration-weauthn-ruby


OR query not honoured in Postgres full-text search SQL

Bug description
The SQL query that is produced when full-text searching on more than one column using an OR condition incorrectly concatenates the two columns to query them singularly.
Also, I'm not sure if this is related or a separate bug, but the order of the concatenation seems to be the reverse of the order of the fields in the query object. This will affect the results of the query given that it is possible to specify with Postgres the order that terms should appear in the searched text, eg. with the <-> operator.
How to reproduce
Example model:
model User {
  id        String @id @default(cuid()) @db.VarChar(30)
  firstName String
  lastName  String
}

Example problem query on this model:
await prisma2.user.findMany({
  where: {
    OR: [
      {
        firstName: {
          search: terms.join(" | "),
        },
      },
      {
        lastName: {
          search: terms.join(" | "),
        },
      },
    ],
  },
})

Produces SQL like the following:
SELECT "default"."User"."id", "default"."User"."firstName", "default"."User"."lastName"
FROM "default"."User"
WHERE to_tsvector(concat_ws(' ', "default"."User"."lastName", "default"."User"."firstName")) @@ to_tsquery($1)
ORDER BY "default"."User"."id" ASC;

A few things to note here:

There is no OR condition in the SQL searching both columns independently, as declared in the query object
The order of the concatenation is the reverse of the order of the columns in the query object
I think only the first search term is being used in the query ($1), unless Prisma is doing something under-the-hood to merge them in some way?

Expected behavior
I would expect the SQL produced to look something like this:
SELECT "default"."User"."id", "default"."User"."firstName", "default"."User"."lastName"
FROM "default"."User"
WHERE to_tsvector("default"."User"."firstName") @@ to_tsquery($1)
   OR to_tsvector("default"."User"."lastName") @@ to_tsquery($2)
ORDER BY "default"."User"."id" ASC;

Prisma information
Please see the "How to reproduce" section
Environment & setup

OS: macOS 14.0
Database: PostgreSQL
Node.js version: v16.20.2

Prisma Version
prisma                  : 5.8.1
@prisma/client          : 5.8.1
Computed binaryTarget   : darwin
Operating System        : darwin
Architecture            : x64
Node.js                 : v16.20.2
Query Engine (Node-API) : libquery-engine 78caf6feeaed953168c64e15a249c3e9a033ebe2 (at<EMAIL_ADDRESS>Schema Engine           : schema-engine-cli 78caf6feeaed953168c64e15a249c3e9a033ebe2 (at ../../node_modules/@prisma/engines/schema-engine-darwin)
Schema Wasm             : @prisma/prisma-schema-wasm 5.8.1-1.78caf6feeaed953168c64e15a249c3e9a033ebe2
Default Engines Hash    : 78caf6feeaed953168c64e15a249c3e9a033ebe2
Studio                  : 0.497.0
Preview Features        : fullTextSearch, views

Hi @sdgluck, I've tried reproducing this issue with<EMAIL_ADDRESS>
There is no OR condition in the SQL searching both columns independently, as declared in the query object

By the results I'm looking at, the OR filter is applied: I'm getting back user entries whose firstname or lastname contain at least one of the terms in ['jon', 'doe', 'foo', 'bar'].

The order of the concatenation is the reverse of the order of the columns in the query object

True, but doesn't seem to affect the results?

I think only the first search term is being used in the query ($1), unless Prisma is doing something under-the-hood to merge them in some way?

The provided term (containing the | symbol) is used as is

Can you please provide an example where the output provided by the Prisma-generated query is different than what you'd expect?
Prisma Schema
generator client {
  provider        = "prisma-client-js"
  previewFeatures = ["fullTextSearch"]
}

datasource db {
  provider = "postgres"
  url      = env("TEST_POSTGRES_URI")
}

model User {
  id        String @id @default(cuid()) @db.VarChar(30)
  firstName String
  lastName  String
}

TypeScript Snippet
Note: this snippet uses deleteMany to clear the user table, please don't run it in production.
import { PrismaClient } from '@prisma/client'

async function main() {
  const prisma = new PrismaClient({
    log: [
      {
        emit: 'event',
        level: 'query',
      },
    ]
  })

  await prisma.user.deleteMany({ })

  await prisma.user.createMany({
    data: [
      {
        firstName: 'Mary',
        lastName: '---',
      },
      {
        firstName: 'Jon',
        lastName: '---'
      },
      {
        firstName: 'Jon',
        lastName: 'Doe',
      },
      {
        firstName: 'Food',
        lastName: 'Bars',
      },
      {
        firstName: '---',
        lastName: 'Bar',
      },
    ]
  })

  prisma.$on('query', ({ query, params }) => {
    console.log('[query]', query)
    console.log('[params]', params)
  })

  const terms = ['jon', 'doe', 'foo', 'bar']

  const users = await prisma.user.findMany({
    where: {
      OR: [
        {
          firstName: {
            search: terms.join(' | '),
          },
        },
        {
          lastName: {
            search: terms.join(' | '),
          },
        },
      ],
    },
  })

  console.log('[users]')
  console.log(users)

  const usersRaw = await prisma.$queryRaw`
    SELECT "public"."User"."id", "public"."User"."firstName", "public"."User"."lastName"
    FROM "public"."User"
    WHERE to_tsvector("public"."User"."firstName") @@ to_tsquery(${terms.join(' | ')})
      OR to_tsvector("public"."User"."lastName") @@ to_tsquery(${terms.join(' | ')})
    ORDER BY "public"."User"."id" ASC;
  `

  console.log('[usersRaw]')
  console.log(usersRaw)
}

void main().catch((e) => {
  console.log(e.message)
  process.exit(1)
})

Stdout
[query] SELECT "public"."User"."id", "public"."User"."firstName", "public"."User"."lastName" FROM "public"."User" WHERE to_tsvector(concat_ws(' ', "public"."User"."lastName","public"."User"."firstName")) @@ to_tsquery($1) OFFSET $2
[params] ["jon | doe | foo | bar",0]
[users]
[
  {
    id: 'clsitcr060001h88w89vdg60w',
    firstName: 'Jon',
    lastName: '---'
  },
  {
    id: 'clsitcr060002h88wiswmk9qn',
    firstName: 'Jon',
    lastName: 'Doe'
  },
  {
    id: 'clsitcr060003h88wykrp0vyu',
    firstName: 'Food',
    lastName: 'Bars'
  },
  {
    id: 'clsitcr060004h88w39b7p0jk',
    firstName: '---',
    lastName: 'Bar'
  }
]
[query]
    SELECT "public"."User"."id", "public"."User"."firstName", "public"."User"."lastName"
    FROM "public"."User"
    WHERE to_tsvector("public"."User"."firstName") @@ to_tsquery($1)
      OR to_tsvector("public"."User"."lastName") @@ to_tsquery($2)
    ORDER BY "public"."User"."id" ASC;

[params] ["jon | doe | foo | bar","jon | doe | foo | bar"]
[usersRaw]
[
  {
    id: 'clsitcr060001h88w89vdg60w',
    firstName: 'Jon',
    lastName: '---'
  },
  {
    id: 'clsitcr060002h88wiswmk9qn',
    firstName: 'Jon',
    lastName: 'Doe'
  },
  {
    id: 'clsitcr060003h88wykrp0vyu',
    firstName: 'Food',
    lastName: 'Bars'
  },
  {
    id: 'clsitcr060004h88w39b7p0jk',
    firstName: '---',
    lastName: 'Bar'
  }
]

Thanks @jkomyno for your detailed response. Looks like I was thrown by the generated SQL and the fact that Prisma seems to do some optimisations based on the search term. I can't produce an example that produces results different than expected, so I will close the issue!


Fix VS profile command generation

This regressed in f06cd17. It seems like the change went untested.
This changeset also avoids calling append() twice.
Closes #15436
Validation Steps Performed

VS Developer Command Prompt works ✅

Wait, why doesn't it work the way it is?

OH, IT'S THE QUOTE. FRICK. SORRY.

Yep, the resulting path makes it more obvious:
cmd.exe /k "C:\\Program Files\\Microsoft Visual Studio\\2022\\Enterprise\\Common7\\Tools\\VsDevCmd.bat" -startdir=none" -arch=x64 -host_arch=x64

I'll edit the PR description.


When using scroll the last item is not selected in the menu

When using Scroll on the page, if the last item does not reach the top of the screen, it is never automatically selected in the left menu.

This is how it works. Unfortunately, there is no good way to fix this behavior.
Lots of other sites with similar navigation work in the same way:
I will close this issue.
In case you have any ideas of how to fix this consistently feel free to continue discussion here!


xstyled v 3.7.0 typescript error

🐛 Bug Report
After updating @xstyled/styled-components and @xstyled/system both to v "3.7.0", following TS issue appeared on all places, where ${system} is used. In version 3.6.0 everything was fine.
To Reproduce
Update to v 3.7.0, as described above and check TS (in. CLI or in IDE)
Expected behavior
No errors.
Actual result

Full dependency list
"dependencies": {
    "@apollo/client": "3.7.1",
    "@lingui/react": "3.14.0",
    "@reduxjs/toolkit": "1.8.6",
    "@sentry/react": "7.17.1",
    "@sentry/tracing": "7.17.1",
    "@xstyled/styled-components": "3.7.0",
    "@xstyled/system": "3.7.0",
    "babel-plugin-macros": "3.1.0",
    "dayjs": "1.11.6",
    "debug": "4.3.4",
    "dotenv-safe": "8.2.0",
    "graphql": "16.6.0",
    "history": "5.3.0",
    "make-plural": "7.1.0",
    "ramda": "0.28.0",
    "react": "18.2.0",
    "react-day-picker": "7.4.10",
    "react-dom": "18.2.0",
    "react-helmet": "6.1.0",
    "react-hook-form": "7.38.0",
    "react-image": "4.0.3",
    "react-redux": "8.0.4",
    "react-router": "6.4.2",
    "react-router-dom": "6.4.2",
    "react-select": "5.5.7",
    "redux-first-history": "5.1.1",
    "redux-saga": "1.2.1",
    "serialize-javascript": "6.0.0",
    "serve": "14.0.1",
    "styled-components": "5.3.6",
    "vite-aliases": "0.8.6"
  },
  "devDependencies": {
    "@babel/core": "7.19.6",
    "@babel/preset-typescript": "7.18.6",
    "@faker-js/faker": "7.6.0",
    "@graphql-codegen/cli": "2.13.8",
    "@graphql-codegen/typescript": "2.8.0",
    "@graphql-codegen/typescript-operations": "2.5.5",
    "@lingui/cli": "3.14.0",
    "@lingui/core": "3.14.0",
    "@lingui/macro": "3.14.0",
    "@ls-lint/ls-lint": "1.11.2",
    "@storybook/addon-actions": "6.5.13",
    "@storybook/addon-essentials": "6.5.13",
    "@storybook/addon-interactions": "6.5.13",
    "@storybook/addon-links": "6.5.13",
    "@storybook/builder-vite": "0.2.5",
    "@storybook/react": "6.5.13",
    "@storybook/testing-library": "0.0.13",
    "@types/debug": "4.1.7",
    "@types/jest": "29.2.0",
    "@types/ramda": "0.28.18",
    "@types/react": "18.0.24",
    "@types/react-dom": "18.0.8",
    "@types/react-helmet": "6.1.5",
    "@types/serialize-javascript": "5.0.2",
    "@types/styled-components": "5.1.26",
    "@types/xstyled__system": "1.19.3",
    "@typescript-eslint/eslint-plugin": "5.41.0",
    "@typescript-eslint/parser": "5.41.0",
    "@vitejs/plugin-react": "2.2.0",
    "babel-loader": "8.2.5",
    "concurrently": "7.5.0",
    "eslint": "8.26.0",
    "eslint-config-airbnb-base": "15.0.0",
    "eslint-config-prettier": "8.5.0",
    "eslint-plugin-import": "2.26.0",
    "eslint-plugin-local-rules": "1.3.2",
    "eslint-plugin-prettier": "4.2.1",
    "eslint-plugin-react": "7.31.10",
    "eslint-plugin-react-hooks": "4.6.0",
    "eslint-plugin-react-perf": "3.3.1",
    "jest": "29.2.2",
    "plop": "3.1.1",
    "rollup-plugin-visualizer": "5.8.3",
    "ts-jest": "29.0.3",
    "typescript": "4.8.4",
    "vite": "3.2.0"
  }

Hi @adambisek, thanks for the bug. Feel free to submit a fix for it.

This is still happening as of v3.8.0


[Enhancement] Add Min/Max Labels to RangeSlider

Summary
For the RangeSlider add Min/Max Labels so that the User can see what the range is, also allow the Disabling of one/both of the Slider handles so have an IsEnabledLow and High for example.
API Changes
Add MinLabel and MaxLabel as Strings/Color etc.
Add IsEnabledLow and IsEnabledHigh for them to be independantly enabled as Bool.
Intended Use Case
This will allow the Slider to have more customisation and control.
Who Will Do The Work?
Bit of both I am putting it out there to see if it's something that is wanted/needed by others if it gets a nod then I am happy to pick it up unless someone else wants it.

[ ] I am willing to take this on myself
[ ] Just putting this out there for someone to pick up

Hi @CliffAgius thanks for your feedback.
if you wish to hide some of thumbs, you have two options

Use regular Slider from Xamarin.Forms box
Set LowerThumbSize="0" if you wish to hide lower thumb and UpperThumbSize="0" if you need to hide upperthumb

@AndreiMisiukevich Yes I have it working great with setting the ThumbSize to Zero but be great to have as part of the control so that it's obvious.  Also means that if the value is set to non-zero in the Model you can still have it turned off in the view.
The main reason for the Issue though is the Fixed position Min/Max labels rather than having to carefully position separate Labels above the control.

Thanks! However, we are no longer adding new features to Xamarin Community Toolkit, focusing on the .NET MAUI Community Toolkit.
Please open a New Feature Discussion to implement this feature in the .NET MAUI Community Toolkit.
I've posted more information about the Future Of Xamarin Community Toolkit here: https://devblogs.microsoft.com/xamarin/the-future-of-xamarin-community-toolkit/?WT.mc_id=mobile-0000-bramin


Feature Suggestion: enable the possibility to share the tokens stack order

There are situations where the position of tokens on the stack is relevant for combat or narrative purposes. In these cases, the GM may want to share the tokens Z axis order with the players. That's why I think it would be great if there was a (optional) way to propagate the z-index of tokens among everyone.
There is a module called ZSync that does this, but I tested it on versions 0.7.10 and 0.8.7 and it doesn't seem to work in conjunction with Your Tokens Visible.
Is there a way for your module to work in conjunction with ZSync, or to incorporate that module's functionality?
Thanks again!

Based on what I see in the source code of ZSync, both these modules work
together as intended without conflict.
ZSync brings the clicked on token to the TOP of the stack for all
browsers, and sets all other tokens to a Zindex of 0 (making them equally
likely to be on the bottom).  The key is that you must control the token to
be allowed to click on it. But other than that it resets the Zindex for all
tokens to either 1 or 0.
'Your Tokens Visible' pushes the hovered-over token to the BOTTOM of your
local browser render stack, if you press 'z'.  It doesn't change the Zindex
of any token. It only changes the order in your own render stack.   It uses
hovering because the point of this feature is to remove tokens that are
obstructing your view (tokens you may not control and thus are not allowed
to click on). It moves them to the bottom of your local stack so anything
that was previously beneath it can be seen. It doesn't change the other
browsers. Players can cycle through whatever they are seeing without
affecting anyone except themself.
It isn't the intention of my module (or zsync apparently) to allow
controlling some kind of objective stack ordering.
Are you asking if I could make a method to push the hovered token backwards
AND synchronize it for every browser so someone can force a large token to
the back for all browsers?
On Tue, Jun 22, 2021 at 5:35 PM Paulo Henrique @.***>
wrote:

There are situations where the position of tokens on the stack is relevant
for combat or narrative purposes. In these cases, the GM may want to share
the tokens Z axis order with the players. That's why I think it would be
great if there was a (optional) way to propagate the z-index of tokens
among everyone.
There is a module called ZSync that does this, but I tested it on versions
0.7.10 and 0.8.7 and it doesn't seem to work in conjunction with Your
Tokens Visible.
Is there a way for your module to work in conjunction with ZSync, or to
incorporate that module's functionality?
Thanks again!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/David-Zvekic/TokensVisible/issues/11, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH3YQQQWUXG5G74M5NWQU5TTUD63XANCNFSM47EQMP6Q
.

Now with your explanation it's clear. I had forgotten that I must click on the token to get Zsync into action. My fault.
I think It's perfect that way. I can use Your Tokens Visible alone, to handle obstructing tokens, and I can click on a given token if I want to propagate its position to all users.
About what you said in the last paragraph, although that wasn't my initial question, I indeed think it would be really cool to have a feature that allows sending the selected token to the end of the stack and synchronize. It would be useful in many situations, like for vehicle tokens, for example. And if you're messing with that, you might consider incorporating ZSync functionality into your module as well, so it's a do-it-all module =)
But I'm actually satisfied with the answer so far. Thanks for your attention and for the module.

I think the ability to control stack order needs to be in Zsync. its poor code cohesion to for 2 independant modules to both try to control this, one pushing backwards and sharing, and another pushing forwards and sharing.  I will leave Zsync to implement a sharable pushback if the author wants to. It makes sense in that module and its probably easier to implement.  The feature in YTV was deliberately intended to be a local only stack order as it frequently happens that 2 different players may disagree on which tokens they need to see at the top of the stack.
I'm closing this unless someone changes my mind about it.


limited decimal precision to 2 places on verify.

addresses TM-848

:palm_tree:

This one needs to be reviewed again because Colin found more 5-digit instances

ok, this one is updated with the requested test and the latest finds from Colin.


Feature: Retract Transport bridges

Added behaviour to Transport's bridges when appear the first enemies encounter closing the bridges and open it when user kill the last enemy.
NOTE: In Level1 we have to update some objects, like the transport tiles floor, add obstacles and the trigger.
I put in the gameobjects' name of the test scene that we should update '- NEW' to recognized fast.
Test Scene -> Level1_RetractBridges.scene (it will be deleted before merged the branch).
I disabled the encounters until Transport to go faster to test. Disable the doors yourself when execute the scene.
Any suggestions to improve or need help, write it! ;)

Task linked: CU-pkdktg Retract Transport Bridges

There is a bit of an issue on the ExitPlatform caused by the rats.
I think they get bugged wen the obstacle appears on them, and somehow they remain there, but they are not there.
Since they are an agent they have an impassable body, so the player gets stuck when crossing there.
Its not an issue that must be fixed, but when passing all this to level one, those rats should be replaced somewhere else, or removed from the scene.


Boto3 requirement in the README.md

Issue #, if available: N/A
Description of changes:
I've added boto3 to the list of requirements in the README.md file. As the deploy will fail if boto3 is not present ( it is not able to detect the region and account for the bucket creation)

LGTM! Would probably be worthwhile to have a setup/check target in the Makefile in the long run, but this is good for now.


Towards #2709 - IP per Task v3

Status Phase 1:

[x] Health Checks need a specific port value instead of portIndex (PR #2731) (Merged)
[x] UI Changes
[x] AppDefinition/V2AppDefinition updated to reflect the latest design doc
[x] DiscoveryInfo introduced in PR #2745
[x] Update MarathonTask to reflect the latest design doc

[x] Remove outdated code
[x] Introduce "ipAddresses" field
[x] Filter out tasks with "ipAddress" from the TXT endpoint

[x] Make Health Checks use "ipAddress" if available (the first one should be used in case of multiple ones)
[x] Add Validation rule that makes sure IpAddress and port cannot both be supplied. If IpAddress is supplied, then the app needs NO port, but the current default is to assign one.
[x] Add a default group to the ipAddress if the user doesn't specify a list of groups. --> To rely on the user definition should be sufficient for the MVP
[x] Make the name of the default group configurable. --> To rely on the user definition should be sufficient for the MVP
[x] Add Documentation.
[ ] Remove the Mesos "doNotUseMe" dependency created to develop based on the Mesos v0.26 RC.
[x] Add integration tests (might be blocked by lack of DCOS image with net-modules) --> There will be no TestSetup for this Milestone except the NetModules Vagrant Image, which is not sufficient for integration tests.

Further Work (not part of this PR):

Add a default group to the ipAddress if the user doesn't specify a list of groups.
Make the name of the default group configurable.
Add integration tests (might be blocked by lack of DCOS image with net-modules)

Except the question regarding the sequence of TaskStatusUpdates and some minor comments - it looks good to me.

@aquamatthias thanks for reviewing such a big PR, I addressed your comments and would greatly appreciate another review.

@aquamatthias, @kolloch: I squashed the commits. This PR should be ready for the last round of reviews.
Thanks a lot for the help along the process.

+1 from my side


docs: v1 redirect

What I did

add a redirect to netlify config, which forwards /v1/* to the last good v1 docs page
add a docs versions dropdown (will only appear on the v2 docs at the moment)

Not done

create a special netlify subdomain for v1 so that we can make updates to the v1 docs without having to change the redirect url

Two things I'm seeing so far: when I go to the v1 page and I click on another component I am redirected back to the v2 of the docs.
So for example, if I go to https://deploy-preview-2161--patternfly-elements.netlify.app/components/accordion/ and switch to the v1 site I get https://deploy-preview-2161--patternfly-elements.netlify.app/v1/components/accordion/.  Then I click on the "autocomplete" component in the sidebar I am redirected to https://deploy-preview-2161--patternfly-elements.netlify.app/components/autocomplete/ and not to https://deploy-preview-2161--patternfly-elements.netlify.app/v1/components/autocomplete/.

Sorry, hit the button before adding the second lol.
The second thing is I'm not seeing the actual components loading on the v1 site probably because it's trying to load https://deploy-preview-2161--patternfly-elements.netlify.app/[resource] instead of https://61f9ac3d5f4a9200081bb953--patternfly-elements.netlify.app/[resource] like the v1 page should.

We might be able to solve that with 301 redirects on the V1 site

there's now a dropdown at https://release-v1--patternfly-elements.netlify.app, and that's the target for the dropdown on this pr. commits to the release/v1 branch will trigger a site build for the v1 docs

The design in this PR isn't perfect, but it works. IMO we should merge and then iterate on the design in a further PR

This is looking good to me, all of the links worked & it stayed on the v1 docs.  Didn't see the dropdown on the home page but not sure if it's supposed to show up there or not.  Also it looks like maybe the javascript / css isn't loading for the demos of the components but that could be something we work on like you said by pushing to that branch?

yeah we'd have to fix that on release/v1

dropdown moved to logo bar
versions.json added to docs/_data
same for the v1 branch

If the dropdown doesn't look 100%, please let's defer that to a subsequent PR

Looks good enough for now. We can clean up the style a little bit once we overhaul the docs. Thanks, @bennypowers!


Fix typos in ML project checklist and requirements.txt

Hi @ageron! Please find a few more corrections.

Hey thanks a lot @vi3itor , you're the best! 👍


Dragonloot Compatibility

please add compatibility for the dragonloot mod (https://www.curseforge.com/minecraft/mc-mods/dragonloot)

yep it will be cool it they did so


[dv/alert_handler] Initial support for low-power groups

This PR provides a basic support for low-power groups to pass CI.
Signed-off-by: Cindy Chen<EMAIL_ADDRESS>

I think this should pass alert_handler CI, but seems like the chip level has failure due to assertion errors, I will take a look soon.

I think this should pass alert_handler CI, but seems like the chip level has failure due to assertion errors, I will take a look soon.

@cindychip I have cherry-picked this fix into the main PR to check it (there are a couple of merge conflicts here).
I fixed some of the assertions, and now the thing that remains is a chip-testbench error in the scoreboard, see:  https://github.com/lowRISC/opentitan/pull/8296


Fails to install on a machine using SSO with a domain user

Describe the bug
I am using an Amazon WorkSpace VDI that uses SSO w/ active directory. My username is taylord on the system, but fleek shows in in ~/.fleek.yml as<EMAIL_ADDRESS>where redacted is my company's name. When trying to do the -- apply step from the installation guide, I get an exit status 1 and the product does not install with this error:
error: syntax error, unexpected '@'.
To Reproduce
Steps to reproduce the behavior:
Attempt to install Fleek using a domain-joined device
Expected behavior
A clear and concise description of what you expected to happen.
It should install successfully.
Environment

OS: Ubuntu Pro 22.04
Shell: bash
fleek version It failed to install, but latest as of writing.

When I remove the @redacted.local from the username fields, it gives me Error: system not found when trying again.

I found a workaround. You need to export the username before the @ then run it again.
export USER=echo $USER|cut -d'@' -f1

Hmm, tried again and it is still failing here.
installing 'home-manager-path'
building '/nix/store/65xf6x3apafl2jv7bs2ajvmg9m0bllcz-user-environment.drv'...
error: opening lock file<EMAIL_ADDRESS>No such file or directory
Oops, Nix failed to install your new Home Manager profile!
Perhaps there is a conflict with a package that was installed using
"nix-env -i"? Try running
nix-env -q

and if there is a conflicting package you can remove it with
nix-env -e {package name}

Then try activating your Home Manager configuration again.
ERROR
ERROR   Error: exit status 1
ERROR
ERROR
ERROR   Error: exit status 1
ERROR
ERROR
ERROR   Error:
ERROR
ERROR   There was an internal error. Run with FLEEK_DEBUG=1 for a detailed error message, and consider reporting it at https://github.com/ublue-os/fleek/issues

Odd, I removed ~/.nix-profile then tried again -- and it worked.


engine: _previousFrameBuffer : stores the previous frameBuffer

during calls to bindFrameBuffer(), so that unBindFrameBuffer can restore it
This should solve https://github.com/samdauwe/BabylonCpp/issues/40
I opted to do it inside Engine, since I did not want this to escape the engine context.

Hello again,
Thanks for the pull request. This fix seems to resolve many broken examples (render target textures, mirror textures, shadows, reflection probes, etc).
Best regards,
Sam


threefold connect can not work on mattermost

Description
env used : main net
version : 2.2.0
made a mattermost deployment and then tried to login with tf connect and it shows this error
contract id :133135

Update:
Investigation:
Currently unable to try/reproduce this issue since all of the deployed instances are unable to start and giving bad gateway as seen in https://github.com/threefoldtech/tfgrid-sdk-ts/issues/1977#issuecomment-1892067483

Blocked on https://github.com/threefoldtech/tfgrid-sdk-ts/issues/1977

works fine, will move it to verification

verified on devnet
version : c94d09d
deployed a mattermost and connected using threefold succesfully

https://app.testlodge.com/a/26076/projects/40893/suites/234374?expand_section=422332#case_4150343


mysite.xyz/nextcloud gives a 404 error after following the Nextcloud guide

Title. I'm on Debian 10, set up my site, SSH keys, etc. all to the letter of what's written on the site, and followed the Nextcloud guide to the letter with no errors, and still get an nginx 404 page even after triple checking everything and even reinstalling the server to try again. Looks like this was mentioned a few times in closed issues, the latest one being here, but they were all closed by the user without posting how they resolved it.

Shouldn't your instance be pointed at a subdomain? (nextcloud.example.org)

Shouldn't your instance be pointed at a subdomain? (nextcloud.example.org)

It can be done either way, but the guide only shows you how to set it up for a subdirectory, not a subdomain.

Go to https://example.org/nextcloud. This will launch the configuration wizard.

Well try setting it up as its own domain. That is my best guess. Just follow https://landchad.net/nginx and add a new config file with your desired subdomain. Rerun certbot to get https.

Shouldn't your instance be pointed at a subdomain? (nextcloud.example.org)

It can be done either way, but the guide only shows you how to set it up for a subdirectory, not a subdomain.

Go to https://example.org/nextcloud. This will launch the configuration wizard.

Did you ever figure this out? I'm running into the same issue.

I am having the same issue. Any updates from anyone?

I am having the same issue. Any updates from anyone?

No updates on my end yet. I'll probably take another stab at it this weekend if I haven't heard anything.

What is your root directive in your nginx config file for nextcloud? Is it the correct folder?

Yes, mine is /var/www/nextcloud

Ok and is your nextcloud pointed at its own subdomain or a subdirectory ?

Did you symbolic link nextcloud into /etc/nginx/sites-enabled ?
I've never installed nextcloud this way. It seems to me, the next step is to contact the guy who wrote the guide -> https://matthewevan.xyz/contact.html

Did you symbolic link nextcloud into /etc/nginx/sites-enabled ? I've never installed nextcloud this way. It seems to me, the next step is to contact the guy who wrote the guide -> https://matthewevan.xyz/contact.html

Yes I made the symbolic link to sites-enabled. Thanks for your help. I'll reach out to the writer.

I installed Nextcloud on a subdomain and just used this config, uncommenting php-fpm at the top and using my own URL: https://docs.nextcloud.com/server/13/admin_manual/installation/nginx.html#nextcloud-in-the-webroot-of-nginx
I no longer get a 403 and it redirects me to login.

Would like to say that I am also experiencing this same issue.
TLDR: Followed https://landchad.net/nextcloud.html instructions.....twice.....no joy just get 404 error using "example.org/nextcloud"
Interestingly enough, if I delete the "mywebsite" html link in the "/etc/nginx/sites-enabled" directory and try "example.org/nextcloud" I am greeted by Nextcloud setup/logon page....aka nextcloud seems to work if it is the only link in the said directory.
As soon as I create a new "mywebsite" link following "https://landchad.net/nginx.html" it brings me back to the 404 page for "example.org/nextcloud"
Makes me think that the html page "nextcloud" somehow needs adjusting to work with the(or any other html page) "mywebsite" page.
I am hoping someone has an idea what to do with the "nextcloud" page or perhaps the author will respond to our errors/woes.
Apologies if I have missed anything. I am a newb to Nextcloud and self-hosting.


Candle Stick chart type

Hi, first of all thank you for this framework.
I’ve already implemented it in my app (not public yet) and would like to know, if there is a plan to add candlesticks as chart type so I can make the chart type switchable?
Thank you.

Anyone?


Marks contexts extracted by AWSPropagation and cuts overhead

This marks contexts extracted by AWSPropagation so that calls to
rootField are reliable even when AWS isn't the current propagation
factory.
This also dramatically reduces extraction overhead by avoiding
allocation of constants, and early returning when required fields are
absent.


Need vaccination data from publish date 2021-03-19 until 2021-03-15

Need vaccination data from publish date 2021-03-19 until 2021-03-15

ni aku buat

still missing for 2021 03 18


Plot problem

I get an error message on this line, any thoughts?
Cheers Grant
rgb.quick_plot( (0,1,2), image.header.get_camera(0), vmin=0., vmax=1., ax=a)
TypeError                                 Traceback (most recent call last)
~\AppData\Local\Temp\ipykernel_9336\3603358142.py in
7                             )
8     a.set_title("Feature %d" % i)
----> 9     rgb.quick_plot( (0,1,2), image.header.get_camera(0), vmin=0., vmax=1., ax=a)
10     leg.plot(a, pos='lower left', s=(0.2,0.1) ) # plot special colorbar
11 fig.tight_layout()
TypeError: quick_plot() got multiple values for argument 'ax'

Hi Grant; I suspect the problem is the second argument of the quick_plot function. You are passing a camera object (image.header.get_camera(0)), which is needed to render hyperclouds (HyCloud.quick_plot) but not expected if HyImage.quick_plot is called.
Long story short - assuming rgb is an image and not a cloud, try replacing line 9 with:
rgb.quick_plot( (0,1,2), vmin=0., vmax=1., ax=a)

Hi Sam,
OK, will try that,
Cheers Grant
From: Sam Thiele @.>
Sent: Friday, September 29, 2023 1:55 PM
To: hifexplo/hylite @.>
Cc: grantboxer @.>; Author @.>
Subject: Re: [hifexplo/hylite] Plot problem (Issue #8)
Hi Grant; I suspect the problem is the second argument of the quick_plot function. You are passing a camera object (image.header.get_camera(0)), which is needed to render hyperclouds (HyCloud.quick_plot) but not expected if HyImage.quick_plot is called.
Long story short - assuming rgb is an image and not a cloud, try replacing line 9 with:
rgb.quick_plot( (0,1,2), vmin=0., vmax=1., ax=a)
—
Reply to this email directly, view it on GitHub https://github.com/hifexplo/hylite/issues/8#issuecomment-1740349782 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBO2QOZVPVLXDVHMA2XXNDX4ZPCRANCNFSM6AAAAAA5JA6V2M .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AFBO2QOSD5N4LCD6UYSEZZDX4ZPCRA5CNFSM6AAAAAA5JA6V2OWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTHXOQVM.gif Message ID: @.*** @.***> >

Hi Sam,
Steadily working my way through using my own PRISMA data in the MWL section.
I have now come to this cell,
mnf, w = MNF(image, bands=5) # calculate MNF filter from image
fig,ax = rgb.quick_plot((0,1,2)) # map the first 3 bands. Note that these have no physical meaning anymore.
fig.show()
and got this message. Any thoughts?
ValueError                                Traceback (most recent call last)
~\AppData\Local\Temp\ipykernel_1516\1775767081.py https://file+.vscode-resource.vscode-cdn.net/e%3A/Dropbox/RemoteSensing/Hyperspectral/HyliteTutorials/~/AppData/Local/Temp/ipykernel_1516/1775767081.py  in
----> 1 mnf, w = MNF(image, bands=5) # calculate MNF filter from image
  2 fig,ax = rgb.quick_plot((0,1,2)) # map the first 3 bands. Note that these have no physical meaning anymore.

  3 fig.show()

ValueError: too many values to unpack (expected 2)
Cheers Grant
From: Sam Thiele @.>
Sent: Friday, September 29, 2023 1:55 PM
To: hifexplo/hylite @.>
Cc: grantboxer @.>; Author @.>
Subject: Re: [hifexplo/hylite] Plot problem (Issue #8)
Hi Grant; I suspect the problem is the second argument of the quick_plot function. You are passing a camera object (image.header.get_camera(0)), which is needed to render hyperclouds (HyCloud.quick_plot) but not expected if HyImage.quick_plot is called.
Long story short - assuming rgb is an image and not a cloud, try replacing line 9 with:
rgb.quick_plot( (0,1,2), vmin=0., vmax=1., ax=a)
—
Reply to this email directly, view it on GitHub https://github.com/hifexplo/hylite/issues/8#issuecomment-1740349782 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBO2QOZVPVLXDVHMA2XXNDX4ZPCRANCNFSM6AAAAAA5JA6V2M .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AFBO2QOSD5N4LCD6UYSEZZDX4ZPCRA5CNFSM6AAAAAA5JA6V2OWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTHXOQVM.gif Message ID: @.*** @.***> >

Hi Sam,
I have worked through the minimum wavelength mapping and it resulted in an “X” file and a “model” file. How do I interpret these two files? One appears to be wavelengths as specified but the other has different set of wavelengths – are these depths of features? See this link for my files from the Cuprite (Nevada area, PRISMA data) – “https://www.dropbox.com/scl/fi/pygzyxtaw14ymwcru5qam/mwl_Cuprite.mwl.zip?rlkey=4tcdb7y19olusoxliep41xihr https://www.dropbox.com/scl/fi/pygzyxtaw14ymwcru5qam/mwl_Cuprite.mwl.zip?rlkey=4tcdb7y19olusoxliep41xihr&dl=0 &dl=0”.
Cheers Grant
From: Sam Thiele @.>
Sent: Friday, September 29, 2023 1:55 PM
To: hifexplo/hylite @.>
Cc: grantboxer @.>; Author @.>
Subject: Re: [hifexplo/hylite] Plot problem (Issue #8)
Hi Grant; I suspect the problem is the second argument of the quick_plot function. You are passing a camera object (image.header.get_camera(0)), which is needed to render hyperclouds (HyCloud.quick_plot) but not expected if HyImage.quick_plot is called.
Long story short - assuming rgb is an image and not a cloud, try replacing line 9 with:
rgb.quick_plot( (0,1,2), vmin=0., vmax=1., ax=a)
—
Reply to this email directly, view it on GitHub https://github.com/hifexplo/hylite/issues/8#issuecomment-1740349782 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AFBO2QOZVPVLXDVHMA2XXNDX4ZPCRANCNFSM6AAAAAA5JA6V2M .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AFBO2QOSD5N4LCD6UYSEZZDX4ZPCRA5CNFSM6AAAAAA5JA6V2OWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTHXOQVM.gif Message ID: @.*** @.***> >

Hi Grant,
Regarding your first error - I made breaking changes recently to the MNF function, which causes your error. Please replace that line of code with:
mnf, loadings, means = MNF( image, bands=5 )
(note that the function now returns three values, the MNF results, the band loadings and the band-means. Previously the means were not returned).
On the minimum wavelength mapping - the X file stores the corrected data that was used during minimum wavelength fitting, while the model file contains the resulting gaussian positions, widths and depths.
Generally it's not recommended to work directly with these files, but instead load the whole directory as a MWL object and then use the deepest( .. ) or closest( ... )  functions to retrieve specific features from within it. These will be returned as a HyImage instance with the following bands: depth, position, width_left, width_right. The MWL mapping tutorial here hopefully shows how to do this :-)
https://drive.google.com/file/d/1a_MsDZIdg9-MsbJ1N3tU58tK4A2uZV91/view?usp=sharing
Hope that helps!
Cheers,
Sam


401 show cloud backend data in display all sites

Show cloud backend data in https://www.webonary.org/display-all-sites/

Also, changed references to "Last update" to "Last upload".

@hanatgit I added a PHP script to recompile all the PO files.


Allow missing dependencies

When I apply configuration to project, which don't have some dependency from the list, it is crashing.
In example I didn't add @mui/lab to the project.
It would be useful to allow it.
Error:
Module build failed (from ./node_modules/react-scripts/node_modules/babel-loader/lib/index.js):
AssertionError [ERR_ASSERTION]: failed to find entry file of '@mui/lab'.
    at Function.get (node_modules/babel-plugin-direct-import/lib/internal/NodeModule.js:48:14)
    at node_modules/babel-plugin-direct-import/lib/internal/PluginOptions.js:46:34
    at Array.map (<anonymous>)
    at Function.parse (node_modules/babel-plugin-direct-import/lib/internal/PluginOptions.js:37:17)

Hey @zvs001 ! Can you share your babel config?

Hi @umidbekk
Here is config file: https://github.com/zvs001/babel-config/blob/master/react/babel.json
Btw you can try to install by readme in root.
I use it as config to different projects, so not all of them require all defined libraries, and it creating this issue.

Oh, I see. But I don't think it's a good idea to ignore errors about missing explicitly provided modules.
You want to make reusable a config, maybe it's better to use babel.config.js file and scan package.json to exclude missing dependencies.

I thought it would be useful to support by library. I think previously I didn't had such issues with babel-plugin-transform-imports.
But you suggestion also can work. Thank you.


astype({"col": "category"}) should convert Series.values type to pandas.core.arrays.categorical.Categorical

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

Ubuntu 20.04

Modin version (modin.__version__):

0.7.3+57.g23015c5

Python version:

Python 3.8.2

Code we can use to reproduce:

if __name__ == "__main__":
    #import pandas as pd
    import modin.pandas as pd

    series_length = 10_000
    df = pd.DataFrame(
        {
            "col1": ["str{0}".format(i) for i in range(0, series_length)],
            "col2": [i for i in range(0, series_length)],
        }
    )

    df1 = df.astype({"col1": "category"})
    print(df1)
    print(df1.dtypes)
    print(type(df1["col1"].values))
    print(df1["col1"].values)

Describe the problem

On Pandas column.values type is pandas.core.arrays.categorical.Categorical while in Modin it remains to be numpy.ndarray. Test for this bug was written in PR #1382 and is marked as xfail at the moment.
Source code / logs

Thanks for the bug report @gshimansky ! I was able to reproduce this on the latest master: af86009.


Proposal: rename functions assert -> ensure & assertGuard -> assert

Feature Request
Prooposal
Rename the followin functions

assert -> ensure
assertGuard -> assert

Why

Since assertGuard works the same way as the assertion function in TypeScript, I think the name assert is appropriate.
The Typia assert function has a return value of T, so rather than being an assert function, it behaves more like "check the value, return the value as is if it is OK, throw an error if it is not". Therefore, the name "ensure" is more appropriate.

This is a breaking change, so when we change it, it will be included in v7

About the assert<T>() function, it has come from typescript-is, with the returning T value definition. I know that typia.assertGuard<T>() function is more proper for the assert word meaning, but I've consider the previous typia and typescript-is users.
Your strategy is too much critical change that every previous typia and typescript-is users may confusing.

I'm really new user, so I didn't know about the history, so I was curious why Typia uses that naming.
I prefer to use a library called unknownutil in addition to Typia, and I used naming like proposal there, so I made this suggestion
Thank you for answering.
Yeah this is too critical change, I know.

https://dev.to/samchon/good-bye-typescript-is-ancestor-of-typia-20000x-faster-validator-49fi
typia has started from faster JSON stringify function only (at that time's name was typescript-json), and I'd developed nestia to utilize both typescript-json and typescript-is libraries to compose easier and faster NestJS decorators like @TypedRoute.Post() and @TypedBody() functions.
The reason why typescript-json had been renamed to typia and started supporting validations instead of typescript-is is, typescript-is had stopped maintaining at that time. typescript-is had several major bugs related to validation, and I initially tried to contribute to typescript-is. However, as typescript-is was discontinued, I've developed my own validator and renamed it typia.
Since I embrace typescript-is and have inherited maintenance from the typescript-is owner, I cannot afford to change the assert() function name. This is especially true because if you look at npm trends, you can see that the majority of typia users came from typescript-is.


VMUser introduce an option for backend authorization.

It would be great to have an option to define Bearer token or Basic Auth configuration for targets.
For instance:
kind: VMUser
  spec
    targetRefs:
     paths:
     - static:
       - ursl: [http://host1:8429,http://host2:8429,http://host3:8429]
       basicAuth:
        password:
          key: password
          name: secretname
        username:
          key: username
         name: secretname

Must produce following vmauth config with Authorization header:
users:
- username: "user"
  password: "***"
  headers:
  - Authorization: Basic BASE64_ENCODED_VALUE
  url_prefix:
  - "http://host1:8429/"
  - "http://host2:8429/"
  - "http://host3:8429/"

It's safe to store headers at configuration file, since it uses secure kubernetes secret.
For multiple, url_map headers should be used.
Related issue https://github.com/VictoriaMetrics/VictoriaMetrics/issues/4361

Can I send a pull request for this feature?

Can I send a pull request for this feature?

Feel free)

@Haleygo @f41gh7 I see this FR was implemented in operator repo. Should we close this ticket as done or follow-up in vmauth is required?

@Haleygo @f41gh7 I see this FR was implemented in operator repo. Should we close this ticket as done or follow-up in vmauth is required?

Yes, https://github.com/VictoriaMetrics/operator/pull/714 provides field TargetRefBasicAuth in vmuser, it builds seperated header with authorization token for each target, close this issue as completed.
And according to this comment, no further move is needed in vmauth.


problems with 0.30 release

Hi,
I get:

Warning: Quoted references are deprecated
on .terraform/modules/notify_slack.sns-lambda-notify-slack.notify_slack/main.tf line 107, in resource "aws_lambda_function" "notify_slack":
107:   depends_on = ["aws_cloudwatch_log_group.lambda"]
In this context, references are expected literally rather than in quotes.
Terraform 0.11 and earlier required quotes, but quoted references are now
deprecated and will be removed in a future version of Terraform. Remove the
quotes surrounding this reference to silence this warning.

(no big deal)
but then more importantly:

Error: Unable to load ".terraform/modules/edf89c618c4d7dec91d040d492f2f1de/functions/notify_slack.zip": open .terraform/modules/edf89c618c4d7dec91d040d492f2f1de/functions/notify_slack.zip: no such file or directory
on .terraform/modules/notify_slack.sns-lambda-notify-slack.notify_slack/main.tf line 74, in resource "aws_lambda_function" "notify_slack":
74: resource "aws_lambda_function" "notify_slack" {

This after upgrading my codebase from 0.11.14 to 0.12.23, albeit I doubt that could be the culprit.

Just FYI I've commented on the module and then used it again and all good.
Another thing that might have interfered: I wrote my module wrapping this module, I wonder if it's a relative path issue.
I'll try to dig into this a bit more, at least fix the warning and open a PR

Just noticed that this is just a wrapper to https://github.com/terraform-aws-modules/terraform-aws-notify-slack I wonder what's the point of this module TBH.
Funny enough I was using that and then I moved over to this to have everything 'consistent' with cloudposse style..


IGAPP-1073: Yarn2 update

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

I've also shortly looked into this issue and realised that yarn2 currently does not yet fully support our monorepo setup. For example I was not able to call the tests from a subproject, even though jest was installed in the root project. Did you also encounter this issue? I did have an issue reffering to this problem, but can't find it anymore. But if you do encounter the issue maybe https://yarnpkg.com/getting-started/qa#how-to-share-scripts-between-workspaces can help.

I've also shortly looked into this issue and realised that yarn2 currently does not yet fully support our monorepo setup. For example I was not able to call the tests from a subproject, even though jest was installed in the root project. Did you also encounter this issue? I did have an issue reffering to this problem, but can't find it anymore. But if you do encounter the issue maybe https://yarnpkg.com/getting-started/qa#how-to-share-scripts-between-workspaces can help.

Thank you for looking into this.
You can call a script container a : from everywhere, also from the subprojects. Script sharing is not a problem I see here. Locally it works fine for me. Something with the caching is not working. Here it is written that you can either cache only ./yarn, but than have to call yarn install on every job OR cache ./yarn and node_modules and only need to call yarn install once. But on Lunes project we only cache ./yarn and do not call yarn install on every job. Locally everything works fine for me.


Can not delete node

Can not delete node in ui, the delete button show the forbidden icon

Useful
Info

Versions
Rancher master UI: v2.0.37

Access
local admin

Route
authenticated.cluster.nodes.index

using view in API ,and i can delete it with api.

@yoke88  - I can't reproduce this.  Can you tell me what browser you are using and what type of cluster this is.

i'm using google chrome version 66.0.3359.117（正式版本） （64 位）， i have never used a touch screen.

I have delete the node in GUI v2.0.36, but it not work , and the same time , there is a problem related to volume add in GUI v2.0.36 ,so i upgraded to GUI v2.0.37 . after the upgrade ,i still can not delete the node,
so i mannuly delete the node with kubectl delete node ceph4 ,then delete the node using API.

Version - v2.0.0
Verified fixed in UI v2.0.41.  Let me know if you are still having issues.


install py3

update install guide with python 3 compatibility

I've re-started the tests to see if the recent Cartopy 0.13.1 release fixes things.... keep those fingers crossed!


"Could NOT find SQLite3" error when building project depending on sqlite

Hi Amir,
First of all thank you for your project, it's great to be able to use sqlite as a regular CMake project.
However, I had problems using it. I hope you are able to answer my few questions, as it could be useful for others.
I have built and installed the sqlite-amalgamation project.
To integrate the sqlite3 library to my project, I have used the way recommended in https://github.com/azadkuh/sqlite-amalgamation/blob/master/README.md:

find_package(Sqlite3)
target_link_libraries(myProjectName sqlite3::sqlite3)

Unfortunately, I have an error message when trying to build my project with cmake:

-- Could NOT find SQLite3 (missing: SQLite3_INCLUDE_DIR SQLite3_LIBRARY)

I am using CMake 3.15.4. I have seen that it contains a share\cmake-3.15\Modules\FindSQLite3.cmake file.
Is your project intended to be found with it?
I supposed those two variables SQLite3_INCLUDE_DIR and SQLite3_LIBRARY are hints for CMake's find_package to find the include dir and library file. If so, it should be mentionned in the README.md that the user needs to pass those to cmake.
Another question, why do I have to provide the sqlite library file path ? Wouldn't I have to provide the library directory instead?
Last question, once I have provided both, I have to do #include sqlite3.h instead of #include sqlite3/sqlite3.h. Is it normal?

@tetsuhaut
to make the story short, we've better to separate this repository from system sqlite (which is already available on linux, android, macOS, ...).
so you can use any sqlite version you want along with any build option you need without messing up with system sqlite and system apps.
this is the main reason for using different include/link path.

@tetsuhaut
cmake by default finds the system sqlite library which is a different library.
depending on where you install this repository by make (or ninja) install, your application needs to know the location of installation to be able to find the this library, it's include path and build options.
for example if you've installed this repository on /opt/usr (please check CMAKE_INSTALL_PREFIX), then in your application build dir you can use:
app_build_dir$> cmake app_source_dir -DCMAKE_PREFIX_PATH=/opt/usr [...other options...]

ref:

CMAKE_PREFIX_PATH
CMAKE_INSTALL_PREFIX

please check new commits on master branch


Verify Staff ID Card

ITS-Pro time category: https://its-pro.ucsd.edu/browse/MA-89
This is complete when the following have been verified:

[x] The staff ID card works in QA, with https://api-qa.ucsd.edu
[x] The user's "personal" access token is passed from the mobile app to the Staff ID WebCard

Prod is throwing a 403 error when calling the API.

Resolved in QA
Ticket submitted for deployment to Prod (CS0200577)


Unable to configure module settings in Minecraft Modules Config

Please use the search functionality before reporting an issue. Also take a look at the closed issues!
Issue description:
It would be wise to transfer the mod configuration to the Modules List/Config in game instead of the unmanageable and uncomfortable manual configuration in the mekanism.cfg file.
The creators of the Biomes O'Plenty module have done aesthetically. You should see how they did it.
Steps to reproduce:
1.Transfer the mod configuration to the Modules List in the game, instead of the unequal and inconvenient manual configuration in the mekanism.cfg file.
2.
3.
Version (make sure you are on the latest version before reporting):
Forge:
Mekanism:
Other relevant version:
If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)
[gist/pastebin/etc link here]

in game config does exist and will be fixed in the next release


Removed redundant errorDetail stringification

refs https://github.com/TryGhost/Ignition/issues/69
@kirrg001 found similar usages of JSON.stringify() for context property like here. The also seem redundant since stringification is handled on the Ignition side similarly to errorDetails - https://github.com/TryGhost/Ignition/blob/master/lib/logging/GhostLogger.js#L237. Maybe there's some other reason for this stringification that I'm missing? :thinking:  Let me know what you think :smiley:

Yeah looks like these stringifications were added to make the log output prettier, which should be handled in the logger itself.

Cool. I'll update all the other instances of JSON.stringify() used for context as well then :+1:


Bugfix in classify file names

This PR intends to fix some bugs in classify file names by using common functions with train.
Multi-cnn results are concatenated.

Thanks.
I merge this one !


openvswitch: 2.17.2 -> 3.0.1; openvswitch-lts: 2.5.12 -> 2.17.3

Some love for the ovs packages. Also inherits the sphinxHook into top-level.
The diff between the two packages is now minimal, so might as well go for a generic.nix setup.

Enables tests
Generates manpages into man output
Sets up meta.changelog
Some reformatting
Generalize the bulder

Ideally we can get this into 22.11, so we don't ship the EOL 2.5.x version there.
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

❯ diff pkgs/os-specific/linux/openvswitch/*.nix
21c21
<   version = "3.0.1";
---
>   version = "2.17.3";
28c28
<     hash = "sha256-5KEXFtCRn1syOSKLMrrcEJtWGl/maLlUfhQ7CxlbvWg=";
---
>     hash = "sha256-RGgR/JGuJFzDGQSmk3H7C/BEb3sk6yOaA320ADUwEcA=";
86d85
<

@ofborg build openvswitch
@ofborg build openvswitch-lts


Expected parent IDs to be set when ordering by parent ID.

Hi Prisma Team! My Prisma Client just crashed. This is the report:
Versions

Name
Version

Node
v18.9.0

OS
debian-openssl-1.1.x

Prisma Client
5.3.1

Query Engine
61e140623197a131c2a6189271ffee05a7aa9a59

Database
mysql

Logs
ma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:request_handler {"name":"PrismaClientRustPanicError","clientVersion":"5.3.1"}
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:request_handler {"name":"PrismaClientRustPanicError","clientVersion":"5.3.1"}
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true
prisma:client:libraryEngine sending request, this.libraryStarted: true

Client Snippet
// PLEASE FILL YOUR CODE SNIPPET HERE

Schema
// PLEASE ADD YOUR SCHEMA HERE IF POSSIBLE

Prisma Engine Query
{"X":true}}}

Hey @sncflesardoines , can you please share your schema with us, as well as a small reproduction, and perhaps a small dataset?

Hey @sncflesardoines  ,
Did you get a chance to have a look at @millsp  previous comment? It'd be helpful for us to move your issue forward.
Without further information, we'll have to close this issue. Thank you 🙏

As we've tried to reach @sncflesardoines twice without success, we're now closing this issue.
Please leave a comment below with a reply to this message if you see this issue, and we'll reopen it. Thanks!


Add e2e test for dummy projects

Motivation
Main motivation is to avoid breaking the dummy relying party or issuer.
In this PR,

I set up an e2e test using the dummy RP requesting a credential to the issuer.
Add the test to the CI pipeline.

Changes

Add a new project for the e2e test: dummy-e2e.

Tests

Add test ids to the relying party HTML.
Add internet identity to dfx.json and a dummy candid file.
Add rust-toolchain.toml
Add a Github workflow to prepare the environment and run the e2e tests.

Todos

[ ] Add entry to changelog (if necessary). NOT NECESSARY, no changes in the SDK projects.

@frederikrothenberger ready for another review


Add SwiftPM errorformat

This command can produce normal errors with a column, but also those
without, so we need both formats.

Thanks!
--
Keith Smiley

On Jun 29, 2018, at 08:47, Daniel Hahler<EMAIL_ADDRESS>wrote:
Merged #1986.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Submitting download-plots.py app

added download_plots app for downloading the graphs with dcc.download
( the app uses 3 images images repeatedly but the graph get's updated everytime we generate the random values using random_values button

HI @someshfengde thank you for turning in the app. I modified it so it downloads a text file because we don't have any examples of that. I also added callback context because we have very few examples there as well.

Thanks @Coding-with-Adam  got it :+1:


Integrate argent web wallet - new version

Description
Integrate new version of argent web wallet
Acceptance Criteria

[ ] Add new version of argent web wallet in current version of Dapp (3525)
[ ] Give a Feedback to Argent X : organised a call if needed

Connectors for webwallet:

https://web.dev.argent47.net -> goerli-alpha-2
https://web.hydrogen.argent47.net -> goerli-alpha
https://web.staging.argent47.net -> mainnet-alpha
https://web.argent.xyz -> mainnet-alpha


Add a prefix attribute

Adds an attribute which adds a prefix onto the file paths handled by rust-embed. get now requires the prefix, and iter returns file paths with the prefix. I'm not sure if this is a backwards-compatible change. The only issue is if another macro uses the prefix attribute, which is probably unlikely, but it's possible. Usually you would wrap every attribute in a crate-specific attribute, e.g. #[embed(folder = "...")], so adding another attribute is not a problem.
use rust_embed::RustEmbed;

#[derive(RustEmbed)]
#[folder = "examples/public/"]
#[prefix = "prefix/"]
struct Asset;

fn main() {
  assert!(Asset::get("prefix/index.html").is_some());
}

Closes #132

I think this is a backwards-compatible change since prefix is an optional attribute. Yes wrapping all the attributes in an embed() would be nice but we can change that later though since it will be a breaking one. Thanks for the PR @Mcat12 .

I think this is a backwards-compatible change since prefix is an optional attribute. Yes wrapping all the attributes in an embed() would be nice but we can change that later though since it will be a breaking one. Thanks for the PR @Mcat12 .


Write document to capture various persona's that UI workflow should support

Currently the focus of the UI is contributor persona, and we are evolving the UI based on the feedback from the users. Closing this issue as of now, and we will revisit it once we get to the stage where we would like to support more personas.


Update readme, package.json to point to ava organization github

Chipping in my little bit based on https://github.com/avajs/ava-codemods/pull/21#issuecomment-220176296

👍