openapi: more hackery

This is a temporary workaround for https://github.com/sigstore/rekor/pull/2091: LogEntry.body is marked as an object but is really a base64 string.

Blocked on merge of https://github.com/sigstore/rekor/pull/2092. Once that's in, I can update the repo + ref for Rekor back to upstream.


Improper authentication results in a "No data key found in JSON object." error

This is pretty misleading and could be obnoxious for users.

Fixed and shipped.


Bevy 0.12

This is blocked by https://github.com/aevyrie/bevy_eventlistener/pull/11 and https://github.com/aevyrie/bevy_mod_raycast/pull/100

Found a few problems with the bevy_sprite_picking backend in 0.12. Basically ComputedVisibility -> ViewVisibility and size() now returns a UVec2 instead of a Vec2, after fixing those, the sprite backend works for me in 0.12. Here's the changes I made to the backend (@TristanCacqueray I can PR to you or you can just snag the simple changes): https://github.com/nametable/bevy_mod_picking/commit/834d6f2853f86039d5fa4411071dbb327e791b3f

Thanks @nametable, to be honest, I am only using the backend for ui-navigation.

Tested with bevy_sprite_picking backend

Thanks for the contribution!


✨[feature Request]: add dark mode toggle

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Adding a dark mode toggle allows users to switch the website's color scheme to a darker palette, reducing eye strain and improving readability in low-light environments.
Use Case
A dark mode toggle on a news website can enhance user comfort during nighttime reading, offering a personalized experience that keeps users engaged longer.
Benefits
adding dark mode can enhance the website.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24EXTD contributor
[X] I have starred the repository

@snehaapratap when u applying dark mode please ensure that , the background color image pink and light colours change to black in same gradient order.

sure @Anjaliavv51 will definitely do that!

@snehaapratap assigning to you go ahead


Feat logentries

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

v5.6.0
GitHub release

Your semantic-release bot :package::rocket:


Fix linting script

@krubenok @pierreTklein @erickzhao
I added some dependencies to make the lint script work because it wasn't working before.
Now I'm facing a separate issue:
When calling the script npm run lint, the build ends with an error

When I just type the script into terminal tslint 'src/**/*.{ts,tsx}' it works fine?????

Pls help me. Ideas on what to do?? Apparently this is a known bug that happens to other people but has also been fixed from time to time??? If we can live with the error, I guess that's fine 🤷♀ but maybe I'm just fried and it's a me issue here
Checkout branch lint-script to play around with it.
tslint 'src/**/*.{ts,tsx}' finds the linting errors
tslint --fix 'src/**/*.{ts,tsx}' finds and fixes the linting errors

@loreina is there a reason you are recommending the tslint plugin from Microsoft with ~20k downloads vs. the one from egamma with ~10M downloads?
https://marketplace.visualstudio.com/items?itemName=eg2.tslint

I did a quick'npm install' and 'npm install -g npm' b/c I was told a minor update was available and it started working?

In the branch I made for this issue I also added a .nvmrc file to keep node versions consistent on the project. Info on nvm here: https://github.com/creationix/nvm


file_watcher feature cannot find assets folder in workspace

Bevy version
v0.15.0  #3f2baf8ec
[Optional] Relevant system information
Observed on both Arch Linux and macOS.
What you did
A basic workspace setup where the actual bevy App launches from a subcrate, like the following Cargo.toml setup:
[workspace]
resolver = "2"
members = [
    "library_a",
    "main_bevy_game",
]

The assets folder for the game resides in the main_bevy_game root. There are no other assets folders in the workspace.
main_bevy_game enables file_watcher feature, and then in main.rs:
    App::new()
        .add_plugins(DefaultPlugins.set(AssetPlugin {
            watch_for_changes_override: Some(true),
            ..Default::default()
        }));

What went wrong
On launch, bevy issues the following warning:
WARN bevy_asset::io::source: Skip creating file watcher because path "assets" does not exist.
Creating a folder at the root of the workspace will suppress this warning, but file changes are not recognized.
Moving the assets folder to the root of the workspace causes a panic:
Failed to create file watcher from path "assets", Error { kind: PathNotFound, paths: ["/Users/notarealuser/workspace/main_bevy_game/assets"] }
(Path altered for privacy)
Additional information
I believe this is from using a raw std::path::PathBuf to test if the assets folder exists whereas in most other cases it gets built out.
I have a quick one-line fix:
bevy_asset crate @ bevy_assets/src/io/source.rs
line 534:
                let path = super::file::get_base_path().join(path.clone());
This builds the path as it does in file::FileWatcher::new() and seems to make everything work as expected.
This might not be the appropriate fix, or perhaps my project structure is not as intended. I'm not sure, so I haven't opened a PR for this one line change.

This seems like a bug to me. The path variable can be traced back to file_path in AssetPlugin which is relative to the project root. And as you have pointed out all the other places that uses this same path appends it to get_base_path.
It was introduced in #13902, and I can see why it wasn't obvious from context. It's pretty error prone that the path is relative to some other folder until it hits that constructor, while just being named path.

You should open a PR if it isn't too much trouble.


Addition of FAQs by Users in About Us Page

There is no FAQs Section on the website, and it should be on the About Us Page.
Addition of FAQs section helps students to clear there doubts.

ok do it

@yatulearn please check my PR


#323 Fix for missed TINY_IMAGE during DockerClient initialization

Fix for No such image: alpine:3.5 #323
@bsideup

@gorelikov merged, thanks for your contribution! :)

Hi there. It's crucial PR for our CI because we still cannot test and build up services with Jenkins. I'm afraid it's to long to wait for 1.3.0 release. So I'd be glad if it would be rescheduled to 1.2.1, for example :)

You could always fallback to using a Jitpack dependency on the merged PR:
https://www.testcontainers.org/usage.html#maven-dependencies


Navbar section image must be of full width

@GVishnudhasan please assign me this issue

Already assigned @nishtha-902

is it assigned to me?

Kindly work on all the navbar including the ones in the dashboard. good luck @nishtha-902. Whoever get the job done ASAP will get a merge @Subhajit-2023-44.

you can assign this task to me...


Add required prop

Ability to set the required attribute on the HTML input element.  This is useful when using modern browsers' builtin form validation.

@Shamus03 Please resolve the merge conflict.

@mattelen We can add this simple improvement now as we have released the v3.

@Shamus03 Please resolve the merge conflict.

Done!


Numerous dependencies missing

electron needs to be globally declared in npm as well as angular and some others I have not found yet. I will look into noting these more clearly in a PR

Could you please clarify which ones?
When you follow Readme, do you get any issues or missing packages errors?

 You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
http://errors.angularjs.org/1.5.3/$injector/nomod?p0=ion-floating-menu
at file:///home/tad/esteem-desktop/scripts/lib/ionic.js:13443:12
at file:///home/tad/esteem-desktop/scripts/lib/ionic.js:15409:17
at ensure (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:15333:38)
at module (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:15407:14)
at file:///home/tad/esteem-desktop/scripts/lib/ionic.js:17899:22
at forEach (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:13696:20)
at loadModules (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:17883:5)
at file:///home/tad/esteem-desktop/scripts/lib/ionic.js:17900:40
at forEach (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:13696:20)
at loadModules (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:17883:5)
http://errors.angularjs.org/1.5.3/$injector/modulerr?p0=ion-floating-menu&p…2F%2F%2Fhome%2Ftad%2Festeem-desktop%2Fscripts%2Flib%2Fionic.js%3A17883%3A5)
at file:///home/tad/esteem-desktop/scripts/lib/ionic.js:13443:12
at file:///home/tad/esteem-desktop/scripts/lib/ionic.js:17922:15
at forEach (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:13696:20)
at loadModules (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:17883:5)
at file:///home/tad/esteem-desktop/scripts/lib/ionic.js:17900:40
at forEach (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:13696:20)
at loadModules (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:17883:5)
at createInjector (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:17805:19)
at doBootstrap (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:15085:20)
at bootstrap (file:///home/tad/esteem-desktop/scripts/lib/ionic.js:15106:12)
http://errors.angularjs.org/1.5.3/$injector/modulerr?p0=steem&p1=Error%3A%2…F%2F%2Fhome%2Ftad%2Festeem-desktop%2Fscripts%2Flib%2Fionic.js%3A15106%3A12)

Quick fix should be available. Please view 268a38954c6b68d5fb68b94dca249b5f0e4d7cb9 and and eb0f8830f533e6f30b6a6eef318c6314c0079696
Let me know if you find any more issues.

Aha my mistake thanks man!

alright so those suggestion didnt fix me up but here is what did:
I obtained a copy of ion-floating-menu and put it into its folder in lib/ion-floating-menu/dist
and did the same with ngcordova into lib/ngcordova/dist it seems these two packages are required but never explicitly installed.


RN0.64.0 Dimensions.get('screen') and screen property of Dimensions eventlistener does not reflect device orientation

RN0.64.0 Dimensions.get('screen') and screen property of Dimensions eventlistener does not reflect device orientation. Works as expected with RN0.63.4
Edit: It seems like the window property also is affected by this bug.
React Native version:
System:
OS: Windows 10 10.0.19042
CPU: (12) x64 AMD Ryzen 5 4600H with Radeon Graphics
Memory: 10.49 GB / 31.36 GB
Binaries:
Node: 14.15.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
Watchman: 20201115.021953.0 - C:\ProgramData\chocolatey\bin\watchman.EXE
SDKs:
Android SDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-201.87<IP_ADDRESS>99119
Visual Studio: 16.8.30717.126 (Visual Studio Community 2019)
Languages:
Java: <IP_ADDRESS> - C:\Program Files\AdoptOpenJDK\jdk-<IP_ADDRESS>-hotspot\bin\javac.EXE
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.0 => 0.64.0
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce

Set up a new React Native project with npx react-native init AwesomeTSProject --template react-native-template-typescript
Add eventlistener in App.tsx:

 useEffect(() => {
    function handleDimensionsChange({
      window,
      screen,
    }: {
      window: ScaledSize;
      screen: ScaledSize;
    }) {
      console.log("Dimensions.get('screen'):", Dimensions.get('screen'));
      console.log('handleDimensionsChange -> window', window);
      console.log('handleDimensionsChange -> screen', screen);
    }
    Dimensions.addEventListener('change', handleDimensionsChange);

    return () => {
      Dimensions.removeEventListener('change', handleDimensionsChange);
    };
  }, []);

Expected Results
That the height and width of screen property reflect the device orientation like with RN0.63.4.

Same issue here using 0.64.0
I confirm that this is working fine with 0.63.4
I add this strange behaviour using 0.64.0 :

Kill your app
Launch your app in landscape mode
Change device orientation to portrait mode
-> Dimensions event is correctly fired with correct dimensions, just one time, then this is broken and it will never fire again. It does not work at all if you launch your app using portait mode first.

Fixed in RN0.64.2


NO-JIRA: Add release notes to commit and print proper output when release errors

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #
Checklist

[ ] Subject and description added to both, commit and PR.
[ ] Relevant issues have been referenced.
[ ] This change includes docs.
[ ] This change includes unit tests.

/lgtm

/retest-required


macOS 10.13.4 Security & Privacy, unable to "Allow"

This looks like it is most likely an issue with 10.13.4 and not karabiner, but I'm creating this issue to track
I just upgraded to macOS 10.13.4. Karabiner-Elements was installed and working before upgrading.
After upgrading, I was once again prompted to enable the kernel extension to be allowed through System Preferences -> Security & Privacy. However, the "Allow" button does not function.
This might be creating issues for other kernel extensions, as well. I've attempted to reboot, select the "Allow" button with the built in trackpad, but no dice.
Google Drive, JAMF, and more seem to be experiencing some issues as well.
The only workaround that reportedly works is to log in as another administrative account and allow the kernel extension. If anyone else runs into this issue, I recommend attempting the above linked workarounds

I have the same problem and haven't have MagicPrefs installed.

Sonos Controller for Mac, version 8.5.1 blocked it for me.

Yep, Sonos Controller blocked it for me as well. Had to close it then it worked perfectly.


error Command failed: yarnpkg

The installation fails with error Command failed: yarnpkg
macOS Hight Sierra 10.13
Node 6.10.3
npm 3.10.10
latest gatsby-cli
If I try the gatsby new gatsby-site -starter everything works perfectly.
info Creating new site from git: git://github.com/gatsbyjs/gatsby-starter-blog.git
Cloning into 'gatsby-blog'...
remote: Counting objects: 769, done.
remote: Compressing objects: 100% (20/20), done.
remote: Total 769 (delta 12), reused 23 (delta 8), pack-reused 740
Receiving objects: 100% (769/769), 1.50 MiB | 1001.00 KiB/s, done.
Resolving deltas: 100% (404/404), done.
success Created starter directory layout
info Installing packages...
yarn install v1.0.2
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning<EMAIL_ADDRESS>🙌  Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency "webpack@1 || 2 || ^2.1.0-beta || ^2.2.0-rc".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.11.0".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.6.0 || ^0.7.0 || ^0.8.0-b || ^0.9.0 || ^0.10.0 || ^0.11.0".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency "react@>=15".
warning<EMAIL_ADDRESS>has incorrect peer dependency "react@>=15".
warning<EMAIL_ADDRESS>has incorrect peer dependency "file-loader@*".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^2.0.0 || ^3.0.0".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS><3".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0-beta || ^16.0.0".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0-beta || ^16.0.0".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency "preact@>=5".
warning<EMAIL_ADDRESS>has incorrect peer dependency "preact@*".
warning<EMAIL_ADDRESS>has incorrect peer dependency "preact@*".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning<EMAIL_ADDRESS>has incorrect peer dependency "react@*".
warning<EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning The case-insensitive file /Users/rdc/Sites/gatsby-blog/node_modules/jspm/node_modules shouldn't be copied twice in one bulk copy
[4/4] 📃  Building fresh packages...
[1/5] ⡀ fsevents
[2/5] ⡀ uws
[-/5] ⡀ waiting...
[4/5] ⡀ pngquant-bin
error /Users/rdc/Sites/gatsby-blog/node_modules/sharp: Command failed.
 ]
Error: You have not agreed to the Xcode license. Please resolve this by running:
  sudo xcodebuild -license accept
gyp: Call to 'which brew >/dev/null 2>&1 && eval $(brew --env) && echo $PKG_CONFIG_LIBDIR || true' returned exit status 0 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Users/rdc/.util/n/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:305:16)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Darwin 17.0.0
gyp ERR! command "/Users/rdc/.util/n/bin/node" "/Users/rdc/.util/n/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/rdc/Sites/gatsby-blog/node_modules/sharp

error Command failed: yarnpkg

  Error: Command failed: yarnpkg

  - index.js:236 Promise.all.then.arr
    [lib]/[gatsby-cli]/[execa]/index.js:236:11

  - util.js:16 tryCatcher
    [lib]/[gatsby-cli]/[bluebird]/js/release/util.js:16:23

  - promise.js:512 Promise._settlePromiseFromHandler
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise.js:512:31

  - promise.js:569 Promise._settlePromise
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise.js:569:18

  - promise.js:614 Promise._settlePromise0
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise.js:614:10

  - promise.js:693 Promise._settlePromises
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise.js:693:18

  - promise.js:638 Promise._fulfill
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise.js:638:18

  - promise_array.js:126 PromiseArray._resolve
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise_array.js:126:19

  - promise_array.js:144 PromiseArray._promiseFulfilled
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise_array.js:144:14

  - promise.js:574 Promise._settlePromise
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise.js:574:26

  - promise.js:614 Promise._settlePromise0
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise.js:614:10

  - promise.js:693 Promise._settlePromises
    [lib]/[gatsby-cli]/[bluebird]/js/release/promise.js:693:18

  - async.js:133 Async._drainQueue
    [lib]/[gatsby-cli]/[bluebird]/js/release/async.js:133:16

  - async.js:143 Async._drainQueues
    [lib]/[gatsby-cli]/[bluebird]/js/release/async.js:143:10

  - async.js:17 Immediate.Async.drainQueues
    [lib]/[gatsby-cli]/[bluebird]/js/release/async.js:17:14

Mac:sites rdc$ node -v
v6.10.3
Mac:sites rdc$ npm -v
3.10.10
Mac:sites rdc$

Updating yarn from version 1.0.2 to the latest version 1.2.1 fixed the error.
Perhaps yarn should be added as a required dependency.

You also need to run sudo xcodebuild -license accept apparently.


Custom format does not work when option text-input is used

Dear @Jasenkoo,
The calendar works nicely with the text-input option enabled. But I am facing an issue which is not present if I don't enable text-input and pick directly the date from the calendar. I need to show the date in the datepicker input box in UTC. For this, I created a custom formatting function. For example the current date is 31/08/2023 12:47 but in the datepicker input box I display it as 31/08/2023 10:47. This works fine without text-input.
If I use text-input option, there is an error related to the format. As you can see from the video, after I click outside the input box the date becomes blank. It works only if I use format="dd/MM/yyyy HH:mm" but I don't know how to customize it correctly to display the date in UTC.
Is this a bug when using text-input or I need to use the customized function differently along with text-input ?
https://github.com/Vuepic/vue-datepicker/assets/51837829/e1bcf906-b655-4b7e-b3b1-7d22acaae99d
The code I use in Playground is
<template>
  <div>
    <VueDatePicker
      :model-value="selectedDate"
      @update:model-value="handleDateUpdate"
      :clearable="false"
      :year-range="[1900, 2470]"
      auto-apply
      :format="formatDateToCustomString"
      text-input
    ></VueDatePicker>
  </div>
</template>

<script>
import VueDatePicker from '@vuepic/vue-datepicker';
import<EMAIL_ADDRESS>
export default {
  components: {
    VueDatePicker,
  },
  data() {
    return {
      selectedDate: new Date(),
    };
  },
  methods: {
    handleDateUpdate(newDate) {
      this.selectedDate = newDate;
    },
    formatDateToCustomString(dateString) {
      const date = new Date(dateString);
      const day = String(date.getUTCDate()).padStart(2, '0');
      const month = String(date.getUTCMonth() + 1).padStart(2, '0'); // Months are 0-based
      const year = date.getUTCFullYear();
      const hours = String(date.getUTCHours()).padStart(2, '0');
      const minutes = String(date.getUTCMinutes()).padStart(2, '0');
      return `${day}/${month}/${year} ${hours}:${minutes}`;
    },
  },
};
</script>

@lealea401 What you are trying to achieve is not possible.

You can't use function for both text-input parsing and format

text-input parser function must return Date or null
format function must return string

To separate these concerns, you need to provide

:format="formatDateReturnString"
:text-input={ format: parseDateReturnDate }

When the function is provided to the text-input format, the value displayed in the input field will fall back to the format prop.
Keep in mind that the Date that is returned from the parser function needs to be in sync. In your case, if your format is set that months start from 0, you will need to bump numbers in the format function in order to return the proper date, otherwise, it will always return one month before the current.

Dear @Jasenkoo, I understand...but without using any formatting, is it possible to create a calendar that gives the dates in UTC?
I saw this example in the documentation

But it works only if you select the UTC from the list.
I was wondering if it would be possible to have it work like this:
<VueDatePicker
            v-model="date"
            :timezone="UTC"
 />

I am working with scientific data and the dates are in UTC so, an UTC calendar would be useful.

@lealea401 Yes, you can use utc prop

@Jasenkoo , thanks! I knew about this property but it was not working as I was expecting. I tried to use the option 'preserve' expecting to see a difference of two hours in the calendar but I see that the input is converted in local timezone. My goal is to to see the time in UTC when I open the calendar as the preserve option would work (preserve : The input date will be the same, meaning, that it will not convert the date in the local timezone, but preserve the original UTC time)
https://github.com/Vuepic/vue-datepicker/assets/51837829/f9a3a787-8727-4216-ae60-2efec4a0275e

Dear @Jasenkoo, could you give me feedback on my last question? If I could have the dates in the calendar in UTC it would be great. Thank you so much.

@lealea401
The date object in the browser must be in the local time zone. You can't remove the timezone, most of the libraries,  just add/sub times depending on the timezone. That said, you will have to convert the date object to a string value if you want to remove the timezone value.
Let's say the current time is UTC 18:00 and your timezone is GMT+1

preserve if you provide the date, it will keep it on 18:00 (expected that you only work with UTC dates and not concerned about the timezone)
true will add +1 and the value will be 19:00 (You will receive UTC date and want to display it in user local timezone)

@Jasenkoo, but the example that you provide here timezone works exactly how I want it to work, i.e.: if you select "UTC" as timezone, and let's say my local time is 07:55 when I open the calendar to pick up a date with hour and minutes the hours-minutes picker reflects the UTC time, i.e. it does not show 07:55 but 05.55.
https://github.com/Vuepic/vue-datepicker/assets/51837829/9f29206d-d13a-4826-a228-581d00a087be
In this example I see that you use :timezone="UTC"
<VueDatePicker v-model="date" :timezone="timezone" />
but it works only if you select the timezone from the select droplist. Ideally it should work like this:
<VueDatePicker v-model="date" :timezone="UTC" />
I thought that using utc='preserve' it would work in the same way, i.e. when you open the watch with hour:minutes, I would see 05:55 not 07:55. Since the time on the pc shows the same time as in the calendar it is not evident for the user that the calendar is set to UTC.
Is it possible to achieve a calendar like in the  timezone  but without selecting the timezone but setting it by default? Unfortunately utc="true" or utc='preserve' do not have the same behavior.
Thank you so much


.Net: Ambiguous call in MapReduce Sample

Hi, I am having while building up the .NET Solution an error due to an ambiguous call,
I am getting: "Severity	Code	Description	Project	File	Line	Suppression State
Error	CS0121	The call is ambiguous between the following methods or properties: 'string.Split(char[]?, StringSplitOptions)' and 'string.Split(string?, StringSplitOptions)'	GettingStartedWithProcesses	C:\git\joslat\semantic-kernel\dotnet\samples\GettingStartedWithProcesses\Step05\Step05_MapReduce.cs	119	Active"
Where: \semantic-kernel\dotnet\samples\GettingStartedWithProcesses\Step05\Step05_MapReduce.cs

@joslat - I'm not able to reproduce this error and its not occuring in our build / release pipeline.  I'm guessing there's some different between our build / development environments.  In anycase, I can switch this to an array of strings to get around the ambitugity on your system.

that would do, I changed it to this locally for it to build, for if it helps :)
string[] words = chunk.Split(new char[] { ' ', '\n', '\r', '.', ',', '’' }, StringSplitOptions.RemoveEmptyEntries);

FWIW: We get warnings/suggestions when using that syntax in our envronment.  There's a strong preference for the collection initializer: [...]


Reporter error in judoscale-delayed_job when log level is set

Rails <IP_ADDRESS>. Occurs when log level is set via config file or ENV variable, for both :warn and :info. (Also occurs for gem version 1.2.3).
[Judoscale] Reporter error: #<NoMethodError: undefined method `reopen' for nil:NilClass>
[Judoscale] /app/vendor/bundle/ruby/2.7.0/bundler/gems/rails-63ea815f1155/activesupport/lib/active_support/core_ext/kernel/reporting.rb:106:in `ensure in capture'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/bundler/gems/rails-63ea815f1155/activesupport/lib/active_support/core_ext/kernel/reporting.rb:106:in `capture'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/job_metrics_collector/active_record_helper.rb:19:in `run_silently'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/job_metrics_collector/active_record_helper.rb:26:in `select_rows_silently'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-delayed_job-1.3.0/lib/judoscale/delayed_job/metrics_collector.rb:37:in `collect'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/reporter.rb:60:in `block (2 levels) in run_metrics_collection'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/reporter.rb:92:in `log_exceptions'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/reporter.rb:60:in `block in run_metrics_collection'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/reporter.rb:59:in `each'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/reporter.rb:59:in `flat_map'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/reporter.rb:59:in `run_metrics_collection'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/reporter.rb:49:in `block (2 levels) in run_loop'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/reporter.rb:48:in `loop'
[Judoscale] /app/vendor/bundle/ruby/2.7.0/gems/judoscale-ruby-1.3.0/lib/judoscale/reporter.rb:48:in `block in run_loop'

Hey Alex, thanks for the report! I'll try to repro this on my end.

I'm having all sorts of issues getting things running locally with Rails <IP_ADDRESS>, so I can't reproduce this exact issue, but it looks like there are some documented issues with logger.silence in Rails 4.
The only real workaround I would recommend is this monkey patch that removes the call to logger.silence from our run_silently helper:
class Judoscale::DelayedJob::MetricsCollector
  def run_silently(&block)
    yield
  end
end

Thanks for taking a look.


Does this support subscription APIs also?

Just need to have some features in my application for auto pay and it seems to be valid with subscription APIs.

Hi @sandeepgit14
No. This doesn't support Subscription APIs as of now


eb scale on single-instance environment

Description
Im currently using a testing environment and i have a scheduled scaling, so eventualy it has 0 instances. My problem is when i try to manually set it to 1 with eb scale 1 it asks:

The environment is currently a single-instance. Do you want to change to a load-balancing environment?
WARNING: If you choose yes, the environment and your application will be temporarily unavailable.
(Y/n):

and the when choosing no nothing happens.
Steps to reproduce
run eb scale 1 or eb scale 0 on a single-instance environment
Observed result
Scale doesnt apply
Expected result
Scale applied succesfully
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)

OS: Amazon Linux 2
EBCLI version: 3.17.1

Just out of curiosity, why don't you terminate the environment and start it up fresh?

Just out of curiosity, why don't you terminate the environment and start it up fresh?

It seems overkill i just want a simple command to initiate a instance inside the environment.

@faculezcano thanks for reaching out. eb scale 0 on single instance environment seems to be working fine for me.

Closing this issue as there has been no update for an extended period of time.

Sorry for commenting on a closed issue, but I faced this exact issue today. I'd like to manually scale the instance count to 1 for some unexpected work that requires the server to be up, while keeping the environment "single instance" which was the configuration prior to the Time-based Scaling scaled the instance count to 0.
As this issue says, using eb scale 1 won't work as it'd add a load balancer, which is something I don't want. I've worked around the issue by adding a one-time "scheduled action" to set the desired instance count to 1 in a few minutes.
But the thing is, the Time-based Scaling will maintain the environment's "single instance" status. Is it using a different method than eb scale 1 for adding an instance? If so, what is it, and it is available as a EB CLI command? I've gone thru the command reference and couldn't find anything.


Add clustering and make size circle fixed while zomming in/out

The (new) observations should be organized in such way that:

[ ] they are clustered: better view at diferent scales
[ ] the circles mantain the same size while zooming in/out

Close as completed via https://github.com/inbo/craywatch/pull/279


Add nodeMaxTxSize

Fixes #2106.

LGTM, but is it okay for this function to require the full LedgerState?

nodeMaxBlockSize does the same thing. We have no abstraction for the "protocol parameters" of a ledger.

bors merge


add basic auth support to proxy chain

I want to be able to create a proxy chain to a remote proxy which is not under my control and is configured to use http basic authentication.
Here is the usage code for the changes I made.
bootstrap.withChainProxyManager(new ChainedProxyManager() {

    @Override
    public void lookupChainedProxies(HttpRequest httpRequest, Queue<ChainedProxy> chainedProxies) {
        chainedProxies.add(new ChainedProxyAdapter() {

            @Override
            public InetSocketAddress getChainedProxyAddress() {
                try {
                    return new InetSocketAddress(InetAddress.getByName(chainingProxyHost), chainingProxyPort);
                } catch (UnknownHostException uhe) {
                    throw new RuntimeException(uhe);
                }
            }

            @Override
            public String getBasicAuthUser() {
                return chainingProxyUser;
            }

            @Override
            public String getBasicAuthPassword() {
                return chainingProxyPass;
            }

        });
    }
});

Chained proxy authorization is already supported. There's no need to change the LittleProxy code at all, simply add a filter to the chained proxy manager. (Here's an example of how BMP does this.](https://github.com/lightbody/browsermob-proxy/blob/master/browsermob-core/src/main/java/net/lightbody/bmp/BrowserMobProxyServer.java#L340)

Thank you for the fast answer and the example. It will do what I want and it is totally ok for me to close this PR.
What I didn't like at the example is that it's a very generic way to do something special. It's not intuitive to implement the filter method to do authentication and it results in a code that is difficult to understand and is doing things I would expect has to be done by the framework.
By the way, having two methods which depends to each other, as I suggest, is also not a beauty solution and way too special. I would prefere some authentication interface which can be returned by a new ChainedProxy method which would be generic enough to allow different authentication types but results in less usage code with a higher knowability. But this is a question of architecture I can't really estimate with my little knowledge about LittleProxy.


Create new branch for Galactic

Modify env.hpp to get_env.hpp according to https://github.com/ika-rwth-aachen/mqtt_client/issues/19
Build and run the node successfully.

Yes, I agree. There should be a way to include both. I know little about CPP, but I think we could use Preprocessor directives.
#if HUMBLE
#include <rcpputils/env.hpp>
#elif GALACTIC
#include <rcpputils/get_env.hpp>
#endif

Forgive me if I'm wrong.

Yes, that should be possible if we can correctly set these compile definitions in CMakeLists.txt based on the ROS_DISTRO environment variable.
I don't have much time on my hands at the moment, but would happily accept a PR from you.


Inquiry About Negative ‘amount’ Values in API Output

I have a question.
When using the following API, I’ve recently noticed addresses with a negative amount. What does this mean?
https://api.astar.network/api/v3/astar/dapps-staking/stakerslist/[contractAddress]
sample output:
  {
    "stakerAddress": "beCWnssJmDmSzRCsj1FR4LfocPx6zZwa8Br3CGsPAcLj4h5",
    "amount": "-60000000000000000000000"
  },
  {
    "stakerAddress": "WDTjELRL7B3pX5ZwYn1bxwxUQ4sX7vv3DFHoPpuUkKKwChE",
    "amount": "-555000000000000000000"
  },

Until now, I have been summing up the "amount" of stakers from this API to calculate the current total staking amount for dApp. However, I have come across dApps that end up with a negative total staking amount due to the inclusion of negative numbers. Therefore, I think it is necessary to correctly understand the meaning of these negative numbers.
Alternatively, if it is some sort of bug, I would appreciate it if it could be fixed.

HI @tksarah thank you for the ticket. Negative numbers usually means unstake. Sum of all stakes/unstakes should be >=0. If you are getting a negative sum this must be a bug which become visible after dApp staking period 2 started.
I will check that.

Thank you for your reply.
From what I've seen of the data, my guess as to what "negative values" mean was the same as yours. Therefore, I was able to understand that part.
On the other hand, I am using this API to create a system that can aggregate data, but since yesterday's aggregation, addresses that take negative values when summed up have suddenly disappeared. Therefore, at this point, I do not have any addresses to share where this phenomenon is occurring.
However, I don't know if this phenomenon is related, but the address "0x74cc66cd0cf57bb2a0f237c89bcf8db92d3721a8", which has already been removed from the list, is still a negative value. (This was "0" a little while ago. Since it's delisted, it makes sense that it remains "0".)
Also, I may need to write this to the astar-app side, but I noticed something new yesterday from a related perspective. The amount of staking by the staker in the values obtained with this API (/api/v3/{network}/dapps-staking/stakerslist/{contractAddress}) is different from the amount of staking displayed on the Astar Portal. (I will refrain from writing this because it is my address)
(For example, while Astar Portal displays 5500, the data obtained from the API is 6000. The difference is not significant, but there is enough of a gap to notice the discrepancy immediately.)

Hi @tksarah please check now. This should be fixed.

Hi @bobo-k2
Here is the English translation of your text:
Thank you!
That's wonderful!
All the gaps I was checking have been improved.
By the way, what was the cause?
I will also let you know about the page I created.
https://agent.sun-t-sarah.work/
Currently, I believe you can check the correct values here.

Hi @tksarah the root cause is fixed in https://github.com/AstarNetwork/dapps-staking-indexer-v3/pull/26 As I suspected above the issue was cause by incorrect handling of dApp staking periods.
Token API PR you mentioned https://github.com/AstarNetwork/astar-token-api/pull/161#event-13551136244 is just to support new indexer data structure
I will bookmark your page. It looks nice and useful. If
Thank you for your contribution and if you find any other inconsistency in Token API data don't hesitate to create an issue.

Thank you!
Please close this issue.

This issue has been resolved.


Initial support for PHP7

This PR provides only an "intermediate refactoring" of the current source code,
which is not the abstract state zephir would need to support PHP code generation,
with total separation of backends.
This PR does only aim to provide PHP7 compatibility and therefor required
some refactoring, which was done in a limited extent.
Stuff which would have to be done for that:

Move the operator/statement/optimizer logic that's depending on the backend to
classes of the backend (which currently partly is just in-place in the old files with conditionals)
So you would have a class providing the general implementation, which is shared between backends (common code for validating parameters, checking input, ...)
and a version per backend which handles code generation (and temp variable usage, ...)

This PR

provides initial support for PHP7 (ZE3) Extensions (compiler and kernel support)
(testcases pass, except preg-match, requires proper reference support in zephir)

Todos

[x] compare generated sources for ZE2

generated code for zephir tests seems to match

[x] complete some backend definitions (in BaseBackend)
[ ] general cleanup, eventually more performance tweaks/documentation

Huge thanks!

:+1: Awesome, eager for the zephir-parser.exe :)

@flip111 It's the same as before

You mean the binary file has been updated in the development branch? I will check it, thank you.

No but you can grab the most current one from appveyor and I mean it hasn't changed for PHP7

These are the errors i was talking about
Generating Code...
        "cl.exe" /D _USRDLL /D PHP7DLLTS_EXPORTS /D PHP_EXPORTS /D LIBZEND_EXPORTS /D TSRM_EXPORTS /D SAPI_EXPORTS /D WINVER=0x0600 /D COMPILE_DL_FTP /D COMPILE
_DL_OPCACHE -Ipecl\zep\utils\ext /D ZEPHIR_RELEASE /nologo /I . /I main /I Zend /I TSRM /I ext /D _WINDOWS /D ZEND_WIN32=1 /D PHP_WIN32=1 /D WIN32 /D _MBCS /W3
/FD /wd4996 /D_USE_32BIT_TIME_T=1 /RTC1 /MP /LDd /MDd /W3 /Gm /Od /D _DEBUG /D ZEND_DEBUG=1 /ZI /D ZTS=1 /I "D:\dev\php7\bin\phpdev\vc14\x86\no\include" /D FD_S
ETSIZE=256 /FoD:\dev\php7\bin\phpdev\vc14\x86\Debug_TS\pecl\zep\utils\ext\ /FpD:\dev\php7\bin\phpdev\vc14\x86\Debug_TS\pecl\zep\utils\ext\ /FRD:\dev\php7\bin\ph
pdev\vc14\x86\Debug_TS\pecl\zep\utils\ext\ /FdD:\dev\php7\bin\phpdev\vc14\x86\Debug_TS\pecl\zep\utils\ext\ /c pecl\zep\utils\ext\utils.c
utils.c
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\main.h(90): warning C4013: 'Z_REFCOUNT_PP' undefined; assuming extern returning int
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\main.h(90): warning C4013: 'Z_ISREF_PP' undefined; assuming extern returning int
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\main.h(93): warning C4013: 'ALLOC_ZVAL' undefined; assuming extern returning int
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\main.h(94): warning C4013: 'Z_UNSET_ISREF_P' undefined; assuming extern returning int
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.h(748): warning C4047: 'function': 'zval *' differs in levels of indirection from 'zval **'
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.h(748): warning C4024: '_zval_ptr_dtor': different types for formal and actual parameter 1
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.h(756): warning C4013: 'ALLOC_INIT_ZVAL' undefined; assuming extern returning int
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.h(763): warning C4013: 'COPY_PZVAL_TO_ZVAL' undefined; assuming extern returning int
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.h(785): warning C4047: 'function': 'zval *' differs in levels of indirection from 'zval **'
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.h(785): warning C4024: '_zval_ptr_dtor': different types for formal and actual parameter 1
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.h(826): warning C4047: 'function': 'zval *' differs in levels of indirection from 'zval **'
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.h(826): warning C4024: '_zval_ptr_dtor': different types for formal and actual parameter 1
d:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\utils.c(103): error C2065: 'tsrm_ls': undeclared identifier
NMAKE : fatal error U1077: '"D:\dev\Microsoft Visual Studio 14.0\VC\BIN\cl.exe"' : return code '0x2'
Stop.

I have been able to build an hello world extension (without zephir) so i'm pretty confident my toolchain is setup right ... though i might have made some mistakes on the zephir part.

@flip111
seems like you are compiling for PHP5 and trying to compile that with PHP7, which cant work

How can i compile for PHP7? is there a switch on zephir to turn it on? PHP sources retrieved as such
git clone -b PHP-7.0.0 --single-branch https://github.com/php/php-src.git .  (so no PHP5 sources should be present AFAIK)

The problem is that if you do not specify a target version,
the target version is assumed to be your PHP version (the version of the PHP running your compiler).
You still can use a PHP5 version for compilation
if you explicitly specify zephir build --backend ZendEngine3

@steffengy thank you very much. Great work. The zephir hello world demo works now!
FYI i think on windows you can not issue zephir build directly (it will give some errors). I found that the build process on windows is different than on linux (where you can use phpize). My zephir build commands:
mkdir zep
cd zep
zephir init utils --backend ZendEngine3
cd utils
cp ../../greeting.zep utils\greeting.zep
zephir generate --backend ZendEngine3

And then to generate core + extensions again:
CD ..
CD pecl\zep\utils\utils
zephir generate --backend ZendEngine3
CD ../../../../
nmake clean
CALL buildconf --force --add-modules-dir=%CD%\pecl\zep\utils
CALL configure --enable-debug --enable-phpdbg --enable-utils=shared
nmake
CD Debug_TS
(echo extension_dir = %CD% && echo extension = php_utils.dll) > php.ini
echo.
echo.
php -r "echo Utils\Greeting::say();"

the zephir extension will be compiled along with it.
It's very frustrating (build times) not being able to compile a single extension on windows. Perhaps i could just call cl.exe myself because there doesn't seem to be a script for this (but this is a php issue, not zephir)

On windows you can also use phpize,
thats what zephir build does, see Windows.md even though it might be outdated for now.

@steffengy that's good to know. Would you know how to use phpize on windows? Some sources claim it's not possible
The windows version of phpize seems to be broken (2012)
On Windows, you don't call phpize but instead you call buildconf.bat. (2015)
Myself if i run phpize.bat i get:
Input Error: Can not find script file "D:\dev\php7\bin\phpdev\vc14\x86\win32\build\script\phpize.js".
Now run 'configure --help'

Because of https://github.com/php/php-src/blob/PHP-7.0.0/win32/build/phpize.bat#L2-L3 where it sets the current directory and then the script directory is not available in the current directory.
Is this a candidate for the php bugtracker, or am i doing wrong here and it should be possible like you say?

@flip111
It's just not documented how it works, but it does work.
You need to build a devpack first though and use the built phpize

@steffengy devpack? Are you refering to these steps? bin\phpsdk_buildtree.bat phpdev ?? I have done this..
I noticed documentation is missing, i'm trying to write down the full procedure somewhere, but i got stuck at phpize...

No I mean you need a devel-pack which contains a working version of phpize.
You get this by building a release archive ( nmake snap or simply nmake build-devel ) and then use <Build_Dir>\Release\php-7.0.0beta3-devel-VC14-x86\phpize.bat as phpize

Hi, thanks for your support again. I've been able to build phpize on windows with the instructions you gave me. Though it doesn't work yet (the makefile is incomplete) ... i'm still working on tracking down the problem with phpize. As for zephir i believe the build command in not supported on windows because of
https://github.com/phalcon/zephir/blob/master/Library/Compiler.php#L1178
and
https://github.com/phalcon/zephir/blob/master/Library/Compiler.php#L1099
The WINDOWS.md file seems to be outdated indeed ...
The full output:
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils>zephir build
Copying new kernel files...
The system cannot find the path specified.
Preparing for PHP compilation...
The system cannot find the path specified.
Preparing configuration file...
Compiling...
Installation is not implemented for windows yet! Aborting!

Also when i didn't launch from the compiler environment but a regular prompt:
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils>zephir build
Copying new kernel files...
The system cannot find the path specified.
Preparing for PHP compilation...
The system cannot find the path specified.
Preparing configuration file...
ERROR: Compiler not found
Compiling...
Installation is not implemented for windows yet! Aborting!

At least there seems to be missing some logic there with messages like Compiler not found --> Compiling...
Perhaps worth to open an issue for this?

@flip111
zephir install is not supported but zephir compile is, there's a difference.
It also cannot work from a regular prompt, since a compiler cannot be found like that.
the first output seems correct, are you sure that the build hasn't worked - since for me anything seems fine, since it passed compilation and reached installation and aborted there since that isn't implemented for windows.
Was no .dll file created or how do you come to the conclusion that the build for your full output failed?

@steffengy
I think i was a bit too quick to come to the conclusion that the output failed. After i tried in the right environment (with compiler setup) i didn't check the files anymore. Anyway .. there seem to have been some files created:
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\utils.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\vc140.idb
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\resp\UTILS_GLOBAL_OBJS.txt

Some questions about this:

How can i build the DLL (extension as shared library). I noticed the config.w32 file which gets generated has EXTENSION("utils", "utils.c", null, "-I"+configure_module_dirname); with 3rd parameter to null (should be true for shared library)
Why are the path names so incredibly long? Seems to have taken a wrong basepath?
Why am i getting those The system cannot find the path specified. messages, and which files are they referring to?

shouldn't matter since it isn't compiling PHP
probably absolute paths
cannot say

does D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\ contain a .dll file?
Have you checked the compile_errors / compile output file?

about 2. and 3. i will try to find this later ...
about 1. this is still a problem ... yes i made another mistake by forgetting to set the backend ... (checking the compiler logs was a good idea) ... though still no DLL file. php_utils.lib seems like a static binary.
File present:
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\php_utils.dll.manifest
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\php_utils.dll.res
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\php_utils.exp
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\php_utils.lib
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\utils.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\utils.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\vc140.idb
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\array.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\array.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\backtrace.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\backtrace.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\concat.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\concat.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\debug.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\debug.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\exception.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\exception.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\exit.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\exit.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\fcall.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\file.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\file.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\filter.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\filter.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\hash.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\hash.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\iterator.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\iterator.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\main.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\main.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\math.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\math.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\memory.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\memory.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\object.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\object.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\operators.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\operators.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\require.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\require.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\string.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\string.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\time.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\time.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\variables.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\variables.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\vc140.idb
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\extended\array.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\extended\array.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\extended\fcall.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\extended\fcall.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\kernel\extended\vc140.idb
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\utils\greeting.zep.obj
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\utils\greeting.zep.sbr
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\utils\vc140.idb
D:\dev\php7\bin\phpdev\vc14\x86\pecl\zep\utils\ext\Release_TS\resp\UTILS_GLOBAL_OBJS.txt

Just tested it locally, for me it works perfectly generating a dll file, so there's likely something
failing during compilation on your end.
(.lib in that case is an object file library and no statically linked binary)

yes there is a problem with the linker ... i edited my previous comment and put the logs at the bottom

You are causing total chaos in your build tree.
It seems like you have used a Debug devpack to build a release extension!?
Debug_TS\php-7.0.0beta3-devel-VC14-x86
Probably you have built with --enable-debug before you used nmake build-devel.

@steffengy yes you are right ... i would like to put everything on Debug until code is ready for Release. (I might need debug symbols for debugging)

@flip111
You could also have debug symbols with release builds but thats another story.
(If you wanted to put zephir into debug mode, which is rarely necessary to track an issue down,
that would also be a bit harder on windows.)
So the problem here is that when windows support was added, the builddev option
hasn't existed yet.
(So there is basically no comfortable way to build a development extension yet)
So you would probably have to do the build steps manually.
cd extFolder\ext && configure --enable-extname --enable-debug && nmake
should cover it


Add bbmap, ampliconclip

TODO: Please replace this header with a description of your pull request.
Installation sequence for tool-installers

[ ] Test using @galaxybot test this
[ ] Inspect CI output for expected changes
[ ] Deploy using @galaxybot deploy this if test install was successful
[ ] Merge this PR

hah - too quick for me!


Standardize copyright headers.

The Linebender standard for copyright headers was decided last year in kurbo#207 as the following:
// Copyright <year of file creation> the <Project> Authors
// SPDX-License-Identifier: Apache-2.0 OR MIT

With Vello 0.1 approaching fast it makes sense to get this done now.
This PR converts all file headers to this standard form, including the standard capitalization.
Additionally, three CPU shader files didn't specify Unlicense in the headers which seems like a mistake. I added the Unlicense identifier to match all the other shaders.

Yeap, the year marks the creation date.


Test-ProxyLogon.ps1 output verification

issue
Display output only shows:
ProxyLogon Status: Exchange Server EX01
Log age days: Oabgen 30,3 Ecp 29,8 Autod 30,0 Eas 30,0 EcpProxy 30,0 Ews 30,0 Mapi 21,5 Oab 30,0 Owa 30,0 OwaCal 30,0 Powershell 30,0 RpcHttp 30,0
Report exported to: \Test-ProxyLogonLogs\EX01-LogAgeDays.csv
Other suspicious files found: 198
Report exported to: \Test-ProxyLogonLogs\EX01-other.csv
shouldn't there be the output - suspicius activity found or nothing suspicious detected?

We manage 30+ Exchange servers, which mean we ran this tool 30+ times. If my understanding is correct, your results indicate that your server is NOT compromised. If it were, you'd see text written in red, somewhere along the lines of "Suspicious activity found for [CVE-2021-26855] - Action required". We saw this a lot, and we also saw your results a lot.
I'm 99% sure you are safe.

Ok, great, thanks for your answer.
Found a webshell on our Exchange and suspicious activitys back till 03.03.21 so i've restored both dc's and the exchange from the backup of 02.03.21
Just wanted to be sure we're fine now.

The script always outputs the log age. This is just to let you know how far back the script is able to see. If your logs are rolling every few days, then of course the script can't detect any activity that may have happened before that point.
Regarding the suspicious files, those are often expected, but it would be good to review the CSV and make sure. We flag any zip file in ProgramData, as outlined in the blog post. There are several products that have zip files there under normal conditions, such as the VMWare Tools. So it's worth reviewing the EX01-other.csv to ensure you only see zip files that you would expect to be there.

Also thanks for your answer.
So I guess to be safe I should restore older logs (february) to see if there are any suspicious activitys found.
I've already reviewed all files listed in the suspicies file csv - all of them are known programs of our infrastructure like (AV, Signature Manager and VMWareTools) and furthermore watched every created file on 03.03 untill fix and isolation on every single domain server with our network monitoring tool (Netwrix).


global pins are saved to manifest.json, not config file

What version?
0.21.0
Which command?
proto pin
What happened?
proto pin --global node saves its default to .proto/tools/node/manifest.json#default_version.
As a user-selected preference, this should probably be moved to one of the user config files, either at .proto/config.toml / .prototools.
proto alias is in the same boat.
Related to #261
Any logs?
No response
Operating system?
Windows
Architecture?
x64

Why does this need to be in a user config file?

Why does this need to be in a user config file?

Because it's user-level configuration that reflects the user's express preference. It's surprising that at the project level, default versions are in the same file, whereas at the user level, default versions are in the various tool folders.

I'd rather not add more file types for no reason.

Agreed. This does not deserve a new file type. But I do think this should be moved to .prototools/config.toml or whatever its successor looks like after the changes in 261.
Part of this was my misconceptions and misreading of https://moonrepo.dev/docs/proto/config
I had assumed that, since .prototools and .proto/config.toml are documented on the same page, that these had a common structure, and that .proto/config.toml could be overridden on a per-directory basis using .prototools.
Even if you want to not pollute config.toml's top-level namespace with tool names, it would make sense to have this be there either as:
[default-version]
node = "20.9.0"
npm = "10.2.1"

or as:
[plugins.node]
default-version = "20.9.0"

[plugins.npm]
default-version = "10.2.1"

The aliases and default version are currently in manifest.json as they are used as part of the version resolution/detection process, as does the other fields in the file. IMO it makes a bit more sense to colocate that information.

IMO it makes a bit more sense to colocate that information.

I’m sorry I don’t quite grok. The idea to me is that I’d have my proto config.toml in my dotfiles and could copy between machines to replicate my setup. On the other hand, the manifest.json files seem to be less user-editable in nature.

Started on this https://github.com/moonrepo/proto/pull/306

The more I work on that PR, the more I believe that we should remove ~/.proto/config.toml and merge it's functionality into .prototools. The "global" config would just be ~/.prototools.

That sounds good! Simple is better!
Not sure what should happen for external drives that don't live under the user's directory - I would think maybe it should pull in the user-level .prototools.

Done and landed in 0.24


Optimise font loading direct embed

Added the @font-face css calls directly in the page to avoid an extra round trip to google.
Currently limited to woff, woff2, truetype, and svg as eof only required in early IE which is not supported
Probably very limited international character support so may need to update the ReadMe to indicate that, but I haven't looked in to that side of it.
If available, uses session storage to completely eliminate FOUT on subsequent hits

Thanks for the font enhancements! Worked well for me so I merged it in.


Visual glitch/flash on refreshContentView() while cell is swiped open

When cell is swiped open such that the cell buttons are visible, updating the content view by calling refreshContentView() causes the cell to briefly show the full content in its un-swiped position.

Thanks for looking into this. I have tested it and LGTM!


update kArmor to use stable KubeArmor release instead of latest

@nyrahul would we want a --latest option or it's fine to manually do this with --image=kubearmor/kubearmor:latest


skilling boost reminder plugin update

Add:

More situation where boosting is useful. Commit
Added a setting for moving the notification arrow in X-Axis. Commit

Fix:

Notification arrow now disappers correctly. Commit
Added error checking

Chore:

Updated comments
Updated README

Rebased as requested in my last PR. Don't ask what happend to it.😅

FYI you never have to close a PR and reopen. Can just rebase and force push.


Initial commit of Shopping cart.

Code Provides for Shopping cart application

The application is aesthetic, it's not completely functional.

Register page

SignIn Page

Home page

Proucts Page

Node Server for Shopping cart.


Consolidating and cleaning up website images

This PR does a few things

Organizes all images (site and doc) into relevant directories under images/
It provides descriptive filenames for some images that had vague image names
Updates all image paths to point to the new path+filename

@carise any input on the folder structure for website images before I make changes to this PR?

lgtm, +1 to @Tabrarian 's comment though

Done. Merging.


useJsonForm hook is not working

Description
useJsonForm hook doesnt renders the form based on a local Json file.
Console displays error Unexpected end of JSON input.
Expected result
The form should be rendered and fields should be editable.
Actual result
Data is retrieved normally from the json file.
Sidebar displays 'Welcome to Tina!' message.
Console displays error:
FAILED SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at index.js:72
Environment
Node: 11.15.0 (Have also tried with 12.x and 10.x with no results)
npm: 6.5.0
OS: Windows 10
Dependencies on the project.
"dependencies": {
    "@kennethormandy/react-fittext": "^0.6.0",
    "firebase": "^6.4.2",
    "gatsby": "^2.13.67",
    "gatsby-image": "^2.2.8",
    "gatsby-plugin-manifest": "^2.2.5",
    "gatsby-plugin-offline": "^2.2.6",
    "gatsby-plugin-react-helmet": "^3.1.3",
    "gatsby-plugin-sass": "^2.1.12",
    "gatsby-plugin-sharp": "^2.2.12",
    "gatsby-plugin-tinacms": "^0.1.7",
    "gatsby-source-filesystem": "^2.1.33",
    "gatsby-source-firebase": "^1.0.0",
    "gatsby-source-firestore": "^1.0.3",
    "gatsby-tinacms-git": "^0.2.4",
    "gatsby-tinacms-json": "^0.4.0",
    "gatsby-transformer-json": "^2.2.15",
    "gatsby-transformer-sharp": "^2.2.6",
    "node-sass": "^4.12.0",
    "prop-types": "^15.7.2",
    "react": "^16.9.0",
    "react-dom": "^16.9.0",
    "react-helmet": "^5.2.1",
    "react-media": "^1.9.2",
    "react-responsive": "^7.0.0",
    "react-responsive-modal": "^4.0.1",
    "react-scrollspy": "^3.4.0",
    "react-textfit": "^1.1.0",
    "react-waypoint": "^9.0.2"
  },

Files info
gatsby-config plugins array:
plugins: [  `gatsby-transformer-sharp`,
    `gatsby-plugin-sharp`,
    `gatsby-plugin-sass`,
    `gatsby-tinacms-json`,
    {
      resolve: `gatsby-source-filesystem`,
      options: {
        path: `${__dirname}/src/data`,
        name: "data",
      },
    },
    "gatsby-transformer-json",
    {
      resolve: "gatsby-plugin-tinacms",
      options: {
        sidebar: {
          position: "float",
        },
        plugins: [
          "gatsby-tinacms-git", "gatsby-tinacms-json"
          // We'll add some Tinacms plugins in the next step.
        ],
      },
    },
]

React function component with the hook.
import React from "react"
import { useStaticQuery, graphql } from "gatsby"
import { useJsonForm } from "gatsby-tinacms-json"

const Home = () => {
  const homeJson = useStaticQuery(graphql`
    query MyQuery {
      dataJson {
        id
        textLeft
        textRight
        fileRelativePath
        rawJson
      }
    }
  `)

  console.log(homeJson.dataJson)
  const [homeData] = useJsonForm(homeJson.dataJson
    , {
    fields: [
      { component: "textarea", name: "rawJson.textLeft", label: "Home left text" },
      { component: "textarea", name: "rawJson.textRight", label: "Home right text" },
    ],
  }
  )

  // console.log(homeJson)
  return (
    <>

          A bigger

          Lorem

          We aim at a world
 where climate change

          Lorem

{homeData.textLeft}

{homeData.textRight}

    </>
  )
}

export default Home

Json local file
{
  "textLeft": "Text template",
  "textRight": "Text template 2"
}

Extra
This is the function where the FAILED SyntaxError: Unexpected end of JSON input is generated.
Its on the gatsby-tinacms-json package.
function useJsonForm(jsonNode, formOptions) {
    if (formOptions === void 0) { formOptions = {}; }
    if (!jsonNode || process.env.NODE_ENV === 'production') {
        return [{}, null];
    }
    validateJsonNode(jsonNode);
    var cms = react_tinacms_1.useCMS();
    var label = jsonNode.fileRelativePath;
    var id = jsonNode.fileRelativePath;
    /**
     * The state of the JsonForm, generated from the contents of the
     * Json file currently on disk. This state will contain any
     * un-committed changes in the Json file.
     */
    var valuesOnDisk = react_1.useMemo(function () { return ({
        jsonNode: jsonNode,
        rawJson: JSON.parse(jsonNode.rawJson),
    }); }, [jsonNode]);
    /**
     * The state of the JsonForm, generated from the contents of the
     * Json file at the HEAD of this git branch.
     */
    var _a = react_1.useState(), valuesInGit = _a[0], setValuesInGit = _a[1];
    react_1.useEffect(function () {
        cms.api.git
            .show(id) // Load the contents of this file at HEAD
            .then(function (git) {
            // Parse the JSON into a JsonForm data structure and store it in state.
            var rawJson = JSON.parse(git.content); //ERROR IS ORIGINATED HERE
            setValuesInGit({ jsonNode: jsonNode, rawJson: rawJson });
        })
            .catch(function (e) {
            console.log('FAILED', e);
        });
    }, [id]);
    var fields = formOptions.fields || generateFields(valuesOnDisk.rawJson);
    // TODO: This may not be necessary.
    fields.push({ name: 'jsonNode', component: null });
    var _b = react_tinacms_1.useCMSForm(__assign({ id: id,
        label: label, initialValues: valuesInGit, fields: fields,
        onSubmit: function (data) {
            return cms.api.git.onSubmit({
                files: [data.fileRelativePath],
                message: data.__commit_message || 'Tina commit',
                name: data.__commit_name,
                email: data.__commit_email,
            });
        },
        reset: function () {
            return cms.api.git.reset({ files: [id] });
        } }, formOptions),
    // The Form will be updated if these values change.
    { values: valuesOnDisk, label: label, fields: fields }), values = _b[0], form = _b[1];
    var writeToDisk = react_1.useCallback(function (formState) {
        var _a = formState.values.rawJson, fileRelativePath = _a.fileRelativePath, rawJson = _a.rawJson, data = __rest(_a, ["fileRelativePath", "rawJson"]);
        cms.api.git.onChange({
            fileRelativePath: formState.values.jsonNode.fileRelativePath,
            content: JSON.stringify(data, null, 2),
        });
    }, []);
    react_tinacms_1.useWatchFormValues(form, writeToDisk);
    return [jsonNode, form];
}

var rawJson = JSON.parse(git.content); is the line of code of that function that throws the error.

Thanks for the report @SamuelVera. Is the repo where this is happening publicly available?

The repo isnt publicly available. I'll update the packages later and see if the problem gets fixed.
Thanks for you response!!

Just updated the packages. The problem is still there.

Is the site in a subdirectory? If yes take a look at how to configure your site for that.
If not, could you add me to the repo, or create an anonymized public fork? That would be super helpful.

I'll check those docs. Also just sent you an invitation to a private repo with the project

I'll check those docs. Also just sent you an invitation to a private repo with the project. @ncphillips

I implemented the config for the git backend but just realized that the fileRelativePath field of the .json file that's queried by graphql is returning "C:/Users/samue/Desktop/Aether/Nexwell/NexwellFront/src/data/Home.json" an Absolute path, that isnt supposed to be like that, right?

Hey @SamuelVera has there been any update on this issue?
I still have not heard of this happening at other times.

I'm going to close this issue for now as I have not heard any other reports, and cannot reproduce the problem

Hey,
I know this issue is closed, but I've been dealing with the same problem. I've got the same setup, and the form is not showing up. The content is displaying as expected, but I get the error as mentioned above.
Is there an update to this?

No updates. I haven't been able to reproduce this issue. If could link to a public repository where this is happening or provide steps to reproduce I can take another look @jarodpeachey
One thing to note is that useJsonForm no longer registers the form with the CMS. You should be using useLocalJsonForm.

Closing as this is stale, feel free to reopen if the issue persists!


Shebang assumes bash to be in /bin which will never be true for *BSD

Shebang says #!/bin/bash. It will never work on *BSD because it is installed from ports to /usr/local/bin/bash. Frontpage claims FreeBSD compat.
Change shebang to #!/usr/bin/env bash which is the common standard these days and a portable approach.

Sounds sensible. Of course PRs are always welcome :-)


Python packaging

Moved all the files in a proper directory structure for python packaging.
Prepared config for sphinx docs

Merging this PR to work on the autodeploy of the docs


Windows default terminal profile selection misbehaves

Issue Type: Bug
The dropdown in the settings UI to select a default terminal profile on windows is broken. Every time I select a different profile a new empty item on the top of the list appears. The description of the items do not move however. Furthermore, the corresponding value in the settings.json will always be "PowerShell", no matter which item I select.

VS Code version: Code - Insiders 1.59.0-insider (50b3811fdc5b5c80ca516a2edfffedcbd464b033, 2021-07-15T05:13:58.348Z)
OS version: Windows_NT x64 10.0.19041
Restricted Mode: No

System Info

Item
Value

CPUs
AMD Ryzen 5 1600 Six-Core Processor             (12 x 3194)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.93GB (7.48GB free)

Screen Reader
no

VM
0%

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30291487
pythontb:30258533
vspre833:30321513
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscus158:30321503
pythonvsuse255:30319630
vscod805:30301674
pythonvspyt200:30323110
vscextlang:30310088
vsccppwtct:30312693
bridge0708:30335490

This is odd.. the Linux and macOS ones have a drop down but the Windows one doesn't?

@TylerLeonhardt I notice the settings have enum values of the following form:
enum: detectedProfiles?.os === OperatingSystem.Linux ? profileEnum?.values : undefined
Therefore, you can validate the issue by making sure the Osx dropdown works. Definitely seems like a polish issue, though.

In that case, yes the macOS drop down did work.

@TylerLeonhardt that's by design. we don't show the windows/linux profiles enum /dropdowns when you're on an osx platform.

There is still an entry in the dropdown labeled "Standard" that is otherwise empty but other than that, the issue seems to be resolved.


DL LM notebook and location of data

01* currently says
if not (
    Path("..")
    / ".."
    / "data"
    / "PET"
    / "mMR"
    / "NEMA_IQ"
    / "20170809_NEMA_60min_UCL.l.hdr"
).exists():
    retval = subprocess.call("../../scripts/download_PET_data.sh", shell=True)

Best to use download_data.sh -p, and use the examples_dir function as below. Note that re-executing that download should be fairly painless, so not sure if you need the if, @gschramm

was fixed


[BUG]: Leak after AttributeError in class with shared_ptr member

Problem description
I have a class Parent with a shared_ptr to an instance of class Member. If I have an AttributeError from accessing attributes of the Parent object (i.e. typo on interactive interpreter), Python reports a leak of its member on exit. I expect no memory leak.
I observe this behavior on Python 3.11 and 3.12 with nanobind 1.8.0.
Minimal example is below:
Reproducible example code
// module.cpp
#include <nanobind/nanobind.h>
#include <nanobind/stl/shared_ptr.h>
#include <memory>

struct A {};
struct B {
  const std::shared_ptr<A> a_;
  B(std::shared_ptr<A> a) : a_{a} {}
};

namespace nanobind = nb;

NB_MODULE(nanobind_example, m) {
  nb::class_<A>(m, "A").def(nb::init<>());
  nb::class_<B>(m, "B").def(nb::init<std::shared_ptr<A>>());
}

// end module.cpp

# Python REPL

>>> from nanobind_example import A, B
>>> B(A()).foo

AttributeError: 'B' object has no attribute 'foo'

>>> exit()

nanobind: leaked 1 instances!
nanobind: leaked 1 types!
 - leaked type "nanobind_example.A"
nanobind: leaked 1 functions!
 - leaked function "__init__"
nanobind: this is likely caused by a reference counting issue in the binding code.

Please see https://nanobind.readthedocs.io/en/latest/faq.html#why-am-i-getting-errors-about-leaked-functions-and-types. To further classify this issue, could you try the following:

Does he leak still occur when you move your code from the global level into a function that you call from the global level?
If it still occurs, also do a import gc; gc.collect() after the function returns.

Does the leak still occur when you move your code from the global level into a function that you call from the global level?

The leak still occurs.

If it still occurs, also do a import gc; gc.collect() after the function returns.

The leak still occurs when running gc.collect() after the function returns.
If it helps to classify the issue, I made the following additional observations:

if I handle the exception --> no more leak message
if I catch the exception but then raise any other exception --> still get leak message

try:
    B(A()).foo
except Exception:
    # raise  # (leak message)
    # raise ValueError("unrelated error")  # (leak message)
    pass # no leak message

(not sure how relevant sys.getrefcount() is, but I observed that if I store the values (a = A(); b = B(b)), each time that an AttributeError is raised and unhandled on b.foo, b's refcount is incremented by 1 (if handled, there is no change). This appears to be true for other Python objects as well, though (list, tuple, arbitrary Python class, etc.).)

If I run gc.collect() after a second, unrelated exception is raised, A and B's destructors are run at that time.
I think the reason it needs a second, unrelated exception to be raised is because Python keeps the last raised exception in memory for post-mortem debugging for interactive sessions. And, to enable this debugging, Python also keeps the object in question in memory.
Not really sure why B's destructor is called but not A's in this case.  However, if we emulate A and B in Python, neither destructor is called:
class A(object):
    def __del__(self): print("~A")
class B(object):
    def __init__(self, a): self.a = a
    def __del__(self): print("~B")

>>> B(A()).foo
AttributeError {...}
>>> exit()
# never get message from destructors

Since the garbage collector can clean it up after the second exception, and there are reasons we would want to keep the objects in memory in the context of the first exception, I am no longer worried about this behavior and think it is probably benign.

What Python version are you on? I think a few rare GC-related leaks at shutdown time like the one you are describing were fixed in 3.12. I'd be curious to hear if that fixes it.

The problem persists in Python 3.12: if an AttributeError on B is the last unhandled exception, the destructor of its member a_ is never run.
The garbage collector appears more eager, though. The destructors for B and A are run immediately after a second exception is raised (vs running on exit or manually running gc.collect())


Update Configuration.md

Hey, I thought I'd add this. Not the most useful, but it may be clear to some people.
I really know nothing about git. So don't be too harsh if I've ruined something

We should probably list airplane.yml as well, but leave a note in place of a link that airplane does not have documentation yet

Maybe something like this?


docker shared folder

not sure if this is the right place.
i have read multiple articles , and even here on a close issue https://github.com/docker/docker.github.io/issues/2979
i am trying to share a container folder with the host and no the way around.
i want to share the (container) apache log directory with the host and the www folder.
to share a folder from the host to the container that would be simple as
sudo docker build -t myimage. &&  docker run  -d --name wordpress -p 80:80 -v /host/folder/:/container/folder/  myimage

problem occurs when u want to share the container folder WITH the host, basically what happen is when running /srv/log/:/var/log/apache2/ instead of sharing "var/log/apache2" with the host,  it shares "srv/log" to var/log/apache2 which make apache crash .
same if i want the share the www folder from the docker to the host.
instead of sharing the www folder with the host, it shares the host folder and exposed it on port 80 :s
i have yet found a solution about it.
i dont wish to hold the files on the host.
is there a way to share a docker folder WITH the host (and not host:container) ?
thanks

up :o

no one as answer for that ?

Thank you for your feedback. However, it looks like your issue is not about Docker documentation, but that you may be having trouble with Docker itself. Please file a Docker support ticket or check out
https://forums.docker.com/  to see if you can find a solution.
If this really is a documentation issue and I have misunderstood, please reopen it with more information.


version 8.0.3, the DismisAsync() not working

private MySheet sheet;
ctor(){
sheet = new MySheet();
}
[RelayCommand]
private async Task OpenBottomAsync(){
sheet.ShowAsync(); //
}
[RelayCommand]
private async Task CloseBottomAsync(){
sheet.DismissAsync(); // errors because   sheet is null
}

I found this is the case for the problem of constructor overriding ..if the the constructor of MySheet class is not the default contructor, instantiate it with that constructor..because of the BottomSheet can't be injected int the IoC  Container Services

closed


reverted santise

Description

A clear and concise summary of the change and which issue (if any) it fixes. Should also include relevant motivation and context.
Resolved or fixed issue:
Affirmation

[ ] My code follows the CONTRIBUTING.md guidelines

asdasd


Update skeletons to match recent config option change

evolutions was renamed to evolutionplugin in a recent change:
https://github.com/playframework/Play20/commit/0d1d91ffa7ff92d3f7bc688217972bd075f1a2ba
This updates the skeletons to match

good catch - thanks Ben!


update gcd implementation to Swift 4 with Xcode 9b4

Checklist

[x] I've looked at the contribution guidelines.
[x] This pull request is complete and ready for review.

Description
GCD implementation has been tested on Xcode 9 b4 and works as expected and the unit tests pass as well.

:+1:


feat(guild): add bulk_ban function

Summary
Implements discord/discord-api-docs#6720 by adding a bulk_ban function to Guild
This is a Code Change

[ ] I have tested my changes.
[x] I have updated the documentation to reflect the changes.
[x] I have run task pyright and fixed the relevant issues.

Related Discord Docs PR was merged.

@ooliver1 @teaishealthy this pr up to y'all


[Web Connector] Ability to open a popup through URL buttons

The web connector offers the ability to send a link to an arbitrary URL through an UrlButton:
https://github.com/theopenconversationkit/tock/blob/903e3c242dd1e43d46ae0499733e6818a2958ffc/bot/connector-web-model/src/main/kotlin/ai/tock/bot/connector/web/send/UrlButton.kt#L22-L29
The existing target attribute can be used to make the button either open the link in a new tab (the default), or open in the current tab (specifically, it reflects the target attribute of the HTML anchor).
For some use cases, notably authentication flows, it can be helpful to instead open a popup window that will then close automatically. Currently, such a popup-opening button has to be implemented through a widget, but this requires copying existing behaviour from various frontend components.
Proposed solution
We could add a parameter to UrlButton which would enable the popup behaviour. In line with the existing target parameter, this new parameter could be a simple string matching the spec of windowFeatures. When this windowFeatures parameter gets specified, the tock-vue-kit and tock-react-kit would add a JS handler that cancels the default browser behaviour and opens the link in a new window. The implementation of this handler could be as simple as calling window.open(button.url, button.target, button.windowFeatures).
Thoughts @rkuffer @Benvii @assouktim?

Sounds good to me


Update civic.json file to new specification

Hi, there! Code for DC is moving to an updated civic.json
specification. This pull request formats your existing
civic.json to the new standard.
Feel free to look it over and make any updates.
========================
There are a few errors remaining in the civic.json,
which will need a correction:
Error in contact: '' is too short
========================
The new civic.json spec keeps the required fields from the older
one, but has a number of benefits. It:

removes fields that are hard to maintain and get out of date quickly
combines partner fields to be more broadly applicable
is usable by civic tech projects outside of government, as well as inside

You'll see that DC Government is using this standard in its own repos:
https://github.com/dcgov
You can learn more about the specification requirements here:
http://open.dc.gov/civic.json

Looks good to me.

Only change to the PR needed is a name value (ideally a person's name) for the contact attribute. Then it will validate correctly.

Can we just put in "ANC FInder" as the name?

Sure


Install Moodle Plugin - Collapsed Topics

Install to dev, then test for review by Shannon & Greg.
https://moodle.org/plugins/format_topcoll

Changes are in dev for review. Once confirmed, this can be migrated to test.

Closing as this is successfully in production now. Note: Moodle 4 makes this plugin moot as it's now supported in courses by default.


Add a helper trait for simplifying behavior when processing an unexpected packet

Why is this a trait if there's only ever going to be one implementer?

As a way of extending UdpSocket to have this as a method so that it has a more "builtin" feel.


Added some hover effects to top scroll button

Related Issue
Closes #748

Description

Screenshots

Checklist

[x] My code adheres to the established style guidelines of the project.
[x] I have included comments in areas that may be difficult to understand.
[x] My changes have not introduced any new warnings.
[x] I have conducted a self-review of my code.

I have added some hover effects in the top scroll button to make it more illustrative just like other buttons.....
https://github.com/rohansx/informatician/assets/121575277/ff8ea62f-a56d-4c94-96a5-5d2958c8a845

@rohansx please review this pR .......Thanks


Can't create a new plugin using the same OAD

What are you generating using Kiota, clients or plugins?
Kiota plugin
In what context or format are you using Kiota?
Source Build
Client library/SDK language
None
Describe the bug
Kiota blocks me from creating a second plugin using the same OAD.

Expected behavior
I should be able to create multiple plugins using the same OAD
How to reproduce

Create a DC + Pugin using repair service
After scaffolding, create a new plugin using the same OAD

Open API description file
No response
Kiota Version
v1.18.100000001
Latest Kiota version known to work for scenario above?(Not required)
No response
Known Workarounds
No response
Configuration
No response
Debug output
Click to expand log
```

</details>

### Other information

_No response_

Thanks for raising this @MuyangAmigo
I believe the error you are seeing is that you are trying to generate the plugin with the same name in the same workspace.
Any chance you can

open the workspace file to use the regenerate option to validate the RepairService plugin already exists
Use a different name if you intend to generate a second plugin in the workspace.

This is by design. Challenge is in trying to generate by adding a new plugin with the same name as an already existing plugin in the workspace. In ttk integration, a name parameter is not passed. This results to Kiota defaulting to the OAD title(which needs to be a human friendly name) as the pluginName. When second generation of a plugin is triggered from Kiota with same OAD, the pluginName passed to kiota would be similar to another already existing in the workspace.json hence throwing the error.

The user could choose to regenerate the already existing plugin from the workspace.json file but given this is not transparent to the user from the ttk extension display, this may not be a solution. Also this would mean if user was to create a different plugin with different endpoints for different declarative copilot teamapps, then it wouldn't be correct to edit the first plugin.
The ttk team is currently not making use of a workspace hence the /.kiota folder. Suggestion is to avoid generating the .kiota folder in the user's current workspace/folder and instead work without workspaces in the ttk integration. This would mean, generating the .kiota folder in the temporary folder instead of the current open workspace. However, if kiota still references the workspace.json file before creating a plugin, this would still fail even if the .kiota folder is not in sight for the user.
Option 3 would be to find another way to default to, as pluginName if the name is not provided in a deeplinking scenario. Maybe adding suffixes to the OAD.title when resulting pluginName is found to exist in the workspace.

My intension is to create an entirely different solution with the same OAD, only difference is that I have a workspace open, but my new solution is expected to be generated in a new folder by TTK.
We can't always expect developers to start without any workspace open correct? I can work on my existing solution while trying to create a new one, I think it's a valid scenario.

+1 to @MuyangAmigo comment:

We can't always expect developers to start without any workspace open correct? I can work on my existing solution while trying to create a new one, I think it's a valid scenario.

I don't know why we create a .kiota folder in a workspace we are not building for (when using Kiota to generate a new project from TTK).

@thewahome, @fey101 This looks like a missing piece of the temp folder support for the TTK integration, as a follow-up of #5298. Please check it out and we discuss later today ok.

Ok, so found (and confirmed with Andrew) that Kiota extension is the one deciding on 'cwd' as in https://github.com/microsoft/kiota/blob/03607d58de6ae15b8a9e2e43fa3cff5a98b80b12/vscode/microsoft-kiota/src/util.ts#L32
We need to change the strategy to ignore any open user's workspace in the TTK integration scenario, as it is both confusing and leading to this type of naming conflicts when generating plugins for the same OpenAPI document.


quick fix for pip 10 and python 2

fix #6

Hey @leon0707, thanks for the PR!
Just looked at the output from travis and found this error:
...
../../../virtualenv/python3.6.3/lib/python3.6/site-packages/twisted/internet/address.py:111: in UNIXAddress
    name = attr.ib(converter=attr.converters.optional(_asFilesystemBytes))
E   TypeError: attrib() got an unexpected keyword argument 'converter'

Looks somewhat similar to https://github.com/mozilla/coverage-crawler/issues/140
Concerning the content of the PR, thanks a lot for the fix concerning pip 10 👍
As for the support of Python 2.*, it may need a lot of changes, since I used the "f" string interpolation, so the package is not currently compatible at all with Python 2 (here and in other places)

@leon0707 I fixed the tests in #8 , please rebase your PR :)


Double / Float columns not generated via Migrations (PostgreSQL)

For the following code and both properties, only integer columns are created via migrations for Postgres.
@Field is a Apollo Graphql Annotation that does not interfere usually.
`
@Property({ type: Number, nullable: false })
@Field((_type) => Number)
latitude: number;
@Property({ nullable: false })
@Field((_type) => Number)
longitude: number;
`
How can I force them to be Double / Float values. number in Typescript is a float value but can mean both integer and double. How is Mikro ORM understanding the exact type without having me specify a custom type.
I am only seeing this now and it's a big problem that needs to be solved quickly.
After extensive googeling the only solution I could find was custom types.
Thank you very much.

Default for number type is to map to integer, you can specify either type or columnType, the difference being that the columnType is always used as is, but the type is mapped (checked for known type names and converted).
// with columnType we need to use the final type name
@Property({ columnType: 'double precision' )
prop1: number;

// with type we can also use known mapped types
@Property({ type: 'double' )
prop2: number;

The difference here might not be that visible, so better example to show it is with JSON properties:
@Property({ columnType: 'jsonb' )
prop1: any;

@Property({ type: 'object' )
prop2: any;

Both props will have jsonb column type in postgres.

❤  thanks for the quick reply, works like charm. Would be cool to find it in the documentation for other people to find it.