Constant FILTER_SANITIZE_STRING is deprecated error

Describe the bug
I hosted it and it shows this error on my localhost webpage

To Reproduce
Steps to reproduce the behavior:

Host it via termux
See the error

Expected behavior
Bridge works
Screenshots
See above.
Smartphone (please complete the following information):

Device: Moto E7 Power
OS: Android 10
Browser Chrome
Version 95

Additional context
I followed this https://parzibyte.me/blog/en/2019/04/28/install-apache-php-7-android-termux/amp/
And also changed
LoadModule php7_module /data/data/com.termux/files/usr/libexec/apache2/libphp7.so
to
LoadModule php_module /data/data/com.termux/files/usr/libexec/apache2/libphp.so
During server setup as it was giving error before(idk if this is relevant)

Fixed if I use php7-apache module isntead of php-apache module

Reopening, since it reproduced on php 8.1

https://stackoverflow.com/questions/69207368/constant-filter-sanitize-string-is-deprecated


CQ-4321398 Fix symlink logic for AMS dispatcher converter

PR contains a fix for [CQ-4321398] Fix symlink logic for AMS dispatcher converter and also incorporates test cases for the introduced changes.
Description

Related Issue

Motivation and Context

How Has This Been Tested?

Added Unit Tests
Manual testing with customer data

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

LGTM. Hope we have run tests with customer data..

@ukgaurav , yes tests are verified with multiple customers data and UT also covers different aspects !

Functionality wise looks good to me.
Just one suggestion. As we can evaluate the enabled & available vhost and enabled & available farms path. In amsDispatcherConfigConverter.js, in functions iterating over files to create symlinks, instead of passing parameters we can directly call the function and evaluate these inside the function as we are doing it in other function.

@prateek610 , it works either ways with me , but the only purpose of passing them as parameters is to make them generic enough and feasible to writing UT in case if ever introduce business logic in it, also if you observe the similar functions in singlefileconverter.js could have brought (common functionality / repetitive code) of creating "symbolic link" to fileoperations.js to make it modular. Today they serve tighly bound purpose with hardcoded paths. Let me know if you still think otherwise, we can make the change.

also if you observe the similar functions in singlefileconverter.js could have brought (common functionality / repetitive code) of creating "symbolic link" to fileoperations.js to make it modular

+1

@ManasMaji / @prateek610  , all the review comments are incorporated , please review again !


Issue: Running multiple scenarios in 1 feature file (Application with SSO)

We are using the "protractor-cucumber-framework" for our test automation needs, we encountered an issue while running multiple scenarios in 1 feature file.
Description: The application under test is having a SSO login, when i run the scenarios using the feature tag / scenario tag, the window for the second scenario opens before the first scenario closes. We tried to close the Webdriver window using browser.close();, in that case the second scenario fails due to the reason "Unable to find session id"
Feature File:
@bookSearch
Feature: To search a book on the online store
As a user I want to search a book online so that I can select a book online
@authorName
Scenario: Search with Book Name
Given I am on the online search page to look up for a book based on author Name
When I click on search
Then the search results related to the book name should be displayed
@Title
Scenario: Search with Title
Given I am on the online search page to look up for a book based on Title
When I click on the serach after entering the Title
Then the search results related to the book  Title should be displayed
Config file:
exports.config = {
	framework: 'custom',

	  frameworkPath: require.resolve('protractor-cucumber-framework'),
suites: {

    DemoSearch: 'test/features/BookSearch/bookSearch.feature'
},

cucumberOpts: {

  require:'test/TestScripts/BookSearch/*_Search.js',

 //   tags:'@authorName,@Title',

    format: 'summary',
    keepAlive: false
},

 capabilities: {
    browserName: 'internet explorer',
     version:'8',
    browserAttachTimeout:20000,
    enableElementCacheCleanup:true,
    javascriptEnabled:true,
   	ignoreProtectedModeSettings:true,
    'ie.ensureCleanSession':false,
     shardTestFiles:true,
     maxInstances:2

},

resultJsonOutputFile: 'TestResult/report.json',

jasmineNodeOpts: {
    defaultTimeoutInterval: 20000
}

};
The step definitions are in 2 different .js files, we tried with all step definitions in 1 file, that doesn't work too. Let us know if there any solution that can be implemented or the Framework / tool needs a update?
Any help is highly appreciated!

It was more of a "StaleelementReference" issue, we handled it after implementing ptor wait and sync code. Closing the issue

I am still seeing this issueon version 0.6.0. Is this fixed ?


Update for user story 426

URL link
Issue
#426
Description
FILL IN DETAILS HERE
Checklist for Pull Requests

[ ] Supplied as many details as possible on this change
[ ] Included the link to the associated issue in the Issue section above
[ ] The code conforms to the general development guidelines.
[ ] The code has unit tests where applicable and is easily unit-testable
[ ] This branch is appropriately named for the associated issue

@oliversberzs - Could you review?


Fully automate dev setup with Gitpod

This commit implements a fully-automated development setup using Gitpod.io, an
online IDE for GitHub and GitLab that enables Dev-Environments-As-Code.
This makes it easy for anyone to get a ready-to-code workspace for any branch,
issue or pull request almost instantly with a single click.

Thank you for your PR!
I'm not sure we need this -- could you open an issue for this and it can be discussed there?
Thanks!


Moving up and down lines with tabs moves the cursor left and right

Moving up and down lines should keep the cursor in the same place within the line visually. Right now it is still operating on the character.

Done!


CAMEL-9108: Fix KafkaProducer URI

Guarantees that if the KafkaEndpoint has a UriParam
of topic the KeyedMessage will be sent to that topic,
if it does not have a topic and the Exchange message
has a header of kafka.TOPIC to use that instead.
If executing an operation similar to:
from("kafka:localhost:9092?topic=A&groupId=B....").to("kafka:localhost:9092?topic=B.....")

The target topic is currently ignored in favor of topic A

I've opened a bug in Jira for this issue:
https://issues.apache.org/jira/browse/CAMEL-9108

Was already fixed in CAMEL-8923.


html.escape not found in python2

Error message:
Traceback (most recent call last):
  File "linkfinder.py", line 375, in <module>
    url = html.escape(endpoint["link"])
AttributeError: 'module' object has no attribute 'escape'

Last time I fixed this issue, it turns out that LinkFinder worked on my machine because I silently have "future" package installed. Any machine running python2 without that package will fail.
Thank you Vishal for reporting this to me.
Here is the point of this issue.
Should I still fix it as python2 support ? Fixing it will take just few minutes but it will make the code bit messier and python2 will be deprecated in 4 months anyway.
@EdOverflow What is your opinion ?

From Vishal opinion, he's ok with using python3 and agree that python2 won't be helpful soon. Also, most people might (or should start) use python3 now. If you're agree with us both, we will just have to update readme to support only python3.

Thank you for bringing this to my attention, @Bankde. I personally prefer sticking to Python 3 since Python 2 will retire soon. This does mean we should probably update the README.md file to make this clear to anyone using LinkFinder.

Yes we should. Could you please update few lines ?
In readme.txt
LinkFinder supports Python 2 & 3.
In linkfinder.py
Line 2: # Python 2.7.x - 3.6.x
So I don't have to create PR.
I have noticed some messes that (possibly!?) come from supporting python2 such in Line 16-26. This might take some time to figure out what happens there so I will create PR later.
Thank you.

Updated accordingly. Let me know if that works for you, @Bankde.

They look good. Thanks.


Switch to sbt-dynver

as mentioned in https://github.com/lightbend/scala-logging/pull/256
and probably related to #254

sbt-ci-release actually includes sbt-dynver, and currently this repo uses sbt-release, which has different expectations than sbt-dynver. so I think this can only happen in the context of #254


Factorial answer incorrect starting 21!

Up till 20! factorial, the answer is correct. But starting 21!, the answers are incorrect by (-1)!. For example, if I calculate 22!, the answer I get is (22-1)!, or 21!
And the answer for 20! and 21! factorial is the same.

In function
    func factorial() -> Double
This line is the problem
 for i in 2 ..< Int(self)
Changing it to this fixes the issue.
 for i in 2 ..< Int(self+1.0)

At first I thought this was a different issue, but you have indeed found a legit bug! Thank you!


[AKS] az aks create: Raise error when specifying --pod-cidr with --network-plugin azure without overlay

Related command

az aks create
Description

Raise an error instead of logging a warning when using --pod-cidr with --network-plugin azure without --network-plugin-mode overlay
Testing Guide

azdev test acs.test_get_network_plugin
History Notes

[AKS] BREAKING CHANGE: az aks create: Specifying --pod-cidr with Azure CNI will return an error instead of logging a warning when not use overlay mode

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

AKS


[QUESTION] Change datatype of the primary key

Hey there,
I really love your database but just recently can into a problem with my initial setup of the database.
This is my current table structure:
{
  "_id": {"$numberLong": "1"},
  "From": {"$numberLong": "123"},
  "To": {"$numberLong": "124"},
  "Reason": "No permission to execute the command",
  "Number": {"$numberLong": "31"},
  "WarningType": "Warning",
  "Time": {"$date": "2020-12-10T19:56:15.8480000Z"},
  "GuildId": {"$numberLong": "1234"}
}

I'd love to change the datatype from System.Int64 _id to System.String
I'm aware of How do I migrate data structures ? #524, but this issue is a bit old and I can't translate it on my own into the new engine system.
Thanks ahead for any help.

I see two possible (untested) ways:
Using a temporary collection
var collectionSource = db.GetCollection("CollectionName");
var collectionTemp = db.GetCollection("CollectionName_Temp");
var documents = collectionSource.FindAll();
foreach (var document in documents) {
  document["_id"] = new BsonValue(document["_id"].AsInt64.ToString());
  collectionTemp.Insert(document);
}
db.DropCollection("CollectionName");
db.RenameCollection("CollectionName_Temp", "CollectionName");

Copy the data (with the new ID column) to a temporary collection
Delete the old collection
Rename the temporary collection to the name of the old collection

Using BsonDocument
Use the "untyped" LiteDbCollection, e.g.:
var collection = db.GetCollection("CollectionName");
var documents = collection.FindAll().ToList();
foreach (var document in documents) {
  collection.Delete(document["_id"]);
  document["_id"] = new BsonValue(document["_id"].AsInt64.ToString());
  collection.Insert(document);
}

Thanks!
I used your second method and can confirm it works properly.
You saved me.
Thank you so much.

This worked for me.  The primary key is an Int64
Public Class ClientRec
Public Property ID As Int64
Public Property Name As String
End Class
Sub Main()
Dim FSDb = New LiteDB.LiteDatabase(DBFileStream)
Dim Clients = FSDb.GetCollection(Of ClientRec)
Dim Client.EnsureIndex(Of Int64)(Function(x) x.ID)
End Sub


"no such file" testing error

Fix this annoyance
=======================grep: /home/runner/work/mushroom-observer/mushroom-observer/log/test.log: No such file or directory
/home/runner/work/mushroom-observer/mushroom-observer/script/extract_log:48:in `initialize': No such file or directory @ rb_sysopen - /home/runner/work/mushroom-observer/mushroom-observer/log/production.log (Errno::ENOENT)

This somewhere in test/models
joe@Josephs-iMac mushroom-observer % rails t test/models
Started with run options --seed 59953

ERROR QueuedEmailTest#test_verify_account_with_user (20.90s)
Minitest::UnexpectedError:         NoMethodError: undefined method `email' for nil
            app/mailers/verify_account_mailer.rb:10:in `build'
            app/models/queued_email/verify_account.rb:14:in `deliver_email'
            app/models/queued_email.rb:214:in `finish'
            app/models/queued_email/verify_account.rb:9:in `create_email'
            test/models/queued_email_test.rb:39:in `test_verify_account_with_user'

ERROR QueuedEmailTest#test_dump (20.93s)
Minitest::UnexpectedError:         NoMethodError: undefined method `dump' for nil
            test/models/queued_email_test.rb:16:in `test_dump'

grep: /Users/joe/mushroom-observer/log/test.log: No such file or directory=================================                             ] 77% Time: 00:00:24,  ETA: 00:00:07
  986/986: [===========================================================================================================================] 100% Time: 00:00:32, Time: 00:00:32

Finished in 32.71975s
986 tests, 15135 assertions, 0 failures, 2 errors, 0 skips

It's in onde of the models starting with "s"
% rails t test/models/s*
...
grep: /Users/joe/mushroom-observer/log/test.log: No such file or directory
...
44 tests, 251 assertions, 0 failures, 0 errors, 0 skips

It's here:
% rails t test/models/script_test.rb -n /parse_log/
grep: /Users/joe/mushroom-observer/log/test.log

In particular status = system(cmd)
  test "parse_log" do
    script = script_file("parse_log")
    tempfile = Tempfile.new("test").path
    cmd = "#{script} 2>&1 > #{tempfile}"
    status = system(cmd)
    errors = File.read(tempfile)
    assert status, "Something went wrong with #{script}:\n#{errors}"
  end


The compatibility with mixamo rigs could be better. Some focus on enhancing that is recommendable.

Thanks again for posting that framework! Better compatibility for mixamo rigs is recommendable, as that seems to be the most popular auto-rigger for rigging Unity bipeds right now. Basically found that it doesn't rig properly with the "Automatic" option in UXR, although did get a usable starting point mapping with the other mapping option ("Try to" option or similar) in UXR.
In the interim, any tips for making a smoother apply of UXR to a biped rigged with mixamo? Thanks in advance!
PS: Been pondering if maybe making hand models a separate rig from a Unity avatar's body could be better, because those mesh issues when doing the wrist rotations were bleh. Recommended to basically use the rigged UXR hand models with a biped model that is rigged and modeled up to wrist? Is that how the Cyber character was done basically?

PPS: Also maybe same conclusion on heads. Ball joint meshes or no meshes for wrists and neck of 3D bipeds in Unity seems like a better plan. Nicely done on that UltimateXR mech design.

UPDATE: Got that functioning better by enabling "Use Arm IK" and "Use Body IK" again in the controller script above that. That had been switched off automatically when trying different modes of adding the joints. However...shoulder of the mixamo rigged model look flipped in UXR (although they function properly in the Unity "muscle" configuration preview). Any tips on solving that or does that need to be modified in code?

Full Mixamo support is on the way. There are some minor adjustments required on the body IK component but it should be ready soon.

Looking forward to that. Thanks in advance!
Enabling a way to easily use the UXR hands with the arm extensions like the
cyborg would be appreciated also. (rig in mixamo, delete or hide the rigged
model’s hand geometry, use the UXR hand models)
On Mon, Oct 10, 2022 at 2:32 PM Enrique Tromp @.***>
wrote:

Full Mixamo support is on the way. There are some minor adjustments
required on the body IK component but it should be ready soon.
—
Reply to this email directly, view it on GitHub
https://github.com/VRMADA/ultimatexr-unity/issues/10#issuecomment-1272892113,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACJ7JDSKWYUQSTIOHLMDT2TWCPA7RANCNFSM6AAAAAAQDCX3XU
.
You are receiving this because you authored the thread.Message ID:
@.***>

All issues should have been fixed in https://github.com/VRMADA/ultimatexr-unity/commit/af6932f5780b7df3121508804c50817201564ad9
There's also a lot of improvements on the automatic rig solving/setup. Please let me know if it solved your issues.


add alias command

implement alias command (https://github.com/rogerdahl/striprouter/issues/5)

Looks great. Thanks!


Feature Request: Option to Exclude Users to Prevent Spamming the Task List

I love that users can utilize the task list, but sometimes spammers may take advantage of it. It would be wonderful to have an option to exclude specific users to keep the task list clean and productive.

great idea!
help brainstorm command names.
Potential command name for banning users.
!taskbanuser,
!listbanuser,
!taskunbanuser
etc.

These are good.
!TaskBanUser
!TaskUnbanUser
!ListBannedUsers

Since you wrote the commands in smaller case, these should do:
!taskban
!taskunban
!listban

It turns out Twitch Chat already has a Ban and Timeout feature available to streamers to guard against spammers.
See image

closing issue.


Block property files: cleaned up trailing whitespace & fixed some typos

The trailing whitespace (3 spaces) occurred with every instance of the
hitbox object. Must have been on the first instance that was
copy-pasted into all the others.
Also threw in a correction of a misspell of wooden_pressure_plate.json as wooden_preassure_plate.json.
EDIT: I've reverted the tabification of the files and fixed 2 missing commas in tripwire.json.

I kinda prefer spaces; and that is more consistent with the files mc already has.

The tabification has now been reverted and another typo fix has been made for tripwire.json.

A formal list of all net changes in this pull request:

Fixed misspellling of wooden_pressure_plate.json as wooden_preassure_plate.json.
Removed all trailing whitespace from multiple instances of the hitbox object in the files.
There were 2 commas missing in twipwire.json, and in the same spot, 2 pairs of bunched-up brackets like this -> }{. These typos have been fixed.
In the blocks_format.json template, there were several instances of "s inside ""s. this causes syntax errors and makes it harder to spot other typos/mistakes when editing the file, so I fixed that by changing the inside "s to 's instead. For example:
"STRING: if it's capable of burning it'll also burn up, unless the value is "ever", "no" (default) means cannot burn, "yes" means can burn",
was changed to
"STRING: if it's capable of burning it'll also burn up, unless the value is 'ever', 'no' (default) means cannot burn, 'yes' means can burn",
There were also some inconsistencies in blocks_format.json where sometimes when one of the valid string arguments were listed, they would be listed as name instead of 'name'. They now all use 's.


✨ Add Language Practice through Voice Assistant

🌟 Feature Overview
This feature will provide users with practice conversations, vocabulary quizzes, pronunciation assistance, and daily language challenges.
🤔 Why this feature?
This feature will be incredibly helpful for users learning new languages.
📋 Expected Behavior
Practice Conversations, Vocabulary Quizzes, Pronunciation Assistance
🖼 Example/Mockups
Imagine opening the app and seeing options for "Start Conversation Practice," "Take Vocabulary Quiz," "Check Pronunciation,".  Users select an option, and the assistant guides them through interactive exercises.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.

I'd like to work on this issue for Hacktoberfest! Please assign it to me.


Fix template paths

During a previous refactor I introduced a bug with the path names for
templates. The command ONLY worked from the local folder where
env_compare gem code lived. Since this is where I did all my testing,
I didn't discover it until someone pointed it out.
This PR:

Refactors how the ERB is referenced so we can include paths
Renames the templates from .erb to .html.erb
Makes the themes easier to include other erb files
Changes the ENV call to an ENV.fetch to make the need to include that
ENV more clear
Closes #26

This is a beautiful cleanup! So far looks good to me, I will check and test to confirm nothing breaks on my end. Since this will be a new release the ** 0.1.3.pre.beta ** references should be removed from the README.

Tested and works as expected! Really nice!

I just realized the CHANGELOG should be updated also.

I just realized the CHANGELOG should be updated also.

Good idea. I'll add that to this commit!


feat: support Bot API 6.7

https://core.telegram.org/bots/api#april-21-2023

Will require re-approval after @grammyjs/types is updated, and import versions are also updated here.

Deps will be updated after the types release.


Request: add vim-smoothie, a smooth scroller

https://github.com/psliwka/vim-smoothie

We had this a while back, but I removed it again as it introduces issues as it remaps a bunch of basic stuff.

Please note that you can easily include it in your own setup:
https://github.com/amix/vimrc#how-to-include-your-own-stuff


v0.2.0 Mobile touchEvents

In v0.2.0 the mobile items are broken in multiple ways :

No iteractivity on items, if I have a button inside my item, it won't be clickable (worked on v0.1.6)
longPressClass is not applied to items (longTouchClass worked on v0.1.6)
Can't drag items on mobile screens, with or without longPress enabled (worked  with flaws on v0.1.6)

Here is my code :
// draggable.tsx

import { ComponentProps, ReactNode, useEffect, useTransition } from "react"
import { useDragAndDrop } from "@formkit/drag-and-drop/react"
import {
  animations,
  handleEnd as coreHandleEnd,
  DragState,
  SynthDragState,
} from "@formkit/drag-and-drop"
import { cn } from "@/lib/utils"

type Props<T> = {
  onChange?: (data: T[]) => Promise<void> | void
  items: T[]
  children: (item: T) => ReactNode
  dragHandle?: string
  checkSame?: (curr: T[], changed: T[]) => boolean
} & Omit<ComponentProps<"div">, "children" | "onChange">

const compareArrays = <_, T>(a: T[], b: T[]) =>
  a.length === b.length && a.every((element, index) => element === b[index])

export const Draggable = <_, T>({
  onChange,
  items,
  children,
  dragHandle,
  checkSame = compareArrays,
  ...props
}: Props<T>) => {
  const [pending, startTransition] = useTransition()

  const onDragEnd = async (data: DragState<T> | SynthDragState<T>) => {
    const parent = data.currentParent.el
    const newData = data.currentParent.data.getValues(parent)
    const isSame = checkSame(items, newData)

    !isSame && startTransition(async () => await onChange?.(newData))
    coreHandleEnd(data)
  }

  const [parent, listItems, setValues, updateConfig] = useDragAndDrop<
    HTMLDivElement,
    T
  >(items, {
    dragHandle,
    plugins: [animations()],
    handleEnd: onDragEnd,
    longPress: true,
    longPressClass: "shadow-xl peer:opacity-50",
    draggingClass: "opacity-50 bg-muted border border-blue-500",
    dropZoneClass: "bg-muted border-dashed relative",
    //nativeDrag: true,
  })

  useEffect(() => {
    setValues(items)
  }, [items, setValues])

  return (

      {listItems.map(children)}

  )
}

// items.tsx

export function Items({ items }: Props) {
  const handleChange = async (data: LitItem[]) => {
    await reorderList(data)
    toast.success("List updated")
  }

  return (
    <Draggable
      items={items}
      onChange={handleChange}
      dragHandle=".drag-handle"
      className="flex flex-col gap-2"
    >
      {(item) => <ListItem key={item.id} item={item} />}
    </Draggable>
  )
}

// list-item.tsx

function ListItem({ item}: { item: LitItem }) {
  return (

         {...}

        <button className="cursor-grab drag-handle" tabIndex={-1}>
          <GripVertical className="size-4 text-muted-foreground" />
          Move item
        </button>
        <button tabIndex={-1}>
          <Edit className="size-4" />
          Edit Item
        </button >

  )
}

@bfourgeaud Hey there! Apologies for these regressions. Yes, I can confirm I'm seeing longPress and longPressClass not having any effect. I'm also seeing some issues when using drag handles which I believe is the cause of this, "Can't drag items on mobile screens, with or without longPress enabled (worked with flaws on v0.1.6)". I'll be working on all of this next.

Hello thanks for your quick response.
I've tried without dragHandle :

The drag works on mobile (and has quite the improvement when working in overflowed containers).
The events inside the dragItem (buttons etc) still have no effect
The longPress & longPressClass still don't have any effect

I hope you'll find the source of the problem ;)

@bfourgeaud Okay, can you when you have the chance check out v0.2.2. Drag. handles should be working now. Buttons within a draggable item should still have click fired, and the long press and longPressClasses should be working again. I'll leave this open until I hear back.

I just tested out v0.2.2, and yes longPress, longPressClass and dragging on mobile working again !
But still having trouble with click fired inside item. I'm doing a reproduction now, updating comment when done.

Here is my repro : https://github.com/bfourgeaud/formkit-dnd-issue105-repro

On mobile the Edit button cannot be clicked
On mobile, the text cannot be expanded onClick
When switching from desktop to mobile, the DND feature isn't working, has to refresh. (Either way)
When longPress=true, on mobile you can still drag items without longPressing

@bfourgeaud Perfect, I will take a look.

@bfourgeaud Hey there! Check out v0.2.3. I believe these have been addressed, but again, I'll leave this open until I hear back from you. Really appreciate the reproduction/instructions; you made it easy for me 👍

@sashamilenkovic 🎉 It works perfectly, thank you !! And no problem for the reproduction, it's the least I could do !

@sashamilenkovic
It seems it doesn't work with "@formkit/drag-and-drop": "^0.2.6".

Hey @bfourgeaud, @sashamilenkovic !
After tested on your  repro : bfourgeaud/formkit-dnd-issue105-repro
Here quick response

The longPressDuration and longPress functions work correctly on iOS (iPhone 15, iOS 17.2, Simulator).
The longPressDuration feature seems inconsistent on the Samsung A51. While it functions as expected in some situations, there are frequent instances where it fails to register the long press action altogether.


Update to arrow-7.0.0

~Draft until arrow-7.0.0 is actually released.~
This includes code from https://github.com/apache/arrow-datafusion/pull/1283
~Once arrow 7 is released (hopefully next week) I'll update this PR to use it and mark as ready to review. Until that time feel free to rebase any branches off this one if you need new features.~
This PR is now ready for review / merge
Rationale for this change
Update to get new code in arrow
What changes are included in this PR?

Update arrow
Update prost dependency 0.8 -->  0.9 and tonic from 0.5 --> 0.6
Change DataFusion code for interface changes
Change Ballista code for interface changes

Are there any user-facing changes?
requires new arrow

wait for this pr to be merged.

This PR is now ready for review / merge

thanks, @alamb  I can go on works depending on arrow-rs 7.0.0.

thanks, @alamb I can go on works depending on arrow-rs 7.0.0.

Sorry it took so long @liukun4515  -- I hope this delay will be reduced by the proposal in https://github.com/apache/arrow-rs/issues/1120
Thank you for all your contributions and your support


Send balance transfer calls and measure time for Ready and InBlock answers

This task is the first to start a new benchmarking cli command. Should be coordinated with #197 .
The following tasks are included:

[ ] Send balance transfer call and measure time for Ready and InBlock answer. Unlike other cli calls, do not query the nonce from the worker, but use a hardcoded, steadily increasing one instead.
[ ] To check if state has been correctly updated after the InBlock, send a state query directly after.
[ ] The shielding key will not be necessary in the future any more. So for now, query it once, before starting the benchmarking, and use it afterwards for encryption, but do not re-query.
[ ] For simplicity in this task, close the connection after receiving the requested answer and re-open for a new call/query

This is for a local, single worker only.

After version update:

There exists already code in typescript to benchmark substrate:
https://github.com/paritytech/sub-flood
https://github.com/nikvolf/sub-bench
The links are from: https://wiki.polkadot.network/docs/build-tools-index#tools
It probably makes sense to setup a benchmark similar to sub-flood, but written in Rust. Also: to really compare the performance with substrate, the benchmark should also be run agains substrate nodes, being run on the same hardware.

I don't think it's part of this task to compare against substrate. If that's something that should be done, I feel like it should be a separate issue, because comparable results do not only require the same hardware but also comparable functionalities.
Also: Feel free to redefine the tasks to your liking, they have been created as a roadmap to fulfil https://github.com/integritee-network/worker/issues/248, but you can create your own of course.

I believe Submitted should work for now.

checking the state doesn't really make sense to me ... when we send a big amount of transactions, it will be hard to know the right state, as we constantly change it. It would leave this part

Concerning: "Ready" or "Submitted": Alain also agrees that "Ready" is enough.


Basic TensorFlow implementation of EM, and associated changes.

It can be selected by passing --em-executable as fast_em.sh (wrapper for
Python) instead of the binary compiled from fast_em.cc.
See comments at the top of fast_em.py.

association_test.R: test all three implementations
bin/test.sh

Add demo for TensorFlow
Add demo of early convergence
Put the output from each implementation in its own directory.

fast_em.R: Test exit code when shelling out to --em-executable
Write number of EM iterations in the assoc-metrics.json output (all
implementations).  This changes the protocol between the R driver and
EM implementation.
Clean up the log output from fast_em.cc

Aside from comments above, looks good. Merge when ready.

OK, I addressed all the comments, except I put a TODO for the v_split thing.  I agree that is probably the issue, but I'm not sure how to fix it yet and I have to do some other stuff.  Right now it is over 200x slower!


We Detected An Unusual Login Attempt

Hello! First of all, I would like to thank everyone who supports and works on this library! You are cool!
Instagram behaves very strangely, some accounts work stably, but the other part of the accounts logs out (change of session ID) approximately every 20 minutes.
I do not send spam (or ML, MF), I only receive information about followers.
Each time he says: "We Detected An Unusual Login Attempt",  but In this case, nothing changes. Maybe someone came across? How does Instagram track suspicious activity? Accounts never work at the same time, proxies for each account are different and assigned to the same account. Request limits have also never been exceeded.

Seems to be happening a lot lately...
I wonder if Instagram is getting more secure.

Hello, getting this error for 3 days already every time i try to login to instagram. I use Ipv6 proxies, tried to change user agent, but still getting this message. Is there any way i can "press" the button "This was me", or maybe i should change something so this banner doesn't even show up?

Was there any success with this? Im having similar issues, im only managing arount 70-80 calls to IG per hour before im being blacked with this error :/

No, im switching ig accounts every 5 mins so they dont get blocked
пт, 14 авг. 2020 г., 12:34 s-fraser2007<EMAIL_ADDRESS>
Was there any success with this? Im having similar issues, im only
managing arount 70-80 calls to IG per hour before im being blacked with
this error :/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/postaddictme/instagram-php-scraper/issues/551#issuecomment-673986395,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKM5XA52JX2TTQPPRBT6PZ3SAUAI7ANCNFSM4JB7P2IA
.

Can I ask how youre doing this please? 😁
currently im using 12 login accounts selected at random
`
$Files = new Psr16Adapter('Files');
$instagram = Instagram::withCredentials($instagram_login->username, Crypt::decryptString($instagram_login->password), $Files);
if (rand(0,1) % 2 == 0)
Instagram::setProxy(['address' => '<IP_ADDRESS>', 'port' => '3128']);
else
Instagram::disableProxy();
$agent = $userAgents[array_rand($userAgents)];
$instagram->setUserAgent($agent);
$instagram->login();
$instagram->saveSession();`


Deploy test reports to Bitrise.io (exit code: 1)

+------------------------------------------------------------------------------+
| (10) Deploy test reports to Bitrise.io                                       |
+------------------------------------------------------------------------------+
| id: deploy-to-bitrise-io                                                     |
| version: 1.3.6                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: go                                                                  |
| time: 2017-08-31T10:27:59Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
Configs:

BuildURL: https://www.bitrise.io/build/715d672c0bd67ab9
APIToken: oCnJV75rw7bYgz7zyDyUWw
IsCompress: false
DeployPath: /bitrise/src/app/build/reports/
NotifyUserGroups: everyone
NotifyEmailList:
IsPublicPageEnabled: true
Issue with input: DeployPath - path not exist at: /bitrise/src/app/build/reports/
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | Deploy test reports to Bitrise.io (exit code: 1)              | 4.04 sec |
+---+---------------------------------------------------------------+----------+
| Issue tracker: ...://github.com/bitrise-io/steps-deploy-to-bitrise-io/issues |
| Source: https://github.com/bitrise-io/steps-deploy-to-bitrise-io             |
+---+---------------------------------------------------------------+----------+

Hi @AsifDev21
path not exist at: /bitrise/src/app/build/reports/

Means that the path you specified does not exist there. Note: /bitrise/src is the directory where your repo is cloned.

I'll close this here as the issue is most likely not related to the step, but if this would not help @AsifDev21 feel free to contact us at https://discuss.bitrise.io/c/issues/build-issues or through the onsite chat or email on bitrise.io


How to disable pressing multiple buttons simultaneously?

Currently, multiple buttons can be pressed simultaneously, which results in multiple commands being sent at the same time. If those buttons are used as navigation buttons, the page will flicker as the screen quickly transitions to the result of the first button then to the result of the second button. Is there a way to prevent this?

After more investigation, this seems to be an effect of lag after pressing the first button.

Distilled as #687


Update manage-protection-update-schedule-microsoft-defender-antivirus.md

Updated Point 4 to reflect the latest  Group Policy

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8935

@JohanFreelancer9 Please copy review

issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/8935


After the syntax tree is parsed incrementally, the identifiers content is lost.

🔎 Search Terms
identifiers
🕗 Version & Regression Information
latest version v5.6.2
⏯ Playground Link
No response
💻 Code
// Your code here

🙁 Actual behavior
After the syntax tree is parsed incrementally, identifiers contain only incrementally changed content. The original identifier is lost. As a result, the method name is duplicate when the method is extracted.
🙂 Expected behavior
After the syntax tree is parsed incrementally, identifiers contain the complete content.
Additional information about the issue
No response

Please provide concrete repro steps in a new issue


Add link to linkedin page

Add link to linkedin page in footer section

Added link to linkedin page in footer section


dataChange incorrect in get_add_actions

Environment
Delta-rs version: 0.8.1
Binding: Python
Environment:

Cloud provider: AWS
OS: Ubuntu
Other:

Bug
What happened:
Attempting to find data change True records yields inconsistent results.
df = delta_table.get_add_actions().to_pandas()
df[df["data_change"] == True]

When I first read the table only the 9 most recent actions showed data change True. After a new commit to the table only the most recent action showed data change True and the previous 9 actions now showed False.
Confirmed from reading the commit logs that data change was True for all of those actions.
What you expected to happen:
Data change to match commit logs.
How to reproduce it:
Read the delta table add actions, make a new commit to the delta table with data change True and read the add actions again.
More details:

@quartox can you share a reproducible example? Or is this outdated by now

I haven't tested this recently. Given there are no other reports of this problem it is probably safe to close.

@quartox thanks for the update!


Threshold per axis

Do you want to request a feature or report a bug?
It is a question and maybe a feature request.
What is the current behavior?
The selection starts with a given threshold on both axis.
What is the expected behavior?
Is it possible to set a threshold per axis?
The use case: If we have some inputs as selectable targets, it would be awesome if the selection only starts when it passes a threshold on the y-axis and ignores the x-axis. If we drag on the x-axis we probably want to mark a text. And if we drag on the y-axis, we probably want to select the input boxes.
Your environment:
Selection-version: 1.2.1
Browser-version: Chrome 77.0.3865.90
Operating-system:  Debian

@colq2 Available in 1.3.0 :)

Very nice, thank you!
I will give it a try tomorrow :)


Jupyter has a different intellisense result compare to python files

Applies To

[X] Notebooks (.ipynb files)
[ ] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

As seen from the screenshot, I have pylance+python+jupyter extension installed. However, there seems to have many differences within the intellisense autocomplete result. Apparently in jupyter notebook part lack of many methods used in creation of python class. And it seems the autocompletion are designed for some jupyter works only but not python works. Is it possible to have a future feature that jupyter notebook can be using the same autocompletion as python files?
VS Code Version
1.68.1
Jupyter Extension Version
2022.5.100
Jupyter logs
No response
Coding Language and Runtime Version
Python 3.10.4
Language Extension Version (if applicable)
2022.8.0
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Local

Not sure why this was closed, but I can answer why there is a discrepancy.
Jupyter notebooks have completions from pylance and from the IPython kernel as well. IPython can provide more information but can also sometimes provide too much information.
There's a setting that can make IPython provide better information but it can slow down completions to the point where the kernel is stuck for periods of time.


Generate ruby client using Heroics

This pull request uses Heroics to generate a ruby client.
I've added a custom script for generating the client:
bin/generate-client

This invokes heroics and prepends our gem libraries komoju/version and komoju/client.
komoju/client overrides the existing Komoju.connect method to support our
passwordless basic auth.

Great!!! LGTM :+1:


Improve README

Change hardcoded accepted string to RegistrationStatusType.accepted.
Tweak central system example code to close the websocket.

@OrangeTux @tropxy Hello! I need someone to approve the test run and review this PR. Thanks. 🙏


Muxes can get caught in infinite loop.

In updating another project from pescador==0.1.3 to 1.0, I was running into an issue where a data stream was hanging indefinitely.
Fortunately, having identified #86 (attempts to re-iterate a mux returned no samples), I was able to figure out why a mux-of-muxes would get caught in an infinite loop.
tl:dr; If a Mux finds itself in a situation where all of its streams are fundamentally exhausted (cannot produce an iterator that yields samples), attempts to iterate will run forever.
This is documented in a test case here.
I think a check here that distribution.any() > 0 would do the trick... @bmcfee any thoughts?

@bmcfee any thoughts?

That does indeed seem like it should fix the issue.  I would have thought that it would trigger a stop iteration once the distribution hits 0 within next_stream, but maybe the logic got messed up somewhere along the refactor.

Working through this now, so partially documenting my thought process, but our fix isn't going to work ... that is, if the "fix" was to put that distribution check in the while condition of the main loop (there's been some code drift since the comment, but that makes the most sense).
tl;dr: distributions are deactivated in two places, (1) when catching the StopIteration exception in iterate, and (2) when activating a new stream. Therefore, when the last stream is activated, distribution will be empty but there is still data in the stream.
:thinking-face:

I was thinking maybe this could be handled in my/our mux refactor (I'll
push a PR with what I started shortly) / #84, because the way muxes are
structured might get organized a bit to fix this. But maybe that's too much
work for this release?
On Tue, Jun 13, 2017 at 10:42 PM Eric J. Humphrey<EMAIL_ADDRESS>wrote:

Working through this now, so partially documenting my thought process, but
our fix isn't going to work ... that is, if the "fix" was to put that
distribution check in the while condition of the main loop (there's been
some code drift since the comment, but that makes the most sense).
tl;dr: distributions are deactivated in two places, (1) when catching
the StopIteration exception in iterate, and (2) when activating a new
stream. Therefore, when the last stream is activated, distribution will
be empty but there is still data in the stream.
:thinking-face:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pescadores/pescador/issues/87#issuecomment-308257273,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4t8xGb6UD1vaZ84OJoWftwjyh7prtxks5sDwI8gaJpZM4NAdXp
.

I've three updated findings / thoughts. I'm reasonably confident in the assessment, so, worth sharing.

I don't think we can fully decouple this issue from #84 (reason to follow).
The logical issue here (and with #84) might effect #81, so I'd call that issue dependent on this one.
Diagnosis: Clarifying my previous comments, Mux.distribution_ is being set to zero under two conditions: (1) a stream produces no samples, and (2) when a stream is activated without replacement. This causes undefined (or at least undesired) behavior for the case with_replacement=False, revive=True, prune_empty_seeds=True. Here, the data structure distribution_ is being overloaded... in reality, we only want to revive 0'ed out streams that produced data, but there's no way to track this.

I propose the following:

Fix this issue first. If this diagnosis is correct, then there's an easy fix (track dead streams explicitly), which will address the test case.
Second, refactor the Mux semantics, e.g. PoissonMux and whatnot (half of #84)
Confirm the statistics of PoissonMux, i.e. #81.
Add additional Mux classes (the other half of #84)

thoughts?

:+1:
On Tue, Jun 13, 2017 at 11:09 PM Eric J. Humphrey<EMAIL_ADDRESS>wrote:

I've three updated findings / thoughts. I'm reasonably confident in the
assessment, so, worth sharing.

I don't think we can fully decouple this issue from #84
https://github.com/pescadores/pescador/issues/84 (reason to follow).
The logical issue here (and with #84
https://github.com/pescadores/pescador/issues/84) might effect #81
https://github.com/pescadores/pescador/issues/81, so I'd call that
issue dependent on this one.
Diagnosis: Clarifying my previous comments, Mux.distribution_ is
being set to zero under two conditions: (1) a stream produces no samples,
and (2) when a stream is activated without replacement. This causes
undefined (or at least undesired) behavior for the case with_replacement=False,
revive=True, prune_empty_seeds=True. Here, the data structure
distribution_ is being overloaded... in reality, we only want to
revive 0'ed out streams that produced data, but there's no way to track
this.

I propose the following:

Fix this issue first. If this diagnosis is correct, then there's an
easy fix (track dead streams explicitly), which will address the test case.
Second, refactor the Mux semantics, e.g. PoissonMux and whatnot
(half of #84 https://github.com/pescadores/pescador/issues/84)
Confirm the statistics of PoissonMux, i.e. #81
https://github.com/pescadores/pescador/issues/81.
Add additional Mux classes (the other half of #84
https://github.com/pescadores/pescador/issues/84)

thoughts?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pescadores/pescador/issues/87#issuecomment-308263509,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA4t8w9CKPLKNM7yf_akU3t45npIJilhks5sDwi1gaJpZM4NAdXp
.

also, wanted to revisit letting prune_empty_streams potentially be False ... IIRC, I think @bmcfee's rationale once upon a time was something like "past emptiness is not indicative of future emptiness".
While I find that a tad dangerous, I do support letting people shoot themselves in the foot, with adequate warnings. So, where should we put a warning about not pruning truly empty streams?


adding function to extract terraform vars from var file

This PR adds the following functionality to the terraform Options module:

Exposes a function that allows you to get a map of all the variables contained in each terraform VarFile specified in a terraform options object. This would allow you to reference these easily later on in a test for comparison, etc.

This is my first time contributing to this repo, so I tried to follow the style guides and everything to the best of my ability. Any feedback would be greatly appreciated!

Thanks for the feedback @brikis98 !
As for the use case, I have found frequently that I've wanted to access a setting I've set in a tfvars file later in a test for use in comparison for assertion/validation. For example, I was changing a module that exposes an option to set a CNAME record. I was planning to use the value we set the CNAME record to for some validation. Since I couldn't access the value from the tfvars file, I had to end up taking it out and hard-code the value in the test and pass in both the var file and that individual var into the terraform options.
So, while this functionally isn't needed since you can get around cases where you do need to access certain variables, you would always need to hard-code them into your test and add additional code to import both a var and a var file in your terraform options. (unless I'm totally missing another way to do this).
Overall my argument is this functionality would allow you to not have to write additional code for use cases like this and keeps configuration more separated from the code. Hopefully what I'm saying makes sense 🤣
If you are OK with adding this, I'll go ahead and address the additional feedback you provided.

Thanks for the feedback @brikis98 !
As for the use case, I have found frequently that I've wanted to access a setting I've set in a tfvars file later in a test for use in comparison for assertion/validation. For example, I was changing a module that exposes an option to set a CNAME record. I was planning to use the value we set the CNAME record to for some validation. Since I couldn't access the value from the tfvars file, I had to end up taking it out and hard-code the value in the test and pass in both the var file and that individual var into the terraform options.
So, while this functionally isn't needed since you can get around cases where you do need to access certain variables, you would always need to hard-code them into your test and add additional code to import both a var and a var file in your terraform options. (unless I'm totally missing another way to do this).
Overall my argument is this functionality would allow you to not have to write additional code for use cases like this and keeps configuration more separated from the code. Hopefully what I'm saying makes sense 🤣
If you are OK with adding this, I'll go ahead and address the additional feedback you provided.

Makes sense to me!

 Don't review yet - still need to update/add tests.

@brikis98 happy (late) new year! I finally got a chance to come back to refactoring this PR a bit. I decided to structure it more like the output module and provide different functions for getting input file values as their different types (string, map, list), along with adding some new error types.

@brikis98 happy (late) new year! I finally got a chance to come back to refactoring this PR a bit. I decided to structure it more like the output module and provide different functions for getting input file values as their different types (string, map, list), along with adding some new error types.

Thank you for the feedback! I'll get to making the updates later this week.

Thank you for the feedback! I'll get to making the updates later this week.

@brikis98 I addressed all your feedback! I do have one thought, though, that I wanted to run by you. With these changes, it seems like maybe this code doesn't quite fit into the options file since it no longer interfaces with the options object. Maybe should be separated into its own module, like input? What are your thoughts?

@brikis98 I addressed all your feedback! I do have one thought, though, that I wanted to run by you. With these changes, it seems like maybe this code doesn't quite fit into the options file since it no longer interfaces with the options object. Maybe should be separated into its own module, like input? What are your thoughts?

@brikis98 I addressed all your feedback! I do have one thought, though, that I wanted to run by you. With these changes, it seems like maybe this code doesn't quite fit into the options file since it no longer interfaces with the options object. Maybe should be separated into its own module, like input? What are your thoughts?

Sorry for the delay. Agreed it doesn't quite fit into options.go. Perhaps var-files.go or similar instead?

Updated to move the code to a different file!

Great, thanks! Would you mind rebasing on master? I can then kick off tests.

Done! @brikis98

Updated!

Hm, looks like a test not related to my code changes failed TestTerraformAwsRdsExample - test . It does look like my tests passed though:
=== RUN   TestGetVariablesFromVarFilesAsString
--- PASS: TestGetVariablesFromVarFilesAsString (0.00s)
=== RUN   TestGetVariablesFromVarFilesAsStringKeyDoesNotExist
--- PASS: TestGetVariablesFromVarFilesAsStringKeyDoesNotExist (0.00s)
=== RUN   TestGetVariableAsMapFromVarFile
--- PASS: TestGetVariableAsMapFromVarFile (0.00s)
=== RUN   TestGetVariableAsMapFromVarFileNotMap
--- PASS: TestGetVariableAsMapFromVarFileNotMap (0.00s)
=== RUN   TestGetVariableAsMapFromVarFileKeyDoesNotExist
--- PASS: TestGetVariableAsMapFromVarFileKeyDoesNotExist (0.00s)
=== RUN   TestGetVariableAsListFromVarFile
--- PASS: TestGetVariableAsListFromVarFile (0.00s)
=== RUN   TestGetVariableAsListNotList
--- PASS: TestGetVariableAsListNotList (0.00s)
=== RUN   TestGetVariableAsListKeyDoesNotExist
--- PASS: TestGetVariableAsListKeyDoesNotExist (0.00s)
=== RUN   TestGetAllVariablesFromVarFileEFileDoesNotExist
--- PASS: TestGetAllVariablesFromVarFileEFileDoesNotExist (0.00s)
=== RUN   TestGetAllVariablesFromVarFileBadFile
--- PASS: TestGetAllVariablesFromVarFileBadFile (0.00s)
=== RUN   TestGetAllVariablesFromVarFile
--- PASS: TestGetAllVariablesFromVarFile (0.00s)

Ah, looks like it might be using an instance that isn't valid? 2021-02-15T15:38:55Z logger.go:66: Error: Error creating DB Instance: InvalidParameterValue: Invalid DB Instance class: db.t2.micro . I thought that was a valid one? https://aws.amazon.com/rds/instance-types/

https://github.com/gruntwork-io/terratest/releases/tag/v0.32.6

https://github.com/gruntwork-io/terratest/issues/784


Cargo build failed

Question
Before asking a question, make sure you have:

Reviewed relevant Rust information: Google your error messages and look at official docs.
Searched open and closed GitHub issues

I tried to use MAC and Linux to run cargo build but both failed. Do I need to download any prerequisites?

Because Tonbo has MSRV(minimum supported Rust version) required, it was already be specified in main barch, see https://github.com/tonbo-io/tonbo/blob/main/Cargo.toml#L14 , but it is not published to crates.io, it will be published as soon as possible.

因为 Tonbo 有 MSRV（最低支持的 Rust 版本）要求，它已经在主 barch 中指定，请参阅https://github.com/tonbo-io/tonbo/blob/main/Cargo.toml#L14，但它尚未发布到 crates.io，这个问题将尽快修复，谢谢 🙏

Thanks

Because Tonbo has MSRV(minimum supported Rust version) required, it was already be specified in main barch, see https://github.com/tonbo-io/tonbo/blob/main/Cargo.toml#L14 , but it is not published to crates.io, this will be fixed soon as possible, thanks 🙏

Thanks

You could manually upgrade rustc above 1.79+ to fixe it temporarily

@ethe

You could manually upgrade rustc above 1.79+ to fixe it temporarily

If successful, I will write a document with a brief description to tell subsequent contributors how to build this project until the bug is fixed.

You could manually upgrade rustc above 1.79+ to fixe it temporarily

Success. Thank you for your reply

@ethe Thank you. I noticed this issue has been fixed


Add trackwidth conversions

Still need trackwidth characterization to verify this works.

Running characterization with the drivetrain simulation example (https://www.chiefdelphi.com/t/infinite-recharge-at-home-autonav-challenges-using-wpilibs-drive-simulator/390485) I had previously had a very large trackwidth (~64 meters) when it should be 0.69 meters. With this change, I now get 15.34 meters.

Running characterization with the drivetrain simulation example (https://www.chiefdelphi.com/t/infinite-recharge-at-home-autonav-challenges-using-wpilibs-drive-simulator/390485) I had previously had a very large trackwidth (~64 meters) when it should be 0.69 meters. With this change, I now get 15.34 meters.

Did you log with meters as well?

Did you log with meters as well?

I implemented the logger code into my project where the encoders returned meters. When I ran the logger, it said verify the robot traveled x rotations which was correct if substituting meters (it traveled x meters).

I implemented the logger code into my project where the encoders returned meters. When I ran the logger, it said verify the robot traveled x rotations which was correct if substituting meters (it traveled x meters).

Did you set the units to meters in the new project section?

Did you set the units to meters in the new project section?

I did chose meters and put my units per rotation in the new project section. However, I just noticed that the generated project did not seem to use that. It generated private double encoderConstant = (1 / GEARING) * (1 / ENCODER_EDGES_PER_REV); and encoder.setDistancePerPulse(encoderConstant); which looks like it was using rotations regardless of the fact that I entered meters and and my meters per rotation. This would be different then my own project that I ran characterization on which returned encoder distances in meters

I did chose meters and put my units per rotation in the new project section. However, I just noticed that the generated project did not seem to use that. It generated private double encoderConstant = (1 / GEARING) * (1 / ENCODER_EDGES_PER_REV); and encoder.setDistancePerPulse(encoderConstant); which looks like it was using rotations regardless of the fact that I entered meters and and my meters per rotation. This would be different then my own project that I ran characterization on which returned encoder distances in meters

That might be another issue with the tool's units then...

That might be another issue with the tool's units then...

After realizing that the robot program is always generated as rotations, and conversions to units are done in frc-characterization, I updated my robot program to report distance in rotations. My robot program was also limiting the gyro angle to -180/+180. Once I reported the accumulated gyro angle, with this PR, it reported the correct trackwidth for me.

After realizing that the robot program is always generated as rotations, and conversions to units are done in frc-characterization, I updated my robot program to report distance in rotations. My robot program was also limiting the gyro angle to -180/+180. Once I reported the accumulated gyro angle, with this PR, it reported the correct trackwidth for me.

Did you have to do the conversions in the analyzer or through the logger?

Did you have to do the conversions in the analyzer or through the logger?

Previously, when I ran the logger and analyzer separately from the cli is when I had the issue with the logger reporting rotations. If instead I ran frc-characterization drive new and set the conversions in the main window and launched the logger and analyzer from there, the unit conversions worked.

Previously, when I ran the logger and analyzer separately from the cli is when I had the issue with the logger reporting rotations. If instead I ran frc-characterization drive new and set the conversions in the main window and launched the logger and analyzer from there, the unit conversions worked.

So we should be able to resolve the issue through better documentation?
Also, were you able to see if switching the units to feet, inches, etc. were accurate?

So we should be able to resolve the issue through better documentation?
Also, were you able to see if switching the units to feet, inches, etc. were accurate?

The combination of this PR and better documentation would fix it.
Yes, when switching between meters, feet, and inches, the trackwidth scaled appropriately.

The combination of this PR and better documentation would fix it.
Yes, when switching between meters, feet, and inches, the trackwidth scaled appropriately.

The combination of this PR and better documentation would fix it.
Would this PR make it clear?

The combination of this PR and better documentation would fix it.
Would this PR make it clear?

Should close #166

Should close #166


Investigate kyverno.io for Crossplane for sanitizing user claim inputs

What: Investigate access control on a granular level
Why: k8s's bult-in RBAC have a "static" way of defining access control on resources. we need more flexible way to control what allowed values are allowed to provide in the yaml manifests

[x] Setup in sandbox
[x] Test what can it do in terms of field validation?
[ ] Find out what RBAC capabilities does it have compared to RBAC and OPA Gatekeeper

Can do filtering based on users! https://kyverno.io/docs/writing-policies/match-exclude/#match-a-label-and-exclude-users-and-roles


Reorganize build scripts, part 2: separate modules

context: #5722, #5730
Please review commit by commit.

Jenkins, test this please

CI error for pfnci-rocm
File "/tmp/flexci/run-00161320/tmp/pip-wrvbfxsp-build/install/cupy_builder/cupy_setup_build.py", line 587, in cythonize |
-- | --
00:09:09.114941 STDOUT 2287] | compiler_directives=directives, **cythonize_options) |
00:09:09.114947 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Build/Dependencies.py", line 1102, in cythonize |
00:09:09.115055 STDOUT 2287] | cythonize_one(*args) |
00:09:09.115058 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Build/Dependencies.py", line 1208, in cythonize_one |
00:09:09.115063 STDOUT 2287] | result = compile_single(pyx_file, options, full_module_name=full_module_name) |
00:09:09.115163 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Compiler/Main.py", line 727, in compile_single |
00:09:09.115166 STDOUT 2287] | return run_pipeline(source, options, full_module_name) |
00:09:09.115172 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Compiler/Main.py", line 515, in run_pipeline |
00:09:09.115251 STDOUT 2287] | err, enddata = Pipeline.run_pipeline(pipeline, source) |
00:09:09.115259 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Compiler/Pipeline.py", line 355, in run_pipeline |
00:09:09.115264 STDOUT 2287] | data = run(phase, data) |
00:09:09.115319 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Compiler/Pipeline.py", line 335, in run |
00:09:09.115322 STDOUT 2287] | return phase(data) |
00:09:09.115328 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Compiler/Pipeline.py", line 52, in generate_pyx_code_stage |
00:09:09.115400 STDOUT 2287] | module_node.process_implementation(options, result) |
00:09:09.115403 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Compiler/ModuleNode.py", line 143, in process_implementation |
00:09:09.115408 STDOUT 2287] | self.generate_c_code(env, options, result) |
00:09:09.115455 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Compiler/ModuleNode.py", line 359, in generate_c_code |
00:09:09.115457 STDOUT 2287] | self.generate_module_preamble(env, options, modules, result.embedded_metadata, h_code) |
00:09:09.115461 STDOUT 2287] | File "/usr/local/lib/python3.7/dist-packages/Cython/Compiler/ModuleNode.py", line 634, in generate_module_preamble |
00:09:09.115496 STDOUT 2287] | code.putln(json.dumps(metadata, indent=4, sort_keys=True)) |
00:09:09.115498 STDOUT 2287] | File "/usr/lib/python3.7/json/__init__.py", line 238, in dumps |
00:09:09.115501 STDOUT 2287] | **kw).encode(obj) |
00:09:09.115527 STDOUT 2287] | File "/usr/lib/python3.7/json/encoder.py", line 201, in encode |
00:09:09.115529 STDOUT 2287] | chunks = list(chunks) |
00:09:09.115537 STDOUT 2287] | File "/usr/lib/python3.7/json/encoder.py", line 431, in _iterencode |
00:09:09.115667 STDOUT 2287] | yield from _iterencode_dict(o, _current_indent_level) |
00:09:09.449872 STDOUT 2287] | File "/usr/lib/python3.7/json/encoder.py", line 405, in _iterencode_dict |
00:09:09.449969 STDOUT 2287] | yield from chunks |
00:09:09.449971 STDOUT 2287] | File "/usr/lib/python3.7/json/encoder.py", line 405, in _iterencode_dict |
00:09:09.449975 STDOUT 2287] | yield from chunks |
00:09:09.450009 STDOUT 2287] | File "/usr/lib/python3.7/json/encoder.py", line 325, in _iterencode_list |
00:09:09.450010 STDOUT 2287] | yield from chunks |
00:09:09.450013 STDOUT 2287] | File "/usr/lib/python3.7/json/encoder.py", line 325, in _iterencode_list |
00:09:09.450037 STDOUT 2287] | yield from chunks |
00:09:09.450038 STDOUT 2287] | File "/usr/lib/python3.7/json/encoder.py", line 438, in _iterencode |
00:09:09.450041 STDOUT 2287] | o = _default(o) |
00:09:09.450084 STDOUT 2287] | File "/usr/lib/python3.7/json/encoder.py", line 179, in default |
00:09:09.450089 STDOUT 2287] | raise TypeError(f'Object of type {o.__class__.__name__} ' |
00:09:09.450097 STDOUT 2287] | TypeError: Object of type function is not JSON serializable |
00:09:09.450171 STDOUT 2287] | Running setup.py install for cupy: finished with status 'error'

Jenkins CI test (for commit b25b9f7b21fdd6cf60aaf68e80ac519b72a44676, target branch master) succeeded!

/test

FlexCI passed!
pfnCI, run Jenkins please.

Jenkins CI test (for commit c42df8f5550259e1b4b45072f17367d7d310752a, target branch master) succeeded!


Onenote plugin dlls not added to signing

Microsoft PowerToys version
main
Running as admin

[ ] Yes

Area(s) with issue?
General
Steps to reproduce
. 'C:\a_work\1\s.pipelines\versionAndSignCheck.ps1' -targetDir 'C:\a_work\1\s\extractedMsi\File'
C:\a_work\1\s\extractedMsi\File
Total items:  307
Not Signed:  + C:\a_work\1\s\extractedMsi\File\File_Interop.Microsoft.Office.Interop.OneNote.dll
Not Signed:  + C:\a_work\1\s\extractedMsi\File\File_ScipBe.Common.Office.OneNote.dll
Not Signed:  + C:\a_work\1\s\extractedMsi\File\OneNoteCompFile_Microsoft.PowerToys.Run.Plugin.OneNote.dll
##[error]Process completed with exit code 1.
Finishing: Verifying entire build is signed and version set
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

@jaimecbernardo fyi


Local build not rendering without newer version of eslint

Reproduction steps
Fork the repository
Create a local clone
Follow the instructions in the repo readme to run the development environment
Results in:

In order to remedy this, I found this thread/answer . After running npm install eslint@latest --save-dev the site was able to build and render as expected
Updated package-lock.json file: package-lock.json
Updated package.json file:
package.json
It appears that there were other updates in addition to the eslint version, but I'm not well versed enough to know whether they are all tied to eslint or if they are others that were pulled in.
Expected Results
development environment builds and renders properly

Actual Results
Error is thrown (as shown above in steps to reproduce) and the environment only renders the header & footer
Anything else?
I think I ran into this issue when creating Olivier's spotlight but was able to build and render the page in deploy.

@krisstern am I potentially doing something wrong in my setup?

@kmartens27 Sorry I missed this earlier... I think I might have fixed it.

I believe I might have during my research into what could be causing the issue, however I don't recall at this moment so let me try that out and see what happens.

Sounds good! Do keep me posted

Hi @kmartens27 that's good to know!

I believe this issue can be closed as the site is now building as expected


Implement style_edition config

This PR adds the style_edition configuration value and the StyleEditionDefault trait and implements the trait for all current configuration options.
This new trait allows each configuration option to specify its default value for different style editions. Before style edition there was no mechanism that allowed changing a configs default value.
A new #[style_edition] procedural macro is added to make implementing style edition much easier. Admittedly I haven't worked with syn and quote all that much so any advice on simplifying the procedural macro code is welcome!

Also want to highlight that I think I'll need to add additional tests to ensure that style edition is set correctly in different scenarios before this gets merged. Mostly leaving this as a note for myself so I don't forget to add those additional tests

Whew, this one looks like it'll be fun to review. I assume the changes proposed here are atomic, and that there's no way to decompose it in any form into two (or more) smaller PRs?

I think we could probably add the proc macro code as a separate PR, and then add everything else as a separate PR. let me know what you think and I'll make the necessary changes

If it helps, I think we could break this up a little. All the proc macro code could be one PR, and then there might be some other changes that could be broken up into smaller PRs, but once we start messing with the configuration a lot of it needs to come together.
Let me know what you think would be best. I'm happy to make any changes.

I think the typical adage about a higher quantity of smaller PRs being preferable to a lower quantity of larger PRs holds here as well. I trust and defer to your judgement around determining the best way to slice and dice the changes

Also, I really want to underscore my appreciation for your efforts on this front. It's obviously no small task, but the work is of paramount importance and I'm grateful you've already made this much progress.
I cannot over stress how significant and beneficial the style edition mechanism is going to be in addressing some incredibly long standing and thorny issues (I will also give yet another shout out to @joshtriplett for coming up with the style edition solution :pray:)

work for this is being done in other PRs


Provider freemanga.to

Proposed provider:

Web: https://freemanga.to/
Example url: https://freemanga.to/manga/read-overlord-manga

Thank you. Will be added in the next update.


"Interval with nullFlavor low time and nullFlavor high time" error sh…

…ould not be returned when entire element is nullFlavored (#109)
Pull requests into cqm-parsers require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR: https://oncprojectracking.healthit.gov/support/browse/CYPRESS-2106
[x] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[x] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Codecov Report

Merging #110 into master will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #110      +/-   ##
==========================================
+ Coverage   87.09%   87.11%   +0.02%
==========================================
  Files          67       67
  Lines        1968     1972       +4
==========================================
+ Hits         1714     1718       +4
  Misses        254      254

Impacted Files
Coverage Δ

lib/qrda-import/base-importers/section_importer.rb
86.38% <100.00%> (+0.26%)
:arrow_up:

Continue to review full report at Codecov.

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


Prepare bikeshed for Process 2020

By September 15, W3C specifications will be developed under a new Process (which introduces new sub-stages to the CR process and new states for the post-REC life); progressively, groups will transition to a new patent policy. See https://lists.w3.org/Archives/Public/spec-prod/2020JulSep/0024.html
See also w3c/modern-tooling#86
This pull request:

updates the existing W3C groups boilerplates to refer to the new process document
adds support for the new Candidate Recommendation Draft status
add supports for marking a CR as Draft or Snapshot
requires a link to issues from the document head for W3C TRs
adds support for implementation report in metadata and requires it for W3C TRs post Candidate Recommendation

Notwithstanding any specific issue in the code, this pull request should not be merged before September 15 (when the new process gets into operation).

@tabatkins how do you want to approach the potential merging of this pull request on September 15 (next Tuesday)?

Happy to just merge it whenever you're ready

Bikeshed is useful for more than just the W3C. PR evaluation and merger shouldn't be held up waiting on them to adopt a process change. If it's ready to be used and non-breaking for existing use cases then don't wait for some arbitrary date.

This is specifically a W3C process change, updating a bunch of W3C group boilerplates to accommodate a W3C changes. Chill your jets.

@tabatkins now ready to merge from my perspective thanks :)


STORM-1701 simple JSON mapping

There is an interesting issue here.  If the tuple contains malformed JSON such that rowKey(tuple) throws a ParseException then the HBase bolt will never process that message, so a retry seems fruitless.  When a similar situation happens in HiveBolt it acknowledges the tuple, logs the error, and discards the message (https://github.com/apache/storm/blob/master/external/storm-hive/src/main/java/org/apache/storm/hive/bolt/HiveBolt.java#L129-L132).
Something similar might be nice here with a new InvalidTuple exception into which each implementation of HBaseMapper can wrap its specific "this tuple will never work" exceptions.  That would also have the nice benefit of keeping an implementation specific detail (throws ParseException) out of the declaration of the very generic HBaseMapper and make it easier for users to implement their own mappers and have these errors handled correctly.
This approach could be extended to any bolt that uses the mapper strategy (e.g. ElasticSearch) or could have its own "will never work" errors, e.g. the Avro bolt receiving non-avro messages.

You're right.  There is no sense in replaying the same broken input.  I'm conflicted on what the right approach is to notify the topology owner of corrupt JSON or a missing row key.  I don't think it is worthy of a collector.reportError() and am wondering if it should be INFO or WARN logging.
I've got the the changes you have suggested complete minus the desired notification. How does this go with the GitHub integration?  Squash on my fork and this PR is automatically updated?

@kristopherkane Yes, squash and push with force option.


fix: Ignore parameter, result and attribute types from outside packages

Summary of Changes
Parameter, result and attribute types which are not python core types have to be defined in the package we analyze. If they are not from within the package we remove them for the stubs generation.

I realized that changes in this PR clash with what we need from Issue #38. Therefore I will revert this PR to a draft and use it as a PR for issue #38.

Yes, probably tomorrow. Could you add a summary of changes?

We also need a syrupy extension and a pytest fixture for stubs (see this example). This way all created stubs get their own file with the correct extension, instead of mushing them all together in on ambr file.

@lars-reimann I fixed how the import paths are generated for stubs, now it should be correct. There was just one case where I wasn't sure how to handle it: If we have an import from another package, how should it look like?
This
@PythonModule("various_modules_package.function_module")
package variousModulesPackage.functionModule

from tests.data.main_package.another_path.another_module import AnotherClass

or this
@PythonModule("various_modules_package.function_module")
package variousModulesPackage.functionModule

from mainPackage.AnotherPath.AnotherModule import AnotherClass

?
Currently the first case is implemented. If it's correct like this, you can review and hopefully close this PR.

The second option is correct, assuming the file containing AnotherClass looks something like this:
@PythonModule("does not matter for imports in Safe-DS")
package mainPackage.AnotherPath.AnotherModule

class AnotherClass

The part between from and import must always equal to the name of the Safe-DS package you want to import from.

@lars-reimann But we are assuming that we did not create the "mainPackage" Stubs yet and don't know where the mainPackage files are. What I concretely mean is, how do imports look like, if we import classes from other packages? Packages we perhaps did not create stubs for? The problem here is that we don't know how the package is named, like in the tests.data.main_package.another_path.another_module.AnotherClass example. Mypy gives us this path to the class, but we actually don't now that "main_package" is the package. Or should I just assume that because our current package, which we are creating stubs for, has the path tests.data.out_current_package.... that we can slice of the tests.data part for tests.data.main_package...., too?

Say we are creating stubs for the package a and are currently working on a Python module with the following content:
from b import SomeClass

def f(p: SomeClass)

Then we also need to create some stub for the class SomeClass, or we can't use it. So limited stubs must be created for the declarations of other packages that package a depends on.

@lars-reimann If I remove those imports for this PR, what about the types that use the imported classes? Should I removed them, too, for the time being?

No, keep the types.

@lars-reimann I removed the imports and created issue #66. You can proceed with the PR review.

:tada: This PR is included in version 0.2.0 :tada:
The release is available on:

v0.2.0
GitHub release

Your semantic-release bot :package::rocket:


Add Support for targeting .NetCore 3.1

Support for targeting .NET Core 3.1

@thudugala This is now done with #21. Thanks anyway for your contribution. 👍

Hope it will be published soon


Add namespaces to a world

Summary
The current behaviour of World allows to add methods of one or more modules in a single namespace. I think it would be interesting to add different namespaces to a World, to better control which method to call and avoid name clashes.
Proposed Solution
I would propose one of the following alternatives:
Given:
module MyModule
  def a_method
  end
end

1. Automatic namespace
When using World(MyModule) the methods of MyModule are accessible by using the prefix my_module. E.g. my_module.my_method. The prefix is the underscore version of the name of the module.
2. Explicit namespace
World(MyModule => :my_module), similar to the point above, but with a specified alias.
I have already a working prototype of this feature. The impact is not high and the new behaviour could be retro-compatible.
The idea of my implementation is to dynamically add a method to the world which returns an instance of Object, which extend the module. If you think it's relevant I can share more details.
I open this issue to gather feedback and if you agree I would be happy to create a PR.
Cheers,
Andrea

Hi @nodo,
Seems like a useful idea, yes. I think it might be more idiomatic Ruby, in the explicit namespace version, to put the name first, so you can use the symbol-to-object hash syntax like this:
World(a_module: MyModule)
WDYT?
How about starting with a feature file in a PR, and we can discuss it more there?

Thanks @mattwynne, I agree with you.
I have created a feature file in an explorative PR (https://github.com/cucumber/cucumber-ruby/pull/1007). I have added a scenario to test retro-compatibility as well.
I like the idea of having two ways of adding methods two a world

using the old version: add helpers to a global namespace
using the new hash syntax: add helpers using the namespace

Looking forward to go ahead with this.

Closed in favour of #1007


changes to run e2e network for exercise

These are the changes required o accomplish some steps of the given exercise. The guide can be found at https://github.com/AnyLedger/business-logic-smart-contracts/pull/1/commits/31eff920cc05f01423f8acdecd7892f8db2f2757

./bootstrap.sh
returns some errors. Is this fine?
` lorenzo@MacBook-Air-di-Lorenzo ~/gitHubRepo/fabric-samples/scripts $ ./bootstrap.sh
Installing Hyperledger Fabric binaries
===> Downloading version 1.2.0 platform specific fabric binaries
===> Downloading:  https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/darwin-amd64-1.2.0/hyperledger-fabric-darwin-amd64-1.2.0.tar.gz
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 29.7M  100 29.7M    0     0  2968k      0  0:00:10  0:00:10 --:--:-- 3719k
==> Done.
===> Downloading version 1.2.0 platform specific fabric-ca-client binary
===> Downloading:  https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric-ca/hyperledger-fabric-ca/darwin-amd64-1.2.0/hyperledger-fabric-ca-darwin-amd64-1.2.0.tar.gz
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 3864k  100 3864k    0     0  1727k      0  0:00:02  0:00:02 --:--:-- 1730k
==> Done.
Installing Hyperledger Fabric docker images
===> Pulling fabric Images
==> FABRIC IMAGE: peer
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
==> FABRIC IMAGE: orderer
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
==> FABRIC IMAGE: ccenv
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
==> FABRIC IMAGE: tools
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
===> Pulling fabric ca Image
==> FABRIC CA IMAGE
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
===> Pulling thirdparty docker images
==> THIRDPARTY DOCKER IMAGE: couchdb
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
==> THIRDPARTY DOCKER IMAGE: kafka
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
==> THIRDPARTY DOCKER IMAGE: zookeeper
Warning: failed to get default registry endpoint from daemon (Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?). Using system default: https://index.docker.io/v1/
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
===> List out hyperledger docker images
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?`


Add ref to asset library version for color grabber

Add origURL to the returned object. This is a reference to the asset library handle of the original image. It can be passed to react-native-color-grabber

Looks good to me @yfuks. I think we definitely need this functionality.
I'll let you merge and publish if you're ok with it!

I just thought of something – I was only using this component to pick images from the library. So I haven't tested this fix with getting images from the camera directly... Don't know if it makes any difference, I suppose the camera image is added to the asset library before this component processes it.
Sent from my iPad

On Apr 18, 2016, at 10:46, Marc Shilling<EMAIL_ADDRESS>wrote:
Looks good to me @yfuks. I think we definitely need this functionality.
I'll let you merge and publish if you're ok with it!
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


deps: update substrate to polkadot-v0.9.43

update substrate to 3c8666b1906680ad9461a6c46fe17439629ab082
update some deps to the latest
add rust-toolchain.toml: rustc 1.69.0 (84c898d65 2023-04-16) / rustc 1.71.0-nightly (8b4b20836 2023-05-22)

Close #1054  or merge it first

the sql tests of mapping-sync failed
cc @tgmichel @nbaztec
@sorpaas maybe we could merge polkadot-v0.9.42 PR first?

the sql tests of mapping-sync failed cc @tgmichel @nbaztec
@sorpaas maybe we could merge polkadot-v0.9.42 PR first?

I checked and seems the error is here https://github.com/paritytech/frontier/blob/master/client/db/src/sql/mod.rs#L344
the code cannot find any logs for the block hashes so doesn't insert anything.

@nbaztec @koushiro I think I know how to fix this, checking it

@koushiro please cherry pick from https://github.com/moonbeam-foundation/frontier/commit/24f95bc38a38a315f14ed254b10fc7d7aca76aba
The issue was we are injecting the pallet-ethereum Digest directly into the BlockBuilder block constructor, and with recent changes in substrate-test-runtime that is no longer possible, as Executive checks will be run over the block we are trying to produce.
Instead we need to use the new push_deposit_log_digest_item, which will push the digest to frame system storage, which in turn will make Executive final_checks to pass.


Check window.MediaSource before call constructor

MediaSource is an experimental technology. Not compatible with iOS Safary, even with current last iOS version (v12 April 2019).
This JS  function (polyfill) crashes web compiled Dart load on iOS.

Note that without this fix Dart crashes in iOS Safari.
JS generated by:
webdev serve --hostname <IP_ADDRESS> -r

The function polyfill should use only standard JS, and this should be documented/commented in the code at least.

Thanks for the context and patch.  We'll need to run this through the standard Dart SDK contribution process (including gerrit to run on our submit queue):
https://github.com/dart-lang/sdk/blob/master/CONTRIBUTING.md
If you'd prefer, one of us can take this over.

Thanks for the context and patch. We'll need to run this through the standard Dart SDK contribution process (including gerrit to run on our submit queue):
https://github.com/dart-lang/sdk/blob/master/CONTRIBUTING.md
If you'd prefer, one of us can take this over.

@vsmenon
I saw that the patch is already at master branch. Thanks for the merge.

Don't forget to add me in the contributors list, I will be very glad.